A $9 field manual · by Ryan Richardson

You don't need a technical co-founder. You need to become the one.

You can't find one. You can't afford one. And the ones who'd say yes want half your company to write code you can't check. So you hand your idea to developers, hope, and find out months later you got something between disappointing and disaster.

Here's what nobody tells the non-technical founder: leading the build is a learnable skill, not a coding degree. There are six places where founders lose control of the people building their software — and once you can name yours, you stop getting ripped off.

$9. The fastest way to stop getting ripped off by the people who build your software — and start leading them like the technical leader your startup actually needs. Not a course. Not a bootcamp. A field manual.

GET THE BOOK $9

Read it tonight on your phone. Walk into your next dev meeting in control.

The $9 Field Manual

THE
NON-TECHNICAL
CTO

How non-technical founders become the technical leader their startup needs.

RYAN RICHARDSON

Cover preview · final art coming

Why this book exists

Everyone told me the fix was to find a technical co-founder. It nearly cost me everything.

So I did the next thing everyone says: hire developers, trust them, stay out of the technical stuff because "that's not your job." I documented more. I managed tighter. I added oversight. It made everything slower and nothing better — because I was managing people I couldn't actually read.

Then I watched a team take a process that delivered two or three fixes a year, at high cost, and rebuild it to deliver seventy fixes at twenty percent of the cost. Output up thirty times. Cost down eighty percent. The difference wasn't the developers. It was that someone in charge finally knew which questions to ask. That's the entire job of a CTO — and you do not need to write a line of code to do it.

That's not an unusual story. That's the default story. Smart founders with real businesses getting a fraction of what they paid for — and blaming the tech, the budget, or the team. It's almost never any of those. It's that nobody non-technical was leading the technical work.

I wrote this book because I learned every part of it the hard way, and watching other founders walk into the same traps drives me genuinely crazy. It's a long, structured vent — backed by what actually works. And by what learning it the slow way cost me:

A partnership gone wrong that cost me three software products, a consulting business, and years of work — because I let the "technical person" hold all the leverage and never defined what happens when it goes bad.
Six months of salary paid to a developer who knew I couldn't tell whether the work was real, and used it.
Nine in ten vendors landing somewhere between disappointing and terrible — because I evaluated a sales pitch, and the real work only showed up after I'd signed and the leverage had flipped.
App projects I poured money into that still don't make a cent, kept alive past the point I knew they were dead, because I couldn't tell "nearly done" from "never going to ship."

Every one of those is a place a non-technical founder loses control. Every one has a fix. They're all in here.

[ TESTIMONIAL PLACEHOLDER — drop one short reader quote about the outcome ("I finally knew what to ask my developer on Monday") here once real ones exist. Do not fabricate. ]

What's inside

The six places founders lose control of their build.

Six places where the gap between you and the people building your software opens — every time, in every startup, at every stage. Close the one that's broken in your world and you stop bleeding money on it immediately. Lead all six and you're running the build like the CTO you couldn't hire — without touching the code.

LEVER 1

Speak Their Language

Where you lose control first. You think you briefed it clearly. They built something else. Neither side tested whether you actually understood each other.

LEVER 2

Run the Work, Not the Code

You're stuck in decisions that belong to the developers, and absent from the ones only the founder can make. Where to stand, where to step back.

LEVER 3

Hire & Judge Talent

How to tell a great developer from an expensive one when you can't read the code — and how to never again be held hostage by the only person who understands your product.

LEVER 4

Offshore Without Getting Burned

Where founders chase a cheap hourly rate and quietly stop evaluating quality. How to use offshore teams and actually get what you paid for.

LEVER 5

Tools, AI & What to Build

Where developers optimise for clever and you needed shipped. Build-vs-buy, where AI actually works, and how to not get sold complexity you don't need.

LEVER 6

Keep the People Who Build It

Where the cost of the other five shows up: the developer who goes quiet, disengages, or walks — taking the only knowledge of your product with them.

STEP 01

Read it tonight

One sitting, on your phone. It reads like a vent from someone who's been where you are — not a textbook.

STEP 02

Find where you're losing control

Hold your current build against the six. One will be obviously, uncomfortably yours.

STEP 03

Have the one conversation

Not the whole framework. The single conversation with your developer that this points to — and you'll walk in knowing exactly what to say. This week.

What you get for $9

Everything below comes with the book.

The Non-Technical CTO — the full ebook

