You Wouldn’t Build a House Without Plans. So Why Build Software Without Discovery?

Read Time: 4 Minutes

Most people don’t want a spec. They want clarity, fast.

And yet, most software projects still begin with a vague brief, a brain-dump of features, and a hopeful quote based more on guesswork than grounded understanding.

It’s no surprise those projects so often go sideways.

At GGA, we learned this the hard way, and now we start every serious build with one non-negotiable:

Paid discovery.

Here’s what we’ll cover this week:

👉🏼 Why We Charge for Discovery

❌ Why Free Quotes Lead to Expensive Mistakes

⚙️ Discovery Isn’t a Document. It’s a Process

🚀 What a Great Spec Actually Gives You

Let’s dive in 👇

Last week, I recorded another episode of Ctrl Alt Dev with Sean.

Our weekly podcast where we talk all things software, strategy, and staying sane as business owners.

It’s still early days, but I’m loving the chance to chew the fat with someone who’s lived through the same brutal deadlines, vague briefs, and “could you just build us an app?” conversations.

This week’s topic came straight from that chat.

Because somewhere between caffeine and code, we found ourselves asking:

Why do so many software projects still start without a proper plan?

Not a wishlist. Not a wireframe.

A real discovery. With time, thought, and tough questions.

And if that’s the foundation we need for every build, shouldn’t it be something we charge for?

That question sparked this week’s newsletter.

Why We Charge for Discovery

It used to make me uncomfortable.

Asking a client to pay before we’d written a single line of code? It felt… bold.

But then I realised: if we’re being asked to solve a complex, business-critical problem, shouldn’t we start by understanding it properly?

Would you build your dream home with no plans?

Would you trust a free blueprint drawn by someone who barely knows your site, your goals, your taste?

Of course not.

Discovery isn’t an upsell. It’s an essential investment in getting it right.

Takeaway: A well-run discovery is the smartest money you’ll spend on any software project.

Why Free Quotes Lead to Expensive Mistakes

In the early days, we gave free quotes like everyone else. And we always paid for it later.

Here’s what usually happens:

❌ Scope creep

❌ Misunderstood goals

❌ Rework, tension, and “that’s not what I meant” moments

A recruitment firm spent £50k on a half-built candidate portal that never launched.

No spec, no real plan.

We rebuilt it from scratch with 40% less scope and double the ROI.

Why? Because we started with discovery.

You wouldn’t hire a builder with no drawings. Yet people still expect a fixed quote from a one-page brief.

Nugget #1: If you’re not paying for discovery, you’re paying with risk.

Discovery Isn’t a Document. It’s a Process

Our discovery process is structured, but human.

It’s not just ticking boxes.

It’s poking holes in assumptions before they become potholes in production.

It’s a collaborative deep dive into what matters most:

🔍 Where’s the friction in your business today?

👥 Who’s really involved in the process?

⚠️ What happens if this doesn’t change?

🔧 Is this even a tech problem, or is it about process and people?

We challenge assumptions, test ideas, and uncover truths. And most importantly, we define what not to build.

Nugget #2: Discovery isn’t about getting more requirements, it’s about finding the right ones.

What a Great Spec Actually Gives You

A great spec does three things:

✅ Aligns the team around one clear goal

✅ Exposes where complexity can be reduced

✅ Builds confidence in timelines, budgets, and outcomes

It’s not about bloated documents. It’s about creating momentum, with purpose.

The biggest compliment we get after discovery?

“I thought I needed something complicated. Turns out, I needed something focussed.”

You get more than a PDF. You get peace of mind and a path forward.

Nugget #3: Discovery turns a wishlist into a working strategy.

What Can You Do Today?

If you’re starting a new digital project:

🔹 Pause the rush to build: ask the right questions first

🔹 Ditch the guesswork: clarity beats complexity

🔹 Choose partners who challenge you: not just ones who say yes

If you want something specific, meaningful, and built to last, it’s worth slowing down, asking better questions, and building the right thing.

P.S. Whenever you’re ready, here’s how I can help:

Need a fresh perspective on your software? I’m here to help. Book a 1-1 call with me, and we’ll figure it out together.

Do you know somebody else who could benefit from The Automation Advantage?

Before You Go…

How did you enjoy this email? I really value your honest feedback.

🔥 It was AWESOME!

🔥 Very good!

🔥 Okay!

🥶 Needs work!