Your sales team closes a deal on Friday. By Tuesday, the project manager is asking questions sales already answered three times during scoping. By the following Monday, finance is chasing invoice details that live in someone's inbox. This is what happens when you implement HubSpot for companies that sell projects using a playbook designed for SaaS.
The deal is marked Closed Won. Operationally, it's a black box. Sales has no idea what's happening in delivery. Delivery resents the handoff. Finance is reconciling margin in a separate spreadsheet two weeks after the fact.
Companies that sell projects have a fundamentally different shape than companies that sell products. The deliverable doesn't exist until it's built. Selling and delivering are connected — the salesperson promises something operations has to execute, and the margin depends on how cleanly that handoff happens.
Standard HubSpot implementations treat the deal as the unit of work. Deal opens, deal closes, contact gets tagged as customer, end of story. For a SaaS company selling the same product to every customer, that mostly works.
For project-based firms, that model deletes most of the operational reality. A single account can have three active deals at once. A single deal can spawn multiple projects. Each project has its own timeline, cost structure, and risk profile. None of that fits in a pipeline that stops at "Closed Won."
Most firms try one of two things. They buy HubSpot and configure it themselves, copying a template from a SaaS playbook. Or they hire a certified partner who configures it the same way, because that's what the certification trained them to do.
Both approaches end in the same place. A CRM that works for the first thirty days and then starts collecting dust. Sales updates deals when reminded. Operations works in Asana, Monday, or a stack of spreadsheets. Finance runs margin in QuickBooks or NetSuite and reconciles by hand.
The reason is simple: nobody designed the architecture before configuring the tool. They installed software without first defining how a project-based business actually operates digitally. Configuration without architecture is just expensive Excel.
To implement HubSpot for companies that sell projects properly, stop thinking of HubSpot as a CRM. Start thinking of it as the operating system for your entire commercial and delivery cycle.
That requires designing how every object connects before anyone touches the platform. Every project-based business runs on six interconnected objects. Get those right and HubSpot becomes the single source of truth from first conversation to final invoice. Get them wrong and you've built a sales tracker with extra steps.
Contacts represent humans. You track what stage each person is at, what they think of your firm, what their goals and pain points are, and where they sit in the buying group.
The test: can anyone on your team pick up a conversation with any contact after reading the record? If not, you don't have a CRM — you have a Rolodex with phone numbers.
Companies hold the permanent stuff. Fit with your offer. Sales signals. Ongoing projects. Churn probability. MRR where it applies. Competitive context.
The company record is where institutional memory lives. When the salesperson who owned the account leaves, none of this should walk out the door.
A deal represents a specific commercial interaction — not the entire client relationship. One company can have three open deals at once: a website conversation with marketing, a prospecting conversation with sales, an automation conversation with leadership. They might all roll into one engagement later, but right now they live in separate departments at the client. Your CRM has to reflect that or you lose visibility.
Critically, the deal pipeline doesn't end at Closed Won. It includes presale stages (discovery, scoping, proposal, negotiation) and post-sale stages (in progress, maintenance, closed). The salesperson should feel the deal is still alive after signature — because operationally, it is.
Tickets aren't customer support in this model. They're the internal unit of work for every team. Presale tickets: information gathering, blueprint design, proposal creation. Delivery tickets: kickoff, milestone reviews, QA, sign-off.
Each team gets its own ticket pipeline with its own velocity and KPIs. One deal might close with three tickets; another might need twelve. That's measurable now, which means you can finally compare which deal types are actually profitable to pursue.
Projects hold everything that lives after the contract is signed: costs, progress, documents, incidents, team members, pauses. A single deal can spawn multiple projects — a marketing engagement, a website build, and an analytics setup become three separate projects under one account.
Keeping them separate matters because each has its own cost structure, its own delivery team, and its own margin. Lumping them into one record erases the visibility that justifies the implementation in the first place.
The invoice object tracks every dollar in and out. Billed revenue. Project costs. Subcontractor payments. A rollup property on the deal sums associated invoices, giving real-time margin without leaving HubSpot.
If you have an ERP — NetSuite, QuickBooks, Sage Intacct, Acumatica — you integrate via a shared deal ID. One consistent field in both systems is enough. Margin per project becomes a property your CFO can pull on demand, not a quarterly Excel exercise.
The single highest-leverage moment in a project-based business is the transition from sales to delivery. It's also where most firms hemorrhage information.
The salesperson knows what was promised, why it was promised, and what the client actually cares about. None of that survives a verbal briefing two weeks after signature.
In a properly implemented model, the deal moving to Closing triggers an automated handover meeting. The agenda is already built from the presale tickets — every artifact, every deliverable, every signed document. After the meeting, the deal moves to In Progress and the salesperson can open the record at any point and see live project status, fees collected, fees outstanding, and critical incidents. No Slack message. No standup ambush. No "hey, quick question."
If you're starting from scratch or trying to fix a failed implementation, this is the order that actually works:
Here's what most firms miss when they implement HubSpot for companies that sell projects: the data structure you build today is the foundation for the AI you'll deploy tomorrow.
HubSpot's native AI can access every object in your portal. It can generate reports, answer questions, create records, recommend next actions. But it can only do that if the data is structured.
If your project information lives in someone's inbox and your costs live in a shared drive spreadsheet, AI has nothing to work with — it will hallucinate. If your past projects, costs, scope changes, and outcomes are properly modeled inside HubSpot, you can ask an agent: "Look at every project we've delivered in the last two years that resembles this new RFP and recommend how to structure the proposal." That's a question with a useful answer in seconds.
When the architecture is right, the daily friction disappears. Salespeople open a deal and see project status without asking anyone. Operations gets cleaner scoping inputs because tickets force structured handoffs. Finance pulls margin reports without reconciling spreadsheets. The CEO has live visibility into the business from a phone, anywhere in North America.
The bigger shift is cultural. Conversations stop being about "what's happening with this account" and start being about "what should we do next." That's the difference between running a services business and managing chaos that happens to generate revenue.
If you want to see exactly what this architecture looks like before committing to anything — the object model, the pipelines, the handover automation, the margin rollup — here's the complete model we implement. It's the same blueprint our clients approve before we touch their portal, which is the only honest way to buy this kind of work.