Free MVP estimate
Scope, Timeline And A Cost Range For Your MVP, In Two Working Days.
Send a short brief and get back an approach, a rough timeline and a rough cost range for your first version, with the assumptions and exclusions written out. It is a range to plan with, not a quote. You can read a full sample below first.
- 2 working daysfrom your brief
- No call neededa call only if you want one
- Not a quotea rough range to plan with
Already running a live product? This estimate is for a first version. Modernise your SaaS without a rebuild is written for you.
The sample estimate
Read An Estimate Before You Ask For Yours
This is the format you will receive, filled in for ShiftDesk, a fictional staff rota app for small clinics. It shows the scope we heard, what goes in the first version and what we would leave out, the approach, the effort, what moves the cost, and the assumptions, exclusions and risks behind it.
One difference: your estimate gives the timeline in weeks and the cost as a range. This sample shows effort as shares of the work instead: without your scope, any number would be a guess.
Provis TechnologiesMVP estimate
ShiftDesk: the first version, the approach, and what moves the cost
From a one-page brief: a staff rota app for small clinics, run by the office manager.
Illustrative sample. Example Rota Co. and ShiftDesk are fictional. This sample shows the format of an estimate; it is not a quote or a past engagement. Your estimate gives the timeline in weeks and the cost as a range; this sample shows effort as shares of the build instead.
Your brief, in our words
What we think you are building
A web app for small clinics. The office manager builds the weekly staff rota in minutes instead of a spreadsheet, staff see their shifts on their phone and ask to swap, and the manager approves swaps in one place instead of on the phone.
The one user
The one job
Success signal
Decision point
Open questions we would ask by email
- Do staff work at more than one clinic?
- Which rota rules are hard rules (rest periods, required roles on each shift)?
- Must swaps be between staff of the same role?
- Do clinics pay monthly per clinic or per staff member?
The first version
Must, later and cut, with the reason
Must
- Manager builds the weekly rotaThe one job. Everything else supports it.
- Staff see their shifts on their phoneA web app that works on phones; no app store.
- Swap requests, approved by the managerThe phone calls you said you want to end.
- Email reminders before a shiftCheap to send, and enough to test the idea.
- Clinic sign-up and a monthly subscriptionYou said clinics must pay from day one; Stripe handles it.
Later
- SMS remindersEach message costs money. Add it if email reminders are missed.
- Payroll exportUseful, but no clinic will choose ShiftDesk for it.
- Screens for clinics with several locationsThe data model includes location from day one, because adding it later costs more. Only the screens wait.
Cut
- Native iOS and Android appsWe advise against this in v1: the web app does the job.
- Automatic rota suggestionsWe advise against this in v1: learn the real rules first.
Approach
What to build, and what to buy
| Part | Recommended | Why |
|---|---|---|
| Web app that works on phones | Laravel and React | One app for desktop and phone; staff use it in a phone browser. |
| Login and roles | The framework's built-in login | Proven, and two roles are enough. |
| Subscriptions | Stripe Billing | Plans, trials, invoices and failed cards, already solved. |
| Email reminders | Postmark or Amazon SES | Reliable delivery without running a mail server. |
| Admin | Filament, a ready-made Laravel admin panel | No custom admin panel in v1. |
| Hosting | AWS | Room to grow, in your own account. |
Running costs after launch
Paid to the providers, not to us. Your estimate lists each one with its monthly cost at your expected size.
| Service | Charged |
|---|---|
| Hosting | Per month |
| Email sending | Per message, after a free allowance |
| Stripe | Per payment |
| Error monitoring (for example Sentry) | Per month |
| Domain | Per year |
Effort and phases
Where the work goes, and in what order
Share of the whole engagement, in the order the work happens. Project management and the contingency run across all phases. Your estimate turns these into weeks.
Phases (project management and contingency run across all five)
- 1Discovery and design. The written scope, user flows and a clickable prototype of the rota builder.
- 2Build cycle 1. The rota builder. Your first demo you can click through yourself.
- 3Build cycle 2. Staff view and swap requests.
- 4Build cycle 3. Sign-up, billing, email reminders and admin settings.
- 5Test and launch. Testing on a private copy (staging), the go-live checklist, launch.
Team shape
What the contingency covers
The cost range
What puts it at the low end or the high end
Your estimate gives the cost as a range from low to high. These are the choices that decide where in that range you land.
Closer to the low end
- A standard, clean interface rather than custom design
- One location per clinic
- Email reminders only
- Rota rules kept simple: shifts, roles, leave
Closer to the high end
- SMS reminders in v1
- Screens for several locations in v1
- A payroll export in v1
- Complex rota rules: rest periods, overtime, skills
Three decisions that move it most
- SMS or email reminders. SMS adds a paid service and more testing.
- Screens for one location or several. The data model allows several from day one, which is cheap. The screens for managing them are what add cost.
- How complex the rota rules are. Each rule (rest periods, overtime, skills) adds logic and tests.
Confidence
The fine print, written out
Assumptions, exclusions, risks and the next step
We assumed
- Web app only; staff use a phone browser
- Two roles: manager and staff
- One location per clinic at launch; the data model already allows more
- You provide the content and the clinic rules
- Stripe is available in your country
- English only
Not included
- Custom illustration and branding work
- Native app store apps
- Importing old rotas from spreadsheets
- Running costs after launch (hosting, email, Stripe fees)
- Support after launch, agreed separately
Risks
- The rota rules are more complex than the brief. Discovery confirms them before the build.
- Staff don't open the reminders. Test email first; add SMS only if needed.
- Clinics expect payroll on day one. Ask five clinics before the build starts.
Your next step, your choice
- Keep this, and do nothing yet. It still tells you what the first version is.
- A discovery phase. It turns this rough range into a firm quote, from the written scope and prototype.
- Start the build. From the discovery output, in the cycles on page 5.
What's inside this estimate?
- Our understanding of your requirements
- MVP scope: must, later, cut
- Recommended approach
- Effort, phases and timeline
- Key cost drivers
- Assumptions, exclusions and next steps
Document details
- Pages
- 7
- Format
- Last updated
- October 2026
What it is, and what it isn't
A Range To Plan With,
Not A Quote
The MVP estimate gives you clarity on the first version: the approach, timelines, costs and assumptions. A firm price comes later, once we understand your scope in detail.
A clear one-pagerfor your first version
You get
- An approach for your first version
- A rough timeline
- A rough cost range
- The assumptions and exclusions behind them
- Within two working days of your brief
You are not committing to
- A call
- A contract
- Any next step: a discovery phase or a build is a separate decision
-
A firm price comes later.
It needs a closer look at your scope, and the estimate says what that would take.
-
No code or designs needed.
A short brief is enough.
-
A better brief, a narrower range.
The clearer the first version, the tighter the range. The MVP one-pager from our playbook takes ten minutes to fill in.
Who reads it
Read By The Team That
Would Build It
Our team in India (IST) reads every brief. These are products Provis has built and still runs or supports.
-
SaaS platform The Vault
An investor-relations platform listed companies pay to use, with stock-exchange data feeds. Built, maintained and supported by Provis.
-
Data platform OLiS
Poland's official music charts, built from Spotify, YouTube, Apple Music and store sales data, on Laravel and React.
-
PropTech Hauzd
Interactive 3D property tours wired into live real-estate data, for a US PropTech company.
-
EdTech American Community School
A payments platform, a dismissal app and a school store, built and still supported.
Provis Technologies has refined our practice and created some systems that really have made an impact on our campus.
Clutch5.0 · 12 reviews
Google4.6 · 36 reviews
UpworkTop Rated
200+ projectssince 2012
Frequently Asked Questions
Questions Before You Request An Estimate
What it costs you, what you get, and what happens next.
Still unsure? Ask us on WhatsApp or send us your question.
It is free, and it is not a quote: a rough range to help you plan, with the assumptions and exclusions written out. We email it; a call only if you want one.
What you are building and the three to five things the first version must do, typed in or attached as a file. Anything else, such as who it is for or links to designs, is optional.
The scope in our words, what goes in the first version and what waits, the approach and what to buy rather than build, the effort and phases, the cost range and what moves it, and the assumptions, exclusions and risks. The sample above shows the format.
Our team in India (IST) reads every brief.
No. A short brief is enough. If you have designs, a prototype or a deck, add a link.
- 1We read your briefOur team in India (IST) reads every brief, and emails you if anything needs clarifying.
- 2Your estimate, in two working daysAn approach, a rough timeline and a rough cost range, with the assumptions behind them.
- 3A call, if you want oneTo talk it through. Nothing to commit to.
Rather pick a time yourself?
Book a 30-min call with Vivek SharmaCEO & Founder, Provis Technologies
Contact Us