
Booktrope provides a software platform that makes it easy for…
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Booktrope (W15).
Booktrope tried to industrialize a middle path between self-publishing and traditional publishing, and discovered that publishing's brutal power law leaves no room in the middle. Founded in 2011 in Seattle and later a Y Combinator company, Booktrope offered "team publishing": a platform that matched authors with editors, designers, and marketers who worked on a revenue-share basis, with Booktrope keeping 30% and the creative team splitting the other 70%.[1] It raised more than $1 million and its teams produced nearly 1,000 books.[5]
In April 2016, Booktrope abruptly announced it would shut down by the end of May, its cofounders admitting that despite excellent books and strong creative teams, "Booktrope books have not generated sufficient revenues to make the business viable."[2] The shutdown was messy, leaving authors saddled with obligations to the professionals who had worked on their books.[3] The core failure was arithmetic: most books earn almost nothing, and splitting a tiny median pie among an author, an editor, a designer, a marketer, and a 30% platform cut leaves everyone underpaid.
Booktrope launched in 2011 in Seattle with a genuinely appealing idea for the self-publishing age.[5] Self-publishing on Amazon had exploded, but most indie authors couldn't produce professional-quality books — they lacked editors, cover designers, and marketers, and couldn't afford to pay them upfront. Traditional publishing offered those professionals but rejected the vast majority of writers and took most of the economics. Booktrope's "team publishing" split the difference: authors would get a team of professionals who worked for a share of the book's future revenue rather than upfront fees, aligning everyone's incentives around the book's success.
The model attracted authors and creative professionals, and Booktrope raised over $1 million, went through Y Combinator, and produced close to a thousand books.[1] The revenue split — 30% to Booktrope, 70% to the creative team — sounded reasonable in the abstract. But it embedded a fatal assumption: that the average book would generate enough revenue to meaningfully reward an author, an editor, a designer, a marketer, and the platform. In a market where the median self-published book earns very little, that assumption was false, and the model was structurally underwater from the start.
Booktrope was a platform and a hybrid publisher. An author submitted a manuscript, and Booktrope assembled a team — editor, cover designer, marketer, sometimes a proofreader — who worked on the book in exchange for a slice of its future royalties rather than upfront payment.[6] The software coordinated the team, tracked contributions, and handled the revenue splits, and Booktrope published the finished books through the usual retail channels.
The value proposition was real for authors: professional production without upfront cost. But the model layered several stakeholders onto each book's economics, and the total value being divided was, for most books, tiny. Compounding this, critics noted that Booktrope's leadership had little publishing or editorial background yet controlled acquisitions, so the platform lacked the curation that traditional publishers use to concentrate resources on likely hits.[7] Without curation, Booktrope spread creative-team effort and its own attention across a thousand books, most of which would never sell enough to reward anyone.
Booktrope served indie authors who wanted professional book production without paying upfront, plus the editors, designers, and marketers willing to work for a revenue share.
Read the complete post-mortem, the rebuild playbook, and the exact reasons Booktrope is still worth studying now.