Editorial
What we dropped, and why
The three features we won’t ship, the trade-offs behind each, and what we built instead.
Building OutcomeStory meant saying no to a lot of features our competitors treat as table stakes. Every one of those decisions was deliberate: we held the line because each dropped feature would have diluted the thing our customers actually pay us for — turning a single client win into a publishable case study they can send to a prospect the same afternoon.
This post walks through the three features we won't ship, and what we ship instead. If you're scoping an agency tools product and feel pressure to add features your competitors have, we'd like this to be useful.
No public testimonial walls
Most "case study" tools start life as a public wall of quotes — a Testimonial.to style schema where dozens of snippets get laid out in a grid and visitors filter by tag. We considered it, sketched a few designs, and dropped it.
A wall of quotes answers the wrong question. Buyers don't ask "what do twenty random people think about you in general?" — they ask "what's it actually like to work with you on a project shaped like mine?" A quote pulled out of context has no challenge, no metric, no scope; it weighs exactly the same whether it came from a six-week brand sprint or a half-million-dollar transformation engagement. Walls flatten the proof into mush.
What we ship instead is the per-story proof page at /p/[slug]: a single client win, with the closed-won value front and centre, the challenge / what we did / the outcome stacked in editorial order, and a ranked set of that client's own quotes underneath. One page, one outcome, one truth. It's harder to write, and customers tell us that's exactly why they trust it.
No in-app video recording
The other thing our competitors keep adding is in-app video recording: the prospect or client opens a tab, clicks "record", and answers the questions out loud. The output goes onto a wall or onto a proof page alongside text. It's a beautiful demo for product screenshots. We dropped it.
Two reasons. First, the friction is enormous for the person on the other side — the founder needs to remember to record, pick a quiet room, find headphones, hit "allow microphone", retake three times, then wait while it uploads. The win rate on "client recorded a video testimonial" is below the win rate on "client wrote two sentences in a text box", because text takes thirty seconds and video takes twenty minutes. Second, video drifts away from the outcome fast — the words still need to be transcribed, the claims still need to be verified against the project files, and a video review loop turns a four-day process into a four-week one.
What we ship instead is the text intake form at /intake: five structured questions, paste-in friendly, validated client-side, server-side, and at the AI-draft stage. The output is a written case study that anyone can edit, version, and approve in two clicks. It's less cinematic. It's also the format almost every agency buyer actually reads.
No agency CRM
The third feature we won't ship is the agency project tracker — tasks, time, contacts, deals, pipelines, the whole agency management surface that grew up around case study tools to "increase stickiness". We considered it, talked to four agency owners about it, and dropped it.
The honest answer is that an agency CRM is its own product — three engineers, a year of work, and a competitor set led by HoneyBook, Moxie, and Productive. We can't compete there and we don't intend to try. Even worse, adding it would split the engineering attention we've kept laser-focused on the case study draft loop. Every sprint a CRM surfaced as a feature request was a sprint where the draft → approval → publish loop got less polish. Customers didn't ask us for a CRM in the last year; they asked us to make the proof page load faster and to surface closed-won value up front. We listened.
What we ship instead is a deliberately small surface — intake, draft, review, publish — that hands off cleanly to whichever CRM the agency already uses. The closed-won value gets captured at intake, so it appears on the proof page without anyone retyping it into HubSpot.
If any of those trade-offs resonate, the fastest way to feel the difference is to start an intake and see a draft in your inbox by the end of the day.