Most engagements start with the tools, not the motion.
A typical RevOps engagement walks in and configures HubSpot. We walk in and audit the revenue system — stakeholders, hand-offs, where it actually breaks. The portal is the last thing we touch.
The Focal Method
The architect tier above RevOps. Where most engagements stop, ours begins.
A typical RevOps engagement
Walks in and configures the tools. Optimizes how the engine runs.
- HubSpot portal setup
- Workflow + automation builds
- Reporting dashboards
- Retainer for ongoing tickets
- Hands off when configuration is done
The Focal Method
Designs what the engine should be before it touches the portal.
- Revenue system audit (motion, not portal)
- Architecture blueprint signed before code
- Build executes against written gates
- Operate owned by the team that designed it
- Optimize keeps the architect in the room
01/The problem
Most RevOps engagements stop at the wrong altitude.
They optimize the engine without first deciding what it should be.
Where RevOps optimizes how the revenue engine runs, Revenue Architecture decides what the engine should be in the first place. Without that decision in writing, every later build re-litigates it at twice the cost.
They hand off the system before the team can operate it.
Implementation is where most partners stop. The build ships, the invoice clears, and the system drifts inside ninety days. We stay in the room through Operate — the system isn't done when it's live, it's done when it's producing.
Architecture before code. Artifacts, not theatre.
P1
Architecture before code.
No configuration in week one. Phases 01–02 produce a written blueprint that every build decision then executes against. The blueprint is the contract.
P2
Artifacts, not theatre.
Every phase ends with a tangible document or a running system you can hand to a successor. No slideware. If we can't hand it off, it isn't finished.
P3
Gates, not vibes.
Each phase has one written gate criterion. We do not move on until the current phase is closed against that criterion in writing — signed, dated, and on file.
P4
Operations is a layer, not an afterthought.
Run isn't a retainer we bolt on. It is the fifth phase of the same engagement — owned by the team that designed the system, accountable to the metrics they wrote.
03/The Method
The Focal Method. Five phases, end-to-end.
- 01 · Design
Discover
1–2 weeks
- 02 · Design
Architect
2–4 weeks
- 03 · Build
Engineer
8–24 weeks
- 04 · Run
Operate
4–8 weeks
- 05 · Run
Optimize
Ongoing · retainer
01
Discover
Duration · 1–2 weeksOwner · Revenue ArchitectTrack · Design
Audit the revenue system end-to-end. Stakeholder interviews, current-state diagrams, data and tech-stack inventory, GTM motion mapping. We are looking for where revenue stalls — not where the tools are misconfigured.
DeliverableRevenue System Audit15–25 pages · stakeholder map · current-state diagram
Gate to next · Audit signed.
No move to Architect without a defensible current-state diagram on file.
02
Architect
Duration · 2–4 weeksOwner · Revenue Architect + GTM Engineering leadTrack · Design
Design the future-state system. Integration map, AI orchestration plan, change roadmap, success-metrics framework. This is the document the build executes against and the document the operator inherits.
DeliverableRevenue Architecture Blueprint30–50 pages · integration map · AI orchestration · change roadmap
Gate to next · Blueprint locked.
Signed by the executive sponsor and the GTM engineering lead. Scope and metrics frozen before code is written.
03
Engineer
Duration · 8–24 weeksOwner · GTM Engineering podTrack · Build
Build the system the Blueprint describes. HubSpot configuration, CMS work, conversion-focused UI/UX, AI agent orchestration, custom integrations. Every decision references the Blueprint; new scope opens a written change, not a slack thread.
DeliverableFunctional revenue systemModule library · configuration docs · integration runbooks
Gate to next · Acceptance passed.
Acceptance is measured against the success-metrics framework written in Architect, not against vibes at hand-off.
04
Operate
Duration · 4–8 weeksOwner · RevOps teamTrack · Run
Embedded operations during the launch window. Daily cadence, hands-on optimization, training the in-house team, triage authority. We don't leave when it's live; we leave when it's producing.
Deliverable30 / 60 / 90 performance reviewTraining docs · issue log · optimization backlog
Gate to next · 3 weeks green.
Three consecutive weeks of green metrics against the Blueprint targets before we step back.
05
Optimize
Duration · Ongoing · retainerOwner · RevOps + Architect (quarterly)Track · Run
Recurring engagement post-launch. Monthly performance reviews, A/B testing, AI agent maintenance, quarterly strategic planning. Architect involvement returns each quarter to keep the system aligned to the original brief.
DeliverableMonthly performance reportQuarterly strategic review · annual roadmap
Gate to next · Architect re-engages.
Quarterly Architect involvement keeps the system aligned to the original Blueprint, not the loudest stakeholder.
04/Why it compounds
Sharper every engagement. Harder to replace every quarter.
The Method gets sharper every engagement.
Once productized and refined across the first ten engagements, the Focal Method becomes a reproducible advantage. Internal docs, training, certification, and a library of past artifacts compound — each project starts further along than the last.Reposition. report, §3.3 — Process power
RevOps shops can't pivot to this without cannibalising themselves.
Established RevOps agencies sit on productized retainers and operational pricing they've trained the market to expect. They can't claim the architect tier without abandoning the mass-market positioning that pays their salaries.Reposition. report, §2.3 — Counter-positioning
The Run layer creates switching costs that compound.
Once we are embedded in your Run layer — ongoing optimization, AI agent operations, retainer cadence — the cost of replacing us is the cost of re-doing Discover and Architect on a system already in motion. It rarely makes sense.Reposition. report, §3.3 — Switching costs
Start where it makes sense. Two doors in.
Discover is the standalone entry point — an Audit document you keep regardless of whether you continue with us. Architect is the full end-to-end engagement: four to nine months, one named architect, Operate included. We publish floors, not ceilings.
Door 1Standalone
Discover
From $12K1–2 weeks · one architect
A one-week current-state audit. Stakeholder interviews, system diagram, written findings. You leave with a document; whether to continue is a separate decision.
- Stakeholder interviews (5–8)
- Current-state revenue diagram
- 15–25 page Audit document
- Recommended next-step scope
Door 2End-to-end
Architect
$80K–$250K4–9 months · phases 01–04
The full Method — Discover, Architect, Engineer, Operate. One named architect through every phase. Written gates between each. Hand-off when the system is producing, not when it's live.
- Revenue Architecture Blueprint
- Build executed against written gates
- Operate included (4–8 weeks embedded)
- 30 / 60 / 90 performance review
+
Already operational? Optimize is a monthly retainer for systems already in production — cadence post-launch, A/B testing, AI agent maintenance, quarterly architect reviews. $5K–$25K / mo · see Phase 05