Why your CRM migration stalls in month two.
The kick-off feels great, the first sprint ships, then something goes quiet around week six. The pattern repeats — and it isn't the software.
Things we've learned implementing HubSpot for real companies. Written by the people doing the work. --since=2024, 47 entries.
The kick-off feels great, the first sprint ships, then something goes quiet around week six. The pattern repeats — and it isn't the software.
Most clients are paying for ~30% more seats than they're actively using. Here's how to find them and what to do about it.
Stop modelling what management wants to see. Model what reps already do — then tighten.
What you can do with native HubSpot, what you need integrations for, and where to draw the line.
The hardest part of an implementation isn't the implementation. Here's the playbook we run after launch.
An opinionated stack for ops teams under 200 seats. With reasons.
Three rules. Two examples. One bad pattern to never use.
Activity history, ownership chains, and the custom object you'll be tempted to leave behind.
What to look for, what the role actually is, and how to keep them for longer than a year.
A two-page checklist we run the week before every release lands.
What to run, who to involve, and a template that's saved our clients about $400K to date.
Weighted, judgment, AI — what to use when, and what to ignore.
The shape of post-launch support that actually drives adoption beyond 80%.
When the theme is good. When it isn't. What we recommend for our own clients.
The single most useful artifact we produce in week one. With template.
Notes from inside live engagements, edited down to what we wish we'd known earlier.
No newsletter slop. Unsubscribe with one click.