System Discovery — Phase 1 of The Zero Point System
You Can't Build the Right Thing If You Don't Know What's Wrong.
Every failed build, every wasted sprint, every launch that went quiet — they all trace back to the same root cause: someone started moving before they understood what they were actually dealing with.
Building a new product without knowing who it's for or what problem it solves. Fixing a broken system without knowing where it actually breaks. Running a programme without knowing why it isn't working.
System Discovery changes that — before you spend another dollar moving in the wrong direction.
What This Is
Two to three hours of structured, uncomfortable honesty about what you're actually dealing with.
We map reality — not the version you present to investors, not the version that lives in your pitch deck, but what actually exists. Every step in the system. Every person inside it. Every place it breaks down or falls short.
I ask questions most people don't ask. Why does this step exist? What happens when it fails? Who does it actually serve — and who does it leave behind? I push back on assumptions. I name what I see. I record everything so I can go deep after the session and find what the conversation didn't surface.
Then I go away and do the analysis. I replay the session. I map what we covered. I look for the root cause underneath the symptoms, the gap between what the system was designed to do and what it actually does. And I write it down — clearly, specifically, without softening it.
By the end of this process, you will see your situation in a way you have not seen it before. That is the point.
2–3 hours working session — recorded and fully documented
Three written deliverables produced after the session
Debrief call to walk through everything and answer your questions
Everything you receive belongs to you — no expiry, no strings
What You Walk Away With
Three questions. Three documents. Complete clarity.
Whether you're building something new or fixing something broken, these are the three questions that need clear answers before anything else moves.
Current System Map
Answers: What is broken and where?
A visual diagram of your system as it actually exists — every step, every user touchpoint, every handoff, and every place it breaks down. Not how you think it works. How it actually works.
Most founders have never seen their system laid out this clearly. That alone changes how they think about it.
User Archetypes
Answers: Who is this actually for?
2–3 behavioral profiles of the real people who use your system — not demographics, but how they think, what they need, what frustrates them, and what it would take to keep them coming back. Built from what we mapped together, not from assumptions.
This is the difference between designing for who you imagine your users are and designing for who they actually are.
Problem Hypothesis
Answers: What is the real problem — and what would solving it unlock?
One clear, written statement of the root cause — not the symptom you've been treating. Who it affects, why the current situation persists, and what changes when it gets solved. Not a pitch deck. A diagnosis.
Whether you're a founder diagnosing a product gap, an organisation with a broken process, or a social enterprise trying to understand why your programme isn't creating the change you designed it for — this is the document that reframes everything.
Most people can describe symptoms. Very few can name the root cause with precision. This is how you get there.
The Price
This session is free.
Not discounted. Not "free intro then we pitch you." Free.
I am building my portfolio of case studies — documented, real-world examples of the discovery process working for real founders and organisations. To do that, I need real sessions with real problems.
In exchange for the full session and all three deliverables at no cost, I ask one thing in return.
One condition
If the work delivers value, you agree to a testimonial.
If you walk away from this session with genuine clarity — a clearer picture of your system, your users, and your real problem — I ask that you share that in a brief written or video testimonial. Not a review. A real account of what the session surfaced and how it changed your thinking.
If the session doesn't deliver real value, you owe nothing. The testimonial is only asked for if you feel the work earned it.
This will not be free forever.
Once I have the case studies I need, this session moves to a paid offer. The founders who come in now get the full value at none of the cost. No hidden pitch. No obligation to continue beyond the session itself.
What Comes Next
After the session, some founders want to keep going.
The discovery session stands completely on its own. But clarity is just the start — once you know what you're building and who it's for, the natural next step is to design and specify it. Here's what that looks like.
System Architecture
With the discovery in hand, I rebuild your system from first principles — 2–3 architectural options with clear trade-offs, a full Architecture Blueprint, and a User Journey Map showing exactly how your users move through the new system.
Solution Design
Architecture becomes a build package — a locked MVP Scope, a full Product Requirements Document, and a Product Strategy Document. The exact brief you hand to a developer so they build what you actually need, without ambiguity.
Pilot
Before you build the full product, you test the core hypothesis with real users. Defined success criteria, measured outcomes, a clear verdict: keep going, adjust, or stop. This is where assumptions become data.
If you want to go further, we discuss what makes sense for your specific situation after the debrief. No packages to commit to upfront — just the next right step.
What Founders Are Saying
Results will be documented here as sessions are completed.
Name, Role
Company
Results will be documented here as sessions are completed.
Name, Role
Company
About Henry
Henry Ikoh
Systems Architect & Product Engineer
I have spent years working with founders at the exact moment this problem shows up — when they are mid-build, money is leaving, and something feels deeply wrong but nobody can name it.
I have seen this from both sides. As a founder, I built Tradr — a three-sided marketplace that generated 20M naira in sales with a team of four. The concept worked. But we built two full mobile apps before we knew if the model would hold. We ran for 8 months with no defined success criteria and no decision framework.
The product did not fail because the idea was wrong. It failed because we built too much before we knew enough. I know exactly what it feels like to be deep in a build with a growing sense that something isn't right — and to keep going anyway because stopping feels like failure.
I also know what it looks like when a founder gets clarity first. The speed of the build. The confidence in the brief. The dev quotes that come in at a fraction of what they would have been. The launch that actually has users.
That difference — between building blind and building with clarity — is what The Zero Point System is designed to create. System Discovery is where it starts.
Every founder I have run this process with has walked away knowing exactly what to build, who to build it for, and what problem they are actually solving. That clarity is worth more than any feature on your roadmap.
What You're Getting
One session. Three documents. The clarity to actually move forward.
Current System Map
A visual diagram of your system as it actually exists — every step, every touchpoint, every place it breaks. You will see things you couldn't see before. So will everyone you share it with.
User Archetypes
2–3 behavioral profiles of the real people in your system — what they need, what frustrates them, what would make them stay. You will stop designing for who you imagined and start building for who is actually there.
Problem Hypothesis
A written diagnosis of the real problem — the root cause, not the symptom. What it costs to leave it unsolved. What changes when it gets solved. The document that makes the right next step obvious.
Debrief Call
A follow-up call to walk through every deliverable, answer your questions, and make sure you leave knowing exactly what to do next — whether that's with me or on your own.
You will know who you are building for. You will know what problem you are actually solving. You will know where your system breaks down and why. And you will have it all in writing — before you spend another dollar moving in the wrong direction.
Book Your Free Session
Spots are limited. Qualified applicants only.
Free for now. Not free forever.
By booking, you agree that if the session delivers real value, you'll provide a brief written or video testimonial on request.