Web Apps & Platforms
Customer portals, booking engines, dashboards and SaaS products — designed around how your business actually works, and built to keep growing after launch.Customer portals, booking engines, dashboards and SaaS products — designed around how your business actually works.
Off-the-shelf software makes you work its way. We build platforms that work yours.
Service businesses running on spreadsheets, email and manual re-typing.
Companies whose customers need their own accounts and self-service.
Founders turning a proven service or idea into a SaaS product.
Built as modules, not a monolith.
Each part of the platform is its own module on a shared data layer, so new features plug in without rebuilding what works.
Six platforms we build most often.
-
03.1
Customer portals
Self-service accounts where clients see orders, documents, invoices and messages.Self-service accounts for orders, documents, invoices and messages.
-
03.2
Booking & scheduling
Availability, reservations, payments and reminders in one flow.
-
03.3
Dashboards & reporting
Live data from your tools, shaped for decisions rather than decoration.Live data from your tools, shaped for decisions.
-
03.4
SaaS products & MVPs
From a first validated version to a subscription product with billing.From a first validated version to a subscription product.
-
03.5
Internal tools
Back-offices that replace spreadsheets and email chains with one reliable system.Back-offices that replace spreadsheets and email chains.
-
03.6
Marketplaces
Two-sided platforms with listings, roles, payouts and moderation.Listings, roles, payouts and moderation.
Sound familiar?
“Orders arrive by email, phone and messenger — and get lost.”
One ordering portal your customers and team share, with status updates sent automatically.One ordering portal your customers and team share, with automatic status updates.
“Our team re-types the same data into three systems.”
An internal tool connected to your CRM and accounting, so data is entered once.
“Clients keep asking where their project stands.”
A client area with progress, files and approvals in one place.
“We have a proven service and want to sell it as software.”
A SaaS first release with accounts, subscriptions and onboarding — ready to test with real users.A SaaS first release with accounts, subscriptions and onboarding.
What you get.
- Discovery workshop & product scope
- User flows & clickable prototype
- UI kit built on your brand
- Responsive web application
- Admin panel with roles & permissions
- Integrations & API documentation
- Staging environment & QA
- Launch, analytics & handover
A modern stack, connected to the tools you already use.A modern stack, connected to your tools.
We choose the stack for your product and team, and document it so anyone can maintain it.Chosen for your product and team, and documented so anyone can maintain it.
Frontend
Backend & data
Integrations
AI & automation
Ship a first version. Then grow it.
-
v0.101 / Discovery sprint
Map users, roles and data. Agree what the first release must do — and what can wait.Users, roles and data mapped. First release agreed.
-
v0.502 / Prototype
Clickable flows tested with real users before production code.Clickable flows tested with real users.
-
v0.903 / Build
Short cycles with a staging link, integrations connected as we go.Short cycles with a staging link and integrations.
-
v1.004 / Launch
Data migration, QA, monitoring and training for your team.Migration, QA, monitoring and team training.
-
v1.x05 / Iterate
New modules, automations and improvements based on real usage.New modules and automations based on real usage.
Questions we hear first.
No. We start with the smallest release that solves the main problem, put it in front of real users, and add modules once the first version proves itself.No. We start with the smallest release that solves the main problem, then add modules once it proves itself.
Yes. Most platforms we build talk to a CRM, accounting, email and payments from day one — through their APIs or through workflow tools like n8n and Make.
Often, yes. We start with a short technical review, then agree what to keep, what to fix first and what to rebuild over time.
You do. Code lives in your repository and your accounts, and everything is documented for handover.
We stay on for support and new releases — or hand over to your team with documentation and training. Most clients keep building with us.
Let’s map your first release.
Tell us who will use it and what they need to get done. We’ll come back with questions, a first scope and the right team.Tell us who will use it and what they need to get done. We’ll come back with questions and a first scope.
Start a project