How to Spot an Agency That Confuses Sold Hours With Results

Not every software agency is the same. Some work outcome-first: they want to know which customer problem has to be solved, and shape the product to solve it. Others work capacity-first: they sell hours, deliver what is asked and bill for whatever else comes up.

Both models are defensible. It only becomes a problem when the founder thinks they are buying the first and is actually buying the second.

This article looks at signals you can read upfront to tell which way an agency leans, not to distrust agencies, but to help you, as a founder, consciously choose what you are buying.

Output vs outcome

An outcome-oriented agency asks where you want to go. Their proposal starts with the customer, the problem and the measurable outcome. The technology comes after.

An output-oriented agency asks what you want built. Their proposal starts with a feature list and ends with hours. The customer and the problem appear in the introduction but stay disconnected from what actually gets built.

Both types can produce nice presentations. The difference is not in the cosmetics. It is in what the proposal is about.

Quick test: does the proposal read like an answer to a question, or like a list of work packages? An answer refers back to the question. A list stands on its own.

A lot of meetings as a warning sign

Some agencies schedule a lot of meetings by default: kick-off, weekly stand-ups, sprint reviews, retros, stakeholder demos. All normal, if they lead to decisions.

It becomes a warning sign when:

• Meetings overlap in substance.
• The stand-up is mostly status updates, not blockers.
• Demos end without a concrete choice about what comes next.
• Only the founder is steering and the agency is mostly reporting.

A lot of meetings can be a rhythm that keeps a team sharp. They can also be a way to bill hours that does not put concrete product on the table. You spot the difference by asking after three meetings which decisions have been made. With outcome agencies, a list follows. With output agencies, you get a repeat of what was discussed.

Vague ownership

Who is responsible when a feature does not work as expected? Who decides whether a built feature satisfies the original ask? Who pays for the fix when the feature turns out to be unusable?

An outcome agency has explicit answers. A capacity agency often has phrases like “we work together” or “we deliver what is agreed”. Those phrases sound reasonable but shift responsibility to you, the founder, at the moment it matters.

Ask specifically: if something is technically correct but not usable in practice, who fixes it, and at whose cost?

Scope shaped by agency logic

Some scopes are technically sensible but oddly organised from the customer’s point of view. For example:

• “First all login functions, then all profile functions, then all workflows.” Technically clean; for the customer it means nothing useful can happen until month three.
• “Backend first, then frontend.” Safe for the architects, but the founder cannot collect customer feedback until launch.
• “Infrastructure and CI/CD first, then features.” Sounds responsible, rarely fits an early product.

An outcome-oriented approach is vertical: build one narrow workflow from start to finish, so there is customer value to look at. A capacity-oriented approach is horizontal: build layers and assemble at the end. The second fits mature organisations. For a startup it is usually an expensive way to learn late.

No clear acceptance criteria

“When is this done?” is a question the agency should answer before building. Acceptance criteria are the sentences you check work against: “a new customer can create an account in under 3 minutes and complete their first action”.

Proposals without acceptance criteria leave the judgement of what counts as “done” to the supplier. For the agency, “done” is a step closer to invoicing. For the founder, “done” should mean: a customer can use this.

Ask the agency to write acceptance criteria for the three most important features. If they find that hard, they care about logging hours, not about delivering outcome.

No explicit assumptions

Every quote rests on assumptions. An outcome-oriented bidder names them in the proposal: “we assume data X, integration Y, user role Z”. A capacity-oriented bidder leaves them implicit, which means that when one of those assumptions turns out to be wrong, the price stays and an extra bill comes after.

For every proposal, ask: which assumptions make your estimate valid? What happens if one of them turns out to be wrong?

The eleven items a software quote should include covers this part in more depth.

How to ask better questions

A few questions that separate outcome- from hours-oriented proposals:

• “What is the measurable outcome this phase delivers?”, Outcome agencies have an answer. Output agencies repeat the scope.
• “What do you do if it turns out the original assumption is wrong?”, Outcome agencies adjust the approach. Output agencies bill change requests.
• “What decision can I make after phase 1 that I cannot make today?”, Outcome agencies treat phases as decision points. Output agencies treat phases as technical milestones.
• “What would make you stop the build?”, Outcome agencies name conditions (customer signal, scope shift, broken assumption). Output agencies name none.

These are not trick questions. Good agencies just answer them honestly. The ones who find them slightly uncomfortable are telling you something useful.

When to pause for a second opinion

Three moments where an independent perspective often adds a lot of value:

• Before you sign a first quote without comparable quotes for reference.
• When you have two quotes close in total but very different in structure.
• When you feel the proposal sounds reasonable but you cannot clearly explain what is on the table after phase 1.

In all three cases, an hour with someone who has seen hundreds of quotes is cheaper than another week of reading it yourself.

Judge the quote on the right things, not just the headline total. A cheap proposal that sells capacity costs more in six months than a more expensive proposal that sells outcome. Or the other way around, that is not something you can figure out alone.

---

Facing this decision?

Send me the context or book a free call. We will look at the most sensible next step before you commit time, money or focus.

Book a free call → · Email directly: hello@yourstartup.expert