How to vet a Salesforce integration consultant before signing the SOW. 7 items that separate generalists from specialists, plus the red flags that signal a bad fit.
A Salesforce® integration project goes from "should work in 4 weeks" to "8 months and still broken" almost always for the same reason. The consultant picked at SOW signing did not have the capability the project required. The CFO learns this in month 5 when the integration cannot ship and the renewal conversation gets uncomfortable.
This post is the 2026 vendor checklist Sapota's Salesforce team gives founders evaluating integration consultants. 7 items that sort generalists from specialists, plus the red flags that filter out 80 percent of bad fits in the first conversation.
The role covers the work between Salesforce and every other system the business runs. Common scopes:
Each scope has different technical patterns. A consultant who shipped 3 CRM-to-ERP integrations may struggle with marketing data flows. A MuleSoft architect may over-engineer a point-to-point Apex callout. Capability fit matters more than brand fit.
Consultants cluster into 3 profiles. Each fits different engagement shapes.
Holds platform certifications across MuleSoft, Salesforce Functions, custom Apex callouts. Designs the integration topology, picks the right tool per integration, oversees implementation.
Fit: enterprise programs with 5+ source systems, MuleSoft licence already in play or under evaluation.
Cost: USD 200 to USD 500 per hour for senior architects. Annual MuleSoft licence USD 80K to USD 500K depending on tier.
Boomi, Workato, Jitterbit, Mulesoft Composer. Builds visual integrations on top of low-code middleware platforms.
Fit: programs with 3 to 8 source systems where citizen-developer maintenance matters. Faster to ship than custom-code; lower licence cost than MuleSoft enterprise.
Cost: USD 100 to USD 250 per hour. Middleware licence USD 10K to USD 80K per year.
Custom-code-only integrations via Salesforce Apex callouts, Named Credentials, and Platform Events. No middleware platform.
Fit: point-to-point integrations under 5 systems. Engineering team can support custom code long-term.
Cost: USD 80 to USD 200 per hour for senior Apex developers. No platform licence beyond Salesforce itself.
These 7 items sort consultants in a 30-minute call. Real practitioners answer with specifics; pitch-deck consultants give surface-level descriptions.
The consultant should name 3 specific recent integrations they shipped. Specific source systems, specific data flows, specific outcome metrics.
What a real answer sounds like: "Shipped NetSuite to Salesforce customer sync last month. 50K customer records, daily delta, OAuth 2.0 with refresh token, dead-letter queue for failed updates, average end-to-end latency 8 minutes." That answer demonstrates capability.
What a fake answer sounds like: "We have extensive integration experience with major ERPs." That is marketing speak.
OAuth 2.0 is the modern auth standard. The consultant should explain their specific pattern: client credentials vs authorization code flow, refresh token rotation, secret management, scope handling.
What to listen for: token storage strategy (Named Credentials in Salesforce vs external secret manager), refresh failure detection (silent vs noisy), per-environment configuration (sandbox vs prod credentials separated). Consultants that handwave OAuth produce integrations that work for 6 months then break silently when a token expires.
Every integration has failures. The discipline is in how the consultant handles them.
What to listen for: defined error categories (transient vs permanent), retry policy (exponential backoff with jitter), dead-letter queue for permanent failures, alerting on failure thresholds, replay mechanism for fixed failures. Consultants without explicit error handling produce integrations that look successful but lose data.
Retries are dangerous without idempotency. A retry on a non-idempotent operation can double-charge a customer or create duplicate records.
What to listen for: idempotency key per request (UUID or business key), receiver-side dedup logic, defined retry count limit, escalation path on retry exhaustion. The Apex callouts pattern covers the specifics for Salesforce-side implementation.
Integration timing matters. Some flows need real-time (order placed in Shopify, must reach OMS in seconds). Some flows are batch (nightly customer master sync to data warehouse).
What to listen for: explicit decision per integration, awareness of trade-offs (latency vs cost vs complexity), specific patterns for each. Platform Events for streaming. Bulk API for high-volume batch. Change Data Capture for moderate-volume real-time. The SOQL selectivity reference covers the data-volume-dependent patterns.
Integration is not done at go-live. The monitoring stack catches drift, failures, and silent data loss.
What to listen for: metrics layer (request count, latency p50/p99, error rate), alerting layer (defined thresholds, escalation paths), log retention (days to weeks for debugging), trace correlation across systems. The integration is operationally healthy only when the monitoring stack proves it.
Most integrations need 6 to 12 weeks of post-launch tuning before they stabilise. The consultant who disappears at go-live leaves 80 percent of the value on the table.
What to listen for: defined scope for first 90 days, named engineer for continuity, response SLA, escalation path. The "we hand off and you can come back if you need anything" answer is a red flag.
The tool choice depends on scope and budget.
5+ source systems with overlapping integration patterns. Enterprise budget that justifies USD 80K to USD 500K annual licence. Need for citizen-developer accessibility on integration changes. Long-term hub-and-spoke architecture commitment.
MuleSoft shines on the "build it once, reuse it everywhere" pattern. Connectors to standard systems exist; the API-Led Connectivity pattern keeps integrations reusable across consumers.
Need to run Dataverse-native logic that exceeds the Apex 10-second sync limit, requires Node.js or Java runtime, or integrates with external systems that need long-running operations.
Functions sit inside the Salesforce platform but run on Heroku infrastructure. The benefit is platform-native deploy and security; the cost is Functions-specific licence and complexity.
Point-to-point integrations under 5 systems. Engineering team has Apex expertise. Latency requirements that match Apex callout limits (120-second max, 100 callouts per transaction). Budget that does not justify middleware licence.
Custom Apex is the lightest-weight option. Named Credentials handle OAuth, Platform Events handle event-driven flows, Apex callouts handle synchronous integrations. The Apex callouts reference covers the patterns.
The right consultant explains which tool fits which integration. Consultants pitching MuleSoft for every project are over-engineering; consultants pitching custom Apex for every project are under-engineering.
The 3 patterns that filter 80 percent of bad fits:
"We have done many Salesforce integrations" beats nothing but loses to specific recent shipping examples. Real consultants volunteer specifics; pitch-deck consultants stay at the brand level.
Consultants pitching MuleSoft for every integration are working on commission or over-engineering. MuleSoft fits roughly 20 percent of integration programs. For the other 80 percent, the cost outweighs the benefit.
The right consultant says "MuleSoft makes sense for this program because A, B, C; for the other program, we would use Apex callouts because D, E, F".
A fixed-bid SOW that scopes "implement integration between Salesforce and ERP" without specifying retry behaviour, idempotency, and monitoring is open-ended. The consultant is incentivised to skip the operational discipline because it does not appear in the scope.
The right SOW lists retry policy, idempotency mechanism, alerting thresholds, log retention, and post-launch support window as explicit deliverables. The scope drives the consultant's incentives.
The 30-minute initial call should cover the 7 checklist items. Score each answer 0 (unable to answer), 1 (surface-level), 2 (specific and detailed).
A score of 10 or higher across the 7 items signals a capable consultant. A score below 8 signals either inexperience or capability gap. A score below 5 is a hard skip.
The 2 most diagnostic items are #1 (recent deployments) and #4 (retry with idempotency). Consultants who score well on these typically score well across the board; consultants who score poorly on these usually score poorly everywhere.
3 engagement structures dominate integration consulting.
Defined scope, defined timeline, defined price. Typical Salesforce integration project: USD 40K to USD 200K depending on complexity. Works when scope is genuinely fixed; breaks under scope creep.
Hourly billing. Typical senior rate USD 150 to USD 300 per hour for Salesforce integration specialists. Works when the client has internal project management and trusts billing honesty.
Sapota's standard. 2-week paid trial scoped to one integration deliverable. USD 1,800 to USD 2,400 per engineer per month rolling monthly after conversion. No lock-in.
The trial structure works for integration projects because the first 2 weeks reveal capability gaps that pitch decks hide. A consultant can pitch retry-with-idempotency cleanly; only the actual code reveals whether they ship it cleanly.
Before signing the SOW, read the integration architecture patterns the consultant should know:
A consultant that can engage at depth on these 4 has the integration capability the SOW needs. A consultant that handwaves them does not.
Sapota's Salesforce team holds 5 Salesforce certifications including Administrator, Platform Developer I and II, and Marketing Cloud Consultant. We have shipped integrations across NetSuite, SAP, Oracle Financials, Shopify, Snowflake, and BigQuery.
Visit the Salesforce service page for the team capability list and engagement model. The complete SFMC implementation guide covers 70+ patterns across the full Marketing Cloud and integration surface.
The 2-week paid trial scoped to one specific deliverable runs USD 1,800 to USD 2,400 per engineer per month after conversion. Walk-away terms documented up front. No lock-in.
The technology decisions matter but the capability fit matters more. The right consultant for an enterprise hub-and-spoke MuleSoft program differs from the right consultant for a point-to-point Apex callout integration. The 7-item checklist exists precisely because pitch decks hide capability gaps.
The founders who get this right vet consultants deliberately and walk away from bad fits fast. The founders who get this wrong pick on price or brand and pay the cost in months 4 through 8 of the engagement.
Other posts in the same topical cluster. The pattern in the post above usually shows up alongside the patterns below, either because they live on the same surface of the platform or because the same engagement type runs into both. Pick the one closest to the problem in front of you and start there.
Marketing CloudJul 09, 2025
E-commerce automation sends coupon emails from a coupon bank DE. When the bank runs out of codes, emails ship blank. RaiseError Activity stops the automation with a controlled error instead of an embarrassing send.
Read More
Marketing CloudJan 05, 2026
Complete 2026 guide to Salesforce Marketing Cloud implementation services: discovery, architecture, DE design, journeys, MC Connect integration, testing, post-launch. Timeline plus cost.
Read More
Marketing CloudDec 11, 2024
Client buys a dedicated IP and wants to blast 500k emails from it on day one. ISPs don't know the IP, reputation is zero, and the batch lands in spam. Here's the warming plan we use.
Read More
Marketing CloudApr 01, 2026
Open rate drops from 22% to 14% over 3 months with the same content. The cause is almost always list hygiene. Here's the 4-step process we use to rehab engagement without burning the domain reputation.
Read MoreWe build trust by delivering what we promise – the first time and every time!
We'd love to hear your vision. Our IT experts will reach out to you during business hours to discuss making it happen.
"Collaborate, Elevate, Celebrate where Associates - Create Project Excellence"
SapotaCorp beyond the IT industry standard, we are
