Right-tool, not house-tool

Most consulting shops sell what they know. If the agency lives in HubSpot, you’re getting a HubSpot build. If the partner is certified in Salesforce, you’re getting Salesforce. The recommendation arrives before the discovery call ends because the conclusion was already in the room.

We try not to do that.

The principle has a name on our approach page: right-tool, not house-tool. It sounds obvious. It is not common. And once you start looking, you’ll see the alternative everywhere — the proposal that opens with a logo, the “audit” that ends with the same toolchain the consultant’s last six clients got, the implementation that bends your workflow around someone else’s roadmap because the consultant’s billable hour depends on familiarity.

Why the default fails the client

The economics are simple. A consultant who knows one stack deeply has a higher hourly margin on that stack than on anything else. They can ship faster, debug quicker, charge more confidently. So they sell what they know. The client gets the tool the consultant likes building in — not the tool that fits.

That works fine for the consultant. It works less fine for the operator who, two years later, is paying $48,000 a year for seat licenses on a platform that solves problems they don’t have, doesn’t solve the problems they do, and can’t be exited without a migration project as expensive as the original build.

The right-tool principle is not anti-platform. We use HubSpot when HubSpot fits. We use Airtable, Notion, custom builds, Postgres, the same names everyone else uses. The point isn’t which tool. The point is which question gets asked first.

What week 1 actually looks like

When we start a CRM engagement, the first two weeks are audit. No tool gets named. The conversation is about your team.

We shadow the sales motion. Who picks up the phone first. What happens between “they replied to the form” and “we sent the proposal”. Where the data lives now — the spreadsheet, the email chain, the one consultant’s Google Drive, the CRM nobody finished migrating off. We interview the people who actually do the work, not just the person who signed the contract.

The questions sound boring on paper:

• How many opportunities are open right now, and where would you look to find that number?
• What is the thing your team is doing at 3pm on a Wednesday that they hate?
• When a deal closes, what is the manual handoff to delivery that nobody has time to write down?
• What’s the report you keep meaning to build and never have?
• If you left for a month, what would break first?

The answers tell us the shape of the system before we name a single product. By the end of week 2, we know whether you need a CRM at all (sometimes the answer is no — sometimes it’s a clean Airtable and a scheduled report). We know which integrations matter and which are vanity. We know what the team will actually use versus what looks good in a demo.

Then we pick the tool.

Strong opinions, weakly held

Right-tool is not the same as no opinions. We have them. We will tell you HubSpot’s pricing ramps fast once you grow past the free thresholds — many teams underestimate where they’ll land. We will tell you Salesforce is over-scoped for a fifteen-person services firm. We will tell you the custom build is the right answer when you have unusual data, a team that can own it, and a five-year horizon.

But those opinions are arguments, not announcements. They live downstream of the audit. They change when the facts change.

That’s the difference between “we use Tool X” and “for what you described, here’s why Tool X”. The second one is reversible. The second one lets you push back when something doesn’t match your reality. The second one survives the engagement, because the reasoning is documented and your team can re-decide if your situation changes.

What this costs us

Being honest about this: the right-tool principle is a worse business model than house-tool consulting. We invest in tools we’ll use for one client and then not the next. We pass on work where the fit is wrong. We can’t cross-sell a stack. We don’t get partner commissions because we won’t take them — they corrupt the recommendation.

We are okay with that. The alternative is a practice where every engagement starts with the same answer, and the only variable is which client gets sold which thing. That’s a sales motion, not a consulting practice. We’d rather stay small and stay honest.

If you’re scoping a CRM right now, ask the next three people who pitch you the same question: what would have to be true about my business for you to recommend against your usual stack? If they can’t answer it specifically, you know what they’re selling.

If this is your shape

You’ve outgrown the tools you have. You’ve talked to two or three shops. You can feel them positioning you for their stack before they understand your business. You want someone to spend the first two weeks listening instead of selling.

That’s what we do. A discovery call is thirty minutes, no deck.