← ALL BLUEPRINTS / AGENT BLUEPRINT
Revenue analyst agent for a small financial services firm on HubSpot where marketing and sales report different quarterly numbers
A data agent that reconciles marketing and sales numbers against one governed metric dictionary, answers plain-English revenue questions with the definition and source shown, and sends a weekly executive digest that both teams sign off on. The result is one quarterly number per metric, with every gap between the marketing view and the sales view explained instead of argued about.
| ROLE | REVOPS / OPERATIONS | PLATFORM | HUBSPOT |
|---|---|---|---|
| INDUSTRY | FINANCIAL SERVICES | ||
| DRAWN BY | HACKING DEMAND | ISSUED | OCTOBER 23, 2026 |
What The Reconciler does
Every quarter the leadership meeting at this firm (a 30-person financial services company selling advisory and account services to businesses) stalls on the same problem: marketing reports one count of qualified leads and sourced pipeline, sales reports a different count of opportunities and funded accounts, and the CEO cannot tell which is right. The cause is usually not bad data but different definitions: marketing counts MQLs by form-fill date, sales counts opportunities by close date, attribution is first-touch in one report and last-touch in another, and funded accounts live in an onboarding system outside HubSpot. The Reconciler works for the RevOps lead and the leadership team. It owns a written metric dictionary (one approved definition per metric, with an owner), answers questions against those definitions using HubSpot and connected systems through MCP, produces a bridge that explains exactly why a marketing number and a sales number differ, and publishes a weekly internal digest. It is internal only. It never drafts client-facing or prospect-facing messages, and anything that would leave the building goes to compliance first. Because the firm chose build and maintain, the agent, connectors and dictionary are kept working by an outside team as HubSpot properties, pipelines and reports change.
Built on HubSpot
The firm already runs marketing and sales in HubSpot, so the disputed numbers start there, and HubSpot Breeze is a good fit for quick in-CRM questions and record summaries in the sidebar. Breeze alone cannot see the onboarding or accounting systems where funded accounts and revenue live, and it does not enforce a governed metric dictionary or produce a record-level bridge between two teams' numbers. A custom AI build on top of the HubSpot MCP server, plus read-only connectors to the other systems, covers that gap while keeping HubSpot as the system of record. Airtable holds the dictionary because RevOps can edit it without engineering, n8n handles the scheduled digest, exports and archive logging, and Databox can display the governed numbers for people who prefer a dashboard. For an 11 to 50 person firm without a data engineer, this avoids standing up a full warehouse on day one; a warehouse can be added later if more systems join.
What starts it
- A RevOps lead, marketer, salesperson or executive asks a question in the team chat channel or the HubSpot sidebar, such as 'How many qualified leads did we get in Q2 and why does sales show fewer?'
- Scheduled weekly run every Monday at 6 a.m. to build the executive digest and the marketing-to-sales bridge for the quarter to date
- A HubSpot dashboard report or saved view used in leadership meetings returns a number that differs from the dictionary-governed number by more than the tolerance RevOps sets
- A change to a lifecycle stage, deal stage, pipeline or attribution setting in HubSpot, which flags any metric definitions that may now be affected
- Quarter close, which triggers a full reconciliation pack for the RevOps lead to review before numbers go to the board or owners
What it reads
- HubSpot CRM through the HubSpot MCP server: contacts, lifecycle stage history, lead status, deals and deal stage history, campaigns and attribution reports
- Client onboarding or account-opening system (read-only API or nightly export) for funded accounts, account open dates and assets brought over
- Accounting or billing system for recognized fee revenue, so pipeline and revenue are never confused
- Paid media and webinar platforms (for example Demio) for spend and registrant counts that marketing uses in its own reports
- The metric dictionary, kept in Airtable, with definition, formula, source fields, owner, approval date and change log
- The firm's existing dashboards in Databox and HubSpot, read so the agent can explain any dashboard number that does not match the governed one
How it works, step by step
- Lock the definitions firstBefore any answers go live, RevOps, the head of marketing and the head of sales agree on definitions for the disputed metrics: what counts as a lead, an MQL, an SQL, an opportunity, sourced pipeline, influenced pipeline, a funded account and revenue. Each gets a formula, the exact HubSpot properties or external fields it uses, the date it is measured on, and an owner. The Reconciler only answers using approved definitions and says so when a question uses an undefined term.
- Answer questions with the receipt attachedWhen someone asks a question, the agent picks the matching definition, queries HubSpot and other systems through MCP, and replies with the number, the definition used, the date range and date field, the record count, and a link to a HubSpot list or report so the asker can check the records. If the question is ambiguous (for example 'leads' could mean contacts created or MQLs), it asks which one rather than guessing.
- Build the marketing-to-sales bridgeFor each disputed metric, the agent produces a walk from the marketing number to the sales number: records counted by one team but not the other, timing differences (created in Q1, converted in Q2), duplicates, contacts without an associated company or deal, deals with no original source, and attribution model differences. Each line shows the record count and a HubSpot list so the gap is traceable, not just asserted.
- Catch the data problems causing the gapThe agent flags the hygiene issues that keep creating disagreements: deals missing an associated contact, lifecycle stages moved backward, original source overwritten, duplicate companies, and funded accounts in the onboarding system with no matching HubSpot deal. It posts a short fix list to RevOps. It does not change CRM records itself; fixes are made by people or by an approved, logged n8n workflow.
- Publish the weekly executive digestEvery Monday, the agent assembles an internal digest: quarter-to-date leads, MQLs, SQLs, opportunities, pipeline, funded accounts and revenue against plan, each with its governed definition, the bridge summary, what changed since last week, and open data issues. RevOps reviews and approves the draft before it is sent to leadership, and the sent version is saved to the firm's recordkeeping archive.
- Close the quarter with one numberAt quarter end, the agent produces a reconciliation pack with the final governed numbers, the full bridge, any definition changes made during the quarter and their impact, and a list of adjustments RevOps made by hand. Marketing and sales leads sign off before the numbers go to owners or the board.
When a person takes over
- Definition disputes: when marketing and sales disagree on how a metric should be defined, the agent lays out both versions and the numeric impact of each, then hands the decision to the RevOps lead (with the CEO as tiebreaker). It never picks a definition on its own.
- Gaps it cannot explain: if the bridge leaves an unexplained difference above the tolerance RevOps set, the agent stops, posts the unresolved records, and assigns them to RevOps rather than smoothing over the gap.
- Anything that could become external: if someone asks the agent to turn a number into a client email, a marketing claim, a pitch deck stat or a press line, it declines to draft it and routes the request to compliance with the source data attached, because performance and business claims require compliance review under the firm's approved-language rules.
- Quarter-close sign-off: the final reconciliation pack goes to the heads of marketing and sales for approval before any figure is shared with owners, investors or the board.
Rules it follows
- Internal use only: the agent does not draft, send or schedule any outbound communication to clients or prospects. Any figure headed for customer-facing use is routed to compliance for review against FINRA and SEC approved-language and recordkeeping rules before it can be used.
- Recordkeeping by default: every digest, reconciliation pack and agent answer that informs a business decision is logged with timestamp, asker, definitions used and data sources, and the weekly digest is retained in the firm's approved archive so it can be produced on request.
- No client-level financial detail in chat: answers return aggregate counts and totals by default. Questions that would expose individual client account values or personal data are refused in shared channels and limited to users with matching permissions in HubSpot and the onboarding system.
- Read-only access: MCP connectors to HubSpot, onboarding and accounting are scoped read-only. The agent proposes fixes but never edits records, merges duplicates or changes properties.
- Show the definition every time: no number is returned without its definition, date field, date range and source. If a definition is missing or unapproved, the agent says so instead of improvising one.
How you know it works
- Number of open discrepancies between marketing-reported and sales-reported figures at each quarter close, tracked toward zero unexplained gaps
- Time from quarter end to signed-off reconciliation pack
- Share of agent answers accepted without a follow-up correction from RevOps
- Count of recurring data hygiene issues (missing associations, overwritten original source, unmatched funded accounts) week over week
- Hours RevOps spends each week assembling the leadership digest by hand
From pilot to live
- Phase 1: Definitions and one disputed metric (weeks 1 to 3)Run a working session to write the metric dictionary, connect HubSpot through MCP read-only, and point the agent at the single most argued-about number (usually MQLs versus SQLs or sourced pipeline). RevOps tests answers against known reports and builds the first bridge for last quarter to prove the gap can be explained.
- Phase 2: Cross-system data and the digest (weeks 4 to 7)Add the onboarding system and accounting through MCP or nightly exports so funded accounts and revenue join the picture. Turn on the Monday digest in draft mode, with RevOps approving each issue. Compliance reviews the guardrails, the archive setup and the refusal behavior for external requests before the agent opens to the wider team.
- Phase 3: Full team access and ongoing maintenance (week 8 onward)Open the agent to marketing, sales and leadership in chat and the HubSpot sidebar, run the first quarter-close reconciliation pack, and set a monthly maintenance review: check connector health, update definitions when pipelines or lifecycle stages change, and retest a fixed set of benchmark questions after every HubSpot configuration change.
Tools that fit
HubSpot
CRM and marketing software
Airtable
Visual data organization
n8n
Workflow automation platform
Databox
Dashboards and AI analytics
Demio
Webinar hosting software
Some tool links are partner links. Hacking Demand may earn a commission at no extra cost to you.
This blueprint is a version of The Revenue Analyst (data agent) ↗
Want The Reconciler built for you?
Our experts build it inside your stack. Then we hand it off, maintain it, or operate it with you. Agents and programs get better with tuning, so most teams keep us on to run them. Bring this blueprint to a scoping call.
Scope this agent ↗ Get your own blueprint ↗Good questions.
Straight answers.
Does an internal revenue agent fall under FINRA and SEC rules if it never talks to clients?
The agent itself is internal, but internal business records can still be subject to retention requirements, and any number that later appears in client or prospect communication is subject to approved-language and review rules. That is why the design archives every digest and decision-relevant answer, refuses to draft outbound content, and routes any request to use a figure externally to compliance. Have your compliance lead confirm the retention period and archive location before go-live.
Will the agent tell us whether marketing or sales is right?
No. It shows both numbers, the definitions behind each, and a record-level bridge explaining the difference. The decision about which definition becomes the official one belongs to your RevOps lead and leadership. Once that decision is written into the dictionary, the agent applies it consistently and flags any report that still uses the old definition.
What happens when we change our lifecycle stages or deal pipeline in HubSpot?
The agent detects the configuration change and lists which metric definitions depend on the affected properties. Under the build and maintain arrangement, the maintaining team updates the definitions and connectors, reruns the benchmark questions to confirm answers still match, and notes the change and its impact in the next digest so nobody is surprised by a shift in historical numbers.
Every good build
starts with a conversation.
New builds, remodels, and additions, powered by AI. Let’s plan the work.