What This Covers
- Booking and appointment systems — for service businesses, clinics, consultants, anyone who takes scheduled appointments
- Client portals — a private, logged-in area where your customers can check status, download documents, or track an order
- Internal tools — simple dashboards or systems that replace a messy spreadsheet-and-email process
- Custom logic for an unusual business process — if it doesn't fit a template, that's exactly what this service is for
Being Honest About Scope
Custom web application work is the one area where we won't give a fixed headline price up front — we'd rather tell you plainly than quote a number that doesn't survive first contact with your actual requirements. We'll have a real conversation, give you a clear scope document before any work starts, and quote against that specific scope.
How We Scope a Custom Project
- You describe the problem you're trying to solve, not the solution you think you want.
- We ask follow-up questions, often several rounds, until the scope is genuinely clear.
- We write a short scope document: what's included, what's not, and the price and timeline attached to it.
- You approve the scope before any development starts — no surprise work billed after the fact.
- We build in stages with visible progress, not a single delivery at the end.
A Straight Answer on Budget Range
Most of the custom tools we build for small businesses land somewhere between $2,500 and $8,000 depending on complexity — a booking system toward the lower end, a more involved client portal with several user roles toward the higher end. If your project is likely to be significantly larger, we'll say so early.
How We Build It
We lean toward straightforward, well-understood technology over anything exotic — a custom tool should be maintainable by whoever supports it in five years, not just by the person who built it. You own the finished system fully: the code, the database, the hosting account, handed over in your name.
Maintenance and Support After Launch
A custom tool usually needs some ongoing attention — security updates, small adjustments as your process evolves, occasional bug fixes. We agree a maintenance arrangement as part of the original scope document, so you know from day one what ongoing support costs and covers.
The Kind of Problems This Typically Solves
These are illustrative examples of the category of work, not specific past projects: a clinic that takes forty phone calls a day just to book appointments, and would save hours weekly with a simple online booking page. A trading company whose customers keep calling to ask "where's my order," who'd benefit from a basic status-lookup page. A small team managing inventory across three spreadsheets that don't talk to each other, who need one simple shared system instead. If your situation rhymes with any of these, that's the conversation worth having.
Who Can Access and Manage the System
Most custom tools need more than one level of access — an admin who can see everything, staff who can use it day to day but not change settings, sometimes a read-only view for someone who just needs to check status. We set up proper user roles and permissions as part of the build, so you're not stuck giving everyone the same full access just because the system wasn't built to tell the difference.
Data and Security, Handled Properly
A custom tool often holds information that matters — customer details, bookings, internal records. We build with standard, well-understood security practices: proper authentication, encrypted connections, sensible data backups, and no storing of sensitive information in ways that wouldn't survive a basic security review. We'd rather build slightly more conservatively here than take shortcuts that only become visible as a problem after something's gone wrong.
What You Get at Handover
Beyond the working application itself, you receive plain-language documentation of how the system works — not just code comments only another developer could read, but an explanation a non-technical business owner can actually follow, plus admin access and a walkthrough of how to use it day to day.
When We’ll Tell You Not to Build Custom
Sometimes the honest answer is that an existing off-the-shelf tool already does what you need, cheaper and faster than a custom build would. We'll tell you that plainly when it's true, even though it means less work for us — a client who trusts that advice comes back for the project that genuinely does need a custom build.
This Kind of Project Rarely Ends at Launch
Unlike a brochure website, a working tool tends to reveal what it actually needs once real people start using it — a field that should've been optional, a step that's more annoying than expected, a report someone didn't realise they'd want. We build the first version to solve the core problem well, and expect a short follow-up iteration once it's been used for a few weeks, which we'll quote separately and honestly rather than pretend the first version will be perfect.
Starting the Conversation
You don't need technical language to describe what you need — describe the actual problem in plain terms, the way you'd explain it to a colleague, and we'll translate it into the right technical approach from there. The worst outcome is a business owner staying quiet about a real need because they're not sure how to phrase it in "developer language"; there's no such requirement here.
Who Owns the Finished System
You do, fully, the same as with a standard website — the code, the database, the hosting account, all set up and handed over in your name. We don't retain control over a custom system as leverage to keep you as a client; if you want to bring in a different developer for future work, you can, because you genuinely own what was built.
How We Test Before Handover
Beyond our own testing during development, we ask you (or a few people from your team) to actually use the system before we call it finished — real staff trying real tasks, not just us clicking through our own code. The issues that surface this way are almost always different from what we catch ourselves, and catching them before launch is far cheaper than catching them after.
Connecting to Tools You Already Use
A custom tool rarely needs to replace everything you already use — often it just needs to talk to one or two systems you're already running, like your accounting software or a payment provider. We check what you're currently using early in the scoping conversation and build the integration in from the start where it's genuinely possible, rather than bolting it on awkwardly after the fact or asking you to switch systems you're already comfortable with.
If You’re Not Technical Yourself
Most of the business owners we talk to about custom tools aren't developers, and don't need to be — that's our job. What matters on your side is being able to describe the actual business problem clearly; we'll handle translating that into the right technical decisions, and we'll explain those decisions in plain terms at every step, not just at the final handover.
Have a Process That’s Outgrown a Spreadsheet?
That's usually the exact signal that it's time for this conversation. Describe the process as it works today, warts and all, and we'll take it from there.
Training Your Team to Use It
A tool nobody on your team actually uses is a wasted investment. Beyond the written documentation, we offer a live walkthrough session with whoever will use the system day to day, so the handover isn't just a document nobody reads but an actual working session where questions get answered on the spot.
Still Not Sure If You Need This or Just a Website
If you're unsure whether your idea is "a website feature" or "a custom application," that's a completely normal question and not one you need to answer yourself — describe what you're trying to do and we'll tell you honestly which category it falls into, and what that means for price and timeline.
What Happens to Your Data If You Ever Leave
You own the data in the system you pay us to build, in full — not a vague "export available on request" promise. We build with a straightforward way to export your data in a usable format (a spreadsheet, a standard file type), so you're never stuck with information trapped in a system only we can open, whatever your reason for moving on might be.
Frequently Asked Questions
Have a process that needs a real tool, not a spreadsheet? WhatsApp 0328-4675162 describe the problem and we'll start scoping it with you.