About to sign with an agency for your MVP and not sure whether what they promised is realistic — or just what you wanted to hear?
That's a fair question. And it has a catch: almost every agency will say yes to everything in the first meeting. The difference shows up three months later, when the project is on hold, the budget is gone, and the product still hasn't reached a real user.
What the budget doesn't tell you
The number on the first proposal doesn't say much on its own. It tells you how much they're going to charge. It doesn't tell you when you'll have something working, who makes product decisions when something falls outside the scope, or what happens if the deadline slips.
Say you're a founder with a home services marketplace idea — straightforward flow, clear scope. You get three quotes: a large agency at $40K with a six-month timeline, a freelancer at $8K with no delivery date, and a mid-sized studio at a fixed price with a specific deadline. The question isn't which one is cheaper. The question is which one gets you something to show a real user in eight weeks.
That's the criterion that matters when you're launching a first version.
Generic agency vs. product studio
There's a real difference between an agency that does development and a team built around product thinking. It's not marketing — it changes how decisions get made.
A generic agency executes what you ask for. If the scope is poorly defined — and in an MVP it almost always is — they charge for every change, or they deliver exactly what you asked for even if it won't validate anything useful.
A product studio will push back before you start. They'll ask what you're trying to learn, who the first-week user actually is, and what the minimum flow is to find out. That can feel uncomfortable. But it's the difference between spending money to build and spending money to learn something that matters.
Before you sign, check whether the team has that conversation with you — or just sends the quote.
The questions that actually matter
There are three areas worth checking before you close any agreement.
Code ownership. Is the repository yours from day one? It sounds obvious, but it isn't always. Some studios work in their own repos and hand over the code at the end. If something goes wrong along the way — or if you want to switch teams later — you're left with nothing. The code should be in your GitHub from day one.
Stack decisions. Can they explain why they're choosing the technologies they're choosing, or do they just say "this is the best option"? You don't need to be a developer to tell if the explanation makes sense. What you do need to know is whether they're choosing for your project or for what's most comfortable for them.
Delivery rhythm. How will you see the progress? A weekly demo is a reasonable baseline. If the answer is "we'll send email updates" or "we'll do a review at the end of the month," that's a warning sign. Projects without frequent checkpoints drift on their own.
Why the lowest price is almost never the right variable
Price matters — especially when your budget is tight. The problem is when it becomes the only variable.
The lowest quote almost always comes with one of three conditions: no delivery date, hourly billing that grows with every change, or a solo freelancer juggling other projects. Any of those can end up costing you more than paying a little more upfront.
What's worth looking for instead: a fixed price with a written delivery date. Knowing from day one how much you're spending and when you'll have something working. That lets you plan — when you can go find users, when you have something to show an investor, when you can decide whether to keep building or pivot.
What happens with speed promises
There's a claim that gets thrown around a lot: "two weeks and you have your MVP." Sometimes it's real. Sometimes it's a way to close the deal fast and stretch the timeline later.
The difference is in what fits inside those two weeks. A two-week MVP has to be a concrete, functional flow — not thirty screens, not three user types, not a reporting dashboard. If the two-week quote includes all of that, either they don't understand your project, or they're selling something they won't be able to deliver.
A good sign: the team helps you cut scope before you start. They ask what can be removed, not just what you want to add.
How Cambalache works
At Cambalache, we work with a fixed price and a written delivery date before anything starts. The code lives in the client's GitHub from day one, we run a demo every Friday, and if we miss the agreed deadline, we keep going at no extra cost.
We don't resell no-code tools or platforms as if they were custom development. Every project is built for what that product actually needs — the stack is chosen based on the use case, not on what's easiest for us.
Our MVP plans — Validate, Launch, and Scale — have fixed prices and defined timelines. We send the proposal with scope, price, and delivery date within 24 hours of the first meeting. Not as a formality, but because that's how you get to decide with real information instead of promises.