Tech & workspaces
Software development for startups and SaaS
For startups and SaaS companies, we build the MVP that puts an idea in front of real customers, the subscription billing to sell in several countries and the product site that explains what the software does. Founders learn quickly whether there is demand. If there is, the code is ready to grow with a team.
Typical problems
- The first version takes months because it tries to include every feature at once
- A rushed prototype has to be thrown away as soon as paying customers arrive
- Charging subscriptions to customers in several countries means dealing with VAT, currencies and failed payments
- Nobody on the founding team is technical enough to make architecture calls or judge suppliers
Suggested bundle
From idea to first subscriber
Picture a founder who wants to launch a shift-scheduling tool for care homes and clinics. In the first conversation, we set the wish list aside and pick the path that proves the value: the manager builds the month's rota, staff see their shifts on their phones and ask to swap. Reports, payroll exports and everything else wait for the next phase.
The MVP goes into testing with a handful of organisations the founder already knows. User sessions show that shift swaps are what people use most, and the product shifts its focus accordingly. Meanwhile, a landing page collects sign-ups from people who want to try it.
Once the first paying customers appear, billing goes live: monthly and annual plans, a free trial, invoices with the right VAT and automatic retries for failed payments.
Technical choices that keep doors open
- Mainstream, well-supported technology, so hiring developers is never the bottleneck
- Each customer's data kept clearly separate from day one, which a multi-tenant product depends on
- An audit trail of who did what, which business customers expect and the GDPR rewards
- Separate test and production environments, with automatic backups
- Documented APIs, so customers can connect their own systems
When the product uses AI
Many new products include an assistant or AI features. The EU AI Act requires users to be told when they are talking to an AI, and some uses carry stricter rules. We deal with that while designing the product, not after launch.
Frequently asked questions
What goes into an MVP?
Only the core path that proves the product's value, from sign-up to the moment the user gets the result they came for. Every other idea is parked on a backlog. We agree that path with you before writing any code, so the first version reaches users as early as possible.
Do we own the code?
Yes. With the final payment, ownership of the code, the domain and the content passes to your company. We hand over a documented repository, so an in-house team or another supplier can pick it up.
How do we charge VAT to customers in other countries?
There are two routes. With a merchant of record such as Paddle or Lemon Squeezy, that company sells to the end customer and handles each country's VAT. With Stripe, you sell directly and the tax calculation is set up in the system, but filing stays with you. We help you choose based on your market and volume.
What if none of the founders is technical?
We can act as your fractional CTO in the early stage. We make technical decisions with you, review proposals from other suppliers and help you hire when it is time for your own team.
Another team built our product. Can you take it over?
Yes. We start with a software audit to see what state the code is in and what needs fixing first. Then we decide with you whether to build on what is there or rewrite parts of it.
How much does it cost to build an MVP?
Each MVP is quoted from its requirements and the core path we want to prove. A short conversation is enough to understand the scope and put a proposal together. Request a quote
Shall we talk about your project?
Tell us what you have in mind and what you want to achieve.