Buyer guide
Should I engage a C2C contractor or buy a fixed-price software project?
In short
A C2C engagement buys an engineer's work over a period, steered by you in sprints against a written scope. A fixed-price project buys a defined result at an agreed price. Fixed price suits a clear, stable specification. A C2C engagement suits work that will change as you learn. Both need a written scope.
Who is this guide for?
Founders and engineering managers choosing between engaging a contractor's company for ongoing work and buying a defined project, and wanting to see what each puts on whom.
What you are buying
In a fixed-price project you buy a result: the specification is agreed first and the supplier carries the risk of how long it takes. In a C2C engagement you buy an engineer's work for a period, and you steer what that work is.
Who carries which risk
A fixed price moves the schedule risk to the supplier and the specification risk to you: if the spec is wrong, changes cost extra. A C2C engagement keeps both with you, but the work follows what you learn.
How change is handled
Fixed-price contracts handle change through change requests, which can be slow and argued over. A sprint-based engagement handles change at each sprint boundary: you re-order the next two weeks.
When fixed price fits
A defined piece of work with a clear finish, such as a migration with a known target or a small app with a stable specification, suits a fixed price. The supplier must be able to price it honestly, which needs a real look at what exists.
When C2C fits
A product still being shaped, work that depends on discoveries along the way, and ongoing work on a system already running suit a time-based engagement with a written scope that you review each sprint.
Contractor status in both cases
A fixed-price project is normally a clear service, and that helps with classification. A C2C engagement can drift towards direction of the person's hours and methods. Keep it a service with a scope and take advice if it starts to look like staffing.
How I run it
On a C2C contract I work in two-week sprints against a written scope, and you see working software at the end of each one. I quote after a short discovery call, against that scope.
How do the options compare?
| C2C engagement | Fixed-price project | |
|---|---|---|
| You buy | An engineer's work over a period | A defined result |
| Who steers | You, sprint by sprint | The specification |
| Change | Re-order the next sprint | Change request |
| Main risk | Drift without a scope | A wrong specification |
| Fits | Evolving product, ongoing work | Stable, well-defined work |
What should I check before I sign?
- You can say whether the specification is stable.
- You know who carries the risk of overruns in each model.
- Change is handled in writing either way.
- A written scope exists either way.
- You know what you will see at the end of each sprint or milestone.
- You asked an accountant about classification if you choose C2C.
- Ownership of the work is in the contract.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
Can I start with a fixed-price discovery and then move to C2C?
Yes. A short fixed-scope review is a sensible start, and an ongoing engagement can follow once the work is clear.
Is fixed price cheaper?
Not by itself. A supplier prices the risk it carries, so compare total cost and what is included.
Which gives more control?
C2C gives you more control over what is built next. Fixed price gives you more certainty about what you pay.
Do both need a scope?
Yes. A scope is what stops either model from turning into an argument.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.