Custom Business App Development: A Plain Guide for UK Small Firms

A custom app is worth paying for when there’s a specific, repetitive job that off-the-shelf software handles badly, and a small tool on a phone or tablet would make it quicker or less error-prone. If an existing app already does most of what you need for a few pounds a month, use that instead.
I build custom Android apps from £300. They install from a file rather than from Google Play, which suits a lot of small business jobs better than people expect. Here’s how I think about whether you need one, how a project runs, and what changes the price.
When a custom app makes sense
Most of the apps I’ve built started with something small that annoyed me or my family every day. A few from my published projects:
- VolumeRestore puts the volume back where you want it when Android mistakes a car stereo for headphones and turns it down.
- SortNewest makes the file picker show the newest files first, so you’re not tapping the sort menu every time you attach a photo.
- ColourIdentifier lets you tap part of a photo and get the colour’s name and hex code. I’m colour blind, so this one was personal.
- James Sounds is a picture soundboard I built for my brother James, who is non-verbal.
None of these are big apps. Each one does one job well, and that’s usually the sweet spot for a small business too. Think of a checklist your team fills in at the end of each job, a calculator for the quotes you currently work out on the back of an envelope, a simple stock count for a market stall, or a tablet on the counter that shows today’s bookings in big, readable text.
It’s probably not worth building something custom when:
- A well-known app already does it and the subscription is cheap.
- You need it on iPhones as well. I build for Android.
- Members of the public need to find it and install it themselves from an app store.
- It has to handle payments, medical records or anything else heavily regulated.
What “sideloaded” means
Sideloading just means installing an app from an APK file instead of through the Google Play Store. You download the file, Android asks whether you trust where it came from, you say yes, and it installs. It’s how I distribute my own apps from GitHub, and it’s what you get when you order one from me.
For an app used by you and your staff, that has real advantages:
- No developer account, store fees or store review to get through.
- The app isn’t public. Only people you give the file to can install it.
- It can be built for older Android versions if that’s what your staff actually use, although supporting very old devices can add to the price.
And a few things to know before you commit:
- Updates don’t arrive automatically through a store. We agree how you’ll get them, such as a new file or a download link.
- Each phone needs a one-off permission to install apps from that source.
- Some work phones managed by an IT company block sideloading altogether, so check first if yours are set up that way.
How a project runs
It’s the same eight stages I use for websites, listed on my services page:
- Brief. You tell me the job the app needs to do, who’ll use it and on which phones or tablets.
- Written quote. Features, devices, delivery and how updates will work, with the total price.
- Deposit. It comes off the total.
- Prototype. An early version or mock-up, so we find out quickly if I’ve misunderstood something.
- Build.
- Corrections. The rounds of changes we agreed.
- Handover. The app file and instructions for installing it.
- 30 days of fixes for anything that doesn’t work as agreed.
I do this mainly at weekends, so we’ll agree a realistic delivery estimate up front rather than me promising next week.
What affects the price
£300 is the starting point for a small, focused app. The final figure depends on:
- How much it does. One screen that records a checklist is a very different job from something with logins, reports and photos.
- Whether it needs the internet. An app that keeps everything on the phone is simpler than one that syncs to a server.
- Which devices and Android versions it has to run on.
- How you want it delivered and updated.
If it needs a server or online account behind it, that’s an ongoing running cost as well as extra build time, and we’ll talk about who owns it and who pays for it.
Looking after your data
The safest data is data you never collect. Where I can, I keep information on the device rather than sending it anywhere. James Sounds works completely offline, which keeps it simple: there’s no account, no server, and nothing to break when the signal drops. If your app does need to store customer details, we’ll keep it to what you actually need, and you’ll need to cover it in your own privacy information.
Got an idea?
Describe the job rather than the app. “My team keeps forgetting to photograph the meter readings” tells me far more than “I need an app with a camera feature”. Send it through the enquiry form on my services page and I’ll tell you whether a custom app is the right answer, or whether something you can download today would do.