SaaS and MVP · written at the studio, London
SaaS and MVP development
Wizards of Web Ltd · Saunders Ness Road · 23 October 2026
Wizards of Web Ltd builds SaaS products and MVPs from London. An MVP here is the first version a real customer can pay for or use: accounts, the one workflow that makes the product worth opening, and a way to take payment when payment is part of the offer. We use Laravel, MySQL and Vue, and we keep the first release small enough to launch.
What goes in the first version
Sign-up and login, the core records, and the action the customer repeats. Billing when the product is sold as a subscription. Admin screens so you can see accounts without asking a developer.
A marketing site can sit in front of it. The product and the brochure are separate pieces of work.
What waits
Extra roles, a public API, native mobile apps, and integrations with every tool in the category. Those are real, and they are not the first release. We will list them so they are not forgotten, then build them when the first version is in use.
After launch
The same studio can keep building once customers are using it. The point of the MVP is to learn which part they use. The next release follows that, not the original wish list.
Questions we get asked
What is MVP development?
It is building the smallest version of a product that a real user can use, so you can learn what to build next. It is not a clickable picture of the finished system.
Do you build SaaS products?
Yes. We build the application, the accounts, and subscription billing when the product charges a recurring fee.
How do you decide what the MVP includes?
We write down the one job the customer hires the product to do, and we build that path end to end. Everything else is a later release.
Can you continue after the first version?
Yes. The usual path is to launch, watch what people use, and build the next piece with the same team.