Built&Written

My partner (CEO) and I (CTO) launched builtwritten.com about a month ago. I handle all the technical work. Stack: Next.js, TypeScript, Supabase.

We kept seeing the same pattern: entrepreneurs and coaches want to write a book to build authority, but the production process kills them. Draft in ChatGPT, paste into Google Docs, format in Atticus, design a cover in Canva, fight with Kindle Create, upload to KDP, get rejected for cover dimensions. Five tools. Weeks of context-switching. Most quit before they publish.

So we built one editor that handles the full pipeline — AI co-writing with Voice DNA (learns your tone from writing samples), professional formatting, cover design to KDP specs, and one-click PDF/EPUB export.

Here's what we did for growth in month one:

- Published 58 blog posts, each 3000–5000 words, targeting long-tail keywords like "how to write a book when you have no time" and "scared to write a book"

- Created named frameworks in each post (R.A.I.L., Talk-Shape-Polish, KDP-Ready Stack) instead of generic "5 tips" content

- Built comparison pages (vs Atticus, vs Vellum, vs Ghostwriting, vs SidekickWriter)

- Result: ~200 daily impressions in Google Search Console, up to 6 organic clicks per day, and ChatGPT already recommends us as a top KDP AI tool

What hasn't worked yet:

- Almost zero external backlinks so far (working on it now)

- Conversion from blog readers to signups is low — most traffic is informational

- No Product Hunt launch yet (planning for later this month)

Revenue: $0. Pre-revenue, focused on product and content.

Two questions for the IH community: For those who've thought about writing a book — what actually stopped you? The writing itself, or everything that comes after the draft? And any tips on converting informational blog traffic into SaaS signups?

Happy to share details about the content strategy, SEO approach, or tech stack.