Riyadh · Karachi · Delaware soon 07:00 – 15:00 UTC  ·  contact@coalescence.me

Solutions

Web Application Development

Enterprise web platforms engineered for long service life and continuous change, on whichever stack the organisation is best placed to run.

First release
10–16 weeks
Engagement
Fixed price or dedicated team
Stack
Chosen at discovery

The approach

Systems that outlive the framework they were built on.

We design web platforms around a documented domain model, a defined API surface and automated tests that cover business rules. Those decisions outlive any framework, so the choice of language and database follows the organisation — the skills already in your team, the licences you already hold, the platform your regulator has already approved. We build on what you run, and the resulting system can be extended by any competent engineering team, including your own, for as long as it remains in service.

C# / .NETJava / SpringNode.jsPython / DjangoPHP / LaravelGoReactAngularVueTypeScriptPostgreSQLSQL ServerMySQLOracleMongoDBRedisDockerKubernetesAzure DevOpsGitHub ActionsGitLab CI

A working set, kept current. The stack is chosen after discovery against four things: the skills you retain in-house, the licences you already hold, the platforms your regulator has approved, and what the workload genuinely requires. Where your estate is standardised on something absent from this list, we staff to it.

platform console — requests
10–16wkFirst release
2wkIncrement
1Team

Capabilities

What the practice covers

  1. 01

    Enterprise portals

    Role-aware portals for customers, staff, partners and regulators, with single sign-on, granular permissions and complete audit trails.

  2. 02

    Workflow and approvals

    Multi-stage approval chains with delegation, escalation and SLA tracking, configured to your organisation's actual signing authority.

  3. 03

    APIs and integration

    REST and event-driven services connecting ERP, CRM, payment gateways and government platforms through documented, versioned contracts.

  4. 04

    Legacy modernisation

    Phased migration away from whatever the system runs on today — Web Forms, classic ASP, Oracle Forms, legacy PHP or Java, desktop databases — with the existing platform serving production throughout the transition.

  5. 05

    Dedicated offshore teams

    Vetted engineers in the languages your platform already uses, working as a managed extension of your team, within your sprints and repository, on your working hours under a single contract.

  6. 06

    Performance engineering

    Query optimisation, caching strategy and load testing against production-scale data volumes ahead of go-live.

On handover

What you receive

Every engagement ends with the client holding the artefacts needed to run, extend and re-tender the system without us.

  • Architecture decision records and a documented data model
  • CI/CD pipeline, environment parity and repeatable deployments under your ownership
  • Automated test suite covering business rules and integration paths
  • Operations runbook, API documentation and a structured handover to your team

Common questions

Frequently asked

How long does a web application take to deliver?
A focused internal platform reaches first production release in 10 to 16 weeks. Larger multi-role portals typically run four to eight months, delivered in two-week increments with working software available from the third week.
Can you take over an application built by another supplier?
Yes. We begin with a code and infrastructure audit and provide a written assessment of technical debt and operational risk. Stabilisation work is completed before new features are introduced.
How are dedicated offshore teams contracted?
A monthly rate per engineer with a three-month minimum, scaling with one month's notice. Engineers work your hours in your tooling and repository, and you interview each candidate before they join. The engagement is held under a single contract whichever office delivers it.
Do you work to fixed price or time and materials?
Both. Fixed price suits replacements with well-defined scope. Dedicated-team engagements suit products where requirements continue to develop. We recommend a model after discovery.
Which technology stack will you use?
Whichever one survives the next decade in your hands. The decision is made during discovery against four things: what your team can maintain without us, what your existing licences and hosting already cover, what your regulator or group IT has approved, and what the workload genuinely requires. We are not a single-vendor shop, and we will say so if your incumbent stack is the right answer.

Begin with a two-week discovery

Discovery produces a domain model, a risk register and a written estimate, retained by the client regardless of whether the build proceeds.