I run a small Salesforce consultancy, and I also work as a subcontractor on projects led by larger Salesforce partners. So I've seen both sides from the inside. Neither one is better in general. They're built for different projects.
Short answer: hire a large system integrator when the program is big enough to need many people working in parallel, across countries or business units, with formal governance. Hire a small consultancy when the project has a clear shape, you want the senior person you met on the sales call to do the work, and you'd rather pay for that person than for layers of management.
When a Large System Integrator Is the Right Call
Many workstreams at once. A multi-cloud rollout across regions, with data migration, integrations, change management and training all running in parallel, needs a lot of people at the same time. That's what big firms are built for.
Global or regulated programs. Multiple countries, languages, time zones and compliance regimes need coverage and process a small team can't provide alone.
Procurement requires it. Some companies can only buy from approved vendors above a certain size. If that's your situation, the decision is already made.
Around-the-clock support. If you need a large team on call around the clock after go-live, a big firm has the bench for it.
When a Small Consultancy Is the Right Call
You want the senior person doing the work. With a large firm, the architect on the sales call is often not the person building your org. With a small consultancy, the person you meet is usually the person who designs and builds it.
The project has a clear shape. A Sales Cloud or Service Cloud launch, a first Agentforce agent, a Data Cloud build, an integration or an org cleanup. These need depth, not a crowd.
You care about cost per hour of real work. Big firms carry account management, project management and overhead layers that show up in the rate. A small team spends more of the budget on building.
Speed. Fewer handoffs, faster decisions, and the person who understands the design is the one answering your questions.
The Risks of Each, Honestly
Small consultancy: key-person risk. If one person holds the knowledge, you're exposed if they're unavailable. Ask how the work is kept in source control, documented and handed over. On my projects every build ships with a solution document and lives in your repo, so your team or anyone else can pick it up.
Small consultancy: capacity. One architect can't staff a 30-person program. Ask how they scale. Mine is a bench of contractors I bring in for delivery while I lead the project.
Large integrator: the bait and switch. Senior people in the pitch, junior people on the build. Ask who exactly will be on your project, by name, and how much of their time you get.
Large integrator: cost and pace. More people means more coordination. For a mid-size project, a lot of the budget can go to managing the team instead of building.
The Middle Option People Miss
Large firms bring in small specialist firms all the time. On a lot of big programs, the deep technical work is done by subcontractors. If you have a large integrator for the overall program, you can still bring a specialist in for one hard piece, like Agentforce or Data Cloud, and get both.
Questions That Tell You Which One You Need
- How many workstreams need to run at the same time?
- Does procurement limit who you can hire?
- Who, by name, will design and build the work?
- Is the scope clear enough to write down before work starts?
- How is the work documented and handed over at the end?
- What happens after go-live, and who does it?
If you answered "one or two workstreams" and "yes, the scope is clear," you probably don't need a large integrator.
Want an honest read on which fits your project? Book a call. If a big SI is the better fit, I'll say so. More on how I scope work on the packages page.