Web application development
A web application is software that happens to run in a browser: portals, dashboards, internal tools, admin systems. Nothing to install, nothing to update on every machine, and it works on a laptop, a tablet and a phone. This is different from a website — a website is read, an application is used.
Is this you?
- A critical process runs on one shared Excel file that three people edit at once.
- Customers and dealers phone your office for information they could see themselves.
- Your desktop software runs on one machine, in one office, and nowhere else.
- Every branch keeps its own version of the same data.
- Reporting means exporting from two systems and joining them by hand.
What we build
- Customer, dealer and vendor portals with self-service access
- Internal tools and admin systems replacing shared spreadsheets
- Dashboards for management, live rather than compiled monthly
- Role-based permissions, approvals and audit trails
- Document management with versioning and access control
- Bulk import, export and reconciliation utilities
- Integration with your existing systems rather than replacement of them
- Deployment on your server or your cloud, your choice
What this is not
If what you need is a site that customers read and search engines rank, that is website development, and it is a different job with different priorities.
Businesses running a process on spreadsheets, desktop software tied to one machine, or a system that only works inside the office.
- A written scope you approve before any code is written
- A price agreed against that scope, not discovered later
- Source code, database, documentation and IP yours on final payment
- Training for your team, and close support through the first month
Questions people ask about this
How do you price a project?
Against a written scope, agreed before any code is written. We do not publish indicative figures, because the same-sounding requirement can differ several times over in cost depending on the specifics.
What drives the number: how many distinct user roles there are, how many screens and reports, how much data has to be migrated from existing systems, how many other systems it must talk to, and whether your process is already documented or has to be worked out first. A first conversation is usually enough for us to tell you the rough order of magnitude.
How long does a project take?
It depends on how much of the system you want live at once, which is why we usually suggest starting with one module rather than everything.
What holds true regardless is the shape of it: you see something working every two weeks from the start of the build. You are never waiting three months to find out the project went wrong in week two.
Who owns the source code?
You do, on final payment. Source code, database, documentation and intellectual property in the work are assigned to you in the contract. There is no licence that expires and no situation in year three where you discover the software is not yours.
We also hand over in a usable state: documented, commented, and written so another developer can pick it up.
Can it run on our own servers rather than the cloud?
Yes. We build to be deployable either way and the decision is yours. On your own infrastructure you carry the backups, uptime and patching, or you pay somebody to; on cloud you get easier scaling and remote access. Regulated and data-sensitive operations often have good reasons to keep everything in-house, and we build for that without argument. The exception is AI processing, which currently runs through a hosted API.
Tell us what isn’t working
A first conversation costs nothing and commits you to nothing. Bring the problem — the mess of spreadsheets, the report nobody can produce, the process that breaks every month-end. We will tell you honestly whether custom software is the answer, and roughly what it would take. Sometimes the answer is that you do not need us. We will say so.