8 Months of Code Earned $0. One Question Closed $70.
The Case: $70, one customer, 8 months in
What he does. He sells Announcify, a hosted changelog tool that SaaS companies embed so they can show users what they shipped without building their own.
Backstory. His first product, PDFQuizGen, got traffic and signups and never got a dollar, so he moved on and spent months building Announcify instead of selling it — GitHub integration, Linear integration, AI-generated changelogs, analytics, custom domains, multiple widget layouts. His own words: he was hiding behind development because coding is easier than asking. The window that made this case work isn't a market shift, it's that in 2026 a solo founder can build six integrations alone and still discover that none of them were the blocker.
Product. - Hosted changelog, embedded on the customer's own domain - GitHub and Linear integrations to pull shipped work - AI-generated changelog entries - Multiple widget layouts, custom domains - View analytics on the changelog itself
Pricing. $70, one customer, one payment. The post never says whether that's a monthly plan or an annual one.
Key numbers. - First payment: $70 (1 customer) - Time on Announcify before that payment: 8 months - Total time trying to make a SaaS work: almost 2 years - Revenue before this payment: $0 - Previous product, PDFQuizGen: traffic and signups, zero payments - Buyer's blockers before he'd pay: 2 (Linear integration, security improvements) - Time from "he said he would pay" to shipped and paid: a few weeks - Customers who told him what to build: 1 - Reddit post: 441 upvotes, 329 comments
Stack. GitHub, Linear, AI-generated copy, custom domains, embeddable widget, analytics. Framework and hosting not disclosed.
Why this works (and what most readers will miss)
1. He turned a support thread into a signed spec. The buyer used the product, listed what was missing, and the founder asked directly whether the missing parts would produce a payment. That question is a pre-sale wearing a feature request's clothes. Most founders build the request and hope; he priced the request first.
2. A changelog is an embed, not a dashboard. Once the script is in the buyer's app shell, it stops competing for the buyer's attention every week. Tools that live inside someone else's product churn like a favicon churns — which is to say, almost never, because removing it is a deploy.
3. The 8 months of over-building are why the conversation worked. This is where the founder's own lesson is slightly wrong. He says he wishes he'd talked to people earlier, and he's right about the timing. But the reason the conversation converted is that the product was already 90% done, so the buyer's remaining objections were two items instead of twenty. Talk to people early, yes — talk to them with something already load-bearing in their hands.
The Distilled Read
He didn't sell a changelog tool. He sold two weeks of his own hands. The thing that produced the $70 was a scoped, named, agreed-upon gap between what one buyer had and what he'd pay to have. That's the whole product. Six integrations built in a vacuum earned nothing; two built against a named person earned money. And notice that Linear appears twice in his own telling — once in the months of building, once in the list of what the buyer still needed. He'd already "built" it. The buyer's version was a different object. That gap is the case. If you have to guess what the missing piece is, you don't have a product, you have a hobby with a deploy pipeline.
The 8 months are sunk. The script is the asset. He now owns a repeatable sequence: get a SaaS builder to install the widget, let them use it until they complain, write the complaint down, ask whether fixing it converts them, then fix it. That runs again on the next twenty CRM builders, and the next twenty Jira shops, and the next twenty Height users, and every integration after the first is a template swap on code that already exists. Two products fall out of one playbook here: the widget itself, and the paid "we already did your security review" package. He is one conversation away from having both and doesn't know it yet.
$70 is not revenue. It's a price discovery event that cost 8 months. Score the bet honestly. Capital at risk: near zero. Time to first dollar: 8 months, which is terrible. Decay risk: severe, because a changelog widget is exactly the shape of thing a coding agent generates in an afternoon by next year. Optionality: thin, since a changelog tool doesn't fork into three other businesses. This is bet two of twenty, not the one that pays. The fatal move is treating first-$70 as permission to spend another 8 months. The rule going forward: each of the next twenty customers must take under three weeks from first conversation to payment, or the bet is closed and the capital — his hours — moves.
He found his buyer by accident and it still beat traffic, which should terrify you. PDFQuizGen had traffic and made zero. One directed conversation made $70. Directed conversation converts somewhere near 1 in 30; traffic on an unloved dev tool converts near 1 in never. But 30 conversations for $70 is a wage, not a business, so the price has to move or the room has to change. And the room is wrong. He's selling into r/SaaS, the most crowded and least funded market on earth. Changelogs aren't a dev problem, they're a marketing problem — the pain lives with the founder who shipped nine things last quarter and whose users noticed none of them. Go build the first ten changelogs by hand, free, hosted, for founders in that exact condition, then charge to keep them alive.
The gate was never the feature. He wrote "a Linear integration and some security improvements" as if the second half were a footnote. It's the entire business, and none of the 329 commenters flagged it. What that buyer was actually purchasing was permission to put a stranger's script inside his own product, in front of his own customers. Eighteen months out, an agent will generate the widget, the layouts, the AI summaries, and the GitHub sync in one sitting — all of it, free, in the buyer's own repo. What no agent will do is answer a subprocessor questionnaire, sign a DPA, keep the embed CSP-safe, and publish a security page a nervous CTO can forward to his own board. Every operator selling embedded tooling is optimizing the feature list. The winners will be the ones who published their trust surface before anyone asked for it, because when the code becomes free, the only thing left to sell is the reason to let you inside the walls.
Steal-the-Playbook
- Pick one vertical, not the category. Not "SaaS companies." Pick "seed-stage CRM and sales tools with a public roadmap." That's a list you can finish in a week.
- Find 30 of them shipping in silence. Their GitHub releases page is active, their /changelog is empty or last updated four months ago. That contrast is your entire cold message.
- Do the work free for two weeks. Build their changelog by hand from their commits, host it on your domain, send a Loom of it live. No pitch, no trial link.
- Ask the closing question out loud. "If I ship X and Y, will you pay $Z on the first?" Get it in writing in the same thread. Do not open the editor before you have a yes.
- Ship a public security page in week one. Subprocessors, data retention, CSP notes, a DPA template. It costs a day and answers the objection that actually stops the wire.
Stack: domain ~$12/yr, Stripe payment link (2.9% + 30¢), Cal.com free, Loom free, Notion for the spec. Under $20 and one weekend to be live.
Bottom Line
He spent 8 months building and a few weeks selling, and only the few weeks made money. The $70 is not validation of the product; it's validation of the question.
Ask the buyer what he'd pay for before you build it, and you turn a roadmap into an invoice.
When the code goes free, the only thing left to sell is the reason to trust you inside their product.