The artifact is named, not described.
Not "the audit phase output" but the Revenue System Audit. Not "the design doc" but the Revenue Architecture Blueprint. Names are what your procurement team can search the SOW for.
AuditabilityThe Focal Method.
Our five-phase methodology for building Revenue Architecture on HubSpot
Every phase produces a named artifact you review before the next phase commits budget. Every gate is a real decision point [continue, redirect, or stop] with a document procurement can defend either way.
01 · FrameScope
Artifact: Revenue System Audit
1–2 weeks · from $7.5K02 · OutlineDesign
Artifact: Revenue Architecture Blueprint
2–4 weeks03 · ConstructBuild
Artifact: Configured portal + handover
8–24 weeks04 · ActivateHandover
Artifact: 30/60/90 review + Playbook
4–8 weeks05 · LeverageOperate
Artifact: Monthly report + QBR
Ongoing · Run-tierWhat the Focal Method is .
A methodology, not a process. The distinction is what makes the work auditable, defensible to procurement, and stoppable at any phase boundary if it doesn't fit.
The Focal Method is GiantFocal’s five-phase delivery methodology for building, launching, and operating a revenue system on HubSpot. The five phases are Discover, Architect, Engineer, Operate, and Optimize. Every phase produces a named artifact, every artifact is reviewed by you before the next phase commits any budget, and every engagement runs through the same sequence in the same order.
By “revenue system” we mean the integrated stack that runs your commercial motion on HubSpot: the lifecycle model, the property layer, the deal-pipeline architecture, the cross-Hub data contract, the integration topology, the reporting layer, the workflows that operate it, and the team that owns it after launch. A revenue system is not the CRM. The CRM is one component. The system is the integration that turns the CRM, the Marketing automation, the Service tickets, the Content layer, the data sync, and the Commerce billing into one operating surface for your revenue motion.
A methodology produces a named artifact at every phase. A process produces a status update. That distinction is what makes the Focal Method auditable, defensible to procurement, and stoppable at any phase boundary if the work does not fit.
Most HubSpot engagements ship on time. Then they break at month 18.
You've seen the pattern. The reports that worked at QBR-1 don't tie out at QBR-7. The vendor talked about iterations — never produced an artifact procurement could defend. The team is now budgeting for a re-platform that should have been a 90-day fix.
Most operators reading this have lived through at least one HubSpot engagement that shipped on time and then broke at the 18-month mark. The sequence library has grown to 300 entries and nobody owns the cleanup. The CRO and CFO disagree on pipeline velocity and both are pulling from the same portal. The previous vendor talked about sprints, stand-ups, and retros — but never produced an artifact procurement could defend at the renewal conversation.
Most buyers, after that experience, think the answer is to pick a vendor with a more rigorous “methodology”. They go shopping, and every agency uses the word. The decks all show a five-step or six-gate process: Discover, Define, Develop, Deliver. Plan, Build, Operate. Each one looks rigorous. Each one, in practice, produces the same outcome as the last vendor: a deliverable nobody can defend at the next phase boundary.
The real difference between a methodology and a process is one specific thing: a methodology produces a named artifact at every phase that you (and your procurement team) can review before the next phase commits budget. That is the difference between “we’re 60% done” (process language, untestable, defensible only on trust) and “you have the Revenue Architecture Blueprint in your hands and you can stop here if it doesn’t fit” (methodology language, procurement-defensible, falsifiable at every gate).
The Focal Method exists so you never have to take a vendor’s word for it at any phase boundary. Every phase produces an artifact. Every artifact is yours to keep. Every gate is a real decision point where you can continue, redirect scope, or stop.
The artifact ships before the next phase commits budget.
You don't see the Blueprint after the build is half-built. You see it on day 30, with the Engineer SOW unsigned. Stopping is a real option, not a face-losing one.
DefensibilityThe artifact is yours to keep — either way.
If you continue with us, the Audit fee credits 100% toward the Architect-tier engagement. If you don't, the Audit goes into an internal RFP or to a different vendor. We build artifacts to that standard on purpose.
OptionalityFive phases, same order, every engagement. One named architect through all of them.
We track Method conformance per engagement — the discipline of holding every phase against its named artifact, with written justification required for any deviation. At every phase boundary, you review the artifact and decide whether to continue.
01
Phase 01Frame
1–2 weeks · Audit02
Phase 02Outline
2–4 weeks · Blueprint03
Phase 03Construct
8–24 weeks · Portal04
Phase 04Activate
4–8 weeks · 30/60/9005
Phase 05Leverage
Ongoing · Run-tier01
Frame
Duration1–2 weeksPhaseScopingPricingFrom $7.5KCredits100% to Architect
Inventory your current stack, map the data flows between existing tools, name the migration risks, and build the 3-year Total Cost of Ownership model your procurement team will need. Inside the Audit: full source-system inventory, property and lifecycle map, integration retirement list, named cutover risks, recommended phasing, and 3-year TCO at three engagement-tier price bands.
You walk in with a fragmented GTM stack and walk out with a procurement-defensible scope plus a 3-year TCO model ready to take to the board.
Named artifactRevenue System AuditSource-system inventory · property + lifecycle map · 3-year TCO · cutover risks
02
Outline
Duration2–4 weeksPhaseDesignOutput30–50 page BlueprintReviewerProcurement + sponsor
Take the Audit's findings and produce the comprehensive system-design document. Every property to be created or migrated (named, typed, with validation rules). Every workflow (named, triggered, with branching logic). Every integration point (named, with mapping logic). Every custom object (named, with associations). Every lifecycle stage transition (named, with the event that triggers it). Every cutover risk (named, with mitigation).
Every architectural decision is named in writing so scope drift becomes architecturally impossible before any engineer-hour is billed.
Named artifactRevenue Architecture Blueprint30–50 pages · property + workflow + integration spec · cutover plan
03
Construct
Duration8–24 weeksPhaseBuildCutoverPhased per HubSign-offPer-Hub acceptance
Configure the HubSpot portal exactly per the Blueprint, with phased cutover per Hub and stakeholder sign-off at each gate. Handover includes per-Hub acceptance checklists, the workflow inventory with retention map, the integration runbook, data-integrity validation reports, rep enablement for user-facing changes, and the cutover log with sign-off signatures.
The portal you receive matches the Blueprint exactly, so you get the system your procurement team approved — not a vendor's interpretation of it.
Named artifactConfigured portal · Handover documentationPer-Hub acceptance checklists · workflow inventory · integration runbook · cutover log
04
Activate
Duration4–8 weeksPhaseHandoverCadence30 / 60 / 90 dayOwnerInternal admin
Catch the data drift, sequence sprawl, and integration exceptions that emerge in the first 90 days after a system goes live — before they compound into the 18-month break. Two artifacts ship: the 30/60/90 performance review (three data points with named exceptions, named root causes, named remediation) and the Operating Playbook (the runbook your internal admin uses to operate the portal after our team rolls off).
You get data drift caught at 30 days instead of at the board meeting, and your internal admin owns the system with a runbook in hand instead of a vendor's email address.
Named artifacts (2)30/60/90 Performance Review · Operating PlaybookThree data points · named exceptions · full runbook of workflows, properties, integrations, routing, reporting
05
Leverage
DurationOngoing · Run-tierPricing$5K–$25K/moMinimum12 monthsCadenceMonthly + quarterly
Operate the system on a calendar cadence. The monthly performance report covers data quality, workflow exceptions, integration health, lifecycle conversion rates, and reporting drift. The quarterly strategic review surfaces architectural debt before it becomes a re-platform decision. We are a HubSpot Gold Solutions Partner with an active pathway to Platinum, certified across all six Hubs — the Optimize layer is where that ongoing certification depth pays off.
The system stays healthy on a calendar cadence and architectural debt surfaces in the quarterly review instead of in a re-platform conversation at month 18.
Named artifacts (recurring)Monthly Performance Report · Quarterly Strategic ReviewData quality · workflow exceptions · integration health · architectural debt surfacing
What's the difference between a methodology and a process?
A methodology produces a named artifact at every phase that you (and your procurement team) can review before the next phase commits budget. A process produces a status update. The artifact is procurement-defensible and falsifiable at every gate; the status update is defensible only on trust. Every vendor calls their process a methodology; the test is whether they hand you something named you can review before the next invoice clears.
What does the Revenue System Audit include and how much does it cost?
The Audit is a 1–2 week paid scoping engagement, from $999. Inside: full source-system inventory, property and lifecycle map, integration retirement list, named cutover risks, recommended Architect phasing, and a 3-year Total Cost of Ownership model at three engagement-tier price bands. It's the document procurement signs the Architect SOW against or takes to another vendor. Either way it's yours to keep.
Does the Audit credit toward an Architect engagement?
Yes. 100% of the Audit fee credits toward an Architect-tier engagement signed within 12 months. For buyers who proceed, the Audit is effectively free. We do this on purpose: it removes the "will the cheap option bias the recommendation" question, because there is no commercial benefit to us biasing toward Architect over a smaller scope.
How long does the full Method take, end to end?
Discover is 1–2 weeks. Architect is 2–4 weeks. Engineer is 8–24 weeks — the variance is migration complexity and Hub count. Operate is 4–8 weeks of post-launch embedded support. Most Architect-tier engagements run 4–9 months end to end (Discover through Operate). Optimize is the ongoing layer that starts after, on a 12-month minimum.
Can I stop the engagement at any phase boundary?
Yes, that's the entire point of the methodology. After Discover you can take the Audit to a different vendor. After Architect you can operate the Blueprint with an in-house team. During Engineer you can hold any Hub from go-live until acceptance is met. After Operate you can transition into Optimize or own the system independently with the Playbook. Every artifact is built to a standard that holds up if you walk away with it.
What does the Revenue Architecture Blueprint actually contain?
A 30–50 page system-design document. Every HubSpot property to be created or migrated (named, typed, with field-level validation rules). Every workflow (named, triggered, with branching logic). Every integration point (named, with mapping logic). Every custom object (named, with associations and reporting role). Every lifecycle stage transition (named, with the trigger event). Every cutover risk (named, with mitigation). Our ICP-2 clients regularly adopt the Blueprint as their internal RevOps reference document after we roll off.
What's the difference between Operate and Optimize?
Operate is the 4–8 week post-launch handover phase that catches drift in the first 90 days — it's included in every Architect engagement. Optimize is the ongoing Run-tier engagement that operates the system on a calendar cadence with monthly performance reports and quarterly strategic reviews. Operate ships the Playbook so your team can run the system; Optimize is for buyers who want us to keep running it.
What kind of HubSpot work falls outside the Focal Method?
Quick-fix portal cleanups, one-off workflow builds, and template installs don't need a five-phase methodology but they need a HubSpot admin for two days. If that's the actual scope, we'll tell you in the first Discover call and point you at HubCrafted.
The Method is for buyers who are about to recommit budget to a revenue system and want the architectural decisions written down before they do.
Start with Discover
Book a Revenue System Audit. Walk out with a procurement-defensible scope.
Two weeks. One named architect. A 3-year TCO model and a recommended Architect phasing your board can sign against. Audit credits 100% toward an Architect-tier engagement — or it’s yours to take to another vendor.
HubSpot Gold PartnerActive pathway to PlatinumAll 6 Hubs certifiedCMS · Marketing · Sales · Service · Ops · CommerceAPAC · Globalmid-market focus5 phases · 5 artifactsEvery gate is yours to review