The Right Questions to Ask Before You Pick a CRM Setup Partner

The number of agencies offering to set up your HubSpot has grown at roughly the same rate as the number of businesses discovering that migrating a working, if messy, CRM is harder than the sales team made it sound.

Some of those agencies are excellent. Some are competent at the basics and out of their depth beyond them. And some are very good at a discovery call and considerably less good at delivering what was discussed in it.

This guide is for a 60 to 200 person Australian business that already has systems in place, an existing CRM, a spreadsheet-and-inbox hybrid, or a HubSpot portal that never got finished properly, rather than one starting from a blank account.

Start With What You Actually Need

Before you speak to a single provider, get clear on your own situation. The most common reason a CRM setup goes poorly is that the business didn't define what success looked like before the engagement started, so the provider defined it for them, usually in terms of deliverables they were already confident delivering.

Work through these four questions first.

What's actually migrating, and from where? At this scale it's rarely a blank account. It's a previous CRM, several spreadsheets some teams still trust more than the system, or a partially built HubSpot portal that needs untangling. Each of these carries different risk and a different timeline, and the honest answer here shapes everything a provider quotes you.

What does your team look like, across which departments? How many people will use the CRM, in which roles across marketing, sales and service, and what's their current comfort with the platform? A business with a RevOps hire already in place needs a different kind of onboarding approach to one where nobody has owned the CRM before.

What do you need operational in ninety days? Not eventually, in ninety days. This forces prioritisation and gives you a concrete benchmark against which to judge a provider's proposed timeline.

Do you need ongoing support or a one-time build? A CRM that's set up and handed to an internal team needs different deliverables to one a provider will keep maintaining. Decide which model suits your team before the conversations start, and be honest about whether the people who sign off on it across departments actually agree on the answer.

What a Good CRM Setup Service Actually Delivers

This is the list to test every provider against. A credible setup service delivers all of it. A partial setup delivers some and calls it done.

Pipeline configuration built for your sales process

Not HubSpot's defaults, yours. The seven default HubSpot deal stages, Appointment Scheduled through to Closed Won, are a starting point, not a sales process. A proper setup maps your specific buyer journey into stages with clear entry criteria, sets probability percentages based on your actual historical win rates, and on Professional and Enterprise plans, configures required properties at each stage so reps can't advance a deal without entering the data that makes the pipeline reliable.

Custom contact and company properties

A setup service that leaves HubSpot's default property set intact, or adds a dozen custom properties without reviewing which will actually get filled in, hasn't done the configuration work. The right output is a structure that's clean, purposeful, and matches what the team genuinely needs to see on a record.

Clean, validated data migration

Everything currently sitting in a previous CRM or a collection of disconnected spreadsheets needs to move accurately, without duplicates, with fields mapped to the correct HubSpot objects, and validated against a sample before the full import runs. A proper migration process isn't an import. It's an audit, a mapping document, a deduplication pass, a test import, a validation check, and then the live import. If a provider describes their process in one sentence, ask them to describe it in five.

Core workflow automation

Lifecycle stage progressions, deal stage task creation, lead routing from form submissions, and internal notifications for high-intent signals aren't advanced features, they're the baseline that makes the rest of the platform worth having. A setup that doesn't include at least foundational automation across departments in scope is leaving the most valuable part of the platform unused.

Integrated email and calendar connections

HubSpot's Gmail integrations allow reps to log emails, track opens, access records, and enrol contacts in sequences from their inbox. These should be configured and tested for every team member before go-live, not left as something people set up when they remember.

Custom reporting and dashboards

Pre-built dashboards cover the basics. They don't answer the specific commercial questions leadership asks, which channel is producing your best customers, where deals are stalling, what next quarter looks like. A setup service should build a small set of custom reports around those questions using HubSpot's custom report builder.

Role-specific training

One all-hands session produces a team vaguely aware of HubSpot and confident in none of it. Role-specific training, sales on deal management and sequences, marketing on workflows and reporting, service on tickets and SLAs, produces adoption. Each session should be recorded.

Handover documentation specific to your setup

Not a link to HubSpot's knowledge base. A document describing your specific portal, what the pipeline stages mean, what each workflow does and when it triggers, which properties are required and why, how the integrations work. This is what lets your team maintain the CRM independently.

The Risk Checks Worth Running on Every Provider

Beyond the deliverables, a handful of risk signals are worth testing in your evaluation conversations.

Ask who will actually do the work. Large agencies often sell with senior practitioners and deliver with junior staff. Ask directly, who's the day-to-day implementation contact, and will they be the same person in week four as in week one? The person building your pipeline needs to have absorbed everything from your discovery session, not received a one-page brief.

Ask for a reference at your scale. A case study from a 20-person business isn't evidence they can serve a 150-person one with three departments live on the platform. Ask for a reference at a similar size and structure to yours, and ask that reference specifically whether the setup held up six months after go-live.

Ask what happens when scope changes. It always does, and with more people involved in the decision, it does more often. Requirements that seemed clear in scoping evolve once each department starts using the platform in practice. Ask how those changes are handled: a formal change management process, a pre-agreed rate for out-of-scope work, or an uncomfortable negotiation.

Ask about data handling under the Privacy Act. Your customer data is subject to the Privacy Act 1988 and the Australian Privacy Principles. Any provider handling or migrating your contact data should confirm how it's stored, who has access, and whether processing happens outside Australia.

Ask whether they have a documented data breach response plan. A migration that goes wrong is one of the more plausible ways customer data ends up exposed, moved without the right access controls, or sitting briefly in an unsecured staging file. Under the Notifiable Data Breaches scheme, a breach likely to result in serious harm has to be reported to the OAIC and to affected individuals. Ask the provider directly whether they have a documented response plan for exactly this scenario, and whether that responsibility is spelled out in the contract, not assumed.

The Success Metrics Worth Agreeing Before You Start

A CRM setup measured only by go-live date has no accountability for whether it actually worked. Before signing, agree on how you'll evaluate success, not just completion.

Platform adoption rate. At thirty days post-launch, what percentage of the team is actively using the CRM daily, across every department involved? Adoption is the leading indicator of everything else.

Data completeness. At sixty days, what percentage of deals have the required fields populated? If required properties were configured correctly, this number should be high without manager intervention.

Lead source attribution. Are contacts generated through your website forms correctly attributed to the channels that produced them? Original source data in HubSpot is captured at first conversion and is immutable, if the tracking code wasn't in place from the start, you can't retroactively attribute the contacts you missed.

Pipeline reporting reliability. Are the dashboards producing numbers the team trusts and uses to make decisions, or is the Monday pipeline review still built from a spreadsheet someone assembled over the weekend?

Conclusion

Choosing a CRM setup service for a business this size isn't complicated if you know what to look for. Clear deliverables. Honest risk checks. Success metrics agreed before the work starts, not invented at the handover meeting.

At ninety days, the right setup produces something specific: every department using the platform as a matter of course, a pipeline that reflects current reality, marketing and sales reading from the same data, and reports leadership actually opens. When something needs to change, a new stage, a new workflow, a new integration, there's either an internal owner who can act confidently or a partner who knows the setup well enough to move quickly.

Any provider worth hiring should be able to describe that outcome before they begin, and be willing to be held to it at the end. For the warning signs to watch for in the pitch itself, see the red flags in a CRM setup pitch, and for what a realistic project actually looks like week to week, here's the scope and timeline. If the decision in front of you is choosing an onboarding partner more broadly, our partner selection guide covers that.

If you want to see how we approach every one of these criteria, let's talk, or see our RevOps and HubSpot work directly.