Web applications built around your business
Dashboards, portals, internal tools and integrations, designed and built around how your business works. When a standard website or an off-the-shelf product doesn’t fit, we help you work out what you need and build around it.
When a website is not enough
A business website tells people what you do. An application lets them do something, such as access information, manage a process, work with data or complete a task.
- Design and development together
- The interface and the system behind it are considered from the start, not as separate problems.
- Is a custom build the right answer?
- We’ll question that. The useful answer may be smaller than the first brief, or an integration with something you already use.
What does it need to do?
Start with the job. Each answer shows the kind of project it usually is.
I need people to sign in and see their own information
Customer and member portalsA clear way to sign in, see information relevant to them and complete agreed tasks. Roles, permissions and data access are defined in the scope.
I need my data in one place, and to work with it
Dashboards and data toolsRelevant data in an interface people can understand and use. We agree where the data comes from, what is shown and what users can do with it.
I need to manage a process behind the scenes
Internal business toolsTracking enquiries, managing records, reviewing submissions or moving a task through an agreed workflow.
I need a form that does more than send an email
Forms and workflow applicationsConditional steps, validation, saved progress or review processes, where the project requires them.
I need my systems to share information
IntegrationsConnecting third-party services and APIs so information moves between the systems you use. We check access, documentation, limits and ongoing costs before relying on them.
I mainly need pages that explain my business
Website designA fixed-price website package is the better fit.
These are examples of possible projects, not a bundled set of features. We confirm what is feasible and appropriate during scoping.
What to bring to the first conversation
A rough description is enough to start. You don’t need a technical specification.
What we agree with you
We consider how people use the application alongside how the data, permissions and integrations work.
We use Next.js where it suits the project, alongside the services and infrastructure the requirements call for. The technology follows the job.
- The main users, journeys and tasks.
- Data sources, structure and ownership.
- Accounts, authentication and access permissions.
- Form validation, error states and recovery paths.
- Integrations and external dependencies.
- Responsive behaviour and accessibility requirements.
- Hosting, monitoring and ongoing support responsibilities.
Scoping and pricing
A dashboard, a simple internal tool and a customer portal are different projects, so there is no single starting price.
For a defined brief, we can agree a fixed scope and price. Where there are important unknowns, we may propose a separately priced discovery phase before quoting the build.
Third-party subscriptions, usage charges and infrastructure costs are identified separately. Changes outside the agreed scope are discussed and approved before work begins.
Want to see custom engineering in practice? The showcase shows a four-step enquiry form with a Cloud Function behind it, built for a counselling practice. The page explains our connection to it.
The quote depends on
- Users, roles and main workflows.
- Features and interface complexity.
- Data sources and integrations.
- Security, accessibility and operational requirements.
- Content migration or existing system changes.
- Hosting and support needs.
Ownership and hosting
Your quote sets out the code and project assets handed over after payment, any third-party licences, and how access to infrastructure and services will be managed.
- Dependencies and responsibilities
- We document the dependencies that matter, so you know what the application needs to run and who is responsible for each part.
- Hosting and support
- Quoted to the project. The £39/month standard static-website plan is not a blanket price for running every database, API or application workload.
How a web app project runs
A senior engineer leads your project from the first conversation to launch.
- 01
Start with the problem
We discuss what is happening now, who needs the application and what a useful result would look like. Existing systems, constraints and data all matter.
- 02
Define the first useful version
We separate what is essential from what can wait. Where helpful, we use flows, wireframes or a prototype to make the requirements concrete before committing to the full build. If discovery or prototyping needs a paid phase, we explain the scope and price before beginning it.
- 03
Agree the delivery plan
We set out what we’re building, what is excluded, the dependencies, milestones and acceptance criteria. You receive the price and commercial terms for the agreed phase before it starts.
- 04
Design, develop and review
We build against the agreed scope and review progress at planned points. Feedback and change requests are handled openly, with any effect on cost or timing agreed before additional work.
- 05
Test, launch and hand over
We test against the agreed requirements, prepare the production setup and document how the application is run. We agree who handles hosting, credentials, support and future changes.
Questions about web apps
Is this the same as your Advanced website package?
No. An Advanced website covers more extensive content or scoped website enhancements. An application may involve accounts, persistent data, permissions and business workflows. We’ll help you work out which route fits, so you don’t need to classify it yourself.
Do you only use Next.js?
Next.js is part of our application-development approach, but the full setup depends on the requirements. We agree the relevant infrastructure and services during scoping rather than promise the same stack for every project.
Can you connect to our existing systems?
Potentially. We need to check the available APIs, permissions, documentation and any commercial restrictions first. We won’t promise an integration before understanding those dependencies.
Can we start with a smaller version?
Yes. We can define a focused first version around the essential task, with later phases scoped separately. A smaller release still needs appropriate testing, data handling and operational planning.
Can you take over an existing application?
We can discuss it, but we need to review the codebase, dependencies, access and current issues before committing. Any initial review is scoped and priced if substantive investigation is needed.
How do you handle security and personal data?
We identify the relevant data, access controls and security requirements during scoping, and agree the measures and responsibilities needed for the project. If specialist compliance, independent testing or formal assurance is required, that must be explicitly scoped rather than assumed.
What happens after launch?
We agree handover, support, maintenance and hosting responsibilities before launch. Ongoing support and new features can be scoped separately, and neither is unlimited by default.
How much will it cost, and how long will it take?
We need to understand the requirements before giving a meaningful answer. We’ll explain the next scoping step, identify major unknowns and agree pricing and timing before starting the relevant work.
Tell us what needs to work better
A customer experience, a repetitive task or a system that no longer fits. Describe what’s happening now and what you want to change.
We’ll help you work out whether a custom build is the right next step. The extra prompts in the form are optional.