Most banks, credit unions, wealth management firms, and commercial real estate companies buy Salesforce work in one of three ways. They pay a partner by the hour, they sign a fixed-price contract for a defined result, or they buy a managed services plan that handles requests as they come in. Each model solves a real problem. Each one also leaves a gap, and the gap usually shows up as a missed date, a change order, or a system your team does not use.
Delivery-as-a-Service vs. Time and Materials
Outcome-Based Contracts and Managed Services: Which Salesforce Delivery Model Fits Financial Services?
This guide explains how each model works, where it tends to break down, and why Fortimize delivers its work through a fourth model, Delivery-as-a-Service. To be upfront, Delivery-as-a-Service is the model we sell. We moved our own business to it after years of working the other ways, and this guide explains why.
The Four Delivery Models at a Glance
- Time and materials: You pay for every hour the partner works. The scope can only change with a change order, and the budget grows with it.
- Outcome-based contract: You pay a set price for a defined result. The price holds as long as the requirements do.
- Traditional managed services: You pay a monthly fee for a bucket of support hours or a ticket queue. The partner keeps the system running and responds to requests.
- Delivery-as-a-Service: You pay a set amount each quarter for a dedicated team that works from a shared roadmap toward business outcomes you agree on. The plan can change without a change order.
The difference that matters most is who carries the cost when the plan changes. On a Salesforce program, the plan almost always changes at least once.
Time and Materials: Flexible, With the Risk on You
Time and materials, often shortened to T&M, means you pay the partner’s hourly rate for every hour its consultants work. It is the most common model in the Salesforce market because it is easy to start. Nobody has to agree on a fixed price up front, and you can change direction whenever you want.
The problem is that the partner is paid for effort, not results. When the work takes longer than planned, the partner earns more and your budget grows. Discovery can run for months. A data question that should take a day becomes a week of billed analysis. Change orders, which are contract amendments that add cost for work outside the original scope, often arrive after the work is already done.
Nobody on a T&M contract has to be acting in bad faith for this to happen. The contract rewards hours, so hours are what it produces. For a bank or credit union, the result is a budget that is hard to defend to leadership and a go-live date that keeps moving.
T&M can make sense for a short, well-understood piece of work where you have strong internal oversight. It is a poor fit for a multi-phase Salesforce program with core banking and lending integrations, where the unknowns are real and the hours add up quickly.
Outcome-Based Contracts: Certainty Until the Plan Changes
An outcome-based contract, sometimes called fixed-scope or fixed-fee, sets one price for a defined deliverable. The partner commits to building a specific list of requirements by a specific date. On paper, this moves the risk to the partner, which is why many buyers prefer it after a bad T&M experience.
The weakness is the requirements list. To fix the price, the partner has to lock the scope early, before anyone fully understands the data, the integrations, or how your teams actually work. When you learn something new partway through, the contract leaves two choices. The partner absorbs the cost and cuts time somewhere else, or the partner issues a change order. Either way, the conversation shifts from what the business needs to what the contract says.
Fixed-scope contracts also tend to carry a cushion. A partner taking on all of the risk builds extra margin into the quote, so you pay for uncertainty whether or not it shows up.
This model works well for packaged work with few unknowns, such as a defined assessment or a prebuilt accelerator. Fortimize prices several of its own offers this way, including the Org Reset and the ROI Roadmap. It works less well for a full implementation, where the right answer changes as you learn.
Traditional Managed Services: Steady Support, Little Progress
Traditional managed services cover the platform after go-live. You pay a monthly fee for a set number of support hours or a ticket queue, and the partner handles user requests, fixes, and routine changes. Service levels usually promise how fast the partner will respond, not what it will deliver.
This model is good at keeping a Salesforce org running. It is not built to move the business forward. Work arrives one ticket at a time, so nobody owns the roadmap or asks whether the system still does what you bought it to do. Unused hours often expire at the end of the month, and larger improvements get pushed into a separate project with its own contract.
For a financial institution, that usually means the org stays stable while adoption slowly drops, the data drifts out of line with the core system, and the next phase of the roadmap never starts.
Delivery-as-a-Service: A Dedicated Team Working Toward Your Outcomes
Delivery-as-a-Service, or DaaS, is the model Fortimize uses for implementation and ongoing work. You get a dedicated team at a set quarterly price. The team works in two-week sprints, which are short, planned work cycles that each end with working software your stakeholders can see. The sprints aim at business outcomes you agree on together, such as faster loan referrals or one view of each member, rather than at a locked list of requirements.
Four things make it different from the other models.
- The work starts with a roadmap. Before the first sprint, we turn your business goals into a phased roadmap that shows what goes live in each phase and what each phase is worth to the business. Changes are logged and prioritized against that roadmap every week, and we review the roadmap with you each quarter, so it stays tied to your goals instead of sitting in a file after kickoff.
- Your spend is predictable. You know what you will pay each quarter, the same way you would with a fixed-price contract.
- The plan can change without a change order. When the team learns something that changes the plan, the priorities adjust within the same spend. The change is a decision in the weekly status call, not a contract amendment. The destination holds, and the route can bend.
- The team is accountable for the outcome, not the hours. Each week the team reviews progress against your goals and reads risk against the date, so a slip shows up while there is still time to fix it.
Here is what that looks like in practice. On one community bank launch, we learned partway through that some of the bank’s data lived in a different system than planned. Under T&M, that means more hours. Under a fixed-scope contract, it means a change order. Under DaaS, it was a decision on the status call that was already on the calendar. The bank went live with 192 users in 14 weeks and logged 38 referrals in the first three days, 20 of which converted.
DaaS also closes the gap between project work and managed services. The same team that builds the solution can stay on to keep it current and move the roadmap forward, so there is no handoff to a support desk that does not know why things were built the way they were.
The results are tracked. Since 2012, Fortimize has delivered more than 1,000 Salesforce projects, and 98% of them finished on time and on budget. Customers rate us 4.9 out of 5 on the Salesforce AppExchange, and the average client stays with us three and a half years. For three years running, warranty fixes have stayed under 1% of our hours, and we have not billed for any of them. Our teams are onshore and usually five people or fewer, and the people you meet are the people who do the work.
Frequently Asked Questions
What is the difference between Delivery-as-a-Service and managed services?
Traditional managed services keep a Salesforce org running by responding to requests, usually from a bucket of hours or a ticket queue. Delivery-as-a-Service gives you a dedicated team at a set price that works in sprints toward business outcomes you agree on. Managed services maintain what you have. DaaS keeps improving it, and the same team can cover both the build and the ongoing support.
Is Delivery-as-a-Service more expensive than time and materials?
The quarterly price is set in advance, so you can compare it directly with a T&M estimate. The difference is what happens when the work takes longer than planned. A T&M estimate is a starting point, and the cost grows with the hours. A DaaS price is what you pay, and the priorities adjust instead.
How is Delivery-as-a-Service different from an outcome-based contract?
Both tie the work to results. An outcome-based contract locks the price and the requirements together, so any change to the requirements becomes a change order. DaaS locks the price and the outcome, and lets the requirements move as you learn. That is why we do not issue change orders.
What happens if our priorities change in the middle of a quarter?
You raise it in the weekly status call, and the team reprioritizes the upcoming sprints. Work that matters less moves later in the roadmap. Your spend for the quarter does not change.
Does Delivery-as-a-Service include roadmapping?
Yes. Every engagement starts with a roadmap built from your business goals, and we review it with you each quarter so it keeps pace with your priorities. If you want the roadmap before you commit to delivery, the ROI Roadmap is a fixed-price engagement of four to six weeks that builds the phased plan and the business case behind it.
Can we move an existing project or support contract to Delivery-as-a-Service?
Yes. About 34% of Fortimize clients came to us from another Salesforce partner. Most start with an Org Reset, a two-week assessment that documents what was built and what to fix first, and then move into DaaS for the work that follows. We do not need the previous partner involved.
Choosing the Right Model for Your Next Phase
If you are planning your next Salesforce phase, ask any partner four questions before you sign.
- What happens to my cost if the work takes longer than planned?
- What happens when we learn something that changes the plan?
- Who on your team is accountable for the business outcome, not just the hours?
- Who keeps the roadmap tied to your goals once the work starts?
If the answers point to change orders or more hours, the contract leaves the risk with you.