I read one client SOW and found 102 questions it never answered.

Each one was a change order waiting to happen, an argument about what “done” meant, or a wrong assumption someone would have built on anyway. I find them before the budget is committed, while they still cost nothing to fix.

Blessit George

Product discovery and scoping for founders and business owners committing real money to a build. Thirteen years, 100+ products, 20+ built end to end. Two of my own ventures failed, so I know how this goes wrong from both sides of the table.

You'll find out in month eight. With the money gone.

You have something you want built and someone who can build it. What you don't have is anyone whose job is to say which parts of the plan are assumptions, which assumption breaks the whole thing if it's wrong, and what the cheapest way to find out would be.

Your developers will build what you ask for. Your designers will make it look right. Whoever writes the spec will write down what you said, faithfully. Everyone in the room is paid to move forward.

How we work together

Every engagement is priced to scope. Tell me what you're building and I'll quote against what you need.

Scope Pre-Flight Check

Send me what already exists: the SOW, the RFP response, the wireframes, the brief.

In three to five days you get back every contradiction in the document, every question it doesn't answer ranked by what it will cost you to find out late, the assumptions that are load-bearing and untested, and a straight go / refine / stop.

Priced to scope, from $1,500. Fixed fee, and not credited toward anything else. If the honest answer is stop, that has to cost me nothing to say.

Best for anyone about to sign a development contract, whether you're a founder buying your first build or a business commissioning a system from an agency.

Discovery to Buildable Spec

Full product discovery, translated into something your team can actually build from.

Prioritised scope, user stories with testable acceptance criteria, functional specs, process maps, and test scenarios. Then a walkthrough with your engineering and design teams, so the handoff lands instead of sitting in a folder.

The two backlogs below are this service. That is the output itself, not a marketing rendering of it.

A few weeks, scoped to your project. Best for funded founders with a team and no product lead, and for businesses who need the spec to be right before a vendor starts building against it.

Fractional Product Lead

Ongoing product leadership without a full-time hire.

Roadmap ownership, prioritisation, direction for your engineering and design teams, and a product brain in the room every week. It's the difference between a team that ships and a team that's busy.

Monthly, three-month minimum. Best for founders building continuously who keep making product decisions alone, and for owner-led businesses running a software project with nobody in-house to own it.

Not sure which?

That's the normal starting position. Tell me what you're building and where you're unsure.

If none of these three is the right shape, or if you don't need me at all, I'll say so.

Book a call →

What you actually get

Client names changed, and anything proprietary to how their business makes money taken out. Nothing else. Every story, every acceptance criterion, and every question I couldn't answer from the source and had to raise.

This is the deliverable, not a sample of it. Open either one and read the whole thing.

Case studies

An industrial group’s vehicle recycling arm

They asked for more leads. Leads weren’t the problem.

They came for a lead generation website. Discovery found the demand was never the problem — and more leads would have amplified the cost, not the revenue.

70–80% first-pass UAT acceptance

Read the whole thing →

MyonPet — my own venture, in build

I ran this on my own company. It cost me a feature set and saved me most of a year.

The whole product sat on an assumption I had never tested: that owners would track their pet daily, unprompted. I checked. They wouldn’t.

80% of planned scope removed

Read the whole thing →

Blessart Digital — my own venture, failed

I spent months researching a market and never asked anyone for money.

Several owners asked to see a proposal. I read that as validation. Nobody had paid me anything, and I had built a company on it.

Zero clients landed

Read the whole thing →

And yes, you should be asking whether someone whose consulting business failed is the right person to advise you.

It’s a fair question. The difference is that this practice isn’t built on months of research and a positioning document. It’s built on thirteen years of delivered work, and the artifacts are open above for you to judge directly rather than take on trust. Blessart is why I don’t let anyone confuse interest with demand. I earned that one the expensive way.

An industrial group’s vehicle recycling arm

They asked for more leads. Leads weren’t the problem.

An established business with real revenue, no online presence, and a plan to fix that. They came to us for a lead generation website.

I ran the discovery. What surfaced wasn’t a demand problem. Their tracking and coordination happened offline and by hand, and it was costing them money and time on every single transaction. Sending more leads into that would have amplified the cost, not the revenue.

So the recommendation wasn’t the website they asked for. It was to move the operation itself online, mapping customer, inspector, warehouse, and operations touchpoints as one connected ecosystem, and let demand generation follow a process that could actually handle it.

Every major functional decision went through their CEO directly. It’s live and running.

The modules I specced hit 70–80% first-pass UAT acceptance.

The brief was reasonable and the client wasn’t wrong to ask. But the thing they wanted to buy wouldn’t have fixed the thing that was hurting them. Finding that out took discovery, and discovery is cheap compared to building the wrong thing well.

MyonPet — my own venture, in build

I ran this on my own company. It cost me a feature set and saved me most of a year.

I set out to build a pet habit tracker. The premise was the one everybody nods along to: owners log their pet’s daily routines, and with enough of that data we tell them something useful.

The assumption I hadn’t tested was whether owners would track at all. Not whether tracking is useful, but whether they’d do it, repeatedly, unprompted. The entire product sat on top of that and I’d never checked.

So I checked, with closed-group surveys and two small pilot programmes over a few weeks. The answer was clear. They liked the idea and they didn’t do it. The data layer the whole product depended on was never going to exist.

