What are watermelons and grapes in software projects?
THE SHORT ANSWER
A watermelon is a big software engagement: twelve people, eighteen months, variable scope, and one bad outcome can kill the relationship. A grape is a small bet with the same upside. Watermelons and grapes is how New Era Systems describes shrinking the risk of a project while keeping its full value.
Why the size of the bet matters
A big engagement isn’t adversarial because anyone has bad intentions. It gets that way because the stakes are too high for honesty. Once both sides are deep in, nobody can absorb a scope change without conflict, so problems get managed instead of surfaced.
Shrink the blast radius of a mistake and that changes. The client can raise problems early. The practitioner can correct course without a fight. You don’t build trust by never failing. You build it by making failure survivable.
What it looks like in practice
The work ships as small, finished pieces, and each one is a checkpoint. You can continue, change course, or stop, and no piece is big enough to trap you. The methodology has the full argument, and prototype-first covers how the first grape gets made.
COMMON QUESTIONS
Is this the same as Agile?
No. Agile takes a watermelon and cuts it into pieces, and you still bought the watermelon. Here the bet itself is the size of a grape, with the upside of the whole watermelon.
Why are large software engagements risky?
When a project stretches across months with variable scope and a large team, neither side can afford to be honest about early problems. Both have too much invested, and the adversarial relationship tends to set in around month four.
What makes small bets possible now?
AI-accelerated development cut the time to implement, so a project that once took a large team can be small enough that a mistake costs little. What stays scarce is knowing what to build, describing it precisely, and holding the line on quality.
KEEP READING
Definitions What is anti-discovery?
Anti-discovery is how New Era Systems replaces the paid discovery phase. It is a free targeting exercise that takes days, not weeks, and looks for enough signal to build something real. If we can't find that signal, we tell you and both sides walk away with no invoice.
Read the guide →
Definitions What does prototype-first software development mean?
Prototype-first means you use working software before you commit to building the rest. At New Era Systems, the prototype follows a free targeting exercise, and if it doesn't convince you to proceed, you owe nothing. You pay once there is evidence that the work is worth continuing.
Read the guide →
Deciding Should your firm build its own compliance software or keep renting it?
Build when the vendor charges you again for every client and the tool sits inside the product you sell. Keep renting when the bill is small and stays small, or when the software has nothing to do with what clients pay you for. To check, add up what you pay per year, then compare it with the cost of owning.
Read the guide →BRING US THE PROBLEM.
A targeting exercise that costs you nothing, a working prototype before you sign anything, and a date that holds.