Mobile apps
An app is worth building when there is a reason to open it a second time. We start with that question, not with screen design.
Two different reasons to build an app
The first: an app for your customers. Orders, bookings, notifications, history. It pays off when the customer comes back regularly, because a one-off contact is served just as well by a good mobile site.
The second: an app for your team. Handling enquiries, orders and notifications for people working in the field rather than at a desk.
In both cases the app does not stand on its own. We wire it into what already runs in your company: the AI agent that qualifies enquiries and the CRM where you run the sale.
What it covers
An app for your customers
iOS and Android. For businesses the customer returns to: orders, bookings, notifications.
An app for your team
Internal, for people working away from a desk. Enquiries, orders and notifications without going back to the office.
Wired into the AI agent and CRM
An enquiry made in the app lands straight where you run the sale, with the context already filled in.
Published from your account
The app lives in the App Store and Google Play under your account, not ours. We help you open them, but you stay the owner.
Scope agreed in conversation
We do not start from a list of screens, but from what has to happen when someone opens it.
What goes with this
An app is usually the interface to something that already runs: the AI agent and the CRM from AI automation.
For a business the customer visits before buying, the first step is a website AI can read or a store AI can buy from. What it costs is on pricing, and who does the work on who we are.
Frequently asked questions
Do I need an app if I already have a website?
Not always, and we say so plainly. An app pays off where the customer returns regularly or where the team works away from a desk. For a one-off contact a good mobile site is enough: nobody installs an app for a single transaction.
iOS or Android?
Both, from one codebase. We build in React Native, so you do not pay twice for two separate apps. We still agree the scope after talking, because an app for customers and an internal app for the team are two different projects, even though both end up as an icon on a phone.
Whose account does the app sit under in the App Store and Google Play?
Yours. We help you open the developer accounts and we handle the release, but you stay the owner of the app in both stores. That means you can change suppliers at any point without losing the app or its ratings.
Will the app connect to what I already use?
Yes, that is the point of it. We wire it into the AI agent and the CRM, so an enquiry made in the app lands straight where you run the sale, with the context already filled in by the agent.
How long does it take to build?
Between 14 and 30 days. The difference comes from scope, not screen count: an app that shows data and takes an enquiry ships faster than one with payments and customer accounts. We give the timeline together with the quote, before we start.
What does it cost?
It depends on scope, and the spread is wide: an app with one screen and one button is not the same work as one with accounts, payments and stock syncing. A range covering both would tell you nothing, so we do not publish one. You hear the figure in the first conversation, once we have agreed what has to happen when someone opens the app. You pay for the scope you order, one-off or on a monthly plan.
What happens to the app after launch?
We stay with it. An app is not a product you hand over once: iOS and Android ship new versions, and the app stores change their requirements and can pull an app that stops meeting them. We agree the scope of that support together with the billing model.