The CRM setup industry has a dirty secret: it's very easy to look like you know what you're doing before the contract is signed.
A confident sales conversation, a logo-heavy case study page, a methodology PDF with a lot of arrows in it. None of these tell you whether the person who will actually configure your pipeline has done this for a business like yours or is going to figure it out alongside you at your expense.
The first sign that a setup service is selling a product rather than solving your problem is a quote that arrives before any real discovery has happened.
If a provider can tell you what the engagement will cost after a thirty-minute introductory call - without knowing how your team sells, what your current data looks like, which systems need to integrate, or how many people need training - they're quoting a template, not your project.
The proof: Ask them what they still need to know about your business before they can give you an accurate scope. A good provider has a list. A red flag provider gives you a price.
A CRM that's configured around your actual sales process gets used. One configured around a generic template of what a sales process should look like gets worked around, or ignored.
If a setup service doesn't ask specifically how your team currently moves a lead from first contact to closed deal, what information needs to be captured at each stage, and what the handoff between marketing and sales looks like - they're building a pipeline in the dark.
HubSpot's default deal stages (Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought In, Contract Sent) are a starting point. A provider who leaves them unchanged and calls it configured hasn't done the work.
The proof: Ask them what they'll do with the information from your first conversation before they start configuring. If the answer doesn't mention mapping your specific process to the CRM architecture, keep looking.
"We'll help you move your data across" isn't a migration process. It's a reassurance with nothing behind it.
A proper data migration for a small business involves: 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, and validation that the data arrived correctly and with the right associations.
Skipping any of these steps produces a CRM that starts life with duplicate contacts, broken company associations, or missing deal history. That's not a small problem to fix later, it's the kind of thing that makes your team distrust the platform from day one.
The proof: Ask them to walk you through their data migration process step by step. Count the steps. A confident answer has at least four or five. A vague answer has one: "we'll do an import."
A single "platform overview" session for the whole team isn't training. It's an introduction to an interface that nobody will use confidently after the meeting ends.
The sales rep who needs to know how to manage deals, log calls, enrol contacts in sequences, and use the HubSpot mobile app needs different training to the marketing manager who needs to know how to build workflows, create smart lists, and read campaign attribution reports. Training them together on the same content means both leave knowing HubSpot exists and how to do one thing each.
The proof: Ask how training is structured across different roles. The answer should name the specific roles and describe what each session covers. If it doesn't, the training plan wasn't written with your team in mind.
"We'll deal with integrations once the core setup is done" is the sentence that precedes a go-live delay, a scope dispute, and a discovery that the accounting software connection they assumed was straightforward actually requires custom development.
Every external system that needs to connect to HubSpot - email, calendar, advertising platforms, accounting software, support tools - should be identified and assessed in the scoping phase, not discovered mid-project. The difference between a native HubSpot marketplace integration and a custom integration is significant in terms of cost, timeline, and ongoing maintenance.
The proof: Share your full tech stack with every provider during scoping. Ask them to identify which connections are native HubSpot integrations and which would require custom work. A prepared provider has an answer. A red flag provider tells you they can connect anything without knowing what you're connecting.
A CRM that is switched on and then left to fend for itself is one that will develop problems your team will not know how to fix.
The questions, issues, and process gaps that matter most appear after go-live - not during the build. A workflow that fires on the wrong contacts, a report that doesn't answer the question it was built for, a team member who wasn't in the training session. If the engagement ends at go-live with no defined support arrangement, you're on your own from the moment things get interesting.
The proof: Ask specifically what happens after go-live. Who's the point of contact? What's the response time? Is there a structured check-in at 30 or 60 days? A vague answer about "always being available" isn't a support plan.
A setup service that delivers a configured HubSpot portal without documentation is handing you a car with no manual. You know it works because someone turned the key. You have no idea what anything does or why it was built that way.
Good documentation is specific to your setup - it describes your pipeline stages, what each workflow does and when it triggers, which properties are required and why, and how each integration is configured. This is what allows your team to maintain the CRM without calling the agency every time something needs to change, and what makes bringing in a new partner manageable if you ever need to.
The proof: Ask to see an example of documentation they've delivered to a previous client (appropriately anonymised). If they can't produce one, documentation isn't part of their standard delivery - which means it will not be part of yours either.
Every red flag on this list is a version of the same problem: a provider who's selling a service rather than solving your problem. The tells are always in the details, or the absence of them. Vague answers, generic processes, and confident reassurances that dissolve under simple follow-up questions.
The right CRM setup service doesn't mind being asked hard questions. They have answered them before and they have the specifics to back up the answers.
We have answers for all seven. Come test them. Start a conversation with us.
Watch our latest HubSpot tutorials on YouTube, or join us over on Facebook.
Happy HubSpotting!