Custom web and mobile apps
I build apps that run in the browser and on the phone: bookings, client portals, orders. I connect them with what already works in the company instead of adding yet another separate system.
You are here: Apps.
When does an app make sense?
- Clients book by phone or email and mistakes happen easily.
- Clients should be able to check the status of an order or booking themselves.
- The team works in the field and needs access from a phone.
- Off-the-shelf apps don't fit the way the company works.
What you get
- A web or mobile app shaped around the process.
- Accounts and permissions for different roles.
- Connections to the systems you already use.
- Testing on test data before launch.
- Deployment in the cloud or on your server.
- Documentation and a handover.
What it looks like
A suggested process. We'll fit the details to the project. How I work
- 01Discovery
How the process works today and what should get better.
- 02Scope and screens
We agree exactly what will be built and what the screens will look like.
- 03Building in stages
One part of the app after another, checked on test data.
- 04Deployment
Launch, training for the people who will use it, and handover.
How much does an app cost?
The price depends on the number of screens and roles, integrations with other systems, whether a phone app is needed, and on moving existing data. First we agree the smallest version that solves the problem.
You can pay once or by subscription. How payment works
Related projects
Projects from my employment, clearly labelled. Screenshots show test data.
Crew: people and 1:1 meetings
The largest module and the one where it all started. Conversations between a manager and their report have an agenda, a record and a follow-up, and around them is everything a team needs.
Screenshot with test data.See the module
Parking
Booking spaces on a plan of the car park instead of meetings in the calendar. You see straight away which space is free on a given day and time.
Screenshot with test data.See the moduleQuestions and answers
Don't see your question? Write to me.
Web app or mobile app: which one?
If the app has to work on computers and phones and doesn't need phone-only features, a web app that runs in the browser is usually enough. A mobile app is worth considering when you need notifications, the camera or offline work.
Can the app be extended later?
Yes. We start with the version that solves the most important problem and add features when it is clear they are needed.
Will the app connect to the software we use?
Usually, yes. First I check what your software allows, for example data export or an integration interface.
Where will the app run?
In the cloud or on a server in the company. Where it runs follows from the requirements, not from fashion.
What do I get at the end?
A working app, access to all of its parts and an explanation of how it works and what it takes to maintain it. We agree the details of the handover before we start.
Industries
How this service looks in specific industries:
Have an idea for an app?
Describe who will use it and what it should make easier. We'll start with the smallest version that makes sense.See also
Custom software and internal tools
Small apps and internal dashboards, for example for bookings, handling requests or keeping records.
More about the serviceWebsites for companies
I design and build company websites, from a simple business card to a site with many subpages.
More about the serviceWebsites and apps