How to Vet a CRM Development Company Without Getting Sold a Guess

Ask this before you ask anything else: do you actually need one built?

For a lot of businesses, an off-the-shelf tool already covers quoting, dispatch, inventory and billing with a bit of configuration. If your process fits inside a general-purpose product, buy the license. Don't build.

We turn down projects like that regularly. Cases where a specialist would do better, or where an existing product already solves it for a tenth of the price. We say so on the first call, not the third.

The honest starting point for this conversation isn't the CRM. It's the spreadsheet everyone secretly runs the business on right now, the one with the tabs nobody wants to explain to a new hire. If that spreadsheet is genuinely bespoke, tracking things a general-purpose tool can't, that's a real signal. If it's a workaround for a tool your team never learned properly, that's a different problem. And a cheaper one to fix.

What a CRM development company actually builds, versus what you're buying with a license

A license gets you someone else's idea of how a sales pipeline should look, with configuration options around the edges. A custom build gets you quoting, dispatch, inventory, billing, workflow, roles and reporting built to match how your business actually runs. Not the other way around.

A build worth paying for also includes the parts vendors like to treat as extras. Importing data from your prior CRM should be part of the scope, not a change order two months in. So should integrating with the email, calendar, phone system and accounting software you already use, as part of the same project, not a separate negotiation once you're already committed.

Our own version of this, CRMs & internal tools, runs 8 to 18 weeks and starts at $38k.

Four questions to ask any CRM development company before you sign

Who owns the code? Ask exactly where the repository lives and whose cloud account the infrastructure runs in. Our answer: you own the code outright from day one, the repos sit in your organisation, and infrastructure runs in your cloud account, not ours. If a vendor's answer involves the words "shared" or "licensed back to you," keep asking.

How was this estimate built? If a number gets handed to you on a sales call before anyone has documented your workflows, ask what work happened before the number was written down. Usually the honest answer is: none yet.

Then there's the harder question, the one vendors dodge. What happens if the estimate turns out to be wrong? Scope changes should be priced before the work starts, not billed as an overage after the fact. If a vendor can't describe that moment concretely, assume you'll be arguing about an invoice later.

Last one. What happens if we stop working together? You should get a full handover — architecture walkthrough, runbooks, a support window with an end date you were told up front. For us, that's two weeks. Not a login that quietly stops working.

Why the number on a sales call usually isn't real

A number given before anyone has documented your workflows isn't an estimate. It's a placeholder that happens to have a dollar sign in front of it.

We run a discovery week before we quote anything real: a flat $4,800, credited back in full if you continue with us. It ends in a written scope, an architecture sketch, and a fixed estimate — not a range, a number. Estimates come after discovery, not before. That's the only reason ours holds once work starts. You can read what's actually in that week here.

What CRM & internal tools actually cost here, and how it's billed

CRM & internal tools run from $38k, typically 8 to 18 weeks, billed on milestones: 30% at kickoff, the remainder on phase acceptance, Net 14. Fixed-scope work includes 30 days of post-launch fixes, so the thing you signed off on gets a month of us watching it before you're on your own. You can see the full structure on the fixed-scope project page.

If the need isn't a single build but ongoing feature work, we also run a dedicated squad — one designer, two engineers, one lead — from $18k a month on rolling three-month terms.

Hold any vendor you're evaluating to this same standard: milestone billing, a stated post-launch window, terms you can read in one sitting.

Ownership, exit terms, and the security paperwork nobody wants to chase down later

We sign NDAs by default and complete vendor security questionnaires as part of onboarding, because in logistics, healthcare, fintech and insurance, someone on your side has to check that box before a contract moves. We don't hold formal compliance certifications. We'd rather tell you that plainly now than have it surface awkwardly during your own vendor review.

Code lives in your organisation from day one. Infrastructure runs in your own cloud account, not ours. If the relationship ends, you get the same handover regardless: architecture walkthrough, runbooks, two weeks of support. Not a scramble to find someone who understands what was built.

A named lead stays with the project from the first scoping call through launch. No handoff to whoever's free that sprint.