How We Built KeySolved: Turning a Locksmith Audience Into a Co-Owned SaaS in 21 Days

Picture the call every auto locksmith dreads. All keys lost. A stranded customer, a car that won't open, and about twenty minutes to fix it before patience runs out.

Now the hard part. Which transponder chip does this car use? Which programming method? Will your tool even talk to it, and on which firmware? The answer is scattered across a manufacturer PDF that's three updates out of date, a Facebook thread from 2019, and a forum post that's now locked. Guess wrong and the job's dead — sometimes the car is too.

Alex Welsh had watched locksmiths hit that wall for years. He runs The Locksmith Mentor, an education business that has spent years teaching people this trade. He knew the exact question they kept asking, because they asked him every single day. He had the audience and the answer in his head. What he didn't have was the product.

Twenty-one days after our first call, KeySolved was live and taking payments.

The short version

• **KeySolved** is a subscription reference app for auto locksmiths: search a car (or paste a numberplate) and get the chip, the programming method, the right tools and the field tips — on your phone, on the job.
• It went from a **kickoff call to a live, billing product in 21 days** — a real production SaaS, with logins, payments and an official UK vehicle lookup, not a prototype.
• **Alex brought the audience and the know-how. We built and run the product.** It's co-owned 50/50, with no money upfront and a fully transparent Stripe both sides can see.
• Alex announced it to his email list and **signups landed the same day**. Within weeks there were **paying subscribers across 7+ countries**.
• The lesson for any creator: the product was hiding in the one question his audience kept asking. Yours probably is too.

What is KeySolved?

KeySolved is the single reference an auto locksmith needs to do a job, built to work on a phone in a van. You search by make, model and year — or paste in a UK numberplate and the vehicle comes back from official government vehicle records in about a second.

The page for each car tells you the things that decide whether you finish the job: the transponder chip (the little electronic key inside the fob), the programming method, the skill level, the security-code workflow, and exactly which Autel, Xhorse, OBDSTAR or Lonsdor tools will work — including the firmware quirks the tool makers don't mention. It shows where the OBD port is with an illustration, and the field tips other working locksmiths have added and voted up.

It works offline, because vans don't always have signal. And every entry is checked before it goes live. It isn't a forum guess or a screenshot — it's the reference the trade had been waiting years for, in one place.

The product was hiding in one repeated question

Here's the part that matters if you have an audience of your own.

Alex didn't invent a product out of thin air. He noticed that every locksmith he taught was stuck on the same problem — scattered, unreliable, out-of-date information — and that nobody had built the thing they actually needed. The product was sitting inside the single question his audience asked him most: which key, which tool, for which car?

That's the test. Not "what could I sell them?" but "what do they keep asking me, over and over, that's painful to get wrong?" A repeated, painful, specific question is the seed of a product. A vague interest isn't.

Alex had years of evidence. The same questions in the comments. The same problems in his course. The same frustration in the Facebook groups. When the demand is that obvious and that repetitive, you're not guessing any more — you're just building the answer.

Why the audience mattered more than the code

I can build software fast. That's not the rare part any more. The rare part — the thing almost nobody has — is a warm audience that trusts you and is waiting for you to point them somewhere useful.

Alex had spent years building that: an audience of locksmiths who'd learned the trade from him, watched his videos and bought his courses. That trust is the asset. It's also the thing money can't easily buy — you can pay for ads, but you can't pay for "this person taught me my trade, so I'll listen."

This is the gap I keep writing about: creators and service businesses are sitting on distribution they can't fully spend. They have the audience; they don't have a product to sell it. KeySolved closed that gap. Alex brought the distribution and the domain knowledge. I brought the build. Neither half works alone — an audience with nothing to buy is wasted, and a brilliant product with no distribution dies quietly. Put them together and you get a business.

That's the whole idea behind building a product with me: you bring the audience, I build and run the product, and we own it together.

How we built it in 21 days

The natural worry is: surely something built that fast is held together with tape? It isn't, and here's how the three weeks went.

Week one — the whole app, on fake data. I built the entire interface first, mobile-first, running on mocked data before any real backend existed. You can click through the whole product and feel it long before it's "real." Alex and I locked the brand and — after arguing about the name for 48 hours — landed on KeySolved on the same morning, independently. He emailed: "You already got it, could be a sign."

Week two — the real engine. Logins, the database, and Stripe billing with a special founding-member tier. The unglamorous, important plumbing that makes software safe to take money through.

Week three — launch. The numberplate lookup wired into official UK vehicle data, offline support so it works in a dead-signal car park, AI-generated diagrams showing where each OBD port lives, and a way for locksmiths to plug KeySolved straight into AI tools like Claude.

Three weeks, kickoff to a live product taking payments. If you want the general version of this, here's what really happens in a 30-day build, week by week.

