I sell Salesforce work both ways: fixed-scope launch packages and time and materials by the hour. The question I get on almost every scoping call is which one is cheaper. That's the wrong question. The right one is how much of the work you can describe today.
Short answer: pick fixed scope when you can write down what "done" looks like before work starts, like a Sales Cloud launch, a Service Cloud rollout or a first production Agentforce agent. Pick time and materials when the work is open-ended or keeps changing, like ongoing enhancements, a messy org you're still untangling, or staff augmentation on someone else's project.
What Fixed Scope Actually Means
A fixed-scope project has three things written down before anyone builds anything: what gets delivered, the price, and the go-live date. Change any of those and you get a revised quote before work continues, not a surprise invoice.
That only works if discovery happens first. On my launch packages the order is always the same: a discovery session, a written scope with a quote and a date, then the build. Skip discovery and "fixed scope" is just a guess with a number on it.
Fixed Scope Wins Here
A new implementation with a known shape. Most first launches look alike: leads to opportunities to quotes, or cases routed to the right queue. A Sales Cloud or Service Cloud launch typically runs 4 to 5 weeks. A first Agentforce agent runs 4 to 6.
You need a budget number before you start. Finance wants one figure, not a burn rate. Fixed scope gives them that, and puts the estimating risk on the person who has done the work before.
You want a clear finish line. Everyone knows what done means, so you avoid the slow drift where a 6-week project turns into a 6-month one.
Time and Materials Wins Here
Ongoing work with no end date. Enhancements, admin, releases and the changes users ask for after go-live. That's what managed services hours are for.
An org you can't scope yet. If nobody knows what's in the org, quoting a fixed price means padding it heavily or getting it wrong. Better to spend a short, fixed amount understanding it first. That's why the Org Health Check exists: 1 to 2 weeks, fixed scope, and you come out knowing what's at risk and what to fix first.
Capacity on someone else's project. When a consulting firm or an internal team needs a senior architect or developer for a stretch of their own roadmap, hourly by role is the honest model.
What Actually Moves the Quote
People expect the cloud or the license tier to drive cost. Usually it's these:
- Starting point. A new org is faster than an existing one that needs cleanup first.
- Data to migrate. How many records and source systems, and how clean they are.
- Integrations. Each system Salesforce has to talk to adds design, build and testing.
- Scope beyond the package. More processes, automations, reports or objects than it includes.
- Custom code. Apex or Lightning Web Components where configuration isn't enough.
- Timeline. A go-live date tighter than the usual weeks.
If you're comparing quotes from different partners, compare them on those six things. Two quotes that look far apart are often scoping different amounts of migration and integration.
The Hybrid Most Teams End Up With
In practice the cleanest setup is both: a fixed-scope launch, then the same team on a monthly managed services plan. No handover to a new team that has to learn your org from scratch, and the first round of changes your users ask for gets done by the people who built it.
The Quick Decision Framework
Fixed scope if:
- You can describe "done" before work starts
- It's a new implementation or a well-defined phase
- You need one budget number up front
- You want a go-live date in writing
Time and materials if:
- The work is ongoing or keeps changing
- Nobody can say yet what's in the org
- You need senior capacity on your own roadmap
- Priorities will shift month to month
Both if:
- You're launching something new and plan to keep improving it after go-live
Still not sure which way your project lands? Book a call and I'll tell you how I'd scope it. More on the packages and how engagements work on the packages page.