9 Questions to Vet a CRM Setup Service for Small Businesses

Finding a CRM setup service is easy. Finding one that actually delivers what it promises is harder than it should be.

The sales conversation is almost always good. Experienced team. Proven process. Realistic timeline. The gaps appear later, when the data migration arrives incomplete, when the workflows were never built, when your "dedicated contact" turns out to be a support inbox with a two-day response time.

These nine questions are designed to surface those gaps before you sign. They're the questions worth asking every provider on your shortlist, on the same terms, so you can compare answers honestly rather than comparing one agency's best moment with another's worst.

Question 1: How do you approach the scoping process before building anything?

Why it matters: A CRM setup that starts building before discovery is finished produces a configuration that reflects assumptions rather than your actual business. The pipeline stages will be wrong. The properties will be missing. The automations will fire on logic that made sense in theory.

What a good answer looks like: A discovery process that involves the people who will use the platform - sales reps, marketing managers, service team members - before any configuration starts. A written architecture document produced at the end of discovery, describing your specific pipeline, property structure, and automation logic, which you approve before the build begins.

What a weak answer looks like: "We have a standard template we customise for each client." Templates are fine as a starting point. They're not a substitute for discovery.

Question 2: What does your data migration process include?

Why it matters: For most small businesses, existing customer data -contacts, companies, deal history, activity notes - represents years of relationship-building. Migrating it badly means starting the new CRM with corrupt, duplicate, or incomplete records that undermine the team's trust in the platform from day one.

What a good answer looks like: A pre-migration audit of the source data, a field mapping document showing where each field lands in HubSpot, deduplication before the import runs, a test import on a sample dataset before the full migration goes live, and validation testing to confirm the data arrived correctly and with associations intact.

What a weak answer looks like: "We'll help you do an import." An import is not a migration process, it's one step in a migration process. Ask them to describe the other steps.

Question 3: Which integrations are native HubSpot connectors and which require custom development?

Why it matters: HubSpot's App Marketplace has over 1,700 integrations. Most are point-and-click to connect. Some use cases require custom development because a native connector doesn't exist or doesn't cover the specific data flow you need. The difference in cost, time, and ongoing maintenance between these two scenarios is significant, and it should be identified in scoping, not discovered mid-project.

What a good answer looks like: A clear assessment of every external system you use - accounting software, email, marketing tools, support platforms, industry-specific software - with each categorised as either a native integration or a custom requirement. For custom integrations, a specific scope and timeline, not a placeholder.

What a weak answer looks like: "We support all major integrations." Ask them to name your specific tools and tell you which category each one falls into.

Question 4: How is training structured across different roles?

Why it matters: A team of fifteen people doesn't all use HubSpot the same way. Sales reps manage deals and log activity. Marketers build workflows and review campaign reports. Service team members handle tickets and manage the conversations inbox. Training everyone together on a general platform overview produces a team that knows what HubSpot can do and is confident in none of it.

What a good answer looks like: Separate training sessions for each role, each focused on the specific tasks that role performs in HubSpot. Sessions recorded so new team members can access them when they join. Documentation specific to your setup, not a generic HubSpot user guide.

What a weak answer looks like: One training session for the whole team covering the full platform. That's an introduction, not enablement.

Question 5: What's your timeline from kickoff to go-live, and what drives it?

Why it matters: For a small business, a six-month implementation timeline is a significant distraction. But a two-week timeline that skips discovery, migration validation, and training is a risk. The right timeline is determined by the complexity of your specific requirements, not by what the agency has available or what sounds most competitive in a sales conversation.

What a good answer looks like: A timeline broken into phases - discovery and scoping, architecture design, build, migration, testing, training, go-live - with a realistic duration for each phase based on your specific requirements. A clear explanation of what could extend the timeline and what's needed from your team to keep it on track.

What a weak answer looks like: A confident timeline with no explanation of what determines it. Ask what would make the timeline shorter or longer, the answer reveals whether it's based on your situation or a standard pitch number.

Question 6: Who will actually do the work?

Why it matters: Agencies often sell with senior practitioners and deliver with junior staff. In a CRM implementation, the person building your pipeline needs to have absorbed everything from your discovery sessions - not received a one-page brief from someone who attended those sessions on behalf of the delivery team. Continuity of knowledge between the scoping conversation and the build is one of the clearest differentiators between implementations that work and ones that don't.

What a good answer looks like: A named implementation contact who will be your day-to-day person from discovery through to go-live, with a clear role description and enough seniority to make configuration decisions without escalating everything.

What a weak answer looks like: "You'll be working with our team." Ask specifically: who's the person leading the build, have they done this before for a business at our scale, and will they be the same person answering our questions in week six?

Question 7: What documentation will we have at handover?

Why it matters: Without documentation specific to your setup, the knowledge of how your CRM was built lives in the implementation team's heads. When you need to change something - a new workflow, a new pipeline stage, a new integration - you're either dependent on the agency or starting from scratch. When a new team member joins, there's nothing to hand them except a tour from whoever has the most context.

What a good answer looks like: A handover document that describes your specific portal - what each pipeline stage means and its entry criteria, what each active workflow does and when it triggers, which properties are required and why, how each integration is configured. This document should be part of the defined deliverables in the scope of work, not something offered as a courtesy.

What a weak answer looks like: A link to HubSpot's knowledge base or a promise that they'll "document as they go." Ask to see an example of the documentation they have delivered to a previous client.

Question 8: What does post-go-live support look like?

Why it matters: The questions, issues, and requirements that matter most appear after go-live, not during the build. A workflow that didn't behave as expected in production. A report that doesn't answer the question it was built for. A team member who needs help with something the training didn't cover. For Australian and New Zealand businesses especially, a support arrangement with an agency fourteen hours behind you is significantly less useful than one in your timezone.

What a good answer looks like: A named support contact with a defined response time. A clear description of what's covered in the post-go-live period and what falls outside it. An optional ongoing retainer for teams that don't have internal HubSpot capability. A structured check-in at thirty or sixty days post-launch to catch and fix issues while they're still small.

What a weak answer looks like: "We're always available if you need us." Ask what "available" means specifically, response time, hours of availability, and what happens if the issue is urgent.

Question 9: How do you measure whether the setup was successful?

Why it matters: A CRM implementation that's measured only by go-live date has no accountability for outcomes. The platform went live — but is the team using it? Is the pipeline data trustworthy? Is the automation producing the commercial results it was designed for? Success measured only by completion is a low bar, and it protects the agency more than it protects you.

What a good answer looks like: Specific commercial metrics agreed at the start of the engagement - platform adoption rate at 30 days, deal data completeness at 60 days, lead source attribution accuracy, and whether the pipeline reporting is driving decisions rather than being ignored. A setup service that defines success this way is accountable to outcomes, not just deliverables.

What a weak answer looks like: "We'll make sure you're happy with the outcome." Ask them to define what outcome they're committing to, in specific and measurable terms.

Wrapping Up

Ask all nine in your first proper conversation with every provider on your shortlist. Don't let one good answer or one impressive client name weight the evaluation, score every provider on every question and compare the full picture.

The providers who answer all nine with confidence, specificity, and without deflecting are the ones worth shortlisting. Vague answers on data migration, training structure, or post-go-live support aren't a sign that the agency is being modest. They're a sign that those things aren't their strength.

We have answers to all nine. If you want to hear them, let's talk.

Catch our latest HubSpot masterclasses and tutorials on YouTube, or join us over on Facebook for a healthy dose of marketing reality and HubSpot User Group event updates.

See you there!