Loading page…
A custom website builder on top of Notion that found 75+ early customers through build-in-public posts and later sold for about $300,000.
75+ first customers from Twitter · 6% monthly growth after turnaround
Find a manual workaround that already has users, make it easy enough for nontechnical customers, and share the build where those customers already follow founders.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Noah Bragg built Potion after noticing that people were manually turning public Notion pages into websites. A workaround called Fruition let users point a custom domain at a Notion page through Cloudflare, and he saw hundreds of people attempting the process even though it required awkward code. Potion made the workflow easier: users kept their content in Notion, while Potion pulled the pages, generated a hosted website, and improved the presentation for SEO. The target audience was creators, entrepreneurs, portfolio owners, bloggers, and wiki builders. Noah announced that he would build a SaaS in public, gained about 1,000 followers from the first semi-viral tweet, and said his first 75-plus customers came from Twitter. After a six-month plateau caused partly by churn, he spent about two months pushing a version two, added affiliates, and returned to about 6% monthly growth. He eventually listed Potion on Acquire, lowered the asking price from $400,000 to $350,000, received three offers, and closed the sale for about $300,000 within roughly two months.
Potion got its first 75-plus customers from Twitter because the product and the channel matched. The audience was made up of creators and entrepreneurs, exactly the people who enjoy following a founder build a tool for their own workflow.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Founder Noah Bragg described Potion in an interview and reported about a $300,000 acquisition, 75-plus first customers from Twitter, a six-month plateau, a two-month recovery push, and roughly 6% monthly growth afterward. The sale and traction figures are founder-reported and unaudited; the interview does not provide MRR, profit, churn, or customer-count verification.
For Potion, the first dollar should come from charging for the convenience that the free workaround cannot provide. The underlying demand already existed: people were willing to route Notion pages through Cloudflare and custom code to get a website.
Potion's flywheel had three parts: public building, product feedback, and distribution through adjacent creators. Sharing the build on Twitter brought the first 75-plus customers and gave Noah a stream of reactions while he was still shaping the product.
Potion spent about six months in a period where growth was flat, partly because of churn, and Noah was unsure which changes would help. The useful response was a bounded recovery sprint rather than endless tinkering.
Potion is a presentation and hosting layer for Notion content. Customers write pages, blog posts, portfolio material, or wiki content in Notion, then Potion pulls that data and turns it into a hosted website with a custom domain and better SEO-oriented presentation. The product is valuable because it preserves the editing workflow users already know while removing the need to build a separate CMS, frontend, and publishing pipeline. The core experience should feel immediate: connect Notion, choose a site identity, preview the pages, publish, and keep editing in Notion. Useful product depth comes from templates, navigation, metadata controls, redirects, analytics, forms, custom code where appropriate, and reliable synchronization. The product should also make the boundary with Notion clear. If Notion changes its API, page model, or public-sharing rules, the publisher needs a safe way to detect failures and explain them. A good Potion-like product is therefore not merely a proxy. It is a dependable publishing system that turns an existing workspace into a public web presence.
Potion monetizes the gap between a free Notion page and a professional public site. The customer pays for convenience, custom-domain publishing, presentation quality, hosting, and features that make a Notion-backed website credible to visitors. A clean pricing ladder can separate a personal site from a creator or business plan, with limits based on sites, pages, collaborators, traffic, or premium templates. Keep the basic promise consistent across plans: content remains editable in Notion and the public site stays online without custom code. Add-ons such as custom CSS, forms, analytics, team roles, or migration support can increase account value, but they should not make the core publishing path confusing. The acquisition outcome of about $300,000 gives the business a concrete exit reference, yet the interview does not provide MRR, margin, or customer lifetime value. Track those operating numbers from the start. In a platform-dependent product, low support burden and predictable renewals are especially important because a buyer is purchasing dependable cash flow as well as code.
Potion's architecture naturally centers on the Notion API, a rendering layer, hosting, custom-domain management, caching, and a billing system. A lean implementation can use server-rendered pages for SEO, a queue for synchronization, object storage for assets, and edge caching for public traffic. The cost drivers are API calls, hosting and bandwidth, domain or certificate operations, support, and engineering time spent handling upstream changes. Keep tenant data isolated and make the sync process observable: last successful fetch, page count, error reason, retry state, and publish version should all be visible to support. The founder's ability to reduce the business to about two hours of weekly work helped make it transferable, so automate onboarding, billing, support triage, and routine health checks early. Do not confuse low founder hours with zero operating cost. Measure infrastructure cost per active site, support tickets per account, sync failure rate, and the engineering time required for a Notion API change. A buyer values a small, documented operating surface because it lowers key-person risk during an acquisition.
Copy Potion's opportunity discovery method: look for a free workaround that hundreds of people already use, then remove the awkward steps without forcing them to abandon their source platform. Copy the distribution fit too. Build in public where creators and entrepreneurs already exchange workflows, and use affiliates whose own sites prove the result. Change the dependency strategy. A new product should have a clear export path, cache important content, and monitor platform changes instead of assuming the upstream API will remain stable. Narrow the first use case to one type of site, such as creator portfolios, documentation hubs, or small business blogs, then expand only after activation is reliable. Make the before-and-after value visual and measurable: setup time, page speed, search indexing, and publishing frequency. If the product becomes a thin feature that Notion can add itself, the brand and workflow must still earn loyalty. The strongest version owns the publishing experience, customer relationship, and operational reliability while using Notion as an efficient input layer.
Potion's largest risk is platform dependency. Notion can change its API, public-page behavior, rate limits, pricing, or product direction, and a publisher built on top of it must absorb the consequences. The second risk is commoditization: other tools can wrap the same API, while Notion itself could add better website publishing. The third is retention. A customer may launch a site once, then cancel if the content workflow is not part of a regular business habit. Protect the model with fast rendering, dependable sync, exportable data, clear migration guidance, and features that improve the customer's public site rather than merely restyle a page. Churn should be monitored by site type and activation behavior, not hidden inside a blended average. The reported $300,000 acquisition and 6% monthly growth after the turnaround show that a small platform plugin can become a saleable asset, but they do not remove the need for a durable moat. Build around publishing reliability, templates, integrations, and an audience that trusts the workflow.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,435 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click