Client and customer portals
Logins, documents, statuses, notifications. Usually replacing a spreadsheet and a lot of email.
Custom software is not finished at launch. It needs hosting, monitoring, dependency updates, and someone to answer when a user cannot log in on a Sunday. I ran SoloCRM for two years and that ongoing weight is exactly why I eventually retired it. It taught me more than any client build.
So every app quote from me includes a running cost estimate for the first two years alongside the build price. If the total does not make commercial sense for you, better to find that out in week one than in month fourteen.
Logins, documents, statuses, notifications. Usually replacing a spreadsheet and a lot of email.
Availability, payments, reminders, cancellations. The hard part is the edge cases, and that is where the time goes.
Turning a pricing structure that lives in someone's head into something a customer can use unsupervised.
Pulling numbers out of the systems you already pay for and putting them on one screen.
Stripe, accounting, CRMs, couriers, whatever has an API. Where there is no API I will say so before you budget for it.
Half-finished projects where the original developer left. Sometimes fixable, sometimes not. Honest assessment first.
Discovery comes first and it is paid. Two to five days, depending on the size of the thing, and you get a written specification, a data model, screen sketches and a fixed build price at the end of it. That document is yours whether or not you hire me for the build.
I do it this way because fixed-price software quoted off a phone call is how both sides end up unhappy. The discovery fee comes off the build cost if you go ahead.
Two to five days. Written spec, data model, screens, fixed build price. Deducted from the build if you proceed.
Often, yes. I will read the code first and give you a straight answer on whether continuing is cheaper than restarting.
Not native iOS and Android. I build web apps that work properly on a phone, which covers most business cases at a fraction of the cost. If you genuinely need App Store presence I will point you to someone who does that full time.
The code is documented and in your repository, on standard frameworks any competent developer can pick up. That is a deliberate choice, not a courtesy.
Retainer or hourly, your preference. Most app clients take a monthly retainer because software needs attention in a way a brochure site does not.
Real numbers from your device and connection, not a screenshot of a score I chose. Nothing is sent anywhere. The measurement happens in your browser and stays there. If one of these ever reads amber on my own site, you will see it, which is rather the point. I audit these for £650.