Tangensys • Plan, deliver, measure
Custom web applications
Define the business workflow before choosing the stack. A useful application replaces a specific bottleneck and gives each user the right actions and access.
The work to plan together
A scope shaped around this requirement.
- Discovery and scopeScope
- Design and buildReview
- Progressive web app featuresCheck
- Be foundSearch, maps and AI answers
- Be chosenClear pages and offers
- EnquiryCall, WhatsApp or form
- Follow-upYour team responds
In short
What does Custom web applications involve?
Custom web application development builds software that runs in the browser for a specific business need, including progressive web apps that work like apps on phones.
When Custom web applications is a useful fit
Businesses with unique processes
Turn the business rules into testable journeys before choosing a technology stack.
Startups building products
Define an essential first release that can validate the product without an oversized build.
Teams replacing spreadsheets
Map data, roles and approvals so replacing a spreadsheet does not lose the working process.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Processes run on spreadsheets and email
- Off-the-shelf tools do not fit
- Staff need an app without app stores
A practical example
A field-service portal could let staff accept a job, attach evidence and update its status while managers review exceptions. Each role needs different permissions.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Discovery and scope
- Design and build
- Progressive web app features
- Hosting and support
Where we usually begin
Offline behaviour, integrations, data migration and support are scoped explicitly. A browser application does not automatically provide every native-device capability.
Practical detail
Keep the first release centred on one workflow
An illustrative service portal starts with a customer request, staff assignment and a status update. A first release can test that route before adding billing, reporting and other modules.
| Part of the work | Example output | How to review it |
|---|---|---|
| Role map | Customer, assigned staff and administrator actions | Each role can perform only its approved actions. |
| First-release backlog | Essential request and update screens | The workflow can be completed without a spreadsheet workaround. |
| Sign-off set | Success, missing input, unauthorised access and failure cases | A reviewer records the outcome of each representative task. |
| Handover | Deployment, data model, access and operating instructions | The owner can identify what is delivered and what remains outside scope. |
Browser-based offline support and native-device features need separate requirements. An app-like appearance does not establish either capability.
Start with one complete operational journey
A custom web application should solve a process that standard tools cannot reasonably cover. Map who starts the task, who reviews it and what record is produced. The build can then be judged by whether the operation works, rather than the number of screens delivered.
Choose a representative journey for the first release. An internal request-and-approval flow is often easier to define than an application containing every future feature. Data migration, roles and external systems can materially change the work and need explicit decisions.
Sign-off should cover permissions, validation, duplicate actions and recovery from an interrupted step. Agree hosting, backups, source ownership and support before release. Advanced development is proposed after the required capability and delivery arrangement are confirmed.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Measure successful task completion, data accuracy and agreed performance targets. Compare the workflow with the previous process using the same types of tasks.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
Can we start with a smaller version and extend it later?
Yes, if the first version completes a useful task and the boundaries are explicit. Identify what is deferred and which future requirements influence the initial design. A phased scope avoids paying for speculative screens while preserving a workable route for approved additions.
Should every planned feature go into the first release?
Usually not. Start with the essential workflow and its sign-off checks, then use real operating feedback to prioritise later work.
Can a web application work offline?
Some workflows can, but storage, synchronisation and conflict rules need explicit design. Offline operation is not assumed from the word “application”.
What is a progressive web app?
A web app that can be installed on a phone and work offline, without an app store.
How is Custom web applications priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days