Before you spend months and real money on development, find out what the first version actually needs to prove — and which of those ten ideas can legitimately wait.
$950 · one product concept · 5 business days once context is ready
V1 Brief — preview
Illustrative — your Brief is built from your own idea and answers.
Not spending is also a decision — it just gets more expensive to reverse the longer it waits.
Right now
A wrong guess costs a conversation.
The V1 boundary is still just a decision — changing your mind here costs nothing but time.
Mid-build
A wrong guess costs sprints.
Code exists for the wrong version. Undoing it means rewriting, not reprioritizing.
After launch
A wrong guess costs trust.
Early users formed an opinion of the wrong product. That's harder to walk back than code.
This sprint happens at the first stage, on purpose — while the boundary still only costs a conversation to change.
The wishlist
The first version
What this produces
3 things ship in V1. The other 4 — real, not forgotten, just not yet.
Tap Build now or Not yet — watch a wishlist become a version.
Not a guess about what development will cost. A bounded price for the one decision that determines what that development actually builds.
What you'll know
The mechanics
Not included
Implementation, a clickable prototype, UI design, and invented market validation.
This isn't a hypothetical framework — it's how we actually scoped a real founder's first release when the real vision was bigger than V1 could carry.
The full vision
A logistics marketplace with a sophisticated variable-pricing engine
What shipped as V1
The operational core: booking, serviceability, payment, admin
Operational V1, shipped — client identity withheld by request
What actually shipped in V1
Explicitly not in V1
The Pricing Engine — distance bands, labor, urgency, specialty items, margin protection — was designed and documented as a defined V2. It was planned, not built. The vision stayed intact; it just didn't have to ship on day one to prove the operational loop worked.
A bigger vision doesn't mean a bigger V1. It means knowing which part of the vision needs proving first — and being honest that the rest is designed, not shipped, until it earns its place.
Read the full Liftly case studyThe other half of this: once V1 is defined, it has to survive contact with real usage.
BUILT
Knipsr — event media platform, launch-ready
A no-login, QR-based guest upload experience up front — durable background processing, retry and recovery, and real event-day load underneath. Simple where guests touch it, engineered where it counts.
See the case study"We could not be happier about working with Zumetrix Labs! What has started as an idea has turned into a really great projekt/product, which only evolved into its full potential through the corporation, ideas, experience, professionalism and openness from our developer."
Founder, Knipsr
We name what ships now, what waits, and why — then build the part that ships so it holds up.
Why can't I just give my developer a feature list?
A feature list is a wishlist, not a decision. It doesn't say what the list needs to prove, who it's really for, or what should wait — which is exactly what makes early development guesswork expensive.
Isn't this just a PRD?
A PRD documents everything a product could have. This sprint decides what your first version needs to prove and cuts the rest on purpose — it's short because most of what's excluded doesn't belong yet, not because we ran out of time.
Why pay $950 before paying someone to build?
Because the $950 decision is cheap to get wrong and expensive to skip. A misjudged V1 costs weeks of development, not a conversation.
What will I actually receive, and can another developer use it?
A Build-Ready V1 Brief: proof target, critical journey, what's in V1, what waits, and a build sequence. It's written to be handed to any competent team — yours, another one, or us.
What if the idea changes later?
It probably will, a little — that's normal. The Brief isn't a contract, it's the clearest starting boundary we can responsibly give you today.
"If an agency scopes my V1, won't they just shrink it enough to sell me V2?"
There's no incentive to play that game: the Brief costs $950 whether V1 turns out small or larger than you expected.
Our job isn't to make your V1 smaller than it should be. It's to make it exactly as small as it can responsibly be.
Three equal branches, on purpose — the Brief doesn't favor any of them, and neither does its price.
Show us the idea
One application. No pitch deck, no prototype required — just what you're actually trying to build and for whom.
We decide if this fits
Standard fit, custom scope, or an honest no — before you pay anything.
We shape V1
Proof target, critical journey, what belongs and what waits. Payment and intake happen here, not before.
You leave with a buildable V1
A Build-Ready V1 Brief and a founder walkthrough — yours, regardless of who implements it.
That's fine, as long as there's a real concept and you're ready to make decisions about it. What we need is a founder who can answer questions, not a finished pitch deck.
One core idea with one primary V1 decision behind it — even if it touches multiple user types or a few integrations. If it genuinely needs multiple business models, original customer research, or full UX/UI design before V1 can be scoped, we'll say so before you pay, not after.
Then that's what the Brief says, with the reasoning behind it. We're not paid more for a longer V1 — the sprint costs the same $950 whether V1 turns out to be small or larger than you expected.
We'll say so before asking you to pay anything, and tell you why — either a custom scope that fits your actual situation, or point you at Product Rescue or Manual-to-System if one of those is actually the better fit.
Once payment, a short intake form, and the context we need to define V1 responsibly are all in place — not the moment you pay. If gathering that context takes a few extra days, the clock waits for it.
No. Notes, a working call, or just clear answers to our questions are enough to start. If you do have research or mockups, they help — but they're not a requirement to apply.