What "co-owned" really means

No upfront cost. I don't invoice Alex for the build. Instead we own KeySolved together and split what it makes after costs, 50/50.

That only works if it's honest, so it's fully transparent: we both see the same Stripe dashboard, the same numbers, the same revenue, in real time. Nobody's guessing what the other side is earning. There's a plain-English heads of terms that sets out who owns what and how payouts work — no 40-page contract, no lawyers needed to understand it.

The deal is simple on purpose: my incentive and Alex's are the same. I only do well if the product does well, which means I'm not building it and walking away — I'm running it for the long haul. The full mechanics live on the partner page, including a calculator that shows what an audience your size could realistically be worth.

Day one — and why launch isn't the finish line

Alex announced KeySolved to his email list. Signups started landing the same day. The first honest customer feedback arrived the day after — exactly the loop you want, because real users tell you what to build next far better than any plan does.

Within weeks there were paying subscribers across seven-plus countries — the UK, US, France, Spain, Denmark, Mexico and Cameroon — on two tiers: a $19/month standard plan and a permanently-locked $9/month founding cohort capped at the first 100 members. A weekly newsletter goes out, drafted automatically and checked by hand. And the catalogue grows every week, because requests from real subscribers go straight into the queue.

Here's the thing I'd tell any creator: the product isn't the moment you launch it. It's the year that follows. Launch is day one of the real work — and it's far easier when there's an engaged audience feeding you what to build.

In Alex's words:

> "For years I have wanted to do this and now it's a reality so thank you. I'm really looking forward to promoting it and you have my word that I'll be making this my main priority."

That last line is the quiet secret of the whole model. When someone co-owns the thing, they market it like they own it — because they do. (We saw the same pattern building FounderOS with a creator, from zero to £8K MRR in month one.)

Could there be a KeySolved in your audience?

Probably — if three things are true.

You have an engaged audience, not just a big one. A few thousand people who trust you beats a hundred thousand who half-remember following you. Engagement is the signal; follower count is vanity.

There's a repeated, painful question they keep bringing you — something specific they'd happily pay to stop getting wrong. That's the product, hiding in plain sight.

And you're willing to market it. This isn't a side project that runs itself. The audience is the engine, and you're the one who turns the key.

If that sounds like you, that's the whole basis of working together. You bring the audience; I build the product and run it; we own it 50/50, transparently, with nothing upfront.

FAQ

How long did KeySolved take to build? Twenty-one days, from our first kickoff call to a live product taking payments. That included logins, billing, an official UK numberplate lookup and offline support — a real production app, not a clickable demo. Most builds run to around 30 days; KeySolved was quick because the scope was sharp and the audience was ready.

Did Alex need to be technical to build it? No. Alex doesn't write code. He brought two things that mattered far more: an audience that trusted him, and deep knowledge of the problem. I handled all the building, and I run the product day to day. The technical side was never his job.

What does 50/50 co-ownership mean in practice? It means there's no fee for the build. Instead we own KeySolved together and split the revenue after costs, 50/50. It's fully transparent — we both see the same Stripe dashboard — and it's set out in a short, plain-English heads of terms. You can read the full mechanics on [the partner page](https://hellocrossman.com/partner).

How did KeySolved get its first customers? Distribution. Alex announced it to his email list and signups arrived the same day, with paying subscribers across seven-plus countries within weeks. There was no ad spend and no cold launch — the audience was already there and already trusted him. That's why distribution, not building, is the hard part.

Can I build a product with my own audience? If your audience is engaged, keeps asking you the same painful question, and you're willing to promote the answer, then yes — that's exactly the model. [Tell me about your audience and we'll find the product hiding in it](https://hellocrossman.com/partner).

---

Related reading

• [Distribution Without Product: Why Creators and Service Businesses Are Sitting on Gold They Can't Spend](https://hellocrossman.com/resources/blog/distribution-without-product-creator-service-business)
• [How We Built FounderOS: From 30K Followers and Zero MRR to £8K in Month One](https://hellocrossman.com/resources/blog/how-we-built-founderos-8k-mrr-month-one)
• [From Course Creator to Software Founder: The Playbook Nobody Wrote](https://hellocrossman.com/resources/blog/course-creator-to-software-founder-playbook)
• [What Happens in a 30-Day Product Build? (Week-by-Week Breakdown)](https://hellocrossman.com/resources/blog/30-day-product-build-week-by-week)

---

Tom Wild builds production-ready software at Hello Crossman — 100+ products shipped, 18 years in product design, including leading product design at Habito on products that handled over £3B in mortgages. KeySolved is one of several products he's co-built with creators and operators who bring the audience. There's probably a product hiding in your audience — let's find it.