Where does a deal live at your MSP?
If the honest answer is “kind of both,” you’re in good company. HubSpot or Salesforce has the pipeline. The PSA has the client, the agreement, and every ticket since they signed. And somewhere between the two, a new client’s contact list exists in three versions.
This post is my take on which system should own what, where the handoff belongs, and where Go Fig fits.
I’ll be straight about that last part up front. Go Fig works in HubSpot, Salesforce, and all other major CRMs. It doesn’t replace your PSA, and it has no PSA connector. The longer version for MSP sales teams is on our IT MSP page.
What does a PSA do for an MSP?
A PSA (professional services automation) system is where an MSP’s service side runs. ConnectWise PSA, Autotask, and HaloPSA are the names you’ll hear most.
The core is much the same across them:
- Service desk. Tickets come in, get routed, and get worked against SLAs (service level agreements).
- Time. Technicians log billable and non-billable time against tickets and projects.
- Agreements. The managed services contract, what it covers, and how it bills.
- Billing. Recurring invoices from agreements, plus billable time and products.
- Projects. Onboardings, migrations, and other multi-step work.
- Reporting. Utilization, profitability, and service levels.
Many PSAs also ship sales features. ConnectWise PSA tracks sales opportunities and a pipeline, and its higher tier adds quotes and proposals. HaloPSA lists sales and CRM features and a quotations module.
So “HubSpot vs. your PSA” is a real choice, not a trick question.
What do HubSpot and Salesforce do best?
They’re built around the buyer, not the ticket. Contacts and companies, deals moving through stages, and the calls, emails, and meetings logged against each one. In HubSpot’s case, marketing lives in the same system, so the first touch, the deal, and the forecast sit in one place.
A PSA’s sales features are built around the service record. They know the client, the agreement, and the tickets. That’s the right center for delivery, and usually not the one an AE wants to work from all day.
That’s why plenty of MSPs keep the pipeline in a sales CRM and the service in the PSA. ConnectWise’s own marketplace lists a HubSpot integration for syncing the two.
Which system should own what?
Here’s the rule I’d use: one owner per record. Every field that matters gets one system that is its single source of truth. The other system reads a copy or leaves it alone.
Two systems editing the same field is how a client’s billing contact ends up right in one place and wrong in the other. Nobody notices until an invoice goes to someone who left last year.
| Record | Owner | Notes |
|---|---|---|
| Prospects and new contacts | CRM | They don’t belong in the PSA until there’s a client to serve |
| Deals, stages, close dates, and amounts | CRM | This is the pipeline your AEs and your forecast run on |
| Calls, emails, meetings, and notes on a deal | CRM | Logged on the deal so the next person can pick it up |
| Quotes | Your quoting tool or PSA | The CRM carries the amount on the deal |
| Signed agreement | PSA | The CRM keeps the closed deal and the notes behind it |
| Tickets and SLAs | PSA | Service delivery, start to finish |
| Time and billing | PSA | Driven by the agreement |
| Onboarding project | PSA | The CRM holds the handoff notes from sales |
| Client company and contacts after close | Pick one | The other system reads a copy, synced one way |
| Renewals | Split | The agreement end date in the PSA, the renewal deal in the CRM |
| QBRs | Split | Service data from the PSA, notes and next steps in the CRM |
The two split rows are where most of the confusion lives, so here’s how I’d handle each.
Renewals
The agreement’s end date belongs in the PSA, because that’s where the agreement lives. The renewal conversation belongs in the CRM as its own deal, with a stage, a close date, and an amount, because that’s where the AE works.
Open the renewal deal well before the end date. Then it shows up in the pipeline review and the forecast instead of surprising someone in the last month.
QBRs
A QBR (quarterly business review) draws on service data, like ticket trends and project status, that only the PSA has. What comes out of it is sales work. The notes, the action items, and the next project to scope belong in the CRM.
Where should the handoff between HubSpot and the PSA happen?
At closed-won. That’s the moment the deal stops being a sales record and starts being a client.
Write down what moves, who moves it, and when:
- The company and primary contacts. Created in the PSA from the CRM, once, then kept in sync in one direction.
- The signed agreement or statement of work. Attached to the client in the PSA, so service knows what was sold.
- The scope notes. What the client cares about, what you promised, and who their technical contact is.
- The kickoff. A date, an onboarding plan, and an email to the client that says what happens next.
If you sync the two systems, keep it narrow. Decide which system owns each field before you turn anything on. A two-way sync on a field both teams edit will overwrite somebody’s work, and the data silo you were trying to fix becomes two systems that disagree.
Can an MSP run sales entirely in the PSA?
Yes. Some do, and it can be a reasonable choice for a small team with a simple motion. One system means no sync and no handoff.
The trade-off is that the PSA’s sales features are built around the service record. If your AEs live in the inbox, run a lot of discovery calls, and want marketing and sales in one place, a sales CRM fits that work better.
Here’s the honest part. If your AEs work entirely in the PSA’s sales features, Go Fig is not a fit today. Go Fig works in HubSpot, Salesforce, and all other major CRMs, and it doesn’t read from or write to ConnectWise, Autotask, or HaloPSA.
Where does Go Fig fit between HubSpot and the PSA?
On the CRM side, up to the handoff.
Go Fig is the sales admin for account executives at IT managed service providers (MSPs). It helps an AE stay on top of their pipeline and move deals forward in HubSpot, Salesforce, and all other major CRMs, and it does not replace the PSA.
Here’s the split in plain terms:
- In the CRM. Go Fig logs calls and notes on the right deal and keeps stages, close dates, and amounts current. Every night it checks for deals with no next step, close dates that already passed, and missing amounts. It works in HubSpot and Salesforce.
- In the inbox. It drafts follow-ups in your voice and sends them from your own Gmail or Outlook after you approve.
- At the handoff. It has the kickoff email, onboarding plan, and account notes ready when the deal closes.
- What stays with your team. Setting up the client in the PSA, building quotes, and everything on the service side.
Every change Go Fig wants to make waits for your OK. Client emails and stage changes always will. You can let internal updates, like logging a note, run on their own and take that back anytime.
It doesn’t build quotes either. Quoting stays in your quoting tool or PSA. On the Team plan, Go Fig can draft proposals and statements of work from email, the CRM, or a PDF.
The full split, with a table of where each piece of work lives, is on the IT MSP page under your PSA stays your PSA.
Talk it through on your own setup
Every MSP splits the work between its CRM and its PSA a little differently. On a 30-minute demo, a solutions engineer connects your CRM and inbox with you and shows where Go Fig fits in yours.