Summary
You’ll have a working MVP that customers can sign up for, log into, and pay for, with the right permissions in place and an admin view that lets you run the day-to-day without patching spreadsheets.
I’ll turn that into a web app MVP people can log into, pay for, and use. I lock scope early, show you working software fast, and build the fundamentals first so launch day isn’t a scramble. If you want to move, the next step is a short workshop to nail the flows and the exact MVP boundary.
I start by turning your current demo into a scoped plan that can ship. We’ll agree the exact user roles, the paid path, and the admin work you need to run the product. Then I build in short stages, with a staging link early, so you can click through real screens and confirm the direction before I go deeper.
Who you are working with
I’m Mads Nørrebo, a product developer. I build web apps for founders and small teams who have proof of demand and need the first version to be usable, billable, and supportable. Most of my work starts right where you are now: a clear idea, a waitlist or internal users, and a manual process that is starting to break.
I’m the person writing the scope, building the app, and shipping it. That keeps decisions fast and reduces handoffs. I also build the “boring” parts early, because late-stage billing and permissions work is where schedules slip and products launch with gaps you can’t charge through.
How the order runs
After you sign, I move from scope to working software in a straight line: lock the MVP boundary, confirm the flows with a clickable prototype, then build and iterate in staging until it’s ready to launch and hand over.
- Scope lock workshop On order I run a half-day product discovery workshop with you. We leave with a written scope that names what the MVP includes, what it does not include, and the launch checklist. I’ll also confirm the roles, the paid plan structure, and the three third-party APIs we’re integrating.
- Clickable prototype Within a week I turn the scope into a clickable prototype for the core flows: signup, login, upgrade, and the main “job to be done” inside the app. You review it like a user would. Your approval here is what I build against, so changes stay cheap and obvious.
- MVP build in staging Weeks 1-3 I build the MVP and share a staging link as soon as the first end-to-end slice works. You’ll be able to log in and click through real screens, not just look at designs. I’ll ask for feedback in short batches, and I’ll keep a written list of what is in and what is out.
- Launch and handover On delivery I run a launch-day checklist with you: production setup, Stripe live-mode checks, admin access, and basic monitoring. Then I hand over the repo, environment notes, and a short “how to run it” guide. You get a final walk-through call so you can ship with confidence.
Product discovery workshop
A half-day working session to define the MVP boundary, user roles, paid path, and launch checklist, ending with a written scope I build against.
Web app mvp build
A working web app MVP delivered with a staging link during development and a production deployment at the end, based on the agreed flows and scope.
Stripe billing setup
Stripe checkout and subscription billing wired into the app, including plan setup, webhook handling, and live-mode validation so you can take payments on launch.
Auth and user roles
Login, signup, password reset, and role-based access rules for the roles agreed in the scope lock, so each user sees and can do the right things.
Admin dashboard
An internal admin area to manage users and subscriptions and to view the operational data you need to support customers without database edits.
3rd-party api integration
Integration with up to three external APIs named in the scope, including error handling and basic retries, with a clear note of any API limits that affect UX.
Order summary
These line items cover the full web app MVP build as described, including the scope lock workshop, prototype, staging MVP, and launch handover.
Next steps
If you want me to hold time for this, sign below and I’ll send the booking invoice and a short checklist for the workshop.
- Sign the proposal to confirm the web app MVP build.
- Pay the booking invoice for 50% to reserve the start date.
- Share access to Figma, Stripe, and the current spreadsheet or tool so I can prep the workshop.
What do you need from us before you start?
Access to your current materials and accounts: the Figma, the spreadsheet or current tool, and the Stripe account you want to use. I’ll also need one person who can answer product questions quickly and sign off on the prototype and scope.
When can we see something working, not just designs?
You’ll see two kinds of “working” early. First is the clickable prototype, which confirms the flows before I build. Then I’ll share a staging link as soon as the first end-to-end slice is running, so you can log in and test real screens.
What’s included in the MVP and what’s explicitly not?
What’s included is the list in “What you are ordering”, plus whatever is written into the scope we lock in the workshop. Anything outside that boundary is treated as a change, priced and scheduled before I start building it.
Who fixes bugs in the first few weeks after launch?
I do. For the first two weeks after launch, I’ll fix bugs that are inside the agreed scope and that prevent normal use of the MVP. New features and new edge-case requirements are handled as follow-on work once the MVP is stable.
Payment
50% is due to book the work when you sign. The remaining 50% is due when I deliver. Invoices are payable within 14 days of the invoice date.
Start and schedule. I start after the booking payment is received and I have the access I need. If feedback or approvals pause, the timeline shifts by the same amount the project is waiting.
What I need from you. Before I start, I need access to your current materials and accounts, including Figma, your spreadsheet or current tool, and the Stripe account you want to use, plus one decision-maker for quick sign-off.
Scope and changes. The web app MVP build is based on the scope I lock with you in the workshop and confirm in the prototype. Anything outside that boundary is a change, priced and scheduled before I build it.
Approvals and rework
I ask for written approval on the scope and on the clickable prototype before I move into the main build. If I build against approved work, later reversals are treated as changes.
Access and third parties. If the MVP depends on third-party services, I can only build and test against what their accounts, APIs, and uptime allow. Time spent diagnosing external outages or account issues is follow-on work.
Bug fixes after launch. For the first two weeks after launch, I fix bugs that are inside the agreed scope and that block normal use of the MVP. New features and new edge-case requirements are follow-on work.
Liability limit. I’m not responsible for lost revenue, lost data, or indirect damages related to use of the MVP. If something goes wrong, my responsibility is limited to the amount you paid for the work.








