How to Choose a Salesforce Partner in NZ: 12 Questions to Ask

Choosing a Salesforce partner well comes down to verifying four things: a track record you can check (not just claims), real platform depth on your clouds, a configuration-first philosophy that keeps costs down, and a delivery model where you know exactly who does the work. The 12 questions below test all four — with the answers you should expect to hear.

A blunt disclosure before we start: SaaSKool is a Salesforce consulting partner, so we are not neutral. But a meaningful share of our work is rescuing implementations that went wrong the first time, which has given us an unusually clear view of how they go wrong. These questions are reverse-engineered from those projects.

The 12 Questions

1. "Can I see your AppExchange listing and reviews?"

Anyone can put testimonials on their own website. Reviews on a partner's Salesforce AppExchange consultant listing are tied to verified Salesforce customers — they cannot be invented. A partner without a listing, or with one but no reviews, is asking you to take their word for everything. (Yes, that link is ours. The point stands: ask everyone for theirs.)

2. "Who exactly will work on my project, and what are their certifications?"

The people who pitch are not always the people who deliver. Ask for the named team and their individual Salesforce certifications. A good answer names real people. A bad answer is "our certified team" with no names attached.

3. "Have you done this for an organisation like mine?"

Same size, similar industry, similar clouds. A partner who has only done 200-seat enterprise rollouts will drown a 10-person business in process; a partner who has only done Sales Cloud will improvise on your Service Cloud project. Ask for a reference client you can actually call.

4. "What's your philosophy on configuration versus custom code?"

This one question predicts your five-year cost better than any other. Salesforce's built-in tools — flows, validation rules, page layouts — are included in your licence and survive upgrades. Custom code costs more to write, more to maintain, and is where rescued projects most often went wrong. The answer you want: "Configuration first; code only when a requirement genuinely can't be met any other way."

5. "How will you handle our data migration?"

Vague answers here become your problem at go-live. You want to hear about deduplication, field mapping, a test migration before the real one, and validation afterwards — the essentials we cover in our data migration guide. "We'll import your spreadsheets" is not a migration plan.

6. "What happens after go-live?"

Implementations don't fail at launch; they fail in month three, when questions pile up and nobody owns them. Ask what support is included, for how long, and what ongoing arrangements cost. Partners with real managed-services or fractional-admin offerings have answered this before; partners who only do projects will be gone.

7. "How would you make our org AI-ready?"

A 2026-specific filter. You may not want AI agents this year — but your partner should be able to explain what readiness means: clean data, documented processes, knowledge articles worth grounding an agent in, and which Agentforce capabilities your edition already includes. A partner who can't discuss what's actually included by edition is selling you yesterday's platform.

8. "Fixed price or time and materials — and what's in scope?"

Either model can be fair; ambiguity in either is how budgets double. For a first SMB implementation, prefer a fixed scope with a written list of what's included (our pricing guide covers typical NZ ranges). If T&M, demand a capped estimate and weekly reporting against it.

9. "What happens when we ask for changes mid-project?"

Scope will change — the test is whether the partner has a grown-up process for it. You want: changes are written up, priced, and approved before work happens. You don't want: "we're flexible," which translates to "we'll surprise you on the invoice."

10. "What documentation do we get at the end?"

When the project ends, your team — or your next partner — needs to understand what was built and why. Ask to see a sample handover document from a past project. The orgs we rescue almost never have one.

11. "Where is your team, and when are they available?"

Not a purity test — a logistics one. If your users hit a blocker at 9am Tuesday in Auckland, who answers, and when? Local context (NZ privacy expectations, Xero, the way Kiwi SMBs actually buy) also shortens a lot of conversations.

12. "Why shouldn't we do this ourselves?"

A slightly unfair question with a revealing answer. An honest partner will tell you which parts you genuinely could do in-house and which parts deserve help — and will be specific about where their value is. A partner who insists everything requires them is optimising for billables.

Red Flags at a Glance

| Red flag | Why it hurts | What to ask instead | |---|---|---| | Solutioning before discovery | They're fitting you to their template | "What do you still need to learn about us?" | | "Custom code will handle that" early and often | Maintenance burden for years | Question 4, and insist on the answer | | No AppExchange reviews | Track record can't be verified | Question 1 | | Unnamed "certified team" | Bait-and-switch delivery risk | Question 2 | | Open-ended T&M, no cap | Budget risk is entirely yours | Question 8 | | No post-go-live offering | You're alone in month three | Question 6 | | Urgency built on scare claims (e.g. "NPSP is discontinued!") | They're selling fear, and it's not even accurate | Ask for the official source |

Frequently Asked Questions

How much does a Salesforce partner cost in NZ? Three models dominate: fixed-scope projects (SaaSKool's published packages run NZ$2,500–$15,000 for SMB implementations), monthly retainers for ongoing support (from around NZ$1,000–$1,500/month), and time-and-materials for open-ended work. Be wary of open-ended T&M for a first implementation.

Should I choose a local NZ partner or offshore? What matters is accountability and context, not geography alone. Local partners bring NZ business context, working-hours overlap, and easier references; offshore can cost less per hour but often needs more hours. Hybrid teams — local lead with distributed delivery — are common and can work well.

How do I verify a Salesforce partner's track record? Three checks: their AppExchange consultant listing (reviews there are from verified Salesforce customers), individual certifications of the people on your project, and a reference call with a past client of similar size to you.

What is the biggest red flag when choosing a partner? A partner who starts proposing solutions before understanding your business process. If the discovery conversation is about licences and build hours rather than how your sales or service actually works, walk away.

---

If you want to put us through these 12 questions, we'd genuinely enjoy it — book a conversation or read more about SaaSKool first. And if you're asking these questions because a previous project went sideways, our Salesforce Rescue service exists for exactly that.