Your SaaS, in your customers’ hands.
You know the problem and the first journey to deliver. We develop a SaaS product your initial customers can use, with the foundations needed to join and get value from the service.
A specific use.
A first commercial release
Let a customer sign up and reach the promised result.
A B2B product
Organise the workspaces, members and access rights required.
A subscription service
Connect payments and usage rights when that model is chosen.
What we build.
The core product journey
A coherent experience from arrival to the action that delivers value.
A deployed product on your own domain, open to sign-ups, with a recording of one account going from nothing to the paid action.
Service essentials
Accounts, administration and subscriptions within the agreed scope.
An admin console you sign into, and a billing account in your name at the payment provider with the plans already configured.
A prepared launch
Checks on key journeys, management access and useful usage measurements.
Automated checks that run on every deploy, an analytics workspace under your account, and the deployment pipeline handed over.
How long it takes.
Ten to sixteen weeks to a version your first paying customers can use, and billing rules move that number more often than screens do. A staging product with sign-up and the main journey working is available at the end of week four.
What we need from you.
Ten first customers, by name
Companies or people who have agreed to try the product, with someone to talk to at each. Their answers settle a scope argument in an afternoon that would otherwise run for a month.
A decision on what you charge for
The pricing model before we build accounts, since a per seat plan and a usage plan need different data from the first table onwards.
Company details for the payment provider
Registration documents and a bank account in the company name. Stripe and its equivalents can take two weeks to approve an account, and nobody can pay you before then.