Azure web apps

A web application built on .NET and Azure that your team can run, extend and afford.

How we work

Durations are ranges for a mid-size project. We confirm them with you before we start.

Discovery 1 to 2 weeks
A shared understanding of users, goals and constraints, written down.
We need: Access to the people who know the business, and any existing systems or documents.
Architecture and estimate 1 to 2 weeks
An architecture outline, a backlog, and an estimate with the assumptions behind it.
We need: Priorities: what must ship first, and what can wait.
Build in sprints 8 to 16 weeks, in two-week sprints
Working software every two weeks, a demo and an updated backlog.
We need: A product owner who joins the demos and decides quickly.
Azure infrastructure and CI/CD 1 to 2 weeks, alongside the first sprints
Environments as code, automated builds and deployments, and monitoring.
We need: An Azure subscription, or permission for us to set one up with you.
Launch About 1 week
A rehearsed release, a rollback plan and a launch checklist.
We need: Final sign-off and access to your domain settings.
Support Ongoing, agreed monthly
Fixes, updates, monitoring and a small amount of new work each month.
We need: A named contact and a way to report issues.

What kinds of applications do you build?

Web applications, the databases behind them and the cloud services they run on.

Can you take over an existing application?

Yes. We start with a short review of the code and the hosting, then agree what to fix first.

Who owns the code?

You do. It lives in your repository and your Azure subscription.

How do you keep cloud costs under control?

We size resources to real load, set budgets and alerts, and review spend each month.

A 30-minute call. We listen, ask the awkward questions, and tell you honestly if we’re the right team.