Replace Excel with a custom web app

What the finished solution should accomplish

Move an outgrown Excel workflow into a shared web application while preserving the calculations, history and exports your team depends on.

What this could look like in practice

Consider a workbook used to price jobs. One tab contains rates, another estimates labour, and a macro produces a customer summary. A useful replacement separates maintained rates from individual quotes, stores the price agreed at the time and keeps later edits from changing a historical quote. Simply reproducing the cells in a browser would miss the real requirement.

Decisions to make before building

Inventory formulas, macros, linked files and manual overrides. Identify which columns represent business records and which are intermediate calculations. Choose representative examples, including unusual jobs, and compare the new application’s output against approved workbook results. Agree a cutover date and retain a readable archive so migration does not erase context.

When a simpler option is enough

Keep Excel if the work is exploratory, used by one owner or changes too often to define stable rules. Shared editing, protected ranges and better validation may solve the immediate problem. Build an application when permissions, audit history or repeated multi-person work make the spreadsheet increasingly expensive to operate.

An initial scope could include

• Workbook and formula review
• Data model, import rehearsal and shared interface
• Calculation comparisons, export and cutover plan

How we would check the work

• Compare approved calculations including rounding
• Import a copy and reconcile record counts
• Keep a fallback while the team accepts the new workflow

Will we lose the ability to export to Excel?

Export can remain part of the application. Agree which records and columns people need, and whether the exported file is a report or a source for later re-import. Those are different workflows and need different validation.

Scope, ownership and working together

You work directly with Joel from discovery through implementation. We agree the outcome, exclusions and acceptance checks before a build. You receive access to the code, deployment and handover documentation. Hosting, third-party services and ongoing support are identified separately; owning the code does not make operating costs disappear.

Build a business application — from £6,000 for a bounded scope. Requirements and acceptance checks determine the quote. Permissions, migration, source-system access and the number of workflows affect scope. Hosting, maintenance and further milestones are agreed separately. Smaller extensions to existing infrastructure can receive a smaller quote.

Related next steps

• Custom internal tool development
• Build a custom quote generator
• Custom business dashboard development