Startups
Product, architecture and engineering for founders, and financing strategy with our partners at Salford Ventures. Architecture in week one, a working product in week three, and a codebase your first hire can run.
Bespoke One Coworker. AI assistant. Answers in seconds, estimate in three minutes.
The month-nine problem
By then you have users, a second engineer and a roadmap. Every shortcut from month one now sets the pace of month ten.
Product shipped
Month nineThe head start is spent.
The head start
The bill
Months from the first commit
| At month nine | Built to demo | Built to last |
|---|---|---|
| Changes | One change breaks something two screens away, because the rules live inside the screens. | A change lands in one place, because interface, rules and data are separate layers. |
| Accounts and payments | Permissions are a dozen if-statements, because login and payments came last. | Accounts, roles and payments are designed in week one, before the first screen is built. |
| Releases | Releases slow down, because nothing is tested and every deploy is a held breath. | Shipping stays boring: automated tests and a release pipeline from the first commit. |
| Handover | Nothing ships while one person is on holiday, because only they know how to deploy. | Any engineer can deploy, because the setup and the decisions are written down. |
Founders and young companies we build with, from first version to scale.
Zovi
Beauty Circle
What you get
Every first version we build runs on the same schedule, so at each point you know what you should be holding.
Week 1 to handover
Week 1
We agree the foundations with you and write them down before the first screen is built.
You hold
Kept in your own tools, such as
Week 3
The first release goes live where you can try it. From then on, one review call steers what ships next.
You hold
Kept in your own tools, such as
Handover
We walk whoever takes over through it. Then you run it yourselves, or keep us on to operate it.
You hold
Your market
Pick yours. This is the problem your customers live with, and the first version we would build for it.
The problem
The front desk spends the morning on reminder calls and rebookings. Patient records sit in one system, invoices in another, and nobody sees which patients have quietly stopped coming back.
What we build
A patient app and clinic dashboard built on foundations that hold at the second clinic and the tenth. We built Zovi this way.
Usually connects to
Every patient, every site, one view.
The problem
Senior people spend their evenings on time sheets, engagement letters and status reports. Knowledge lives in inboxes, so every new case starts from a blank page.
What we build
A client portal or a productised service, built to scale past the first ten customers.
Usually connects to
The firm's memory, finally searchable.
The problem
Orders arrive as PDFs and emails and get typed into SAP by hand. Planning runs on a spreadsheet that one person understands.
What we build
Industrial software for a new product line, built to talk to your customers' SAP from the first release.
Usually connects to
Orders that reach SAP without a keyboard.
The problem
Customer service answers the same twenty questions all day. Returns are processed by hand, and by Friday the shop, the stock and the books disagree.
What we build
A commerce product or marketplace built for the traffic your launch plan promises.
Usually connects to
Shop, stock and books that agree on Friday.
The problem
Bookings, changes and documents arrive by email at all hours. The team types them into three systems, and customers call to ask where things stand.
What we build
A booking or travel product built on the integrations that make it work. We built Valhalla Trip this way.
Usually connects to
The customer knows before they ask.
The problem
Applications and claims arrive as documents and get checked by hand against rules everyone knows by heart. Every audit means a week of collecting evidence.
What we build
A fintech or insurtech product built with the audit trail and access control your regulator will ask about.
Usually connects to
An audit trail written while the work happens.
The problem
The roadmap is full, support tickets keep pulling engineers off it, and the internal tools are scripts nobody owns.
What we build
A first version with the architecture, pipelines and documentation to grow on, so month nine isn't a rewrite.
Usually connects to
Engineers back on the roadmap.
Made and hosted in Germany
Your data stays in German data centres run by ISO/IEC 27001 certified partners, under the GDPR. We design, build and support everything from Düsseldorf.
Our own ventures
We build products of our own on the foundations this page describes. The advice here is advice we live with.
Our own product: the clinic CRM and white-label app platform, from the first line of code to production.
Clinic chains win a patient once, then lose them to the clinic down the road. Patients want an app with their own clinic's name on it, and chains need one view across every site.
So Zovi is one platform that every chain runs under its own name, and adding a chain is configuration work. That is a foundation decision: get it wrong in month one and every new customer becomes a rebuild.
Products we built with founders, each with its own case study: the timeline, what we built and the screens.
Clinic and workforce SaaS
The patient app for clinic rewards, memberships, booking and offers, connected to the clinic by invitation or QR code.
AI and talent technology
AI job matching, CV optimisation, interview practice and candidate screening, with people making the final hiring call.
Clinic and workforce SaaS
AI shift scheduling, mobile time tracking, absences, contracts and payroll for shift-based teams across several locations.
Connected and emerging products
A mobile app, a web app with a dashboard, and sensor integrations with the data flows behind them, for care homes.
Connected and emerging products
Fleet management, real-time tracking and an advertising inventory for e-scooters with integrated LED surfaces.
Financing
The product is half of a startup. Through our partners at Salford Ventures GmbH you also get financing strategy and consultation, so the money and the product plan line up from day one.
Which kind of money fits your stage and your plan, how much, and when to raise it.
Sessions with the investment team at Salford Ventures on your plan, your numbers and your story.
Architecture, code and a working version in order, built by us, so technical due diligence is a short conversation.
From the first call to a system in production.
The people you meet in the audit are the people who build and run it.
30 minutes with Sam
Bring the deck or the half-built repo. You leave knowing what the first version needs and what it can skip.
Estimate
Pick web or mobile app, answer a few questions and get an indicative range with timeline and team.
