By the time you're evaluating partners instead of researching whether you have a problem, you've usually already been burned once, either by DIY automations that broke the first time someone touched them, or by an agency that disappeared after go-live. These are the questions that actually separate the two, asked in the order we'd expect them.
About the build itself
1. "Do you architect the process first, or start configuring fields?"
If the answer jumps straight to "we'll set up your Salesforce org," that's a warning sign. Configuration without a mapped process just digitizes your existing chaos. Ask to see how they document your pipeline before they build anything.
2. "What does a deal path look like when it's done, and who approves what?"
A real answer names specific stages and a specific approval gate. A vague answer ("it depends on your needs") this early usually means they haven't built enough of these to have a default.
3. "How is my data migrated, and who's responsible for deduplication?"
Migration is where most implementations quietly go wrong: duplicate records, orphaned fields, a "clean" new system full of the same mess it replaced. Ask specifically how they inventory and dedupe your legacy data before it ever touches the new org.
About the relationship
4. "Who do I actually talk to during the build, and after?"
Watch for a handoff between the person who sold you the engagement and the person who builds it. That gap is where requirements get lost.
5. "What happens if something breaks a month after launch?"
A one-time build with no support plan almost guarantees you'll be back to spreadsheets within a year. Ask what's covered, what isn't, and what the response time actually is, not just what's advertised.
6. "Can I see an example of a deviation you documented instead of quietly fixing?"
This question tells you more than any case study. A partner who tracks and flags deviations from their own standard is one who's thinking about your system's integrity six months out, not just the demo.
About fit
7. "Have you built for a team our size, in our industry?"
A generic enterprise Salesforce build and a lean 15-person team build are different disciplines. Ask for specifics, not just a client logo list.
8. "What's explicitly not included in this quote?"
Scope creep kills more CRM projects than bad technology does. A partner who's upfront about exclusions is one who won't surprise you at invoice time.
9. "How long until my team can actually use this without you in the room?"
A real handoff includes training your team to run the system, not just a login and a thank-you email.
About honesty
10. "What's a build you'd turn down?"
Anyone who says "we take everything" hasn't thought hard about fit. A partner with a clear sense of who they're wrong for is more trustworthy than one who's right for everyone.
11. "Can I talk to a client, even an old one who left?"
Reluctance here is data. Even one honest reference conversation about what went wrong tells you more than a page of testimonials.
12. "What happens to my data and access if we ever part ways?"
You should own your CRM, full stop. Any hesitation about exportability or admin access is a red flag worth walking away from.
The build is the easy part to demo. The relationship after go-live is the part that actually determines whether the system survives.
Where we'd land on these, honestly
We're not neutral here, so take this with that in mind: Apex Flow architects the process before touching a field, runs the same fixed five-stage build on every engagement so nothing depends on memory, documents deviations instead of burying them, and pairs every launch with a retainer specifically because a build with no ongoing care tends to decay. We'd rather you ask us these questions directly than take our word for it.
Bring us your list. We'll answer all twelve on a call.
Book a Strategy Call