TL;DR
Building a product from an internal tool sounds appealing, but it requires a second business operating in parallel with your first. Before committing, answer the pricing, support cost, and opportunity cost questions honestly.
You built a tool to solve a problem in your own business. It works. Other business owners in your network start asking about it. Someone offers to pay for access. Suddenly you are wondering whether you are sitting on a product business inside your service business.
Sometimes that is exactly right. Often it is a very expensive distraction. Here is how to tell the difference before you commit.
What Owners Get Wrong
The first mistake is assuming that because the tool is useful to you, it is ready to sell to someone else. Internal tools are built for a specific context, a specific team, and a specific level of technical tolerance. The person who built it can work around its gaps. A paying customer cannot. The gap between "works for us" and "ready to sell" is usually six to twelve months of engineering work and a support structure you do not have yet.
The second mistake is treating interest as demand. When peers ask how something works, they are curious. Curiosity is not a purchase intent signal. Before you invest in productizing anything, you need people who have agreed to pay and ideally have paid already, even in a beta or pilot form.
The third mistake is underestimating what a product business actually requires. Pricing, billing infrastructure, onboarding, documentation, bug fixes, feature requests, customer support, uptime guarantees. These are not side tasks. They are a second business operating in parallel with your first one.
The CFO Perspective
The financial question I ask first is: what is the margin on your core service business right now? If a service business is running at 60 percent gross margin and the owner wants to productize a tool, I want to know whether the product can reach a similar margin, and how long it will take.
Most early-stage software products run at high gross margins eventually, but they require significant upfront investment to get there. Customer acquisition, integration work, and support load in the early days often mean the product runs at a loss while the service business is subsidizing it.
A business owner I worked with had built a client reporting tool for their consulting firm. It was genuinely good. Three of their peers had asked about licensing it. We walked through the numbers. The tool needed two months of engineering work to be stable enough for external use. Support would take roughly four hours per week per customer at the start. Pricing at $300 per month per seat meant they needed 15 customers just to cover the support and maintenance time at any reasonable cost of that time. Getting to 15 paying customers in a niche B2B tool with no distribution was a 12 to 18 month project, minimum.
None of that made it a bad idea. It made it a real business decision, not a side project.
Questions to Answer Before You Start
Who Is the Actual Customer?
Your network asking about a tool is not a customer profile. Write down: industry, company size, the specific pain the tool solves, how they would find you, and how they buy software today. If you cannot answer all of those, your market is not defined yet.
What Would You Charge and Why?
Tool pricing is almost always wrong on the first attempt. Founders undercharge because they know how cheap the tool was to build. But customers care about value, not your cost. Map the value the tool creates for a customer, then price to a fraction of that value. Then ask: how many customers at that price to make this worth the time investment?
What Does It Cost to Support One Customer?
Before you have customers, estimate this honestly. Time to onboard. Average support tickets per month and time per ticket. Infrastructure cost per customer. If the support cost per customer is more than 30 percent of the monthly revenue per customer, the economics are going to be painful as you scale.
What Breaks in Your Core Business if You Do This?
This is the question most founders skip. Productizing a tool takes owner time and attention away from the business that currently pays the bills. If your service business requires your direct involvement to run well, splitting your focus will hurt revenue before the product starts contributing. Model that gap explicitly before you decide.
What to Do About It
- Get five paid commitments before writing a line of code for external use. Not letters of intent. Not enthusiastic conversations. People who have put money down, even $500 for a pilot seat. Real demand, not social proof.
- Build a one-page financial model. Assume 18 months to reach 20 customers. Estimate your time cost at your service billing rate. Add infrastructure and support costs. Calculate what the product needs to earn to justify pulling you away from your core business.
- Set a time budget. Decide in advance how many hours per week you will spend on the product without it affecting your service revenue. Hold that boundary strictly for the first six months.
- Price higher than feels comfortable. Early customers in a niche B2B product are buying access to you and your expertise as much as the tool itself. Price accordingly. You can always lower. You almost never can raise.
- Define your kill criteria upfront. At what point, with what metrics, will you decide this is not worth continuing? Write it down before you start. Sunk-cost bias makes this impossible to assess clearly once you are inside it.
Turning an internal tool into a product can be genuinely valuable. But it is a business decision that deserves the same financial scrutiny as any other major investment of your time and money.
If you want help modeling whether a product idea makes financial sense for your business, book a free call at peterxiacpa.com/book.
Next step: run your numbers through the free CFO scorecard.
Frequently Asked Questions
- How do I know if there is real demand for my internal tool?
- Curiosity from peers is not demand. Real demand is people agreeing to pay, even a small pilot amount, before you invest in making the tool production-ready. Aim for five paid commitments before building for external use.
- What is a reasonable support cost target for a software product?
- A rough rule: support cost per customer should stay below 30 percent of monthly revenue per customer. Above that, the economics become painful as you scale because every new customer adds a disproportionate cost burden.
- Should I price my tool based on what it cost me to build?
- No. Build cost is irrelevant to customers. Price based on the value the tool creates for them, then charge a fraction of that value. Early B2B customers are also paying for your expertise and support, so price higher than feels comfortable.
Get weekly CFO insights
No fluff. Real finance strategy for Canadian business owners. Unsubscribe any time.
Related Articles
Should Recurring Subscription Revenue Be Forecast Differently Than One-Off Sales?
Subscription revenue and one-off project or product sales have different risk profiles and need separate forecasting logic. Blending them into a single revenue line hides churn risk, obscures pipeline problems, and produces a forecast with false precision.
4 min readHow Much Detail Does a Budget Actually Need? Avoiding Over-Engineering
Over-engineered budgets with dozens of line items feel rigorous but rarely survive past the first quarter. The right level of detail is enough to surface the decisions that matter, which for most small businesses means 15 to 20 lines, not 80.
4 min readWhy Your Receivables Spike at Month-End and How to Smooth Out Invoicing
Batching all your invoices at month-end is the most common reason receivables spike and cash flow feels unpredictable. Spreading invoicing across the month flattens your AR, speeds up perceived collections, and makes cash flow much easier to forecast.
4 min readNeed financial strategy for your business? Explore our CFO services or book a call.
