Post-mortem: AI coding agents built 14 apps in seven weeks, then the landing page got zero clicks on its main button
A solo developer used AI coding agents to ship a 14-app suite with over 1,000 commits, then found that two teams used it for free, 78% of visitors left after one page and nobody clicked the main call to action. He narrowed to one product.
Evidence: The author reports this. We have not checked it beyond reading the source.
The business problem
When AI agents make features cheap, a solo founder can keep building instead of choosing one problem, testing demand and launching, which leaves a large product nobody understands or pays for.
What was tried
What the author did: over seven weeks, AI coding agents wrote most of the code for a suite called Align (meeting rooms, docs, chat, a task tracker with Jira and Linear sync, a Chrome extension, a Mac menu-bar app, an MCP server, a status page and an admin dashboard), about 375,000 lines and up to about 190 commits a week. He planned Show HN and Product Hunt launches but kept building instead. What he changes next: pick one product (a Chrome extension that reads live captions without adding a bot to calls), freeze every other feature until 20 teams use it weekly, rewrite the landing page to explain only that one thing, reply to every comment and follow up personally with each person who tries it, and post an update with real numbers after 30 days.
What was reported (failed)
Over 1,000 commits and 14 apps shipped. Two outside teams use it, neither paying. About 195 landing page visitors in 15 days, 78% viewed one page and left, zero clicks on the main button, about 10 visits from search. No revenue or cost figures are given.
Limitations
Self-reported by the builder, with no screenshots of analytics. The coding agents and models used are not named and the build process is not described in detail, so this is a lesson about scope and launch rather than a reproducible coding workflow. The refocused plan has no results yet; a 30-day follow-up is promised. The market (AI meeting notes) is crowded, which also affected the result. New account on the site.
What you need
The source does not say.
Before building feature two, write down the one user and the one number (for example weekly active teams) that must move first.
A prompt to try
Here is the list of everything I have built and my landing page copy: [paste]. Pretend you are a first-time visitor with 10 seconds. What do you think this product does? Then pick the single feature most likely to get 20 weekly users and rewrite the page headline and subheading for only that feature.
Sources
- DEV Community (Amit Rajput) ↗ Firsthand write-up, published October 29, 2026
Source published: October 29, 2026. Last reviewed here: October 30, 2026. Spot a mistake? Tell us.
Get new workflows like this by email
A short selection of the most useful new workflows, including the ones that did not work. Free, and you can unsubscribe at any time.
Related workflows
Make app demo videos with Veo, then switch to motion transfer from your own footage when it fails
A solo builder of a jiu-jitsu training app generated move demo videos with Veo, found it could not do groundwork moves, and switched to filming the moves themselves and transferring the motion onto an AI athlete with Wan 2.2, plus AI voice cues.
A third AI model audits the code before launch: 100 bugs found in a no-code founder's SaaS
A founder with no coding skills builds with two AI models and points a third at the codebase only to audit, before taking payments. It found about 100 bugs, including broken payment credits, then became a standing check.
Localize an iOS app with code-aware CLI agents, .xcstrings and separate App Store copy files
An iOS developer describes using Claude Code to find missing strings and Codex CLI to translate .xcstrings, store metadata and screenshot text. App Store entry and screenshot layout remain manual.
Write AI test specifications before implementation, or hide the function body from a fresh test-writing chat
A small-SaaS developer reports a double-refund bug despite passing AI-generated tests. Their revised Claude Code routine separates test specifications from implementation and uses a fresh chat for diff review.