I cut the habit tracker, and I cut the AI features stacked on top of it. What survived was the part that was genuinely ours and needed no daily input from anyone: the nutrition analysis engine, built with a certified pet nutrition coach.

That removed roughly 80% of the planned scope and projected build cost, before any of it got written.

It’s in alpha, bootstrapped, and approaching its first year.

I could have built the original version. It would have been beautifully specified and dead on arrival. That’s the failure I’m hired to prevent, and I know its shape because I nearly walked into it with my own money.

Blessart Digital — my own venture, failed

I spent months researching a market and never asked anyone for money.

I started an independent consulting practice for SMEs. Months of research pointed me at well-run local businesses in the US and UK. I built a positioning, built a marketing plan, and warmed owners up over email and WhatsApp. Several asked to see a proposal.

I read that as validation. It wasn’t. Nobody had paid me anything. “Send me a proposal” is the cheapest thing a business owner can say, and I’d built a company on it.

What I did next was the actual failure. I pivoted toward healthcare because healthcare was the thing moving. I had no relationships there, no credibility there, and no reason to think I could win beyond the fact that it was busy. Then I held on for months, because it was mine and I’d built it.

I never landed a client.

What I’d tell myself now:

  • Interest is not demand. Get someone to pay before you build a business around them.
  • Moving toward whichever market is loudest isn’t a pivot. It’s a way of avoiding the question of whether your offer works.
  • The hardest judgment in product isn’t what to build. It’s admitting the thing you’re attached to isn’t working, early enough for it to matter.

Fair questions

How is this different from the product discovery my agency already does?

The agency’s team documents what’s been agreed. Their discovery is scoped to produce a statement of work, and it ends in a build, because a build is what the agency sells. I don’t build, and nobody downstream of me is waiting on a yes.

The two backlogs above are that difference in practice. An agency or a developer would have documented the WaveStore SOW as written. I documented it and raised the 102 questions it never answered, before anyone built against them.

Can’t I get this out of ChatGPT or Claude?

Some of it, yes, and you should try before you talk to me. Point a model at your SOW and it will find real problems.

What it won’t tell you is which of those problems matters. Models work from patterns in what has already been written, so you get the generic answer: the risks that are true of every project shaped roughly like yours. What a model can’t do is sit in a room with your stakeholders and notice the thing nobody wants to say out loud, recognise the particular way an integration like this one has gone wrong on three previous builds, or work out why your business model makes an obvious-looking feature the wrong call.

I use these tools throughout my own process, so this isn’t an argument for doing things slowly by hand. The output is only as good as the questions put in, and the questions come from having watched this go wrong before.

I’m not a startup. We’re an established business buying a system.

Then you’re the first case study on this page. That client had revenue, staff, and a working operation. What they didn’t have was anyone independent standing between them and a vendor’s proposal. Established businesses tend to have more at stake here, not less, because the software has to fit an operation that already exists and already works.

Won’t this delay the build?

Days, or a few weeks, depending on the engagement. The real question isn’t whether that costs you time. It’s whether those weeks cost less than the eight months. On my own product, a few weeks of unglamorous testing removed 80% of the planned scope before a line of it was written.

What if you tell me to stop and I don’t agree?

Then you don’t stop. I give you a recommendation and the evidence under it. You own the decision and you always did. What you’re buying is the argument against your own plan, made properly and made early, by someone with no reason to flatter you. Plenty of clients hear it, disagree, and build anyway. They build with much sharper eyes on the risk they just chose to take.

We’re already mid-build. Is it too late?

No, but the question changes. Before a build, the work is about what to build. Mid-build it’s about what to cut, and cutting is harder, because the sunk cost is real and sitting in your repo. It’s still cheaper than finishing something nobody wants. Bring me what you’ve got and what isn’t landing.

About me

I've spent thirteen years around products, inside enterprises, inside startups, and inside agencies where I ran discovery for clients who arrived asking for one thing and needed another. Over a hundred products worked on. Twenty-odd taken from an idea to something real people used.

I started as a developer, moved into solution architecture, and ended up in the room where the decisions get made: workshops, stakeholder alignment, scoping, the arguments about what's in and what's out. Somewhere in there I stopped being the person who documents what clients want and became the person who asks whether they should want it.

So that's the work now. Reading the scope and the assumptions sitting underneath it, putting the risks in front of your stakeholders while they still cost nothing, designing cheap experiments that test the product rather than flatter it, and building the scope that survives contact with reality.

Most people you ask to build for you have never had their own money on the line. I've had mine on the line three times. Twice it didn't work. That's why I'll tell you to stop.

Where I work from: Based in India, delivering for clients in the US, UK, and Australia for years. Calls happen in your working hours.

Blessit George at work

How it works

  1. A 30-minute call

    You tell me what you're building and where you're uncertain. I ask questions. There's no pitch.

  2. A scoped proposal

    What I'd do, what you get, how long it takes, what it costs. Within two working days.

  3. The work

    Sessions with you, and with your team where it matters. Artifacts delivered as we go, not dumped at the end.

  4. Handoff

    Your engineering and design teams get a walkthrough, not a document. If they can't build from it, it didn't work.

Tell me what you're building.

Thirty minutes. What you're building, and what you're unsure about. If I'm not the right person, I'll tell you that too.

Book a call