Skiff: a Notion acquisition still meant a product shutdown
Skiff’s encrypted workspace joined Notion, but its mail and collaboration services closed. Acquisition and customer continuity are different outcomes.
- Product
- Skiff
- Founder
- Andrew Milich and Jason Ginsberg
- Launched
- n/a
- Model
- Former encrypted productivity suite
Published · 1 min read · 2 sources
Key takeaways
- Skiff’s founders dated its start to April 2020 in Notion’s acquisition interview.
- Notion announced Skiff joining on 9 February 2024; Skiff says its services sunset on 9 August 2024.
- Accounts did not become Notion accounts; optional email forwarding ended in February 2025.
What it is
Skiff offered encrypted Mail, Pages, Calendar and Drive. Its own migration notice now records the end of those services, making this a product-continuity case rather than a current product recommendation (Migration notice).
Timeline
- April 2020: Andrew Milich said Skiff became official on April Fool’s Day, alongside co-founder Jason Ginsberg (Notion interview).
- 9 February 2024: Notion announced Skiff was joining, emphasizing shared product vision and attention to detail (Notion announcement).
- 9 August 2024: Skiff says all its services were sunset. Accounts and data were not converted into Notion accounts (Migration notice).
- 9 February 2025: the stated end date for automatic email forwarding, which had to be activated before the service sunset (Migration notice).
Why it worked
Here “worked” refers to attracting an acquirer, not preserving the standalone service. Notion’s co-founder praised the products’ detail and described following Skiff since its early Docs work. That is the buyer’s account, not proof of sustainable standalone revenue (Notion interview).
The founders described a clear mission around control, communication and privacy. The acquisition story shows strategic alignment; it does not provide acquisition price, profit or customer-retention evidence (Notion interview).
What to learn
- Ask what survives an acquisition: the team, the code, the accounts or the whole service.
- Build export and migration paths before users need them under deadline pressure.
- Evaluate continuity promises separately from privacy promises. Compare Ghost’s nonprofit model and Airplane’s shutdown.
Risks and what didn't work
- The core service ended despite the positive acquisition announcement. Email forwarding was limited and did not mean the workspace remained available (Migration notice).
- The migration notice said accounts would not convert to Notion. Buyers could not assume the acquirer provided a seamless replacement (Migration notice).
- These sources do not establish why the standalone business could not or would not continue. We do not invent a cash-burn or product-market-fit explanation.
FAQ
Short answers drawn from the sections above.
What is Skiff?
Skiff offered encrypted Mail, Pages, Calendar and Drive. Its own migration notice now records the end of those services, making this a product-continuity case rather than a current product recommendation (Migration notice).
Why did Skiff work?
Here “worked” refers to attracting an acquirer, not preserving the standalone service. Notion’s co-founder praised the products’ detail and described following Skiff since its early Docs work. That is the buyer’s account, not proof of sustainable standalone revenue (Notion interview).
The founders described a clear mission around control, communication and privacy. The acquisition story shows strategic alignment; it does not provide acquisition price, profit or customer-retention evidence (Notion interview).
What can indie builders learn from Skiff?
- Ask what survives an acquisition: the team, the code, the accounts or the whole service.
- Build export and migration paths before users need them under deadline pressure.
- Evaluate continuity promises separately from privacy promises. Compare Ghost’s nonprofit model and Airplane’s shutdown.
What didn't work for Skiff, and what are the risks?
- The core service ended despite the positive acquisition announcement. Email forwarding was limited and did not mean the workspace remained available (Migration notice).
- The migration notice said accounts would not convert to Notion. Buyers could not assume the acquirer provided a seamless replacement (Migration notice).
- These sources do not establish why the standalone business could not or would not continue. We do not invent a cash-burn or product-market-fit explanation.
Sources
Every link cited above, in order of first use.
- 1.Migration notice (skiff.com)
- 2.Notion interview (notion.com)
Related case studies
More in SaaS →Rewind and Limitless: an AI memory app and pendant that ended in a Meta acquisition
Rewind recorded everything on your Mac so you could search it with AI. Its maker renamed itself Limitless, built a recording pendant, and was bought by Meta in December 2025. Rewind was shut down two weeks later.
Simple Analytics: a privacy constraint became the product
An Amsterdam analytics business reached a founder-reported $100k ARR milestone without personal tracking. The lesson is a clear constraint, not a generic dashboard.
Buttondown: customer funding, deliberately limited free growth
Justin Duke’s newsletter tool reached paying customers soon after launch. Its stated model prioritizes sustainable pricing and support over maximum free adoption.