The booking is still a phone call
Somebody stops what they are doing, writes a name on a pad, and hopes it gets typed up.
Mobile apps
An app your customers actually keep.
iPhone and Android apps for booking, ordering, memberships and your own team — built properly and put in the stores.
One fixed price, agreed from a written scope before anything is built.
One fixed price, from a written scopeOne build, both app storesSomething on your phone every weekStore accounts in your name
Four reasons owners ask about an app
None of them are about technology. Each one is a job your phone is doing instead.
Your customers live on their phonesA browser tab gets closed. An app icon stays on the screen.
Bookings still come by phoneEvery call is someone stopping work to write down a name.
Off-the-shelf apps do not fitYou pay monthly to bend your business around somebody else's tool.
You have been quoted a fortuneApp shops bill by the hour and start with months of discovery.
The question nobody asks firstWhether you need an app at all. If a website does the job, we tell you that instead.
What carries on happening while you decide
No figures, because we do not know yours. You will recognize all three anyway.
You keep renting somebody else's tool
The monthly goes out whether or not the thing fits how you actually work.
The icon on their screen is not yours
Whoever got there first is the one they open without thinking about it.
Four decisions make an app build
Get these four right in the first fortnight and the price stops moving.
In the first versionBook a slotPay in the appA reminder before itTheir last order, one tap
What waitsGift cardsMembershipsReferralsA second language
The line between these two columns is what the fixed price is quoted against, and you help draw it before anything is built.
One is opened by somebody outside your door deciding. The other is opened in a basement with no signal. They are not the same app.
Does anyone need an account?Only to see what they booked before
How do they pay?In the app, or when they arrive
What if the card is declined?They keep the slot, we ask again
Who holds the customer data?You do, in your own account
Four answers, settled in writing in the first week. Settling them later is how an app build turns into an hourly bill.
The listing writtenScreenshots and privacy answersSubmitted for reviewLive on the App Store and Play
The developer accounts are opened in your name, so the listing that goes live is yours rather than ours.
The first version does one job properly.
We write down every job the app has to handle, then agree which of them ship first and which wait. That line is what the fixed price is quoted against, and you help draw it.
What you get
One build, both stores, everything in this list inside the fixed price.
One fixed price from a written scopeNever billed by the hourStore accounts and code in your name
Booking and orderingWhere most start
Customers book, order and pay in a few taps. No phone call.
An app for your team
Job sheets, schedules and site photos for the people doing the work.
Works with no signal
A job sheet still opens in a basement, then catches up later.
Loyalty and memberships
Points, passes and renewals that quietly bring people back.
Messages that get read
A notification on the lock screen, not another email nobody opens.
Into both stores
Listings, screenshots and the review process, handled for you.
Kept running
Updates for each new phone release, crash watching, small changes.
Everything in your name
Store accounts, code and customer data, yours from the first day.
Eight weeks, and one of them is yours
You are not asked to trust a process. You approve every screen before it is built.
01Week one
What it needs to do
Every job the app must handle, written down plainly, then one fixed price against that list.
02Week two
Screens on paper first
You see and approve every screen before a line of code is written.
Your approval03Weeks three to eight
Built and testable
You get a working version on your own phone every week, on the handset you actually carry.
04Launch
Into the stores
Listings, screenshots and review handled, then updates on an optional care plan.
What actually gets made
Not a prototype. Four things that exist at the end, in the stores, in your name.
On both stores
The customer app
Book, order and pay in a few taps, without calling you first.
Built for the van
The app your team carries
Job sheets, schedules and site photos for the people doing the work.
Loyalty and memberships
The reason they come back
Points, passes and renewals that quietly bring people back.
Read, not deleted
The message on the lock screen
A notification they see, not another email nobody opens.
The half nobody puts on a website
Most of the work, none of the pictures, and where an app launch usually stalls.
The store accounts
Apple and Google developer accounts opened in your name, with the signing keys kept where you can reach them.
The review process
Screenshots, privacy answers and the back-and-forth with reviewers, handled until the listing is live.
New phones, new systems
Every new handset and system release checked against the app, so it does not quietly break.
Three things we will not do
All three are normal in this trade. We will not do them, in writing.
If people use you once a year, a good website does the job. We say so before you spend anything, even though the app is worth more to us.
Apple, Google, the code and the customer data go in your name. It stays yours if we part ways, and moving it takes an email.
One fixed price from an agreed scope, and a flat monthly to keep it live in the stores. Working out what to build is not a separate invoice.
What an app usually sits on
An app is rarely the whole job. These three are the pieces around it.
Desktop Software
The back-office half of the same system: what your counter and your office run on while the app takes the bookings.
Read the pageWeb Development
The website the app connects to. Most apps sit on top of something that already has to be built properly.
Read the pageLead Generation
Catch the inquiries the app brings, including the ones that arrive long after you have shut for the day.
Read the pageBy trade: healthcare, restaurants, retail, real estate and beauty and wellness. Or see the work first.
Questions people actually ask
If people use you once a year, a good website is enough and we will say so. An app earns its keep when customers come back often, or when your team needs it on site.
One fixed price from an agreed scope, plus a flat monthly to keep it live in the stores. Tell us what you want it to do and you get the number and the plan together.
A typical app is planned at eight to twelve weeks from first sketch to store listing, and the scope sets the real date. You get something on your phone to try every week rather than one reveal at the end.
One build goes to both. The App Store and Play listings, the screenshots and the review process are handled inside the same project.
That is often the first app worth building. Job sheets, schedules and site photos for the people on site, given to your team rather than listed publicly.
You do — your store accounts, your code, your customer data. It stays yours if we part ways.
