← All founder workflows

How to tell whether your internal tool is actually a product

Turn an internal tool into a product by selling it to three companies that are not like yours. A tool built for your own workflow is validated for exactly one customer — you — and the usual failure is discovering that everyone else's process differs in the specific place your tool assumes. Charge from the first external user, watch how much configuration each one needs, and check ownership of the code before you sell anything. Three paying strangers, each needing under a day of setup, is a product.

30 days $0 to run6 stepsUpdated 2026

The workflow

0/6 done

  1. If it was built at a job, on company time, or with company resources, the employer may own it — and this conversation is far cheaper before revenue than after. Get written permission or rebuild it cleanly on your own time and equipment. Founders who skip this step build a business on an asset someone else has a claim to.

  2. Your naming conventions, your stack, your team size, your tax jurisdiction, the fact that one person does two roles. Each assumption is a customer you cannot serve without changes. Writing the list takes an hour and usually reveals that the tool is far more specific to you than it felt — which is normal, and fixable, but only if you know it.

  3. Not your friends and not companies in your exact situation. Charge a real price from the first one. Three external customers is enough to see whether the assumptions hold, and paying customers complain honestly in a way that free pilot users never do — free users tolerate friction and then quietly stop.

    Competitor research
    Input
    Internal tool that generates client-ready reports from project management data
    What comes back
    12 reporting tools exist at $19–$200/mo, all requiring a specific project-management platform. Agency forums repeatedly complain about rebuilding the same report each month across two systems. Multi-source is the wedge — and it is also the assumption your internal version quietly makes, since you use one system.

    What this step looks like when it is done properly — the free Idea Validator covers the same ground as part of its research.

  4. Track the hours each new customer takes to get working. If customer three needs three days of your time, you have a consultancy, and the economics of a subscription will not support it. The setup hours are the single most reliable indicator of whether an internal tool can become a product a small team can sell repeatedly.

  5. If setup collapses toward hours, build the product. If it stays high but customers pay well, sell it as a service with software attached — a perfectly good business. If neither works but the tool is genuinely useful, open sourcing it builds reputation and costs you a maintenance burden you should enter knowingly.

    Runway CalculatorFull tool
    Input
    3 external customers at $89/mo, average 11 hours setup each, founder rate equivalent $70/hr
    What comes back
    $770 of setup labour against $267/mo revenue — each customer takes nearly 3 months to repay onboarding before any profit. Either cut setup below 3 hours or charge a $600 onboarding fee. As it stands, growth makes the cash position worse, not better.

    Run it yourself — free, no signup:

    8%
    Runway
    5+ years
    Cash never reaches zero inside five years: you break even at month 12 and it climbs from there. That holds exactly as long as the growth rate does.
    Break-even month
    Month 12
    The month the borrowing stops. Worth more attention than the runway number.
    What cash ÷ burn would tell you
    12 months
    It says 12 months, because it assumes your MRR never moves. That assumption is the entire difference between running out next year and not running out.

    Under six months: cut, because you need a certain effect fast. Above twelve: grow, because growth compounds and cutting caps your ceiling. The founders who get this wrong grow when they should cut — growing feels like progress.

  6. The tool stays honest as long as you depend on it. Products spun out of internal tools decay when the founder stops using them daily, because the feedback loop that made the tool good in the first place was your own frustration — and no roadmap replaces it.

Questions founders ask about this

Is an internal tool a good basis for a product?
It is a strong start with a specific trap: it is validated for exactly one company. The tool usually encodes assumptions about your process, and those assumptions are where external customers get stuck.
Who owns a tool I built at work?
Often your employer, depending on your contract and whether you used company time or equipment. Settle it in writing before you sell anything — the conversation gets much harder once there is revenue.
How many external customers prove an internal tool is a product?
Three that are meaningfully different from your own company, each paying and each needing under a day of setup. Setup time is the number that separates a product from a consultancy.
What if every customer needs customisation?
Then it is a service with software attached, which is a legitimate business but a different one. Price it accordingly, with an onboarding fee, rather than pretending the subscription covers the work.
Should I open source my internal tool instead?
It is a reasonable option when the tool is useful but not sellable, and it builds reputation and distribution. Go in knowing that maintenance is a real ongoing cost.

Next, founders usually do this

The tools used above have their own pages — MRR & Runway Calculator — and the SOP SOP: Get your runway and burn under control runs the same ground in more depth. Also worth reading: the Nine Lives Doctrine, and real verdicts from ideas kitty has run this workflow on.

kitty.build runs this entire workflow for you

Every step above — the research, the competitor read, the numbers, the honest verdict — is what nine specialist AI boards do automatically when you feed her an idea. She will tell you to kill it if it deserves killing. First idea is free.

Feed her an idea — free

No card · Failed tasks are free · Your repo, your domain, your revenue