The Contract Decision Nobody Prepares You For
You have done your research on how to find a software development agency. You have a shortlist, you have read the warning signs, and you are ready to evaluate proposals. Then you sit down with an actual contract and realize you have no idea what you are looking at.
The two models dominating the industry are fixed price and time and materials (T&M). On the surface, the choice feels obvious: fixed price means you know exactly what you will pay. Time and materials means the agency bills for whatever hours they spend — which sounds like a blank check. So you demand a fixed price.
That instinct is understandable. It is also how a lot of software projects end up delivering something technically correct that does not actually solve the problem — while the business owner has no recourse and no way to add the features that would have made it work.
Why Fixed-Price Contracts Feel Safe — and Often Are Not
Fixed-price contracts appeal to decision-makers for the right reason: they cap financial exposure. You agree on a scope, the agency quotes a number, and you pay that number. No surprises on the invoice.
The problem is structural. For a fixed price to be honest, the agency has to know exactly what they are building before a single line of code is written. For most custom software projects — especially anything involving AI integration, workflow automation, or an evolving product — that certainty does not exist. Building software is a process of discovery. You will learn things during development that change what you need.
When an agency offers a fixed price anyway, they are managing their margin, not your project. Scope that was not explicitly specified becomes a change order. Features that were implied but not documented get quietly dropped. Every question about requirements that surfaces mid-build gets answered in the way that is cheapest for the agency, not most useful for you.
The result is a common and painful pattern: you receive a product that matches the contract, does not match your actual need, and costs three times the original quote to modify — because modifications are now change orders billed at a premium rate.
Key Takeaways
- Fixed price requires certainty that rarely exists before a project begins
- Agencies protect their margins in fixed-price contracts by narrowing scope, not by working more efficiently
- Every undocumented assumption becomes a paid change order
- The cost of modifications post-delivery is typically 3–5x the cost of including them upfront
Why Time and Materials Sounds Risky — and Sometimes Is
Time and materials contracts bill you for actual hours worked at an agreed rate. There is no ceiling. Just the agency's team, logging hours against your project each week.
The legitimate concern: without a budget cap, an inefficient or undersupervised agency can run indefinitely. If you are not receiving clear reporting on where hours are going and what has been completed, you have no lever to pull.
But T&M has something fixed-price contracts structurally cannot: honesty. The hours reflect real work. When your requirements evolve — and they will, because building software always produces new information — T&M accommodates that without penalty clauses. You are not punished for learning what your users actually need.
The risk of T&M is not the model itself. The risk is using it without milestones, without regular delivery checkpoints, and without clear visibility into what the team is actually shipping. That is a governance problem, not a contract problem.
The Contract Structure That Actually Protects You
Experienced operators — founders who have been through a software project once and want to do it differently the second time — typically use a phased structure with milestone-based payments.
Instead of one contract covering the entire project, the engagement is divided into phases: discovery, design, prototype, build, acceptance testing. Each phase has a defined deliverable and a payment gate. You approve the output of one phase before authorizing the next. Within each phase, work is billed at a time-and-materials rate.
This gives you the accountability of fixed-price contracting — you can halt the engagement at any phase boundary if the work is not meeting expectations — with the transparency of T&M. You are not locked into a failing agency by a contract that has already absorbed your deposit. You own a defined deliverable at every exit point.
This is also how you protect yourself against scope creep. Each phase is scoped clearly. Changes to scope within a phase are visible and agreed before they are executed. Nothing gets quietly absorbed or quietly deferred.
Key Takeaways
- Phased contracts with milestone payment gates combine the accountability of fixed-price with the honesty of T&M
- You own a defined deliverable at each phase boundary — no sunk-cost trap
- Scope changes are visible and agreed within each phase, not hidden or deferred
- The structure gives you a clean exit point if the agency is not performing
What the Proposal Tells You Before You Sign Anything
How an agency responds to the contract structure question is itself a signal worth reading carefully.
An agency that produces a detailed fixed-price quote within 24–48 hours of your first conversation has not thought carefully about your project. They have applied a template, priced to win the deal, and protected their margin. The speed is a warning, not a feature.
An agency that asks substantive questions — about your users, your constraints, your definition of done, what success looks like in six months — before proposing anything is doing the harder work of actually scoping your project. They may offer a fixed-price discovery engagement followed by milestone-gated T&M for the build. That is not a hedge; that is an agency that understands how software projects actually work.
Proposals that include named developers, explicit non-scope (what is not included), and a clear explanation of the payment schedule are proposals written by people who have run projects before. Proposals that include glossy case studies and a single bottom-line number are proposals written to close a sale.
Three Questions to Get Answered Before You Sign
Whatever contract model you agree on, get clear written answers to these before you commit.
First: what is explicitly excluded from scope? Make the agency document what they are not building, not just what they are. The gaps in a proposal are where disputes live. If something is not written down as out of scope, it will eventually be treated as in scope by you and out of scope by them.
Second: who will actually be working on the project? Ask to meet the developers assigned to your engagement. Agencies that close deals with senior architects and hand off execution to junior developers are common. If the proposal includes senior rates, the people building your product should be senior.
Third: what do you own if the relationship ends at each milestone? A contract that does not define what you own at each delivery gate — source code, credentials, documentation, infrastructure access — is a contract written to protect the agency. You need to be able to walk away with a working, deployable product at each phase boundary, not a half-finished codebase that only the agency understands.
Key Takeaways
- Get explicit written documentation of what is excluded from scope
- Meet the developers assigned to your project before signing, not just the sales team
- Confirm you receive full ownership of working, deployable code at each milestone
- A contract that does not define exit ownership protects the agency, not you
The Bottom Line
At StepTo, we scope every project with a paid discovery phase, define deliverables at each milestone, and walk clients through exactly what the contract includes and what it does not — before anyone writes a line of code. We are not going to hand you a fixed-price quote in 48 hours, because an honest quote requires actual scoping work. If you are evaluating agencies right now and want to understand what a well-structured software development contract should look like for your specific project, we are happy to have that conversation.
Building a team in Eastern Europe?
StepTo helps European and US companies build senior-led nearshore engineering teams in Serbia. Let's talk about what your next engagement could look like.
Start a conversation