Diagnose the constraint. Prioritize the leverage. Rebuild the system.
The Alba Revenue Architecture Method exists for one reason: so effort and budget go to the real constraint, not the loudest symptom. Most commercial problems announce themselves somewhere other than where they live. Weak enquiries get blamed on the website; a slow pipeline gets blamed on the sales team; flat revenue gets blamed on marketing. The method is how I find where the problem actually lives before anything gets built, bought, or rebuilt.
In one line: the method is an eleven-step sequence — observe, understand, map, examine, diagnose, separate causes from symptoms, prioritise, design, implement, measure, refine — that treats your revenue as one connected system and refuses to prescribe a fix before the diagnosis is done.
Symptoms are loud. Constraints are quiet.
A commercial system — positioning, demand, website, CRM, sales process, follow-up, reporting — fails as a system, not as a list of parts. The visible failure is almost never the actual one. Enquiries can dry up because the offer is interchangeable, not because the ads are bad. Deals can stall because qualification is broken three stages earlier, not because the proposal needs polish. If you fix the symptom, the constraint stays in place and quietly caps everything you do next.
Diagnosis comes first because sequence is where the money is. The same fixes, applied in the wrong order, produce a fraction of the result — a beautiful new website in front of a confused offer converts confusion faster. So before I recommend anything, I insist on knowing which single point in the system, if changed, unlocks the most downstream. That is what the Commercial Clarity Diagnostic is built to find.
Why I don't immediately sell execution.
Most providers earn when you buy their deliverable — a website, a campaign, a CRM build, a retainer. That creates a quiet pressure to diagnose every problem as the thing they happen to sell. I have structured Alba the other way around: the diagnosis is the product, and it is paid, so it does not have to end in a pitch.
If I told you on day one that you need a rebuild, I would be guessing — and charging you for the guess. Selling execution before diagnosis means the client carries the risk of a wrong prescription. I would rather tell you that the redesign you were about to commission is premature, or that the constraint is a pricing decision no agency deliverable can touch. Sometimes the honest finding is that the highest-leverage change is small, unglamorous, and cheap. A studio built on architecture rather than deliverables can say that. An agency paid by the deliverable usually cannot.
Eleven steps, in strict order.
The sequence matters more than any individual step. Diagnosis (steps 1–6) always precedes prioritisation (step 7), which always precedes design and implementation (steps 8–9). Skipping ahead is how businesses end up funding solutions to problems they do not have.
Phase one — Diagnose
Observe the symptoms
I start with what you are experiencing, in your words: soft enquiries, stalled deals, rising spend, a pipeline nobody trusts. Symptoms are the entry point — never the conclusion. At this stage I record them without accepting anyone's explanation of them, including yours.
Understand the business model
How you actually make money: what you sell, to whom, at what price, at what margin, with what delivery constraint. A fix that ignores the economics is decoration. This is also where founder dependency, capacity limits, and pricing structure come into view.
Map the buyer and revenue journey
I trace the path from first attention to closed revenue — every message, page, form, handoff, and follow-up a buyer actually meets — and lay it against how revenue moves internally through marketing, CRM, and sales. The gaps between the two maps are usually where value leaks.
Examine the evidence
Opinions are checked against reality: analytics, ad accounts, CRM records, form submissions, response times, win and loss patterns, and conversations with the people closest to the customer. Where the data and the beliefs disagree, the data leads.
Identify the real constraint
Every system has one point that limits everything downstream of it. I name it precisely — not "marketing isn't working" but, for example, "the offer gives a qualified buyer no reason to act now." A constraint you can name is a constraint you can fix.
Separate root causes from surface symptoms
Each symptom from step one gets traced back to its cause. Some collapse into the constraint. Some turn out to be downstream effects that will resolve on their own once the constraint moves. A few are real but secondary. This separation is what keeps the plan short.
Phase two — Prioritise
Prioritise Fix First / Fix Next / Fix Later
Everything worth doing is sequenced into three tiers by leverage, not by visibility or comfort. The output is a short, ordered plan — including an explicit list of investments that would be premature right now.
Phase three — Rebuild
Design the commercial architecture
Before anything is built, the target system is designed on paper: how positioning, offer, website, CRM, sales process, and reporting should fit together for this business. Design is cheap to change; implementation is not.
Implement the highest-leverage changes
Work begins at the top of the Fix First list and moves in order. Depending on the engagement, implementation is led by me, by your team with my direction, or by outside specialists working to the architecture — more on that below.
Establish measurement and operating rhythm
Every change gets a way of knowing whether it worked: the numbers we will watch, where they live, and a regular rhythm for reviewing them. A fix without measurement is a hope. This is where revenue operations discipline becomes permanent rather than a project.
Review and refine
Once the constraint moves, a new one becomes visible — that is how systems work. We review what the evidence now shows, retire what is finished, and re-run prioritisation. The method loops; it does not end with a launch.
Fix First. Fix Next. Fix Later.
Prioritisation is where most plans fail, because everything feels urgent and nothing gets refused. I use a deliberately blunt structure: three tiers, ordered by leverage. Leverage means one thing — how much of the system improves downstream when this one thing changes. Not how visible the fix is, not how satisfying it feels, and not what a vendor happens to sell.
The constraint
The one or two changes doing the most damage right now. These get full attention until they move. Usually fewer items than clients expect — and rarely the ones they arrived with.
The follow-through
Work that only pays off once the constraint has moved — sequenced so each change compounds the last instead of scattering effort across the whole system at once.
The deferred
Real work, deliberately parked. This tier exists to protect you: it names the investments — often the expensive, exciting ones — that would be premature until the foundation is sound.
The Fix Later list is the most valuable tier and the least popular. It is where I tell clients not to spend money yet — on the rebrand, the new tool, the scaled ad budget — and exactly what has to be true before that spending makes sense.
The diagnosis is only as honest as the inputs.
The method reads evidence, not impressions — which means I need access to the real system, not a curated version of it. Depending on scope, that typically means:
- The commercial surface — your website, current offers, pricing, and any active campaigns or sales materials.
- The numbers — analytics, ad accounts, and whatever reporting you currently rely on, however imperfect.
- The pipeline — CRM access, or an honest export of it, including the deals that died and why.
- The people — short conversations with whoever is closest to the customer: the founder, and anyone who sells or delivers.
- The uncomfortable truths — what has been tried and failed, where money was wasted, and what nobody internally wants to say out loud.
Everything is handled confidentially. What I ask in return is candour: a flattering set of inputs produces a flattering diagnosis, and a flattering diagnosis is worthless.
Every decision written down, with its reasoning.
Strategy that lives in someone's head is a dependency, and the method is explicitly designed against dependencies — including dependency on me. So every material decision is documented in plain language: what we decided, what evidence supported it, what alternatives were considered and rejected, and what would have to change for the decision to be revisited.
In practice this means you hold a written diagnosis, a prioritised Fix First / Fix Next / Fix Later plan, the designed architecture, and a running record of decisions as implementation proceeds. Six months from now, you — or anyone you hire — can read why the system is shaped the way it is. That record is yours. It stays useful whether we keep working together or not, and it is what makes delegation safe.
What I lead — and what can be delegated.
Alba is a studio, not an agency, and I do not hand your account to a junior team. The judgment work — the parts where a wrong call is expensive — is done by me personally. Execution capacity is a different matter: it can and often should come from elsewhere. The distinction is simple: you can delegate the hands without delegating the judgment.
I personally lead
- The diagnosis and constraint identification
- Root-cause analysis and prioritisation
- The design of the commercial architecture
- Positioning, offer, and pricing decisions
- The decision record and its reasoning
- Review checkpoints and re-prioritisation
Can be delegated — to the architecture
- Website build and development work
- Content production and design assets
- CRM configuration and data hygiene
- Campaign operation and day-to-day media
- Routine reporting and dashboard upkeep
- Ongoing execution by your internal team
When execution is delegated — to your team or to specialists — it is delegated to the architecture, not to opinion. The builders work from a documented design with explicit reasoning, and the checkpoints stay with me. That is how implementation scales without the strategy dissolving. It is the same principle behind how I approach sales performance: the system holds the standard so no individual has to. If it matters to you who actually does this work, read about me — there is no team of strategists behind the curtain, by design.
The method starts with a diagnosis.
Every engagement begins the same way: finding the real constraint before anything is built or bought. Every application is reviewed personally, and I will tell you honestly if a diagnostic is not the right next step.