<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Omar Soliman on Medium]]></title>
        <description><![CDATA[Stories by Omar Soliman on Medium]]></description>
        <link>https://medium.com/@theomarsoliman?source=rss-f463622e5a7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*CxwztWAQPyu9tHbL</url>
            <title>Stories by Omar Soliman on Medium</title>
            <link>https://medium.com/@theomarsoliman?source=rss-f463622e5a7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:00:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@theomarsoliman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I review Claude Code changes without reading every line]]></title>
            <link>https://medium.com/@theomarsoliman/how-i-review-claude-code-changes-without-reading-every-line-db01a94e658a?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/db01a94e658a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 21:44:54 GMT</pubDate>
            <atom:updated>2026-11-15T21:44:54.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tiPOQVUmS-SyH2xS" /></figure><p>For about a year, my review process for agent changes went like this: open the diff, scroll, feel tired, check that the tests pass, approve. I’d tell myself I read it. I’d read maybe a third of it.</p><p>The problem isn’t laziness. Claude Code can write 600 lines in the time it takes me to read 60. If review means reading every line, review loses every time. So I stopped trying to win that race and changed what I review.</p><p>Here’s the process I use now. It’s not clever. It just moves my attention from lines to decisions, which is where the bugs I care about actually live.</p><h3>1. Keep each change small enough to have a few decisions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9BAxwESmxUV1_GiW.png" /></figure><p>The first thing I fixed was size. A change that touches 40 files has 40 decisions in it, and I can’t hold 40 decisions in my head. So I ask for one thing at a time, and I stop the agent when it starts doing “while I was here” work.</p><p>My rough rule: if I can’t list the decisions in a change from memory after reviewing it, the change was too big.</p><h3>2. Ask for the decisions before you look at the diff</h3><p>When the agent says it’s done, I don’t open the diff yet. I ask:</p><blockquote><em>What did you decide in this change? For each decision, what else did you consider, and why didn’t you go with it?</em></blockquote><p>This is the most useful prompt I have. The summary an agent gives you by default is a list of what it did, which is the diff in sentences. What you want is the list of choices: picked this library, added a retry here, changed this error message, skipped the existing helper because it didn’t handle nulls.</p><p>The rejected options are where the interesting stuff is. Half the time, the thing it rejected is what I would have done, and now I know to look at why.</p><h3>3. Review the decisions first, then the lines they touch</h3><p>With the decisions in hand, I go through them one by one and ask a simple question: would I have made this call?</p><ul><li>If yes, I spot-check the lines it touched and move on.</li><li>If I’m not sure, I read those lines properly.</li><li>If no, I stop reviewing and tell the agent what I want instead.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wsTZFFc5XBphT7Qz.png" /></figure><p>This flips the order. I used to read code and try to work out the decisions from it. Now I get the decisions and only read the code where it matters. Most of my review time goes to the two or three calls I’d have made differently, not to the 400 lines that are fine.</p><h3>4. Look for the decisions nobody mentioned</h3><p>Agents don’t always tell you everything. These are the ones I’ve learned to look for:</p><ul><li>A fallback or default value that hides an error instead of raising it</li><li>A new dependency, or a new helper that duplicates one we already have</li><li>A changed error message or log line that something downstream might be matching on</li><li>A test that was “fixed” by changing the assertion</li><li>Anything that touches auth, money or deleting data</li></ul><p>If one of those shows up in the diff and not in the list of decisions, that’s my first question back.</p><h3>5. Tie each decision to a test</h3><p>For each decision that matters, I want to know which test covers it. Not “the tests pass”, but “this test fails if we undo this decision.” If there isn’t one, that’s usually the next thing I ask for. It’s also the fastest way to find out whether a decision was deliberate or an accident.</p><h3>6. Keep the decisions with the PR</h3><p>This is the step I skipped for months, and it’s the one I regret most.</p><p>The decisions are useful in review, and they’re even more useful three months later, when someone opens the file and wants to know why there’s a retry around a call that shouldn’t fail. By then the session is gone. The agent doesn’t remember. The person who prompted it doesn’t either.</p><p>So the decisions go in the PR description now, under a “Decisions” heading, with the rejected options. I used to paste them in by hand. Lately I’ve been using <a href="https://braidkit.io/">braidkit.io</a>, which records the Claude Code session on my Mac and, when I’m done, reconstructs the decisions with the options it rejected and the lines each one touched. It can post them on the PR too. It’s new and Mac only, but it’s the first thing that made this step happen without me having to remember.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EhN8PjQDoQQ2bCut4Zl7g@2x.png" /></figure><h3>What changed</h3><p>Review is faster, which I expected. What I didn’t expect is that it’s also better. I catch the bad calls sooner because I’m looking at the calls, not at formatting and variable names. And when I approve something, I can explain why, which wasn’t true before.</p><p>The bigger change is how it feels. Approving an agent PR used to feel like signing something I hadn’t read. Now it feels like a review again.</p><p>If you try one thing from this, try step 2. Ask your agent what it decided and what it rejected before you open the diff. It takes ten seconds, and it changes what you look at.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db01a94e658a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Software Business Right Now Is Cleaning Up After Vibe Coding]]></title>
            <link>https://medium.com/@theomarsoliman/the-best-software-business-right-now-is-cleaning-up-after-vibe-coding-4493e06be559?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4493e06be559</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[freelancing]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 13:19:05 GMT</pubDate>
            <atom:updated>2026-09-28T13:19:05.398Z</atom:updated>
            <content:encoded><![CDATA[<h3>Millions of working apps now exist with nobody who can maintain them. The threads where those owners panic are the clearest customer list a developer has been handed in years.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ucCL74C7Wr-BZvYB.png" /></figure><p>The most useful thread I have read this year was titled “The real cost of vibe coding isn’t the subscription. It’s what happens at month 3.” It ran to 831 upvotes and 286 comments on r/vibecoding, and the comments are a queue of people describing the same wall from slightly different sides.</p><p>Around the third month, the app works and the owner can no longer change it. Every new feature breaks two old ones. The agent that built it cannot hold the whole thing in context any more. There is no test suite, because nobody writes tests for something they are still deciding about. The database rules were set on day two by someone who did not know what a database rule was.</p><p>None of that is a failure of vibe coding. It is what happens to every codebase that outgrows its author, which is normally the point where the author hires someone. Except this author does not know that is the move, and could not evaluate the hire if they made it.</p><p>Several million people are about to be in this position simultaneously. If you are a developer wondering what to build, that is the most legible customer list you will get.</p><h3>The demand is already loud</h3><p>“Anyone else feels like vibe coding hits a wall after a point?” pulled 194 upvotes and 178 comments. “Whats happening to all the vibe coded apps out there?” got 152 comments. A security engineer offered to try to hack ten vibe-coded apps for free and got 136 comments of volunteers, which is a remarkable thing to volunteer for.</p><p>Then there is the thread that should be printed and pinned somewhere: a post about one of the genuine vibe coding success stories of 2025, a product that reportedly did $1M in revenue, was built in ten days and got mentioned on Oprah. The title’s second half is “And its Firebase database”, which is the part the 69 comments are about.</p><p>That is the whole market in one headline. Real revenue, real users, and a foundation nobody checked.</p><p>And on the other side, the people already making money from it. “I’m a vibecoder turned AI consultant for small businesses. I make more than most of you” took 479 upvotes and 173 comments on r/AskVibecoders. Another, quieter post described building six internal tools for a business doing roughly $3M a year with six employees, with no coding background, and feeling like the team had doubled.</p><p>Those two are the same business at different levels of self-awareness.</p><h3>Four things to build, in order of how soon someone pays you</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bwd2ZtPUTVEzx1nP.png" /></figure><h3>1. A pre-launch scan, sold per scan</h3><p>The moment of maximum willingness to pay is the week before launch. “If you’re about to launch a vibe coded app, read this first” got 1,205 upvotes because people know they are about to be exposed and do not know what to check.</p><p>Scan for the specific, embarrassing failures: public database read and write rules, API keys committed to the repo or shipped in the client bundle, authentication that checks the user on the front end only, no rate limiting on anything that costs money, no backups.</p><p>Around $29 a scan. One-time purchases are usually a worse business than subscriptions, except when the trigger event is this sharp and this repeatable. Every app hits launch week once, and people launch more than one app.</p><p>Scope it honestly in the copy. This catches the common mistakes. It is not a penetration test, and saying so is what stops the one bad week where someone thought it was.</p><h3>2. Month-three rescue, sold as a fixed engagement</h3><p>This is the consulting business and it is the one with the best margins, because the alternative the customer is weighing is not another vendor. It is abandoning the app.</p><p>The engagement is the same every time: get it into version control properly, get a test suite around the three paths that matter, fix the auth and the database rules, set up a staging environment, and write the instructions file so their agent stops making the same mistakes.</p><p>Charge a fixed price for the assessment and a fixed price for the fix. Do not sell hours, because the customer cannot evaluate hours and will feel robbed whatever happens.</p><p>The consultant thread above is one person doing this without productising it. The productised version is not harder, it is just written down.</p><h3>3. Deployment that assumes no operator</h3><p>“Vibe coders, where do you deploy your apps and how has it gone?” got 65 comments, most of them variations on it went badly.</p><p>The gap is not hosting. Hosting is solved and cheap. The gap is everything hosting assumes you already have: a staging environment, a rollback that is one button, backups you can test, environment variables that are not in the repo, a status page when it breaks at 2am and the owner is asleep.</p><p>This is the hardest of the four to build and the easiest to charge subscription money for, because it is the only one the customer cannot stop paying for once it is running.</p><h3>4. Internal tools for the businesses that will never hire a developer</h3><p>The quietest thread here is the most interesting one: six internal tools, six employees, roughly $3M in annual revenue, built by someone with no coding background who said it felt like the team doubled without hiring.</p><p>That business was never going to hire a developer. Not because of cost, but because they could not write the job description or judge the work. They will, however, pay someone to build and maintain the six tools, forever.</p><p>This is the least glamorous item on the list and the one I would bet on hardest. It is also where the job market data points: business applications in the US hit a record 5.67 million in 2025, and only about 8.8 percent of those said they planned to pay any wages. Millions of operators, no staff, no developer, a pile of chores.</p><h3>The part that will decide whether this works for you</h3><p>Do not build any of this while looking down at the customer.</p><p>The tone in a lot of developer commentary about vibe coding is contempt, and contempt does not sell services. The person with the broken Firebase rules shipped a product that made money, which is more than most of us did last quarter. They used the tool available to them, hit the limit of it, and are now trying to find help without knowing the vocabulary to search for it.</p><p>That is a good customer. They have a working product, revenue, urgency and no internal alternative. The only reason this market is underserved is that the people qualified to serve it keep posting jokes about it instead.</p><p>The four ideas above, with the threads, stacks and suggested pricing, are at <a href="https://businessideasdb.com/business-ideas-for-developers?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=month-three-cleanup&amp;utm_content=list">business ideas for developers</a>. The agent-side tooling that these same people need is at <a href="https://businessideasdb.com/vibe-coding-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=month-three-cleanup&amp;utm_content=hub">the vibe coding ideas hub</a>.</p><h3>Frequently asked questions</h3><p><strong>Why do vibe coded apps break around month three?</strong> The codebase outgrows what the agent can reliably hold in context, and there is usually no test suite, no version control discipline and no staging environment to catch regressions. The app still works, but changing it safely now requires practices that were skipped during the fast part.</p><p><strong>What are the most common problems in vibe coded apps?</strong> The recurring ones in these threads are permissive database rules, API keys committed to the repository or exposed in the client bundle, authentication enforced only on the front end, no rate limits on paid endpoints, and no backups.</p><p><strong>Can developers make money fixing AI-generated codebases?</strong> Several are already doing it. The pattern that works is a fixed-price assessment followed by a fixed-price remediation, rather than hourly work, because the customer cannot evaluate hours. The trigger points with the highest willingness to pay are the week before launch and the month the app stops being changeable.</p><p><strong>Is there a real market for this or is it a short term wave?</strong> The underlying driver is that more businesses now exist with no technical staff. US business applications hit a record 5.67 million in 2025, of which only about 8.8 percent indicated any planned wages. The people building their own tools are not going to stop, and they are not going to hire.</p><p><strong>What should a developer build first here?</strong> The pre-launch scan. It has the sharpest trigger event, the clearest deliverable, and it can be sold for a fixed price to a customer who has just realised they need it.</p><p>Somebody is going to make a very good living being the person who shows up at month three. It may as well be someone who likes the customer. More ideas at <a href="https://businessideasdb.com/business-ideas-for-developers?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=month-three-cleanup&amp;utm_content=outro">businessideasdb.com/business-ideas-for-developers</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4493e06be559" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Claude Code Skills Worth Building, Taken From What Developers Keep Asking For]]></title>
            <link>https://medium.com/@theomarsoliman/five-claude-code-skills-worth-building-taken-from-what-developers-keep-asking-for-9d70612153f4?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d70612153f4</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 12:22:33 GMT</pubDate>
            <atom:updated>2026-09-24T12:22:33.037Z</atom:updated>
            <content:encoded><![CDATA[<h3>A skill is a folder with a SKILL.md in it. That is the entire barrier to entry, which is why the interesting question is not how to build one but which one anybody wants.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*co7-Hp_mV2-e4CmY.png" /></figure><p>Somebody on r/ClaudeAI posted that they had built a Claude skill which writes prompts for other AI tools, because they were tired of burning credits on bad ones. The post got 1,296 upvotes and 146 comments, and the repo passed 600 stars.</p><p>The skill is a folder. A SKILL.md file with a name, a description and instructions, plus whatever scripts it needs. That is the whole artifact. Claude reads the description, decides a task needs it, and only then loads the rest, so an unused skill costs you almost no context.</p><p>Which means the build is not the hard part. The hard part is picking one anybody wants, and there is a decent way to do that: read what people complain about, not what they upvote in the showcase threads.</p><p>Here are five where the complaint is loud enough that I would bet on the skill.</p><h3>1. A session handoff skill</h3><p><strong>The complaint.</strong> Long projects do not fit in one session, and the second session starts blank. On r/ClaudeCode someone described wiring Claude Code to Obsidian and a notes format just to keep a project’s context alive between sessions, at 95 upvotes and 81 comments. The same question turns up in r/LocalLLaMA as “what tools are you using to give your LLM a persistent second brain”, 106 comments deep, and in r/codex as people asking how to give memory to the Codex CLI at all.</p><p>Everyone is hand-rolling the same thing.</p><p><strong>The skill.</strong> Trigger it on phrases like “wrap up” and “pick up where we left off”. On wrap up, it writes a HANDOFF.md holding decisions made, what is still open, the files that matter and the commands that work. On start, a SessionStart hook loads it back.</p><p><strong>Why it works as a skill and not a doc.</strong> The value is that the agent writes the note in the format it will later read best, which is not how a human writes notes. Pair it with the hook and it becomes invisible, which is the bar.</p><p><strong>Price.</strong> Free. This is an audience builder, and it will be copied within a week of being good. That is fine. Ship it free, put your name on it, sell the next one.</p><h3>2. A launch checklist skill</h3><p><strong>The complaint.</strong> This is the loudest signal in the whole category. “If you’re about to launch a vibe coded app, read this first” took 1,205 upvotes and 187 comments on r/vibecoding. A companion post aimed at people whose app already has users pulled 210 more. A security engineer offering to try to hack ten vibe-coded apps for free drew 136 comments of volunteers.</p><p>People are shipping apps they cannot audit and they know it.</p><p><strong>The skill.</strong> One section per risk: authentication, database access rules, rate limits, secrets in the repo, backups, error reporting. Bundle real check scripts, not prose, so the agent finds the public database rule rather than reminding you that database rules exist. Output a short markdown report with a pass or fail per item.</p><p><strong>Price.</strong> $19 one-time with free updates. This is the rare skill people will pay for, because the alternative to paying is finding out in public.</p><p><strong>The catch.</strong> You are now implicitly promising something. Scope it honestly in the README: this catches the common, embarrassing mistakes, it is not a penetration test.</p><h3>3. A setup diet skill</h3><p><strong>The complaint.</strong> “I removed 63% of my Claude Code setup and it got 10x faster. Stop installing everything” got 235 upvotes and 111 comments on r/ClaudeCode. Alongside it, “CLAUDE.md is a super power” sat at 719 upvotes, and a thread on tuning AGENTS.md for Codex at 203.</p><p>So the instructions file is understood to be load bearing, and people’s setups have quietly rotted into a pile of half-used MCP servers and contradictory rules.</p><p><strong>The skill.</strong> Point it at a project and have it audit the setup: which MCP servers have not been called, which rules in CLAUDE.md contradict each other, which instructions are never triggered, what is duplicated between the global and project files. Produce a diff, not a lecture.</p><p><strong>Price.</strong> Free core, with a paid version that runs across a team’s repos and reports drift. The team version is the business. The solo version is the marketing.</p><h3>4. A demo video skill</h3><p><strong>The complaint.</strong> Somebody automated product tutorial videos with AI and posted about it on r/ClaudeAI. 283 upvotes, 131 comments, and most of those comments were people asking how.</p><p>Every indie founder hits this at launch. The product works, and the thing standing between it and a launch post is a two-minute walkthrough that takes a day to make badly.</p><p><strong>The skill.</strong> Read the app’s routes, write a click-by-click script, drive it with Playwright, generate narration from the script, stitch with ffmpeg, and export at the sizes X and Product Hunt want.</p><p><strong>Price.</strong> $29 one-time. It replaces a specific chore on a specific day, which is the easiest kind of thing to sell.</p><p><strong>Effort warning.</strong> This is the heaviest one here. The browser automation is fine, the narration timing is where the weekend goes.</p><h3>5. A prompt writing skill</h3><p><strong>The complaint.</strong> The one at the top of this post. 1,296 upvotes for a skill whose entire job is turning a vague request into a prompt that does not waste a run.</p><p>That it already exists is not a reason to skip it. It is proof of demand, and the existing one is general purpose. The opportunity is the narrow version: a skill that writes prompts for one specific expensive thing, like a migration, a large refactor, or a test suite from a spec, where a bad first prompt costs an hour rather than a minute.</p><p><strong>Price.</strong> Free, and use it as the front door to whatever you actually sell.</p><h3>What separates a skill people install from a folder nobody opens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SdK9NW8WIRd_Eb_c.png" /></figure><p>Three things, from watching which of these threads convert to stars and which just collect agreement.</p><p><strong>It has to trigger itself.</strong> If the user has to remember the skill exists, it is documentation. The description field is the product. Write it as the condition under which Claude should reach for the skill, not as a summary of what the skill contains.</p><p><strong>It has to do the boring half.</strong> The parts of these that people pay for are the check scripts, the ffmpeg flags, the handoff format. Not the instructions. Anyone can write instructions.</p><p><strong>It has to survive being copied.</strong> A skill is plain text in a folder. If your entire value is the text, you have no business, you have a gift. The ones that hold up wrap something that does not copy: a dataset, an API, a hosted service, or the fact that you keep it current.</p><p>The other build surfaces, hooks, subagents, plugins and MCP servers, each have their own version of this, with the source threads attached. They are at <a href="https://businessideasdb.com/vibe-coding-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=claude-code-skills-to-build&amp;utm_content=hub">the vibe coding ideas hub</a>, and the full skills list with buyer and price for each is at <a href="https://businessideasdb.com/vibe-coding-ideas/claude-code-skills?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=claude-code-skills-to-build&amp;utm_content=list">Claude Code skills worth building</a>.</p><h3>Frequently asked questions</h3><p><strong>What is a Claude Code skill?</strong> A skill is a folder containing a SKILL.md file with a name, a description and instructions, plus optional scripts and reference files. Claude reads the description and loads the full skill only when a task needs it, so a skill costs almost no context until it is used.</p><p><strong>Can you sell Claude Code skills?</strong> You can, but the skill itself is plain files and trivially copied. Skills people pay for usually wrap something that is not copyable: an API, a dataset, a hosted service or ongoing updates. Treat the skill as distribution and charge for what sits behind it.</p><p><strong>What makes a skill trigger reliably?</strong> The description field. Write it as the condition under which the skill should be used, including the phrases a user would actually type, rather than as a summary of the skill’s contents. A skill that does not trigger on its own is documentation.</p><p><strong>How is a skill different from a hook or a subagent?</strong> A skill is instructions plus files that the agent loads when a task calls for it. A hook is code the harness runs at a fixed point, such as before an edit or at session start, whether the agent wants it or not. A subagent is a separate agent with its own context and its own job, such as reviewing a diff.</p><p><strong>What is the easiest Claude Code skill to build first?</strong> A session handoff skill. It is one SKILL.md and a markdown template, it solves a problem every long project has, and pairing it with a SessionStart hook is a small addition that makes it feel automatic.</p><p>If you build one of these, the honest measure is not stars. It is whether you still have it installed a month later. Most skills fail that test, including several of mine. The five above are the ones where the complaint was loud enough that I think the skill survives the month. More of them, with the threads attached, at <a href="https://businessideasdb.com/vibe-coding-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=claude-code-skills-to-build&amp;utm_content=outro">businessideasdb.com/vibe-coding-ideas</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d70612153f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Startups Fail, in the Numbers Nobody Puts Side by Side]]></title>
            <link>https://medium.com/@theomarsoliman/why-startups-fail-in-the-numbers-nobody-puts-side-by-side-f58738af646d?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f58738af646d</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 22:22:36 GMT</pubDate>
            <atom:updated>2026-09-20T22:22:36.811Z</atom:updated>
            <content:encoded><![CDATA[<h3>Half of new US businesses are gone by year five. The shutdown reports blame one thing, the revenue data shows another, and the gap between them is where the avoidable failures live.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JuoOcYNKJhh75Lvr.png" /></figure><p>Two numbers landed in my notes the same week and refused to sit together.</p><p>The first: of every 100 US businesses that opened, about 78 were still trading a year later. That sounds survivable. The second: among startups that actually made it to having revenue worth verifying, the median one brings in roughly $2,310 a month. Not a failure. Not a business either, for most people.</p><p>Startups do not usually die in a fire. They die of not mattering enough, slowly, while the founder tells people it is early days. The published failure statistics describe the fire. The revenue data describes the slow version, and almost nobody puts the two next to each other.</p><h3>Half are gone by year five, and that is the flattering cut</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*27F85CRwHl75fw01.png" /></figure><p>The US Bureau of Labor Statistics tracks private-sector establishments by age. Of the cohorts measured through March 2025, 77.9 percent were still operating after one year, 51.4 percent after five, and 34.7 percent after ten.</p><p>Read that again with the right emphasis. The famous “90 percent of startups fail” line is folklore. The real number is closer to a coin flip at year five. But this counts establishments, which includes the dentist and the landscaping company, not just software. It is the friendliest possible framing of the odds, and it still says half of you will not be here in five years.</p><p>The tech-flavoured version is harsher, because tech businesses raise money and therefore have a clock.</p><h3>“Ran out of money” is a symptom dressed up as a cause</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4OQsop9SSqsxM7Wv.png" /></figure><p>CB Insights read the post-mortems of 431 VC-backed companies that shut down since 2023. The reasons, with companies citing more than one:</p><ul><li>Ran out of capital: 70 percent</li><li>Poor product-market fit: 43 percent</li><li>Bad timing: 29 percent</li><li>Unit economics that never worked: 19 percent</li></ul><p>CB Insights themselves call running out of capital the final cause of death rather than the root problem, which is the most useful sentence in the whole report. Nobody funds a company that is working and then stops. The capital ran out because something upstream was not pulling.</p><p>That something is the 43 percent line. Product-market fit is the polite name for “we built a thing and the people we built it for did not rearrange their budget.”</p><p>And product-market fit is decided before you write code. It is decided when you pick the idea.</p><h3>The survivors are smaller than the story</h3><p>Here is where the picture gets uncomfortable, and where I think most founder advice is quietly dishonest.</p><p>TrustMRR verifies startup revenue through Stripe. A snapshot of 941 active startups carrying at least $500 a month showed a median of about $2,310 in monthly revenue. These are the ones that got somewhere. They shipped, they charged, they collected. Half of them make less than a part-time job.</p><p>In the same snapshot, 41.7 percent had shrinking revenue over the preceding 30 days.</p><p>I find this more instructive than any failure statistic, because these companies did not fail. They are the survivors, and the survivor median is a side income. If your plan assumes that shipping a good product produces a salary, the data says shipping a good product produces about $2,300 a month and a 4-in-10 chance you are currently going backwards.</p><p>That is not an argument against building. It is an argument against building something with a low ceiling on purpose.</p><h3>The categories that struggle are boringly predictable</h3><p>Break the same verified-revenue data down by category and the ceilings show up.</p><p>Artificial intelligence is the most crowded category by a distance: 266 of the 941 startups, about 28 percent of everything with verified revenue. Their median is $2,000 a month, below the $2,473 median for every other category combined, and 49.6 percent of them were shrinking compared with 38.6 percent of the rest.</p><p>Read that as a market, not a moral. The most crowded category pays below average and is losing ground faster. That is what a crowd does to price.</p><p>The pattern repeats wherever the buyer is a consumer who expects software to be free:</p><ul><li>Productivity tools: median $1,144 a month, the lowest of any category with 20 or more startups, and 40 percent of them under $1,000.</li><li>Health and fitness: median $1,450, with only 4.9 percent reaching $10,000 a month, the worst rate in the dataset.</li><li>Education: 57 startups, median $2,083, and 31.6 percent under $1,000.</li></ul><p>Meanwhile the categories selling to businesses hold up: marketing at $3,612, developer tools at $3,139, SaaS at $3,045.</p><p>None of this says do not build an AI tool. It says the phrase “AI tool” is not a wedge, because 266 other people used the same one. The wedge is the industry you point it at and the job you take off someone’s desk.</p><p>I keep the full breakdown updated at <a href="https://businessideasdb.com/worst-startup-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=why-startups-fail&amp;utm_content=intro">the worst startup ideas of 2026</a>, including the red flags I use to kill my own ideas before I get attached.</p><h3>The failure is usually visible at idea selection</h3><p>The part I got wrong for years: I thought idea selection was the cheap step and execution was the expensive one. The data says idea selection sets the ceiling and execution just determines how fast you hit it.</p><p>I run a scanner that reads Reddit for people describing problems and scores each thread 0 to 10 on how good a business it would make. Across 1,416 scored threads, 29.1 percent scored 8 or higher.</p><p>Then I split them by how popular the thread was, and the result was backwards from what everyone recommends. Threads with 1 to 9 upvotes scored 8 or higher 35.1 percent of the time. Threads with 1,000 or more upvotes managed 10.3 percent.</p><p>Popularity and profitability were not just uncorrelated. They pointed opposite ways.</p><p>The wording split even harder. Threads where somebody described doing a task manually scored 8 or higher 53.6 percent of the time. Threads mentioning a spreadsheet, 53.3 percent. Threads asking for “an alternative to X”, 18 percent.</p><p>That is the whole tell. Someone already doing the job by hand has proven the job is worth doing and has shown you exactly what they will pay to stop. Someone asking for a cheaper alternative has told you their budget is the thing they want to reduce.</p><p>The method behind that, and the threads themselves, sit in <a href="https://businessideasdb.com/reddit-business-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=why-startups-fail&amp;utm_content=method">the Reddit business ideas breakdown</a>.</p><h3>The honest version of the odds</h3><p>Put the four sources together and the shape is this. Roughly half of new businesses survive five years. Of the ones that get to real revenue, the middle of the pack earns a few thousand a month and four in ten are shrinking. The most common named cause of death is running out of money, which is what happens when nobody wanted it enough, which was decided before launch.</p><p>My own scar: my first two attempts were clever, novel and in crowded consumer categories. They did not fail dramatically. They sat at a few hundred dollars a month until I got bored, which is the real failure mode and the one nobody writes a post-mortem about.</p><h3>Frequently asked questions</h3><p><strong>What percentage of startups fail?</strong> Using BLS establishment data through March 2025, 22.1 percent of new US businesses close within one year, 48.6 percent within five, and 65.3 percent within ten. The commonly quoted “90 percent fail” figure is not supported by the government series.</p><p><strong>What is the number one reason startups fail?</strong> Running out of capital is the most cited reason, at 70 percent of 431 VC-backed shutdowns tracked by CB Insights. The most cited underlying reason is poor product-market fit, at 43 percent. CB Insights describes running out of money as the final cause rather than the root one.</p><p><strong>How much does a typical startup actually make?</strong> Among 941 startups with Stripe-verified revenue of at least $500 a month, the median was about $2,310 a month, and 41.7 percent were shrinking over the previous 30 days. That is the median for companies already earning, not for all startups.</p><p><strong>Which startup categories perform worst?</strong> In that same verified-revenue data, consumer productivity tools had the lowest median at $1,144 a month, and health and fitness had the lowest share reaching $10,000 a month at 4.9 percent. Artificial intelligence was the most crowded category at 28 percent of all startups, with a below-average median and the highest share shrinking.</p><p><strong>Can you tell a bad startup idea before building it?</strong> Often, yes. In 1,416 scored Reddit threads, complaints where someone described doing a task manually scored as strong business ideas 53.6 percent of the time, against 18 percent for threads asking for a cheaper alternative to an existing product. What people are already doing by hand predicts willingness to pay better than what they say they want.</p><p>The list I check every idea against, with the category data behind it, is at <a href="https://businessideasdb.com/worst-startup-ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=why-startups-fail&amp;utm_content=outro">businessideasdb.com/worst-startup-ideas</a>.</p><p>Revenue figures here are aggregates from TrustMRR, which verifies revenue through the payment processor. No individual company’s numbers are republished.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f58738af646d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Codex vs Cursor: pricing, usage limits, and which to pay for]]></title>
            <link>https://medium.com/@theomarsoliman/codex-vs-cursor-pricing-usage-limits-and-which-to-pay-for-a6c3a7fe5416?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6c3a7fe5416</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cursor]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 14:58:48 GMT</pubDate>
            <atom:updated>2026-09-13T14:58:48.994Z</atom:updated>
            <content:encoded><![CDATA[<h3>Both start at $20/mo, but Cursor sells an editor with any model and Codex sells OpenAI’s agent inside ChatGPT. Pricing, limits, and when to pick each.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7HVcWo5dDNXPEXfy.png" /></figure><p><em>Originally published on </em><a href="https://aistack.sh/compare/codex-vs-cursor"><em>aistack.sh</em></a><em>, where the pricing is kept current.</em></p><p>Both start at $20/mo, but you are buying different things. Cursor sells the editor and lets you spend its usage pool on any model. Codex sells OpenAI’s agent inside your ChatGPT plan, and it rides along in whatever editor you already use, including Cursor.</p><h3>Pricing at a glance</h3><ul><li><strong>Codex:</strong> Free, $20/mo ChatGPT Plus, $100/mo Pro 5x, $200/mo Pro 20x, $25/user/mo Business, API metered.</li><li><strong>Cursor:</strong> Free Hobby, $20/mo Pro, $60/mo Pro+, $200/mo Ultra, $40/seat Teams, $120/seat Teams Premium.</li></ul><p>Prices checked against both vendors’ pricing pages on 2026–09–08.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uNhxkX8yj1Q3QAOy.png" /></figure><p><em>Monthly list prices for every Codex and Cursor plan, checked 2026–09–08.</em></p><h3>Pick Codex when</h3><ul><li>You already pay for ChatGPT and want the coding agent included rather than billed twice.</li><li>You want one agent across the CLI, the web, an IDE extension and iOS, without changing editors.</li><li>You are happy on OpenAI models only, and want ChatGPT Pro’s 5x or 20x usage headroom at $100 or $200/mo.</li><li>You want cloud tasks and automatic code review attached to the same subscription.</li></ul><h3>Pick Cursor when</h3><ul><li>You want the AI wired into the editor itself: Tab completions, inline edit, Bugbot review, not just a sidebar.</li><li>You want to switch between Claude, Gemini, GPT and Cursor’s own Grok and Composer models on the same task.</li><li>You expect to blow through included usage and want on-demand billing at API rates instead of a hard reset window.</li><li>You are buying for a team and want seat administration, pooled analytics and SSO from the editor vendor.</li></ul><h3>The hard differences</h3><ul><li><strong>Entry price.</strong> Codex: free tier, then $20/mo ChatGPT Plus. Cursor: free Hobby, then $20/mo Pro.</li><li><strong>Top individual tier.</strong> Codex: $100/mo Pro 5x or $200/mo Pro 20x. Cursor: $200/mo Ultra.</li><li><strong>What the top tier buys.</strong> Codex: 5x or 20x the Plus allowance, roughly 200 to 2,000 GPT-5.6 Sol messages per 5-hour window on Pro 20x, plus Codex-Spark. Cursor: the largest included usage pool on both model pools, then on-demand usage at each model’s API rate.</li><li><strong>Where it runs.</strong> Codex: CLI, web, cloud, iOS, and an IDE extension for VS Code, Cursor, Windsurf, Xcode and JetBrains. Cursor: its own VS Code fork, plus a CLI, cloud agents and iOS.</li><li><strong>Model choice.</strong> Codex: OpenAI only (GPT-6 Astra, GPT-5.6 Sol, Terra and Luna, plus GPT-5.3-Codex-Spark on Pro). Cursor: Grok 4.6, Grok 4.5 and Composer 2.5 in the first-party pool, plus Claude, Gemini and GPT in the third-party pool.</li><li><strong>Team pricing.</strong> Codex: $20/user/mo ChatGPT Business billed annually, $25 billed monthly. Cursor: $40/user/mo Teams Standard, $120/user/mo Teams Premium.</li></ul><h3>Which is cheaper?</h3><p>Neither at the first paid tier: Codex comes with $20/mo ChatGPT Plus and Cursor’s first paid plan is $20/mo Pro. Codex also runs on the ChatGPT Free plan, and OpenAI currently includes it in the $8/mo ChatGPT Go plan for a limited time. At the top the order flips in Codex’s favour again: ChatGPT Pro starts at $100/mo for 5x Plus usage, where Cursor’s highest individual plan is $200/mo Ultra. For teams Cursor is the pricier side, at $40/user/mo against $25/user/mo for ChatGPT Business billed monthly.</p><h3>Cursor Ultra vs ChatGPT Pro: which $200 plan is better?</h3><p>They meter differently. ChatGPT Pro 20x at $200/mo buys 20x the Plus allowance, roughly 200 to 2,000 GPT-5.6 Sol messages per rolling 5-hour window, and when you run out you buy credits or wait for the window to reset. Cursor Ultra at $200/mo buys the largest included usage pool and then keeps going on on-demand billing at each model’s API rate, so it never hard-stops but the bill can pass $200. Pick Codex Pro if you want a predictable ceiling on OpenAI models, Ultra if you want model choice and are willing to pay overage.</p><h3>Can I use my ChatGPT subscription inside Cursor?</h3><p>Yes, for Codex itself. OpenAI ships a Codex IDE extension that installs into Cursor as well as VS Code and Windsurf, and it prompts you to sign in with your ChatGPT account or an API key, so Codex work bills against your ChatGPT plan while running inside Cursor. It does not make Cursor’s own features free: Tab, inline edit, Composer and Bugbot still draw on a Cursor plan or your own API key. Practically, a $20 ChatGPT Plus plan plus free Cursor Hobby gets you the Codex agent in the Cursor window without a second subscription.</p><h3>What are the usage limits?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*opqKNhIKYkPjI9zz.png" /></figure><p><em>Codex meters messages per 5-hour window; Cursor meters a dollar usage pool.</em></p><p>Codex meters messages per rolling 5-hour window and varies them by model: OpenAI estimates 10 to 100 GPT-5.6 Sol local messages per window on Plus, 50 to 500 on Pro 5x and 200 to 2,000 on Pro 20x, with weekly limits also possible and cloud chats drawing from the same allowance. Cursor meters money, not messages: every plan includes an amount of model usage across a Cursor Models pool and an Other Models pool, and once that is consumed you either add on-demand usage at API rates or upgrade. Cursor’s own guidance puts daily agent users at $60 to $100/mo of usage and power users at $200+.</p><h3>So which should you use?</h3><p>For most people they are not substitutes. Cursor is an IDE and Codex is an agent, and the Codex extension runs inside Cursor. Choose Cursor when the editor experience matters, when you want Claude or Gemini on the same task as GPT, or when you are buying seats for a team. Choose Codex when you already pay for ChatGPT, when you want the same agent in the terminal, the browser and your editor, or when you want OpenAI’s deepest reasoning models with a fixed monthly ceiling.</p><p>The live version of this comparison, with prices updated as the vendors change them, is at <a href="https://aistack.sh/compare/codex-vs-cursor">aistack.sh/compare/codex-vs-cursor</a>. Every other coding agent and AI IDE pair is on the <a href="https://aistack.sh/compare">compare hub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6c3a7fe5416" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Trades Are a Software Goldmine and Tech Keeps Ignoring Them]]></title>
            <link>https://medium.com/@theomarsoliman/the-trades-are-a-software-goldmine-and-tech-keeps-ignoring-them-731d9f142b7f?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/731d9f142b7f</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[business-ideas]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 05:24:28 GMT</pubDate>
            <atom:updated>2026-09-04T05:24:28.002Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Plumbers, electricians, and HVAC techs are drowning in paperwork and quietly paying for tools that fit them. Silicon Valley would rather build another app for other people in Silicon Valley.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FTEHgp5efPIY6hXy.jpg" /></figure><p>There is a plumber somewhere right now who is owed thousands of dollars because he finished a job, meant to send the second invoice, got called to the next emergency, and forgot. He is not disorganized. He is one person doing the work of a company, and the tools built to help him were designed for a business ten times his size with an office manager he does not have.</p><p>Multiply that plumber by every electrician, HVAC tech, landscaper, and solo contractor in the country and you are looking at one of the largest, most underserved software markets in existence. It is also one the technology industry is almost aggressively uninterested in, for reasons that have nothing to do with the size of the opportunity and everything to do with who founders like building for.</p><h3>The demand is real, specific, and searchable</h3><p>This is not a vibe. It shows up in search data as clearly as anything I track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRDG9NznUEWzZPk9YFtRxQ@2x.png" /></figure><p>People are actively looking for <a href="https://businessideasdb.com/idea/trade-invoice-autopilot?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=trades-software&amp;utm_content=trade-invoice-autopilot">invoice follow-up built for trade contractors</a>, roughly 7,200 searches a month for that fix and climbing 45%, attached to an idea whose realistic revenue range runs into the millions because the pain is money left uncollected. There is steady demand for <a href="https://businessideasdb.com/idea/solo-trade-field-service?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=trades-software&amp;utm_content=solo-trade-field-service">field service software specifically for solo tradespeople</a>, around 8,800 searches a month up 34%, from people explicitly adding the word “solo” because every other tool assumes a crew. Even the deeply unglamorous edges have pull: <a href="https://businessideasdb.com/idea/sub-insurance-tracker?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=trades-software&amp;utm_content=sub-insurance-tracker">subcontractor insurance tracking software</a> is up 58%. Nobody builds a startup dreaming of insurance certificate tracking, which is precisely why the person who does will have the field almost to themselves.</p><p>These are not enormous head-term numbers, and that is a feature. They are specific, high-intent searches from people with a real business and a budget, which converts far better than a hundred thousand idle searches from consumers browsing for something free.</p><h3>Why tech refuses to see it</h3><p>So why is this market sitting open? Not because it is invisible. Because of who founders are and who they instinctively build for.</p><p>The typical software founder lives in a world of other knowledge workers. They build project management tools, developer tools, marketing dashboards, because those are the customers they understand and, frankly, the customers they find impressive. A field service app for a solo electrician is not going to get admiring nods at a demo day. It does not feel like the future. So the talent and the funding flow toward the tenth Slack competitor, and the tradesperson keeps running a real, profitable, cash-generating business out of a truck using a notepad and a shoebox of receipts.</p><p>The incumbents that do exist grew upmarket, the way software companies always do, chasing bigger contracts until their product assumes a dispatcher, a crew, and an office. The <a href="https://businessideasdb.com/idea/field-service-crm-hvac?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=trades-software&amp;utm_content=field-service-crm-hvac">big field service platforms</a> are built for the mid-size company with staff, which leaves the solo operator and the two-person shop, the vast majority of the trades, holding a tool that constantly reminds them how small they are.</p><h3>Why the trades are a better customer than the startup you want to build for</h3><p>Here is the part that should change your mind if you are a builder. Tradespeople are, in several concrete ways, a dream customer that software people have talked themselves out of.</p><p>They have money and they understand paying for things that make or save money, because their entire life is quoting jobs and buying tools. A tool that reliably recovers a forgotten invoice or wins back an hour of evening paperwork is an obvious yes, not a “let me think about it.” They are not price-shopping between fourteen free alternatives the way a consumer is, because there often is not a fourteenth alternative built for them. And they are loyal. Win a plumber who tells his whole trade group you built the thing that finally fits, and you have a referral engine that no amount of paid acquisition buys.</p><p>Compare that to the crowded knowledge-worker markets everyone actually fights over, where the customer is fickle, the competitors are venture-funded, and the churn is brutal. The trades are less glamorous and better business on almost every axis that matters.</p><h3>What to build, concretely</h3><p>You do not need to reinvent anything. You need to take a proven category and aim it at the operator everyone abandoned. Pick one trade and one painful chore. Invoice follow-up that chases the money automatically so a busy contractor never eats a forgotten bill. A field service tool that has the courage to leave out dispatching and crew management because your customer is one person. The boring compliance edge, insurance and certifications, that a subcontractor loses sleep over. Each of those is a real business with searchable demand and almost no serious competition, sitting in plain sight.</p><p>The trades are not behind. They are underserved, which is a completely different and far more valuable thing. The paperwork misery is real, the money is real, and the willingness to pay is realer than in almost any market a founder would rather chase.</p><p>I keep the trade and field-service ideas, with their search demand and the specific unbuilt angle for each, at <a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=trades-software&amp;utm_content=outro">Business Ideas DB</a>. The goldmine is not hidden. It is just wearing work boots, and most of the industry has decided that is beneath them.</p><h3>FAQ</h3><p><strong>Is there really demand for software built for tradespeople?</strong> Yes, and it is specific and high-intent. People search for contractor invoice follow-up (around 7,200 a month, up 45%), solo field service software (around 8,800, up 34%), and even subcontractor insurance tracking (up 58%). These are smaller but far higher-converting searches than idle consumer terms, because they come from real businesses with budgets. Figures are from Business Ideas DB keyword data.</p><p><strong>Why is software for the trades so underserved?</strong> Because founders tend to build for customers they resemble and find impressive, which means knowledge-worker tools, not field service apps for solo electricians. The incumbents that exist grew upmarket toward crews and offices, abandoning the solo operator and two-person shop who make up most of the trades.</p><p><strong>Are tradespeople good software customers?</strong> Often better than the startups founders prefer to chase. They understand paying for tools that make or save money, they rarely have a dozen free alternatives to compare against, and they refer heavily within their trade. That combination of budget, low competition, and loyalty is rare in the crowded markets most software targets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731d9f142b7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Side Project Ideas With Real Search Demand (Pulled From Reddit, Not a Brainstorm)]]></title>
            <link>https://medium.com/@theomarsoliman/9-side-project-ideas-with-real-search-demand-pulled-from-reddit-not-a-brainstorm-c57ab9dcbd6c?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c57ab9dcbd6c</guid>
            <category><![CDATA[business-ideas]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Mon, 24 Aug 2026 11:40:04 GMT</pubDate>
            <atom:updated>2026-08-24T11:40:04.450Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every one of these has people actively searching for it. I pulled the numbers so you can stop guessing whether anyone wants the thing before you build it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bOAs0oXaSc-Kgy1RYES0ng@2x.png" /></figure><p>Most side project idea lists are someone’s wishlist dressed up as advice. “Build a habit tracker. Build a CRM for dog walkers.” No evidence anyone wants it, just vibes and a nice-sounding sentence.</p><p>I do this differently. I keep a database that scores real Reddit complaints against real keyword search volume, so before an idea makes any list, it has to clear one bar: are actual people typing the problem into Google every month, and is that number holding or growing? A complaint is an anecdote. A complaint plus search demand is a market.</p><p>Here are nine that cleared the bar. None of them need a team or a funding round. Each one is small enough to be a side project and validated enough to be worth your weekends. The search figures come from <a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=intro">Business Ideas DB</a> keyword data.</p><h3>1. A lead finder that reads Reddit for buying intent</h3><p>Founders keep saying the same thing: their best customers came from a random Reddit thread where someone was openly asking for a tool like theirs. The problem is you cannot sit in forty subreddits all day waiting for that moment. “Reddit marketing” pulls about 9,900 searches a month and is up 34% year over year, which tells you the intent is there and rising. A side project that surfaces “I wish something existed that…” threads in a niche, ranked by how close the person is to buying, is a weekend scraper plus a filter to start. <a href="https://businessideasdb.com/idea/reddit-buying-intent-lead-finder?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=reddit-buying-intent-lead-finder">The full teardown is here.</a></p><h3>2. Proposal and invoicing flow built for one freelancer, not an agency</h3><p>“Freelance invoicing software” gets around 14,000 searches a month. Every serious tool in that space is really built for agencies with an ops person, and solo freelancers keep bouncing off the complexity. The gap is a dead-simple flow: proposal to signature to invoice to paid, nothing else, priced for a person and not a department. <a href="https://businessideasdb.com/idea/solo-proposal-flow?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=solo-proposal-flow">Here’s the breakdown.</a></p><h3>3. A chore board that makes invisible household labor visible</h3><p>The recurring complaint here is not “we need an app,” it is “I do everything and nobody sees it.” A shared kanban board for household tasks turns that resentment into something you can point at. “Household chore app” sits near 18,100 searches a month, up 25%, and the existing options are either childish reward-chart apps or generic to-do lists that ignore the actual dynamic. <a href="https://businessideasdb.com/idea/household-kanban-board?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=household-kanban-board">The idea page is here.</a></p><h3>4. A recipe app that starts from what’s already in your pantry</h3><p>Most cooking apps ask what you want to make. The more common problem is the reverse: you have half a fridge of random ingredients and no plan. Recipe and pantry-recipe terms clear roughly 9,900 searches a month combined. Point a camera or a quick checklist at the pantry, get three things you can actually cook tonight. It is a genuinely useful weekend build with a clear consumer pull. <a href="https://businessideasdb.com/idea/pantry-inventory-recipe-suggester?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=pantry-inventory-recipe-suggester">More detail here.</a></p><h3>5. A daily poetry app, deliberately tiny</h3><p>Not every side project has to solve a business pain. “Poetry app” holds about 12,100 searches a month, up 18%, and this is rated one of the easier builds in the set: a daily poem, an audio reading, a short bit of guided analysis. The point of this one is that it is finishable in a couple of weekends and has a real, quiet audience already looking for it. Small and shippable beats ambitious and abandoned. <a href="https://businessideasdb.com/idea/daily-poetry-app?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=daily-poetry-app">See the page.</a></p><h3>6. A custody calendar built for 50/50 divorced parents</h3><p>This is a narrow, unglamorous, genuinely painful problem, which is exactly why it is a good side project. Co-parenting and custody-calendar terms clear around 8,100 searches a month. Shared calendars like Google’s were not built for two households negotiating handoffs, expenses, and schedule changes without talking to each other. The narrowness is the moat: nobody big wants a market this specific, and the people in it feel the pain every week. <a href="https://businessideasdb.com/idea/shared-custody-calendar-for-divorced-parents?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=shared-custody-calendar-for-divorced-parents">Full context here.</a></p><h3>7. Wikipedia, but built for the rabbit hole</h3><p>“Wikipedia app” holds about 9,900 searches a month and is rated an easy build. The insight is that the best part of Wikipedia, following one link into another until an hour disappears, is an accident of the interface, not a designed experience. A serendipitous discovery app that visualizes the rabbit hole and nudges you deeper is a fun, low-stakes project with an audience that already exists. <a href="https://businessideasdb.com/idea/wikipedia-rabbit-hole?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=wikipedia-rabbit-hole">Here’s the idea.</a></p><h3>8. An execution tool for the AEO era</h3><p>This one is for the indie hacker who wants a project other indie hackers will pay for. “SEO tools” is a giant head term near 18,100 searches a month, but the interesting movement is underneath it: everyone is scrambling to figure out how to get cited by AI answers, not just ranked on Google. A focused tool that helps a small agency actually execute answer-engine optimization, rather than another dashboard, fits into a market that is being rewritten right now. <a href="https://businessideasdb.com/idea/seo-agency-aeo-execution-tool?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=seo-agency-aeo-execution-tool">Read more.</a></p><h3>9. A scheduler that guards date night</h3><p>The highest-demand idea on this list is also one of the softest problems: couples who mean to protect their time together and never do. “Date night ideas” clears roughly 49,500 searches a month. The interesting build is not another list of ideas, it is a scheduler that automatically defends a slot on the calendar and plans it, so the intention survives contact with a busy week. High search volume, low competition, easy to prototype. <a href="https://businessideasdb.com/idea/date-night-scheduler?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=date-night-scheduler">The page is here.</a></p><h3>The thing these nine have in common</h3><p>None of them are clever. That is the point. Each one is a specific problem that a specific group of people are already searching for a fix to, where the existing tools are either too big, too generic, or too expensive for the person actually feeling the pain. That is what a good side project idea looks like: not a novel invention, a known ache with proof that people are hunting for relief.</p><p>If you want the rest of them, with the source threads and search trends side by side, I keep the running list at <a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=side-project-ideas&amp;utm_content=outro">Business Ideas DB</a>. Pick the one whose customers you would actually enjoy spending two years around, and build that one.</p><h3>FAQ</h3><p><strong>What makes a good side project idea?</strong> A problem real people already search for, where the existing tools are built for someone bigger or richer than the person complaining. Validate demand before you build: check whether anyone searches for the fix each month and whether that number is stable or growing. Every idea above was selected on that basis using Business Ideas DB keyword data.</p><p><strong>Where do these side project ideas come from?</strong> From scored Reddit complaints matched against keyword search volume. The complaint proves the pain is real and specific; the search volume proves enough people want it solved to form a market. Business Ideas DB keeps both next to each other so you are not guessing.</p><p><strong>Which of these is the easiest to build first?</strong> The daily poetry app and the Wikipedia rabbit-hole app are rated the lightest lifts, both finishable over a couple of weekends, both with an audience already searching for them. Start with something small enough to finish, since a shipped tiny project beats an abandoned ambitious one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c57ab9dcbd6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Scored 1,416 Reddit Complaints Looking for Business Ideas. Here’s the Map.]]></title>
            <link>https://medium.com/@theomarsoliman/i-scored-1-416-reddit-complaints-looking-for-business-ideas-heres-the-map-749b1bf14b47?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/749b1bf14b47</guid>
            <category><![CDATA[business-ideas]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[reddit]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 10:58:07 GMT</pubDate>
            <atom:updated>2026-08-16T10:58:07.724Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Not the highlights. The whole terrain. What people actually complain about turns out to be far more boring, and far more useful, than any trend piece will tell you.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QPZJc0L_b4CVeesX.jpg" /></figure><p>For about a year I have been running a slightly strange machine. It reads Reddit, finds posts where someone is genuinely frustrated with a task or a tool, and scores each one on how much it looks like a real business hiding inside a complaint. The count is now past fourteen hundred scored posts, and around eighty of them have graduated into fully worked-up ideas with real keyword demand attached.</p><p>Sitting on top of that pile long enough changes how you see the whole question of “what should I build.” You stop looking for the exciting complaint and start seeing the shape of all of them at once. So here is the map, honestly drawn, including the parts that are unglamorous on purpose.</p><h3>The complaints are overwhelmingly about work, not play</h3><p>The first thing the terrain tells you is that people do not complain their way into consumer apps. They complain their way into software for businesses. When the eighty-odd best ideas shook out by category, forty-five of them were straightforward SaaS, tools a business would pay for and expense without a second thought. Apps for consumers were the second cluster, twenty-five of them, and everything else, platforms, services, hardware, was a rounding error.</p><p>That imbalance is not because consumers are happy. It is because consumer frustration tends to be diffuse (“this app is annoying”) while work frustration is specific (“I lose an hour every Friday reconciling these two systems by hand”). Specific is what you can build against. The map is mostly covered in unsexy business software for exactly this reason, and that is the first thing an idea list will never show you, because unsexy does not make a good headline.</p><h3>The same wound appears in a dozen disguises</h3><p>Once you have read enough complaints, the individual posts stop mattering and the patterns start. A handful of wounds show up again and again wearing different costumes.</p><p>One is the solo operator handed a tool built for a company. The plumber, the freelancer, the one-person agency, the landlord with three units, all of them describing the same feeling: the software assumes I have a team I do not have. Another is the invisible recurring chore, the second invoice never sent, the follow-up never chased, the reorder never reminded. A third, and this one genuinely surprised me, is people trying to claw back control from the very technology that was supposed to help them, which is a whole territory of its own that I could write a separate map for.</p><p>The lesson of the repetition is that you are almost never looking at a single idea. You are looking at one underlying human problem that will support five different products aimed at five different niches. Find the wound, then pick the disguise nobody has dressed yet.</p><h3>Search demand is the border between a complaint and a market</h3><p>The uncomfortable truth the map enforces is that most complaints, even loud and upvoted ones, lead nowhere. A thread can have thousands of upvotes and still be a dead end, because agreement that something is annoying is not the same as demand for a paid fix.</p><p>The line I draw is search volume. If people are typing the problem into Google every month, and especially if that number is climbing, the complaint has crossed from anecdote into market. If nobody is searching, the pain is real but not expensive enough to fund a business, and I let the idea die there. Roughly speaking, for every complaint that survives into a real idea, a dozen loud ones get buried at this border. That filter is the single most valuable part of the whole machine, and it is the part most idea lists skip entirely.</p><h3>What the map is missing is not ideas</h3><p>Here is the conclusion that reframed my own building. After a year of this, I am not short on ideas. Nobody is. The validated-idea layer is enormous and gets bigger every week the machine runs. If ideas were the constraint, the map would be a treasure. It is not a treasure. It is a reminder.</p><p>Because every one of those eighty ideas is still just a complaint with a number attached. Not one of them is a business yet. The distance between “here is a validated idea with real search demand” and “here is a company someone pays” is not crossed by having a better map. It is crossed by the deeply boring work of picking one, showing up for the same customers over and over, and doing it for far longer than feels reasonable. The map makes the first ten percent trivial and does nothing for the other ninety.</p><h3>What to actually do with a map like this</h3><p>If you take one thing from a year of scored complaints, let it be this: stop treasure-hunting for the perfect secret idea. That layer is bottomless and nearly free. Instead, use a map like this to do the one thing it is genuinely good for, which is to find a real wound, confirm real people are searching for relief, and pick the specific underserved version of it whose customers you would not mind spending the next two years around.</p><p>Then close the map and go do the unglamorous part, because that is the only part that was ever scarce.</p><p>I keep the full, running terrain, the ideas, the search trends, and the businesses already earning in these spaces, at <a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=reddit-complaints-map&amp;utm_content=outro">Business Ideas DB</a>. Browse it as a map, not a menu. The value was never in any single pin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bOAs0oXaSc-Kgy1RYES0ng@2x.png" /><figcaption><a href="https://businessideasdb.com/">Business Ideas DB</a></figcaption></figure><h3>FAQ</h3><p><strong>How do you turn Reddit complaints into business ideas?</strong> Read for the repeated chore, not the rant, then confirm the fix has real monthly search demand before treating it as a market. Across 1,416 scored complaints, only around eighty survived that filter into worked-up ideas. Business Ideas DB keeps the complaint and the search volume side by side so the border between anecdote and market is visible.</p><p><strong>What kinds of business ideas show up most in Reddit complaints?</strong> Overwhelmingly business software, not consumer apps, because work frustration is specific enough to build against while consumer frustration is diffuse. The most common patterns are the solo operator handed a tool built for a team, the invisible recurring chore, and people trying to reclaim control from their own technology.</p><p><strong>Are Reddit business ideas actually worth building?</strong> Only the ones with search demand behind them. A highly upvoted complaint proves the pain is real, not that anyone will pay to fix it. The demand number is what separates a fundable idea from a popular dead end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=749b1bf14b47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everyone’s Trying to Quit Their Phone. The Apps Meant to Help Barely Exist.]]></title>
            <link>https://medium.com/@theomarsoliman/everyones-trying-to-quit-their-phone-the-apps-meant-to-help-barely-exist-2e933badb004?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e933badb004</guid>
            <category><![CDATA[app-idea]]></category>
            <category><![CDATA[business-ideas]]></category>
            <category><![CDATA[phone-addiction]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Thu, 06 Aug 2026 12:00:59 GMT</pubDate>
            <atom:updated>2026-08-06T12:00:59.750Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The single most consistent cluster of demand in my whole database is people trying to undo what technology did to them. Almost nobody is building for it properly.</em></p><p>If you had asked me a year ago to guess the most crowded, most obvious category in consumer software, I would have said digital wellbeing. Screen time, focus, “quit your phone.” It feels done to death. Every phone ships with a built-in screen-time dashboard nobody looks at, and there are a hundred grayscale-your-screen apps in the store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywThLHz6B_ogl-LAX-mI8w@2x.png" /><figcaption>Source <a href="http://businessideasdb.com/">businessideasdb</a></figcaption></figure><p>Then I actually looked at the demand data, and it turns out the category only feels crowded. What exists is a graveyard of guilt-trip dashboards. What people are searching for is help, and the gap between those two things is one of the widest I have found anywhere.</p><h3>The demand is enormous and it is climbing</h3><p>I keep a database that pairs real complaints with real search volume, and when I pull the cluster of people trying to claw back control from their own devices and habits, the numbers are hard to ignore. “Screen time app” clears around 40,500 searches a month and is up 32% year over year. “Phone addiction app” sits near 22,000 and is climbing 42%. “Gaming addiction” pulls about 27,100 and is up 40%. “Gambling addiction app” is near 14,800, up 35%. Even the emotional aftermath has a market: “breakup app,” about people trying to erase a digital trace of an ex, is at 22,200 and rising 45%.</p><p>Add that cluster up and it is a very large, very fast-growing wave of people typing some version of “please help me stop” into a search bar every single month. That is not a niche. That is a cultural reckoning showing up as search volume.</p><h3>What exists is measurement, not recovery</h3><p>Here is the disconnect. The tools that exist mostly measure the problem back to you. They show you a bar chart of how many hours you lost, slap a weekly notification on it, and call that a product. It is the digital equivalent of a scale that beeps at you. Measurement is not treatment, and deep down everyone reaching for these tools already knows exactly how bad it is. They did not search for a mirror.</p><p>The interesting ideas in the data go the other direction, toward actual behavior change instead of another dashboard. A <a href="https://businessideasdb.com/idea/friend-focus-phone-lock?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=quit-your-phone-apps&amp;utm_content=friend-focus-phone-lock">phone-locking tool built around friends and shared focus sessions</a> treats the problem as social rather than solitary, because willpower alone loses and accountability to a person works. A <a href="https://businessideasdb.com/idea/smartphone-addiction-recovery?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=quit-your-phone-apps&amp;utm_content=smartphone-addiction-recovery">smartphone recovery app built around intentional-use training</a> tries to rebuild the habit rather than just blocking it. These are structurally different from a screen-time chart, and the demand under them is both larger and growing faster than the tired category label suggests.</p><h3>The harder-edged corners nobody wants to touch</h3><p>The clearest opportunities in this cluster are also the least fun to talk about at a party, which is precisely why they are open. Gaming addiction, gambling addiction, the compulsive behaviors that graduated from bad habit to something closer to a disorder. The search volume is right there, growing double digits, and the existing options are a mix of clinical, expensive, and stigmatizing on one side and useless novelty apps on the other.</p><p>A <a href="https://businessideasdb.com/idea/gaming-addiction-recovery?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=quit-your-phone-apps&amp;utm_content=gaming-addiction-recovery">gaming addiction recovery tool that swaps in real-life achievement systems</a> or a <a href="https://businessideasdb.com/idea/gambling-addiction-recovery?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=quit-your-phone-apps&amp;utm_content=gambling-addiction-recovery">gambling recovery app that combines urge-blocking with actual financial repair</a> are not comfortable pitch-deck ideas. They are also aimed at people in real pain who are actively searching for help and finding almost nothing built with care. Discomfort is a moat. The categories that make founders squeamish are the ones with the least competition and the most gratitude waiting on the other side.</p><h3>The honest caution</h3><p>I want to be careful here, because this is the one cluster where “just ship an MVP” is the wrong instinct. Building for people in genuine compulsive distress carries a responsibility that a to-do app does not. If you go here, you go in seriously: real behavioral science, real care about not becoming one more manipulative loop dressed up as help, ideally real clinical input for the hard-edged corners.</p><p>But that responsibility is exactly the barrier keeping the category empty despite the roaring demand. Most builders want the easy consumer app. The people who are willing to take a hard, uncomfortable, high-responsibility problem seriously will find a very large audience that the dashboard-makers left completely unserved.</p><h3>What to do with this</h3><p>The lesson generalizes past phones. When a category feels crowded, check whether it is crowded with real solutions or just crowded with measurement. Digital wellbeing looked done and was actually barely started, because everyone built the mirror and nobody built the recovery. Look for the demand that is large, growing, and slightly uncomfortable to serve, then build the thing people were actually asking for instead of the thing that was easy to ship.</p><p>I keep this whole cluster, the search demand and the specific unbuilt angles, at <a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=quit-your-phone-apps&amp;utm_content=outro">Business Ideas DB</a>. The wave is real and rising. Almost nobody is surfing it properly yet.</p><h3>FAQ</h3><p><strong>Is there real demand for phone and screen-time addiction apps?</strong> Yes, and it is growing fast. “Screen time app” clears around 40,500 searches a month up 32% year over year, “phone addiction app” near 22,000 up 42%, with related gaming and gambling recovery terms up 40% and 35%. The category feels crowded but is mostly full of measurement dashboards, not tools that change behavior.</p><p><strong>Why is digital wellbeing an underserved category if so many apps exist?</strong> Because most existing apps measure the problem rather than treat it. They show you how many hours you lost instead of helping you change the habit. The demand data points toward accountability-based, behavior-change, and recovery tools, which are structurally different from another screen-time chart and far less crowded.</p><p><strong>What are the biggest opportunities in digital addiction recovery?</strong> The uncomfortable corners with the least competition: gaming addiction, gambling addiction, and compulsive-use recovery, all showing double-digit search growth. They demand real behavioral science and responsibility, which is exactly why they remain open while builders chase easier consumer apps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e933badb004" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Long Does It Take to Reach $10K MRR? Longer Than Anyone Tells You.]]></title>
            <link>https://medium.com/@theomarsoliman/how-long-does-it-take-to-reach-10k-mrr-longer-than-anyone-tells-you-d43cc583e78d?source=rss-f463622e5a7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d43cc583e78d</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[microsaas]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Omar Soliman]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 11:05:00 GMT</pubDate>
            <atom:updated>2026-08-04T11:05:00.731Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I checked 787 businesses with payment-processor-verified revenue against their founding dates. One in ten make it inside a year.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/0*xaxVAv00R7nfyKwO" /></figure><p>There is a genre of post that has quietly done more damage to indie founders than any amount of bad technical advice, and it goes like this: <em>“How I got to $10K MRR in four months.”</em></p><p>I have read a hundred of them. I have believed most of them. What none of them tell you is what the denominator looks like, because the person writing is, by definition, the one it worked for. You never read the post from the other four thousand.</p><p>So I went and looked at the denominator.</p><p>One of the datasets behind Business Ideas DB is a set of businesses whose revenue is verified through their payment processor via TrustMRR rather than self-reported, and 787 of them also carry a founding date. That combination lets you ask a question the success posts cannot answer: out of everyone who started, how many got there, and how long did it take.</p><h3>The curve</h3><p>Grouped by how long the business has existed:</p><p><strong>Under 1 year</strong> (273 businesses) | Average MRR: <strong>$4,801</strong> | Reached $10K: <strong>10%</strong></p><p><strong>1 to 2 years</strong> (235 businesses) | Average MRR: <strong>$6,965</strong> | Reached $10K: <strong>17%</strong></p><p><strong>2 to 4 years</strong> (163 businesses) | Average MRR: <strong>$31,781</strong> | Reached $10K: <strong>24%</strong></p><p><strong>4 to 7 years</strong> (76 businesses) | Average MRR: <strong>$18,850</strong> | Reached $10K: <strong>29%</strong></p><p><strong>7 years and over</strong> (40 businesses) | Average MRR: <strong>$24,349</strong> | Reached $10K: <strong>40%</strong></p><p>One in ten inside the first year.</p><p>Not one in three. Not “most of the good ones.” One in ten, and that is among businesses that got far enough to have verified revenue at all, which already excludes everything that died before it processed a payment. The real first-year number, measured against everyone who starts, is worse than this table can show.</p><p>Then look at the far end. Seven years in, still only forty percent. Six out of ten businesses that have survived seven years have not reached ten thousand dollars a month.</p><h3>The part that should change your planning</h3><p>The jump is not where people expect it.</p><p>Between year one and year two, the share reaching $10K moves from 10% to 17%. That is real but modest. The average revenue barely moves, from $4,801 to $6,965.</p><p>Then between year two and year four, average MRR goes from $6,965 to $31,781. That is where the curve actually bends, and it is a long way further out than the four-month success post implies.</p><p>Which means the dangerous period is not the beginning. Everyone expects the beginning to be hard and plans for it. The dangerous period is month fourteen to month thirty, when the novelty is gone, the launch traffic is gone, and the numbers are moving slowly enough that quitting looks like the rational, adult decision rather than a failure of nerve.</p><p>Most people quit there. The data says that is roughly where it starts working.</p><h3>What I am not claiming</h3><p>I want to be careful, because this is exactly the kind of table people screenshot without the caveats.</p><p>This is a survivorship-shaped sample. Every business in it is alive enough to have verified revenue. The ones that quit in month eight are not here, so the real odds are worse, not better.</p><p>It is also skewed young. There are 273 businesses under a year old in this set and only 40 over seven years. Newer businesses are wildly overrepresented, which drags the averages down at the young end and makes the older cohorts a small sample. Forty businesses is not a lot to hang a percentage on.</p><p>And “reached $10K” is measured at today, not at their peak. Some of these were higher once.</p><p>None of that changes the shape. It just means treat the numbers as directional rather than precise.</p><h3>Why this is good news, mostly</h3><p>If you are eleven months in and doing $2,000 a month, the useful thing to know is that you are not behind. You are normal. The average business under a year old in this verified set is doing $4,801, and 90% of them have not hit $10K either.</p><p>That reframing matters more than it sounds, because the main thing that kills small software businesses is not competition or a bad idea. Across everything I have looked at building Business Ideas DB, the most common cause of death is a founder deciding they have failed on a timeline they got from a blog post written by an outlier.</p><p>The businesses that make it are, overwhelmingly, the ones that were still there in year three. Not the fastest. The ones that did not stop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFkPLNWi73-aBGfzoG3LvA@2x.png" /></figure><p>You can see the underlying set on the <a href="https://businessideasdb.com/proven?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=time-to-10k&amp;utm_content=proven">verified revenue pages</a>, where every figure comes from a payment processor rather than a founder’s memory. <a href="https://businessideasdb.com/proven/stan?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=time-to-10k&amp;utm_content=stan">Stan</a> is the extreme end of what is possible, at $3.5 million a month, founded in 2023. It is also one business out of 787, and treating it as the template is how people end up disappointed on a schedule.</p><h3>The honest version of the advice</h3><p>Pick something you are willing to still be working on in two years, because two years is roughly when the interesting part starts.</p><p>That single filter would kill most of the ideas people begin with, which is the point. If the idea only survives contact with a four-month timeline, it was not going to survive at all.</p><p>Everyone optimises for the launch. Almost nobody plans for month twenty, and month twenty is where the businesses in this table were made.</p><p><em>Revenue verified through payment processors via TrustMRR. Demand and idea data from </em><a href="https://businessideasdb.com/ideas?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=time-to-10k&amp;utm_content=outro"><em>Business Ideas DB</em></a><em>, where ideas are scored against real Reddit complaints and real search volume.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d43cc583e78d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>