Five years, every client their own app.
We are a two-person studio. Every client gets their own app, branded as theirs and run as its own project, built on a platform we have spent five years making. That is why it goes live in weeks.
What each app taught the next
The platform was not designed in advance. It was built one client at a time, and every app left something in it for the one after. Here it is, app by app.
Research · four years
A movement methodology, used in university research
A method that worked in studies, with nowhere for a participant to open it each day. We built it as a branded app with structured programmes, daily activities, progress tracking and tools for the practitioners who run it. Four years on, no interruption.
What it taught the platform: programmes. What a day in a programme looks like, how progress is kept, and that every client has their own words for things, so the software has to use theirs.
Coaching · four years
A wellness company with practitioners and their clients
They came to us instead of an agency. Their own branded app delivers meditations, practices and video programmes to their clients, and has run for four years.
What it taught the platform: a second brand. The same engine with a different name, different colours and different rules, and nothing copied by hand. And video, a library big enough that where it is hosted and how it plays became ours to get right.
Wellness
A single practitioner's practice
One person, one practice, the same platform underneath. Small, and still running.
What it taught us: a practice of one gets every improvement the larger apps asked for, at a rate sized for one person, because the platform improves for everyone at once. That is the whole idea, and this is where we first saw it hold.
Fifteen-plus deployments · eight live today
The brands in between
Over five years the same engine has gone out as fifteen-plus branded deployments, across wellness, education, research and community, and eight projects are live today. Each is its own project with its own name on it.
What they left behind: accounts and members, content, messaging and community, and admin tools a team can actually use.
Wellness · live now
MyHive
MyHive is its own app, running on our platform. Practitioners publish their offerings, take bookings and payments, and run programmes for their members. It went from nothing to live with real users, built by the two of us.
What it taught the platform: bookings and scheduling, payments, guests who book without making an account, and many practices running side by side in one app, with the admin tools to look after them.
How we work together
Four steps, the same every time. Under each one, how it went for one of the apps above.
A 30 minute call. You describe what your members do and where it breaks.
The research app began as one: a method proven in studies, and no app a participant could open.
We show you the platform running, with your situation in mind.
Since the first app there has always been one running to show, so you see a working product before you see a proposal.
We send a fixed scope and price. Setup, then a monthly rate.
The practice of one runs on a monthly rate sized for one person, and gets everything the larger apps get.
We build and you launch.
MyHive went from nothing to live with real users, built by the two of us.
Every member gets an answer
Every app on our current platform has a feedback button on every screen. A person reads every message and replies in the app, in the same thread, within one or two working days depending on your plan. Bugs are looked at every morning.
Members also put ideas on a board and vote on them. What they vote up is what we build next.
And what one app's members ask for, every app can have. A feature is built once on the platform and switched on brand by brand, so your members gain from everyone else's.
What your members notice
- A real reply, from a person, in the app they were already using.
- Their idea on the board, with the votes it has.
- The things people vote for arriving, month after month.
- That someone is looking after it, which is the part they remember.
The build is the cheap part
Most founders who come to us have already paid for an app once. Two of the apps on our platform replaced a build the founder had paid for and could not use.
The usual way costs six figures and a year, and then it starts to age. Keeping it running costs a fifth of the build again every year, or a developer of your own. A cheaper build skips the year and usually skips the working app too.
On our platform you pay for none of that alone. Every client shares the cost of security, updates and every new feature, and each one still gets their own app, their own brand and their own project. So it is better in year three than on the day it launched.
And you get two people who have built this before and will tell you when an idea will not work. A founder working straight with developers gets exactly what they asked for, and nobody asks whether it is the right thing.
Build it from scratch
- Up front
- Six figures, and a year.
- After
- A fifth of the build every year to keep it running, or a developer of your own.
- Who thinks about the product
- You.
- In year three
- Code that stopped moving the day it shipped.
Build it cheaply
- Up front
- Tens of thousands, and months.
- After
- You pay for it again, because it does not do the job.
- Who thinks about the product
- Nobody. They build what you say.
- In year three
- Usually nothing you can use.
Start from ours
- Up front
- A setup fee, and live in weeks.
- After
- One monthly rate, with every improvement in it.
- Who thinks about the product
- Two senior people, with you, who push back.
- In year three
- Better than the day it launched.
Why the next app is better than the last
Every app runs on the same platform. When one client needs something, we build it once and it is there for the next, switched on brand by brand.
That is why each new app costs less to make and arrives with more in it than the one before. The first took the longest. The fifth started from four apps' worth of work already done.
And it is the same two people. We have built this before, in your vertical or the one next to it, and we know where it breaks.
What is yours
What is yours stays yours. Your brand, your content and your members' data belong to you and you can take them with you. The platform underneath it you license, which is the reason improvements keep arriving instead of you owning a codebase that stopped moving the day it shipped. Where a client needs the source itself, that is a defined slice and it goes in the agreement in writing.