Development

Hire an Excel developer

Fixed-price builds by engineers who write spreadsheets the way software is written: documented, testable, and yours to maintain after we hand it over.

Get a fixed quote in 15 minutes

✓ No call required  ·  ✓ NDA on request  ·  ✓ Money-back guarantee

What we build

Specified deliverables with acceptance criteria, not open-ended advice

Internal tools

  • Quote and invoice generators
  • Pricing and margin calculators
  • Capacity and rota planners
  • Data-entry front ends with validation
From $750

Reporting infrastructure

  • Power Query ingestion from multiple sources
  • Star-schema data model in Power Pivot
  • DAX measures for period-over-period analysis
  • Refreshable dashboard on top of the model
From $500

Financial models

  • Three-statement models with integrity checks
  • Driver-based forecasts and scenarios
  • Unit economics and cohort analysis
  • Board-ready output sheets
From $500

Migration and rescue

  • Excel to Google Sheets, or the reverse
  • Legacy macro modernisation
  • Splitting a monolithic workbook into layers
  • Documenting an undocumented inherited file
From $500

How we build

The conventions that decide whether a workbook survives its author

Separate input, calculation and output

Three layers, visibly distinguished. Inputs are the only cells anyone types into and are formatted so that is obvious. Calculations are never mixed with presentation. Outputs reference the calculation layer and contain no logic. Almost every unmaintainable workbook we are asked to rescue has these three collapsed into one grid.

No hard-coded numbers inside formulas

A VAT rate written into forty formulas is forty edits and one guaranteed miss. Constants live in a named input cell, referenced everywhere. This is the single change that most reduces the cost of the next modification.

Structured references and named ranges

Tables and named ranges instead of A2:A5000. Ranges that grow with the data do not silently exclude last month's rows, and a formula that reads SUM(Sales[Amount]) tells the next person what it does.

Errors handled where they occur

IFERROR wrapped around an entire formula hides real problems. We handle the specific failure — a missing key, a divide by zero — and let genuinely unexpected errors surface where they can be seen and fixed.

Documentation in the file

A README sheet: what each input means, where source data comes from, what to change at year end, and who to contact. External documentation gets lost; a sheet inside the workbook travels with it.

You own the code

Unlocked modules, readable source, no licence checks. If you decide to take the work in-house or to another developer, nothing we have written stops you.

How the engagement runs

Specification, fixed price, delivery, revisions

1. Send the specification

Describe the tool you want built and what it must do to be accepted. A rough sketch of the output is worth more than a page of prose.

2. Fixed quote in 15 minutes

Scope, price and delivery date. If part of the specification is ambiguous we ask before quoting rather than after building.

3. Build and test

Built against your real edge cases, with the acceptance criteria from the quote checked before delivery.

4. Handover

Documented, unlocked and yours. Revisions included; full refund if it fails the criteria we agreed.

Related work

Other services and reading

Excel development FAQ

Ownership, confidentiality and how we scope work

What is the difference between an Excel consultant and an Excel developer?

A consultant diagnoses and advises as well as builds — the deliverable can be a recommendation. A developer is engaged to build a specified thing: a tool, a macro, a model, with acceptance criteria. If you already know what you need built, you want a developer. If you know the symptom but not the fix, start with the <a href="/excel-consultant">consulting engagement</a>.

Can we hire someone for an ongoing basis?

Yes, though most clients do not need to. We work project by project, and a maintained tool that is documented properly needs a developer a few times a year rather than continuously. Where there is a genuine pipeline of work we agree a block of hours at $150/h rather than a retainer that bills whether or not you use it.

Who owns the code?

You do, on delivery, without conditions. VBA modules, Apps Script projects, Power Query M and any documentation are yours to modify, redistribute or hand to another developer. We do not obfuscate code, licence-lock workbooks or keep anything that would make you dependent on us.

How do you handle confidential data?

We sign your NDA, or provide one. Where the data cannot leave your environment we work from an anonymised sample with the same structure — column names, types and edge cases preserved, values replaced — which is enough to build against for the large majority of projects.