The commission process
How a piece gets made
The same discipline our own products are built with — applied to yours. Five movements, concrete deliverables at every one, demos every week. No mystery.
01
Week 0 · free
Discover
A free consultation where we map the problem, not just the spec. We ask what the software must change about your business — then scope backwards from that.
You walk away with
- A written problem map
- Scope options with trade-offs
- A go/no-go recommendation — even if it's 'don't build this'
02
Days, not weeks
Estimate
AI-assisted estimation against our own delivery history. You get a transparent quote — hours, cost, complexity, the stack we'd choose and why.
You walk away with
- Itemized estimate (hours × phases)
- Recommended architecture & stack
- Fixed milestones with acceptance criteria
03
Weeks 1–2
Design
A design system per product, not per page. Tokens, components and motion language first — so every screen after the first one gets cheaper.
You walk away with
- Design tokens & component library
- Clickable key screens
- Data model & API contract draft
04
Weekly rhythm
Build
Weekly demos on a staging environment from week one. CI/CD with gated releases, migrations and smoke tests — the same pipeline our own products run on.
You walk away with
- Staging URL from week 1
- Weekly demo + written changelog
- CI/CD with automated tests & gated deploys
05
Ongoing
Run
Launch is the midpoint, not the finish. We observe, iterate and carry long-term ownership — most of our client relationships span years.
You walk away with
- Monitoring & alerting in place
- Handover documentation
- Support & iteration retainer (optional)
The fine print, in large type
What you own: everything.
You own the code
Full IP transfer on final payment. Your repositories, your cloud accounts, your data — from day one where possible.
No lock-in, by design
Standard stacks, documented decisions, handover docs as a deliverable. Any competent team can pick up where we leave off — that's the point.
Transparent by default
You see the staging environment, the board and the pipeline we see. Weekly demos are of working software, not slideware.
EU-based, GDPR-first
A Romanian SRL under EU law. Data-processing agreements, EU hosting and privacy-by-design come standard, not as an upsell.
Ways of working
Three ways to commission us
Product build
Milestone-based delivery of a complete product — discovery to launch. Best when you have a vision and need a team that has shipped platforms end-to-end.
Dedicated team
A senior Prime Labs cell embedded in your roadmap, month over month. Best for platforms that never stop evolving.
Team augmentation
Hand-picked engineers joining your existing team — matched for expertise and for fit. Best when you need depth fast without restructuring.
Asked at the desk
Questions clients ask
Who owns the code and IP?+
You do. Full intellectual-property transfer is written into the contract and completes with the final payment. We work in your repositories and your cloud accounts whenever possible, so there's nothing to 'hand over' at the end — you had it all along.
How do you charge?+
Milestone-based fixed pricing for defined scopes, monthly for dedicated-team and augmentation work. Every estimate is itemized — you see hours per phase, not one opaque number. No charge for the initial consultation or the estimate.
How fast can we start?+
The consultation can happen this week; the estimate follows within days. As a focused studio we run at most a few engagements at once — when we commit, you get senior people, not a bench.
What if we already have a team?+
Two options: team augmentation (our engineers join your team and your process) or a parallel workstream (we own a module end-to-end and integrate through an agreed contract). Both are common; the second scales better.
Do you sign NDAs?+
Yes, before the first substantive conversation if you prefer. Confidentiality of your idea, data and codebase is standard in our contract regardless.
What happens after launch?+
Every project ships with monitoring, alerting and handover documentation. Most clients keep a support & iteration retainer; some hand the system to an internal team — we help with that transition too.
Can you work with our existing codebase?+
Yes. We start with a paid technical audit (which you keep either way), then propose either incremental improvement or a staged rewrite — whichever the audit actually supports. We've inherited codebases in most major stacks.