Web applications
Focused web applications for everyday business tasks
Some workflows outgrow spreadsheets, shared inboxes and paper forms. We build small applications that do one job well. Every project starts with discovery, so the data, the people using it and the risks are understood before anything is agreed.
Who it suits
- Businesses with one repetitive workflow, such as quotes, job tracking or stock lists.
- Teams that need a simple dashboard or a portal where clients or staff see their own information.
- Founders who want a minimum viable product to test an idea before investing further.
What is included
- A discovery session and a written scope covering goals, users and core features
- Assessment of user roles, permissions, data and integrations
- A responsive interface for desktop and mobile
- Sign-in and per-user access rules where the scope requires them
- Testing of core workflows before handover
- Documented handover of source code, access and third-party accounts
Outside the standard scope
These items are scoped separately and quoted against your requirements.
- Marketplaces, financial systems, and payroll or accounting integrations
- Regulated applications, including those handling health, legal or financial records
- Advanced AI or automation features, which are assessed case by case
- Hosting, backups, monitoring and support beyond what is agreed in writing
- Native mobile apps
How the work runs
-
Discover
We review the workflow, who uses it, what information it handles and which systems it must connect to.
-
Define
We agree a focused first version, its main risks, and the recurring costs of running it.
-
Build and review
We build in stages and check each stage with you against the agreed scope.
-
Launch and support
We test the core workflows, go live, and hand over documentation along with the support arrangement you chose.
Common questions
How do you judge whether an idea is suitable?
Discovery shows how complex the workflow, data and permissions are. If the idea is larger than a focused build, we will say so and suggest a smaller first step.
Who owns the application?
Ownership, source code handover, licensing and third-party accounts are documented in the proposal before work begins.
Will it need backups and support?
Usually yes. Backups, hosting, monitoring and support are assessed during scoping and written into the proposal with their recurring costs.
Can it grow later?
Yes, if the first version is structured clearly. Additional features are quoted separately against new requirements.
Describe the task you want to simplify
A short description of the work, the people involved and what goes wrong today is enough to start the conversation.