You Built a Tool. You're Sitting on a Product.

Every few months I watch the same thing happen. A company hits a wall — some specific problem their software refuses to handle. The ERP won't track the thing they need tracked. The reporting is built for a business that works nothing like theirs. They go looking for a tool that fits, and the tool doesn't exist. The market either never noticed the problem, or noticed it and decided it wasn't worth solving.

So they come to me and we build the fix. A few weeks or a few months later they have exactly what they needed — custom software that does the one thing the whole market couldn't do for them. And that's usually where the story ends, filed under "operating expense, paid, done."

That's the moment I tend to say something they don't expect. The tool you just paid me to build? You can sell it.

Two ways to deal with a gap

When a business runs into a problem its software can't handle, there are really only two ways out. The first is to bend the business around the tool — change your process, drop the step that doesn't fit, tell your staff "the software doesn't do that, so we don't do that anymore." Quietly, this is what most companies choose, because it costs nothing upfront. It just costs you every day after.

The second is to keep your process intact and build the missing piece. You decide that how you work is a competitive advantage worth protecting, and you pay to make the software match the business instead of the other way around. The companies that end up in my inbox almost always picked this one. They already refused to be flattened into whatever their vendor imagined.

Here's the part they miss. If your process is good enough to defend, and the problem was real enough to pay to solve, the odds that you're the only company in your entire field facing it are basically zero.

The problem you solved for yourself is rarely yours alone. Someone across the street is losing sleep over the exact same thing.

"We're not a software company"

The response is almost always the same two sentences, delivered in the same order. "We're not a software company. And we're not going to help our competitors."

I understand the reflex. It feels like handing your rivals the key to something you fought to build. But look closely at what's actually being said, because both halves fall apart the moment you push on them.

Start with the second one — the fear of helping competitors. You are picturing a competitor who gains your exact advantage by buying your tool. That's not how it works. You've been running this process for years; the software is the last five percent, the part that got written down. The other ninety-five percent — the judgment, the relationships, the reasons behind every decision the tool encodes — doesn't transfer with a license. And realistically, your competitor already has some version of the same headache and is either suffering through it or about to pay someone to solve it badly. You're not arming them. You're selling them aspirin they were going to buy anyway.

Neither was anyone else

Now the first sentence: "we're not a software company." True. But that's a description of your past, not a rule about your future.

Almost none of the software companies you can name started as software companies. They started as a business with a problem, built an internal tool to survive it, and then noticed everyone around them had the same problem. Amazon built its infrastructure to run a bookstore and turned it into AWS, which now prints more profit than the store ever did. Shopify was a snowboard shop that couldn't find e-commerce software it liked. Basecamp was a project-management tool a design agency built to manage its own projects. None of them woke up one day as "a software company." They backed into it because they had already solved something real, and solving it once turned out to be the expensive part.

You don't become a software company by declaring yourself one. You become one the moment you have a working tool and a second buyer. The first buyer was you.

What you actually get

Set the fear aside and look at what's genuinely on the table. This isn't a fantasy about becoming a tech unicorn. It's a short list of concrete, boring, valuable outcomes.

• You get your investment back. That custom software was a cost the day you paid for it. The first external sale flips it into an asset. Sell it three or four times and the tool that was an expense is now paying for itself and then some.
• You turn competitors into a relationship. A competitor who buys your software is no longer purely a rival — they're a customer, a reference, sometimes a partner. In a small market like Lebanon, where everyone in an industry knows everyone else, that shift is worth more than the license fee.
• You get authority. The company that solved the problem everyone else is still fighting becomes the name people associate with that problem. That reputation feeds back into your original business in ways a marketing budget can't buy.
• You get a second revenue line that doesn't compete with the first. Software revenue behaves nothing like your core business. It's recurring, it scales without proportional cost, and it keeps earning while you sleep. You built it once — every sale after that is close to pure margin.

And to be honest about my own seat at this table: I'm the one who built the tool, so of course I'd like to keep building on it. But I say this to clients who have no intention of ever hiring me again, because the logic holds without me. The value is sitting there whether I'm involved or not.

Not every tool is a product

Here's where I'll pump the brakes, because "you're sitting on a product" is a thrilling sentence and thrilling sentences get people into trouble.

A tool becomes a product when the problem is general and the solution travels. A tool stays a tool when it's so tangled in your specific setup that nobody else could run it without rebuilding half of it. The difference is everything, and it's an honest question you have to answer before you get excited.

There's also a real distance between "custom software that works for us" and "product other people can buy." Someone else's data, someone else's edge cases, onboarding, support, a price, a way for them to find you. That gap is exactly the work I wrote about in Everyone Has a Product Now. Nobody Has a Customer. — building the thing was never the hard part. But you're starting from a place most would-be founders would kill for: a product that already has one paying customer who bet real money it would work. That's you. You've already done the part everyone else is guessing at.

This is, more or less, the exact path that produced Stokka. Three different business owners kept asking me for the same inventory tool. For a long time I kept pointing them elsewhere. On the third ask I stopped — because a problem three strangers describe the same way isn't a custom job anymore. It's a product waiting for someone to name it.