Revenue Hub contracts
Six weeks on your own portal, and your team runs it at the end.
HubSpot finally shipped an object for the thing every portal has been faking — what a customer actually committed to, and what has changed since. This is working sessions on your real contracts rather than a course, and it is done with you rather than for you, because the scarce thing here is the judgment and judgment does not transfer by being explained to you. You leave with the architecture decided, the object live, and your own team operating it.
Why this exists
A closed-won deal is the start of a customer's commitment with your organization, not the end of it. But there was never an object for what comes after the signature — so we all built one. Custom date properties. Secondary records standing in for renewals and changes. One deal, somewhere, carrying the whole question of what this customer is currently subscribed to.
Those workarounds were often elegant, and they were the only move available. They aren't anymore. The companies that move first get to decide the architecture before they have another two years of workaround to unwind.
What happens in the six weeks
Where you actually are
Your portal, read back to you — what's carrying the subscription question today, and the architecture decision nobody has made yet. We make it in week one, before anything gets configured.
The product library is a schema decision
Pricing models, price books, rules, discounts — and what each one commits you to downstream. This is the hardest thing in the build to reverse, so it goes early.
Contract structure and terms
Grain, dates, renewal treatment. What one contract means in your business, and which of the three clocks — effective, billing, recognition — each of your fields is actually holding.
Mid-contract change
Expansion, contraction, proration, and the question a diagram can't carry: who is allowed to approve what, on their own authority.
Renewals and the money seam
The renewal motion as a real process, and what finance needs to receive at each event — in their format, at the moment it happens.
Live, and handed over
Your contracts running on your real data, and your team walked through operating it. The engagement's success condition is you not needing me afterward.
What you’ll learn, in detail — the seven judgment calls the six weeks are built around, and how each one is supported.
How the support actually works
The reason this isn't a course is that the information was never the hard part. What's hard is the judgment calls on your own portal, in the week you're making them.
A portal audit you couldn't run by hand
Week one opens with a complete read of your portal — every workflow, pipeline, form, sequence, scoring rule, dashboard and report, not a sample. It's AI-driven, which is the only reason it can be done properly in a week rather than a quarter. You keep the read whatever you decide afterward.
The methodology underneath the architecture questions
The questions we work through — what a process should be before what a system does, outcomes over activity, your team owning what gets built — come from the Value-First methodology developed by Chris Carolan and the Value-First Team. I'm a delivering member of that team, and this work runs on that frame rather than my opinions.
You are not just getting me
Sessions bring in practitioners, coaches and consultants from the Value-First Team and Collective — people who have built this in real portals under real constraints, not presenters working from a deck. Which ones show up depends on what you are actually wrestling with, which is the point: you get the person whose craft matches your problem rather than whoever was scheduled.
You see the AI system, not a slide about it
Most people talking about AI in operations are describing something. I'll show you the actual system we run our own delivery on — how an agent gets scoped, how a write to a client's system gets validated before it lands, how a finding ships with the query that produced it. Then you leave with a version of it scoped to your own portal.
A shared channel, and an answer the same day
Not a support queue. The same way I work embedded with clients: when something is important you raise it in the moment rather than saving it for the next session, and you get an answer that day. The things that need a screen rather than a thread, we put on a screen.
Just-in-time, which is the only kind that lands
Support where support is needed, at the moment it's needed. We listen, we understand, and we deliver value in the only way value can be delivered — close enough to the work that you can actually use it. The six scheduled weeks are the spine; the value shows up in between.
What you leave with
- Contracts live in your own portal, on your real data — not a sandbox.
- The decision memo: who may approve what, with names against it. The artifact a target-state diagram can't hold.
- Your own AI operating pack — agents scoped to your portal, your conventions, your context, and a delegation map for your team.
- The week-one portal audit, yours to keep whatever you decide afterward.
Who this is for
- You run HubSpot, and you sell on subscription, contract, or renewal — including a maintenance or service agreement behind something you installed or sold once.
- Someone on your side can do the work. This is done with you, not for you.
- You have real contracts to model — the messy ones are the useful ones.
Who this is not for
I would rather lose the sale on the first call than have you six weeks in, wishing you had spent the money differently. Each of these has a better answer than this, and I will point you at it.
- You do not sell anything with a term
- If every sale is one and done — no renewal, no subscription, no multi-year commitment — there is nothing here to model. The object exists to hold what a customer committed to over time. Without that, you would be paying to solve a problem you do not have.
- HubSpot is not going to be your system of record
- If the honest answer for your business is an ERP, or your CRM is genuinely Salesforce and will stay that way, six weeks of this is six weeks pointed the wrong direction. I will say so on the call rather than take the money.
- Your billing is on fire right now
- If invoices are going out wrong this month, you do not need six weeks that move at the pace of considered decisions. You need someone to stop the bleeding. That is a different and faster conversation, and I would rather have that one with you.
- You cannot work on your real portal
- Some organizations cannot put production data in front of an outside party. That is a legitimate constraint, not a failing. But the method runs on your actual messy contracts — a sandbox version teaches the mechanics and leaves the hard part untouched, which is not what you would be paying for.
- Whoever does the work has to take every decision back to someone who is not there
- Then six weeks becomes six weeks of waiting. If the architecture calls genuinely live above the person who would come, either bring that person for the weeks that need them, or wait until you can. The decisions are the deliverable.
- You need it generally available, with a support agreement behind it
- The contracts layer is in beta and it moves. Some organizations cannot build on that, for sound reasons. Wait for GA — I will still be here, and you will have lost less than you fear, because the architecture questions do not change when the status does.
- You would rather it were done for you
- That is a build engagement and I would rather sell you that honestly than watch you sit through working sessions you did not want. It is often the right call.
- Nobody on your team has six weeks of working sessions in them
- This does not land as something you attend. If the calendar genuinely is not there until the new year, start then — it will be better by then anyway, partly because of what the work between now and then teaches me.
Not sure which of those you are?
There is a free nine-question read that will tell you. It is what I ask on a first call — how a closed deal becomes money at your company — and it will say plainly if the answer is that you do not need any of this. Nothing is captured; I only see it if you decide to send it.
Take the readiness readWho to bring
Bring the people the decisions belong to rather than a delegate. You need the first one. The work is materially better with the second.
- Whoever owns the portal
- RevOps lead, HubSpot admin, ops manager — the person who will make the architecture calls and do the build. If only one person comes, it is this one.
- Your finance counterpart
- Controller, AR, finance ops. They are the ones receiving whatever this produces, and the handoff between them and sales is most of what we are fixing. Bringing them turns a build into an agreement.
- Whoever runs deal desk or sales ops
- Quotes, approvals, discounting, and the question a diagram cannot carry — who is allowed to approve what, on their own authority.
- A developer, if you intend to build on the API
- Optional. Worth it if a customer-facing surface is anywhere in your plans, because that is a real build rather than configuration.
- Or one person wearing all of it
- At a smaller company that is normal, and it works. You are the whole handoff, which means you can decide in the room instead of taking it back to three people.
Who is running it
I run this with HubSessed and the Value-First Team rather than alone, which is why a question outside my own craft gets answered by the person who actually holds it. You get them, rather than my best guess at what they would say.
The part you should hear before you start
The contracts layer is in beta. It changed once mid-flight while I was building on it, and it will change again. I think being early is worth it — you get to decide your architecture before you have years of workaround to unwind, and almost nobody has shipped on this yet. But you should hear that from me now, not in week three. Questions I can't answer, I take to HubSpot's product team; I have direct lines to the people who own this area and I use them.
How it works, and what it costs
- Which mode you are in decides everything
- Contracts as your term of record is reversible. Contracts that bill is not, once one is activated. Most companies who say they just want their contracts in HubSpot want the reversible one and reach for the irreversible one by default, because it is the one that sounds finished. These are genuinely different pieces of work, which is why the number comes after I have read your situation rather than before.
- Priced after the first call
- Thirty minutes on your portal tells me which mode you are in, what your contract book actually looks like, and whether billing has to move. I would rather price that honestly than put a figure on a page that turns out to be wrong for you in either direction.
- One company, however many people
- The fee is per company, not per seat. Bring your RevOps lead, your Finance counterpart and whoever runs sales ops — the handoff between them is most of what we are fixing, so having them in the same room is the point rather than an upsell.
- Every session recorded
- Yours to keep. The person who could not make Tuesday, and the person you hire in March, both get the whole thing.
- If you'd rather I build it
- Then I would rather sell you that, and say so early. What you have spent here comes off a build engagement within 90 days.
- If you aren't live at week six
- We keep working until you are.
Questions people actually ask
Do we need a particular HubSpot tier?
Creating quotes needs Revenue Hub Professional or Enterprise. A contracts-only setup — contracts as your term of record, without running quoting through the new editor — runs on a single seat, with the rest carried by automation. That is a materially cheaper entry than most people assume. We read your specific portal before you start rather than after, and if the maths does not work for you I will say so on the first call.
Is the contracts layer generally available?
No. It is in beta, enrollment is per portal, and checking yours is part of week one. Being early is both the reason to do this now and the reason you are hearing the risk on this page rather than in week three.
Is this an official HubSpot program?
No, and I want to be precise about that. It is run with HubSessed and the Value-First Team. I have direct lines to the people who own this area at HubSpot and I use them, but nothing I tell you here is a HubSpot commitment or a roadmap promise.
Our accounting lives in NetSuite, QuickBooks or Xero. Does that rule us out?
It changes what live means for you, not whether this is worth doing. Two questions set the complexity of any billing migration: whether you are bringing payment methods across, and whether you need historical revenue-change events to show up in contract reporting. We answer both for your situation in week one, before anything is configured.
Do we have to move off subscriptions?
Not as a precondition. Whether you migrate subscriptions into contracts, run them alongside for a period, or leave them where they are is one of the architecture decisions we make on your real data. Doing it in the wrong order is what hurts — not doing it at all.
How much of our week does this take?
We set the rhythm in week one against your actual calendar, because the cadence that fits a quarter-close week and the cadence that fits a quiet one are not the same cadence. What is fixed is that the sessions are worked on your own portal, so the preparation and the session are largely the same thing rather than homework on top. Week one and week six are heavier than the middle.
What if HubSpot changes something mid-build?
It already changed once while I was building on it — an endpoint moved underneath me. If something moves during your six weeks we cover it in the week it happens rather than teaching around it. That is part of what you are learning: how to hold a build steady on a surface that is still moving.
Could you just build it for us instead?
Often that is the right answer and I would rather sell you it honestly. If you decide that partway through, what you have spent comes off a build engagement within 90 days.
Wish we covered something else? Say so.
This is genuinely new capability — for you, for me, and to a real extent for HubSpot. Nobody has a finished curriculum for it yet, and anyone claiming one is describing something they read rather than something they built.
What is on this page is what I currently believe is worth six weeks of your time. If the thing you actually need is not on it, tell me, and we will look at whether it belongs — before we start or while we are running. I would rather reshape a week than run a session that misses what you came for.
Tell me what to coverOr bring it to the first call — that conversation is the same conversation.
You are closer to this than you think
Most companies can see their sales pipeline in one system and their actual money — invoices, what got paid, what renews — somewhere else entirely. Nobody can see the whole line from someone showing interest to cash landing, so Finance and Sales each hold half a picture and argue about which half is real.
The whole line in one place is what people mean by a unified revenue view: marketing touch, deal, quote, the committed agreement, what gets billed, what actually got paid, what renews. Not a report stitching systems together after the fact — one connected set of records where the money and the relationship are the same data. Until recently you got that by spending a very large amount on an ERP implementation.
That is what changed. And when I look at most portals, the distance to it is far shorter than the people running them believe — the pieces are mostly there and nobody has connected them. Six weeks is not an ambitious timeline for this. It is roughly what it takes.
The first thing is a conversation, not a proposal.
Thirty minutes where I read your situation and tell you honestly whether this is the right thing for you. Some companies need the free audit and their own team and nothing else. Some need a build rather than six weeks of working sessions. I'll say so.