Custom web applications for the work a website can't do
When the job involves logins, records and rules — quotes, bookings, client portals, internal tools — you need an application. We build them to be understandable: a clear data model, permissions enforced in the database, and an interface your team can use without training.
- Role-based access
- Database-enforced permissions
- Built to be handed over
Typical builds
- Client portals where customers see their own jobs, documents or invoices
- Booking and scheduling systems with availability rules and confirmations
- Quoting and configurator tools that turn a set of choices into a priced proposal
- Internal dashboards replacing shared spreadsheets and manual reporting
- Multi-step intake forms that route enquiries to the right person automatically
How we keep the cost sensible
Most application briefs contain about three features that matter and a long list that sounded useful in a meeting. We scope a first version around the three, get it in front of real users, then add the rest based on what they actually hit. That is cheaper than building the full list and discovering half of it goes unused.
Security and data
- Row-level access rules so users only reach their own data
- Roles held in a separate table, never on the user profile, to prevent privilege escalation
- Server-side validation on every write, not just in the browser
- Secrets and API keys kept on the server and out of the front-end bundle
- Audit-friendly records: who changed what, and when, where that matters
You own what we build
The code, the database and the accounts are yours. We document the data model and deployment so another developer can pick it up — no lock-in as a retention strategy.
How the work runs
Workshop
We map the current workflow, the people involved and where time is lost.
Define v1
A scoped first version with the features that remove the most manual work.
Build and test
Built in short cycles with a staging environment you can try at each step.
Launch and iterate
Roll out to users, then improve based on real usage under a support agreement.
Common questions
- What counts as a web application rather than a website?
- Anything with logins, records, permissions or logic: customer portals, booking systems, quoting tools, internal dashboards, configurators. If users create and change data, it is an application.
- Can it replace the spreadsheets we run the business on?
- Frequently that is the brief. We map the spreadsheet's real workflow, then build the parts that cause errors or take the most manual time, rather than recreating every column.
- How is data kept secure?
- Access is controlled at the database level so a user can only read and write their own records, roles are stored separately from profiles, and secrets stay on the server. We can walk through the specifics for your build.
- Do you support it after launch?
- Yes, under a maintenance agreement — monitoring, fixes and a monthly allowance for changes.
Describe the process you want to fix
Tell us what happens today, step by step, and where it breaks. We'll tell you what a first version should include and what it would cost.