DevGateThe engagement model you choose shapes your project more than almost any technical decision. It decides who carries risk, how change is handled, and how much control you keep. Pick the wrong one and even a great team will struggle.
Here's how the four common models compare, and how to pick.
The four models at a glance
| Model | You pay for | Scope | Best for |
|---|---|---|---|
| Dedicated team | A team's time, monthly | Flexible | Long-running products |
| Time & material | Hours actually worked | Flexible | Evolving requirements |
| Fixed cost | An agreed deliverable | Locked | Well-defined projects |
| Partnership | Shared risk and reward | Co-owned | New ventures |
Dedicated team (and staff augmentation)
A dedicated team works only on your product, usually full-time, in your tools and rituals. Staff augmentation is the lighter version: individual engineers join your existing team to fill specific gaps.
Choose it when you have a roadmap rather than a single project, you want to keep product ownership in-house, and you need to scale faster than local hiring allows.
Watch out for teams that "augment" but don't take ownership. Ask whether the vendor is accountable for delivery or just supplies hours. (At DevGate we own delivery of tasks even in a staff-augmentation model—it's worth asking any vendor the same question.)
Time & material
You pay for the time spent and the people involved. Scope can change every sprint.
Choose it when requirements will evolve as you learn from users, or when you're modernizing a system whose full complexity you can't see yet.
Watch out for open-ended burn. Insist on sprint demos, a visible backlog and regular forecasts so you always know what the remaining work is likely to cost.
Fixed cost
Scope, timeline and price are agreed up front.
Choose it when the requirements are genuinely clear and stable—a well-specified integration, a migration with known boundaries, or a defined MVP.
Watch out for change requests. Every change becomes a negotiation, and vendors price uncertainty into the quote. If you can't write the requirements down in detail, fixed cost usually costs more, not less.
Partnership
A longer-term, shared-risk arrangement where the vendor co-creates the product with you—sometimes with reduced fees in exchange for a share of the upside.
Choose it when you're launching a new venture and want a technical partner invested in the outcome.
Watch out for unclear IP and exit terms. Agree who owns what, and what happens if either side wants out, before writing any code.
A simple decision rule
- Can you write the full scope down today? If yes, consider fixed cost.
- Is this a product you'll keep evolving for a year or more? Choose a dedicated team.
- Do you need to start now while requirements are still forming? Start on time & material, then move to a dedicated team once the roadmap stabilizes.
- Are you building something new together, with shared upside? Explore a partnership.
Many successful engagements combine models: a fixed-cost discovery phase to define scope, followed by a dedicated team for delivery.
Questions to ask any vendor
- Who exactly will work on my project, and can I interview them?
- How much working-day overlap will we have?
- How often will I see working software?
- Who owns the code and IP, and when does it transfer?
- What happens if someone leaves mid-project?
If you'd like a second opinion on which model fits your project, book a call with one of our engineers—or read our one-page engagement models guide.
Free guide
Choosing a software partner? Read the engagement models guide.
Models compared, a sample timeline and 8 questions to ask any vendor.