HubSpot is usually bought in a good week and rebuilt in a bad one.
A couple of years in, there are deal stages nobody uses, three properties that mean the same thing, and a dashboard the sales team quietly stopped opening.
The tool is rarely the problem. The setup around it was never designed, it just accumulated, one urgent request at a time.
That is usually when teams start looking for HubSpot RevOps help, and the useful question is concrete: what does a working HubSpot RevOps setup include, and what should change in the first 60 days?
We answer it with two public client builds, a multi-region marketing agency and a Web3 funding platform, because they push HubSpot in very different directions.
Only Engaged Leads Go Into HubSpot
The first rule surprises people: the raw prospect list never touches HubSpot. Cold outreach runs in its own sending tools, and a contact only enters the CRM once they engage.
That one rule keeps everything downstream honest. Contact counts reflect real conversations, reports measure real pipeline, and reps open HubSpot to work leads instead of scrolling past thousands of cold records.
For Thrive Protocol, a Web3 funding platform, outreach ran across email, LinkedIn, Telegram and X. Every engaged project was captured into HubSpot automatically, so the team never had to copy a reply from one tool into another.
Custom Objects When Deals Are Not Enough
Standard HubSpot thinks in contacts, companies and deals. Plenty of businesses do not sell that way, and forcing them into deals is where most messy HubSpot portals start.
Thrive did not close deals. It moved projects toward funding applications across several partner ecosystems, so we built a custom HubSpot setup with objects for ecosystems, projects and applications.
Every project was tracked through the same stages: engaged, opened, replied, booked, applied. Over 12 months that system tracked 777 qualified meetings and 220 grant applications, each one traceable back to where it started.
The lesson travels well beyond Web3. If your team keeps a spreadsheet next to HubSpot to track the thing that actually matters, that thing probably deserves its own object.
Reporting Leadership Actually Uses
Podean, an Amazon marketing agency, ran outbound across 5 regions at once. Each region had its own market, its own message and its own pace, which is exactly how reporting turns into a pile of exports.
The fix was structural. Leads from every region flowed into HubSpot automatically, tagged by region, and leadership got one weekly report that compared regions side by side.
That report decided where to push. The program averaged a 13.2% response rate and 4.54% lead-to-meeting conversion, and the regional view showed which markets earned more volume and which needed tighter targeting.
The test of a RevOps dashboard is simple: does someone change a decision because of it this week? If not, it is decoration.
What the First 60 Days Look Like
Most HubSpot RevOps work follows the same arc, whatever the industry:
- Weeks 1-2: an audit of stages, properties, routing and data quality, mapped as they actually run rather than as the original setup intended.
- Weeks 3-6: architecture, routing and data hygiene shipped in stages, so nobody stops selling while the CRM changes underneath them.
- Week 7 onward: automation and reporting layered on top, then steady improvement based on what the data shows.
Most teams have pipeline data they trust within 60 days of kickoff. If you want to see what that looks like in a full build, the Thrive Protocol case study walks through it end to end.
The Questions We Get Asked
Do we need to rebuild HubSpot from scratch?
Almost never. We fix the portal in stages, keeping what works and replacing what does not, so the sales team keeps working while it changes.
Do we need a more expensive HubSpot tier?
Not by default. We build around the tier and tools you already have, and only suggest an upgrade when a workflow genuinely needs it.
What if half our work happens outside HubSpot?
That is normal. Outreach, billing and support often live in other tools, and the job is connecting them so HubSpot holds the records that matter, without becoming a dumping ground.