From idea analysis and wireframes to design, a working app and a beta in 6 weeks — with an agreed scope, price and deadline. Analytics and payments from the start; you own the code from the first save.
Four things always included in a Balance IT MVP package.
Problem brief + personas + scope → quote within 24h with a 6-week plan.
Fixed price, fixed scope, fixed deadline. A scope change during development means a new quote for a separate sprint.
From brief to real users in 6 weeks. Iterations based on real feedback from beta day 1.
Repository on your GitHub from the first commit. Analytics (Mixpanel / PostHog) set up on your account.
The MVP goal: validate a hypothesis on the smallest budget. Iterate on real feedback instead of inventing features in a room.
Discovery sprint (interviews + JTBD + competitive analysis)
Wireframes + clickable prototype before coding
Sprint-based development + demos every Friday + beta release in weeks 5-6
Fixed scope, fixed deadline, fixed price. A change means a new quote.
Best-in-class for an MVP. You can switch to a dedicated stack after validation.
Early user list ready from week 1. Beta release in weeks 5-6.
Weekly analytics + interviews → priorities for the next sprint.
Choose the pace and scope — always at a fixed price with a fixed scope and deadline. Prices exclude VAT. The amounts shown cover the package scope; extra work requires an agreed scope and a confirmed quote.
4 weeks, 3-5 screens
6 weeks, multiple features
8 weeks, complex scope
Discovery, design, development, payments, analytics, beta. Every element built in from day 1, with nothing left until after the MVP.
1-week discovery sprint: 5-10 interviews + competitive analysis + JTBD map + persona priorities.
Low-fi wireframes → high-fi in Figma → clickable prototype before coding. Iterations based on feedback before development.
Best-in-class for an MVP. Next.js + legacy CMS = full-stack in 2 weeks. Vercel hosting from day 1.
Stripe Billing + Customer Portal + webhooks from day 1. Nothing left until after the MVP.
User events + funnels + retention from the first beta user. You know where customers get stuck.
Beta release on a Vercel preview URL + invite-only access (Postmark email invites). Weekly iterations.
We review these questions with you before we confirm the scope and deliverables.
Scope and handover
What should a user be able to complete in the first release?
Who is responsible for data, access and integrations?
What acceptance criteria must the working release meet?
How will we hand over code, documentation and agreed support?
The Balance IT standard
Fixed price, fixed scope, fixed deadline.
From brief to real users — a fixed deadline.
GitHub from the first commit, Mixpanel on your account.
Weekly analytics + beta user interviews → priorities for the next sprint. No inventing features in isolation.
Each stage has a dedicated team and success metrics. That is how we make MVP projects as polished as our homepage.
Each stage ends with a demo and approval. Only then do we invoice and move on.
Week 1 · 5-10 interviews + analysis
Week 2 · clickable Figma prototype
Weeks 3-5 · sprints + demos every Friday
Week 6 · launch + iterations
Loading projects...
Answers to frequently asked questions about MVPs