I'm explaining it to someone else · 5 min read
The words that survive the room
You are a HubSpot rep, a RevOps lead or an ops person carrying this to the people who decide, and you need the words to survive the room.
If you have five minutes
- Whoever signs for the seat is asking three things: will I finally get a number I trust, what does it cost me, and will it make someone's day worse. Answer all three or the page is read and not acted on.
- Say you will stop being the last to know. Do not say we will automate your invoicing. Ask for the reversible thing first. Bookings, billings and revenue are three numbers with three owners.
- HubSpot can be the receivables ledger and does no revenue recognition. Those are two different people with two different worries, and one message aimed at both reaches neither.
The conversation at the top is a different conversation
Whoever signs for the seat is not asking what the product does. They are asking whether they will finally get a number they trust, what it costs them to get it, and whether it will make someone's day worse. If the page you forward answers the first question and not the other two, it will be read and not acted on.
Say this, not that
- Say: you will stop being the last to know
- Finance finds out a deal closed when the customer calls asking for an invoice. Sales finds out billing went wrong when the customer complains. The agreement in one place fixes the moment each side learns something. That is the benefit, in their terms.
- Do not say: we will automate your invoicing
- Re-keying a closed deal is not only overhead. It is the checkpoint where a controller catches the wrong term, the missing PO number, the discount nobody approved. Offering to remove it sounds like a benefit and lands as removing their control. The honest version is that the check moves earlier, to quote time, when a change is still cheap.
- Ask for the reversible thing first
- Not "let HubSpot bill your customers." Rather: "let HubSpot hold what was agreed, and leave your billing where it is." Finance gets visibility they do not have today, nobody's invoicing changes, and if it does not work the record gets deleted. This is what earns the second meeting.
- Bookings, billings and revenue are three numbers
- Committed, invoiced, earned. They diverge legitimately and each has a different owner. When someone in the room says revenue, find out which one they mean before you answer.
The words, and what each mistake costs
The failure in these rooms is not technical. It is using CRM vocabulary for finance concepts and losing the room in the first ten minutes. Not a glossary; a glossary tells you what a word means. This tells you what the mistake costs.
| Term | What it means | What loses the room |
|---|---|---|
| Bookings, billings, revenue | Committed, invoiced, earned | Using them interchangeably. Three reports, three owners |
| TCV, ACV, ARR, MRR | Total contract value, annualised value, annual and monthly recurring revenue | Quoting whichever is largest. Ask which one the board sees |
| Deferred revenue | Cash or billing received before the revenue is earned | Calling a prepaid annual contract revenue you booked in January |
| Revenue recognition | Revenue recognised as obligations are satisfied, often nothing to do with the invoice date | Treating it as a reporting preference rather than an audited obligation |
| Subledger | The detailed ledger that feeds summary entries to the general ledger | Leaving open whether HubSpot is becoming one. There can only be one for receivables |
| DSO and aging | Days sales outstanding; receivables grouped by days overdue | Not knowing DSO is the number the collections team is measured on |
| Dunning | Automated, escalating payment reminders | Not recognising that HubSpot's invoice reminders are dunning, and that tone is a policy decision |
| Credit memo | A document that reduces an invoice balance | Suggesting they just edit the invoice. Issued documents are never edited |
| Proration | A partial-period charge on a mid-term change | Not warning the billing team before the first prorated invoice lands |
| Period close | The monthly lock on the accounting period | Scheduling anything during it |
Receivables and recognition are different questions, and HubSpot does one of them
One deal shows it. A twelve-thousand annual contract, invoiced upfront on the first of January, paid on the fifteenth.
| Date | What happened | Receivable | Deferred revenue | Revenue recognised |
|---|---|---|---|---|
| Jan 1 | Invoice issued | 12,000 | 12,000 | 0 |
| Jan 15 | Customer pays | 0 | 12,000 | 0 |
| Jan 31 | One month delivered | 0 | 11,000 | 1,000 |
| Dec 31 | Twelfth month delivered | 0 | 0 | 1,000, cumulative 12,000 |
So the sentence to hold on to
HubSpot can credibly be the receivables ledger: it issues invoices, tracks who owes what, ages it, reminds and collects. It does no recognition: no performance obligations, no deferred revenue schedule, no journal entries, no close. Those are two different people with two different worries. The collections lead cares whether their day gets worse; the controller cares whether the close survives an audit. Do not walk in with one message for both.
Five questions they will ask, and the honest answers
- Does this replace our accounting system? No. It becomes the system of record for the agreement and the billing event. Recognition stays where it is.
- Which system is the ledger for what customers owe us? That is theirs to decide, not yours to answer. Say so, and get it in writing.
- What happens at close? Ask for their close calendar before committing to any date.
- Who can authorise a credit memo? If nobody has decided, that is an audit finding waiting to happen, and naming it earns credibility.
- Is the record the agreement? Almost never. The legal text lives elsewhere; the record is the operational version of it.
Where the money stops today
If you want a diagnostic that takes one meeting, follow one closed deal from the handshake to the first paid invoice and ask both sides what happened. The gap between what sales thinks happens after closed-won and what finance describes is the finding, and neither side has ever seen it. Six places it breaks: how finance finds out the deal closed, how terms become a billing schedule, how the signature reaches the system of record, how a mid-contract change gets communicated, how a renewal gets noticed, and what happens when collections chases a customer nobody in the room knows.
If you are a HubSpot rep and the customer says their proxy is humming
Believe them. It probably is, for the person who built it. Then ask who else can read it, what happens when that person is on holiday, and whether finance would put the number in front of the board. A humming proxy is a one-person system, and the conversation is not about replacing it, it is about what it cannot show them.
Where to next
Where this comes from
- Ryan's stakeholder briefing pack and vocabulary card. the four rules, the terms, and what each mistake costs; authored 2026-08-16 and 2026-08-17
- The Sales-to-Finance handoff audit. the six seams and the one-deal diagnostic, from the finance-audience program of 2026-08-16
- HubSpot's Contracts session for admins, 2026-06-25. the questions admins actually asked, and HubSpot's answers
What we do not know yet
- Finance has never spoken in the seven hundred and ninety-four conversations this material was built from; it appears only in the third person. Whether a controller feels this as a problem is being measured, not assumed.
- The one-deal handoff audit has been designed and not yet run at sample size, so the objection list here is what practitioners and HubSpot's own staff have said, not yet what controllers have.
Mid-way through a quote-to-cash build, or stuck on one?
Come walk through it on the show and we will work it out on air, weekday mornings.