The six places founders lose control, the war stories, the hard lessons — written for the founder who's accountable for the product but can't write it themselves.

$29 value

BONUS 1Real Questions. Straight Answers.

The reference section: the blunt questions non-technical founders actually ask — what to pay, how to brief, when to fire a developer, how to read "almost done" — with the honest answer to each. The part readers go back to most.

$19 value

BONUS 2AI for the Non-Technical Founder

A standalone bonus chapter. Where AI genuinely lets a non-technical founder lead and ship faster — and where it just helps a developer sell you expensive noise. Straight answers, no hype.

$19 value

BONUS 3The One-Page Control Diagnostic

A single page you hold your current build against to find exactly where you're losing control — in about ten minutes. No login, no quiz, no email gate.

$15 value

Total value $82$9 today

Launch pricing, on this page. The book exists to start a conversation, not to make $9. Buy it at the price of a sandwich while it's here.

Add the Founder's CTO Workbook — +$19 The book tells you where you're losing control. The Workbook makes you take it back — one working session per lever: the honest baseline audit, the "what is my developer actually producing" table, the exact questions to ask before you next hire, brief, or sign a vendor, and the scripts for the conversations you've been avoiding. The book is the diagnosis. This is the prescription you fill in yourself. You won't see this price again.

Total due today: $9

GET THE BOOK $9

Instant delivery · read it tonight · 60-day refund, no questions

Read this before you buy

This is for you. Or it really isn't.

This is for you if:

You're a non-technical founder and your software — built or being built — is costing you money, time, or sleep.
You've been looking for a technical co-founder and can't find, afford, or trust one.
You pay developers but can't fully tell whether what you're getting is any good.
You've replaced a developer (or agency) and watched the same problems follow the new team.
You've been told "it's almost done" for three months and can't tell if you're close.
You nod in technical meetings, then go look up half of what was said afterward.
You're sitting on an idea and want to lead the build right before you burn money on the wrong one.
You'd rather read the honest version than the cleaned-up, figured-it-all-out one.

This is NOT for you if:

You're already technical and comfortable leading engineers — you live on both sides already.
You want to learn to code. This makes you a leader of builders, not a builder.
You're looking for a course, a coaching upsell, or a 12-week program. This is a $9 book.
Your product is fine, shipping, and no build decision is hurting you.

IT'S A FIT — GET THE BOOK $9

Who wrote it

Ryan Richardson

Built seven businesses over fifteen years — and has the graveyard to prove what each one taught him about leading people who build software.
Delivered over a hundred enterprise technical projects across mining, resources, financial services, government, and startups.
Has hired, fired, and run developers across four countries — which is where the pattern became impossible to ignore.
Started non-technical, learned to lead the technical work without becoming an engineer — and now does it for a living.
Lost three products, a consulting business, and years of work to a partnership he never properly structured. That scar is chapter one of the war stories.

Straight answers

The questions founders actually ask.

The Planning FounderStop hunting for a co-founder to hide behind. Define done before you start — the outcome, not the feature list. Get a technical person with no stake in it to review any serious proposal before you sign. And build nothing until you've sat with the people who'll actually use it. The Planning Founder section is a straight-talk Q&A on cost, hiring, offshore, and build-vs-buy — and the order to do them in so you lead instead of getting led.

The Stuck FounderIf nobody has used any version of it yet, the timeline isn't the problem — that is. The Stuck Founder section is the rescue manual: what to do when the developer goes quiet, how to read "almost done," how to get an honest independent assessment, and how to cut scope without gutting the product — all without needing to read a line of code.

No — that's the whole point. A CTO's job isn't writing code; it's leading the people who do and making the right calls. This book makes you the technical leader your startup needs without becoming an engineer. You'll know which questions to ask, what good looks like, and where the leverage really sits.

No catch. $9 buys the book and the bonuses, full stop. The page only sells the book. If something lands, there are two optional doors at the end — become the technical leader with a community of founders doing the same, or have your product built for you. Neither is priced or pitched here, and you never have to walk through either to get full value from the $9.

One last thing

Stop nodding in meetings you don't understand.

You'll know which kind of founder you are by whether you close this page or open a notebook. Some founders keep hoping for a co-founder who never shows. A few decide to become the technical leader themselves — and start getting what they pay for. The gap between those outcomes isn't intelligence, budget, or luck. It's whether you take control of the build. The first step costs $9 and one evening.

GET THE NON-TECHNICAL CTO $9