The Spreadsheet-to-App Sprint

The spreadsheet your factory depends on deserves to be proper software.

One troublesome manufacturing workflow, turned into a lightweight internal application. Built around your team and existing systems, without replacing your ERP.

Built by Tom Darcy: more than a decade in manufacturing operations, production, MES and automation. Mostly remote, with a fixed scope and a clear finish.

You already know the spreadsheet

Everyone relies on it.
Only one person understands it.

It might be your planning board, estimating workbook, NCR log or job tracker. It’s too important to stay fragile, but doesn’t justify another enterprise software implementation.

I take that one process and build a small application that makes it easier to run, share and maintain. Typical projects are £8,000–£12,000 over 2–3 weeks; tightly scoped Quick Fixes start at £4,500.

Familiar problems. Useful software.

The sort of problems I fix

If an important process depends on a spreadsheet, a shared drive and somebody remembering what to do next, I can probably help.

01

Production planning

Replace the monster planning spreadsheet with a shared planning application.

02

Quoting

Turn a complex costing workbook into a guided quotation tool.

03

Quality

Replace emailed NCR spreadsheets with a controlled workflow and live status.

04

Job tracking

Give production, engineering and sales one view of where every job actually is.

05

Inventory & tooling

Make critical materials and tooling searchable instead of relying on tribal knowledge.

06

Reporting

Capture information once instead of copying it between spreadsheets every morning.

The Spreadsheet-to-App Sprint

One awkward process.
One useful application.

Turn the spreadsheet your factory depends on into proper software. A defined output, agreed acceptance criteria and a fixed price before we start.

Quick Fix

From £4,500

Approximately one week

One tightly scoped workflow, such as a tooling register or a simple tracker.

Larger builds

£15,000+

Scope and schedule agreed first

For more involved workflows or integrations, only where the business case justifies it.

Mostly remote delivery. Documentation and a proper handover included. Hosting, ownership and any ongoing support are agreed before the build.

From spreadsheet to working software

A small project with a clear finish

  1. Show me the process

    Send a spreadsheet, screenshots or a two-minute explanation. We start with a free 30-minute discussion to check whether a build makes sense.

  2. Agree what “done” means

    We define the problem, output, acceptance criteria, scope and price. If discovery is needed, we agree an audit first.

  3. Build it with your team

    I build the application and review it with the people who will use it, using your real workflow and data.

  4. Test, hand over, move on

    We check the agreed acceptance criteria. You get documentation and a handover. New features become another sprint.

A useful tool, properly handed over

What’s included?

  • An agreed workflow, fixed scope, price and acceptance criteria
  • A working application reviewed with the people using it
  • Data imports, exports or integrations as agreed in the scope
  • Testing against the agreed acceptance criteria
  • Documentation and a proper handover

We agree hosting, ownership and any support arrangements before starting. New requirements become another sprint; the project doesn’t become an open-ended development commitment.

If the problem needs more investigation first, a £2,500 Factory Workflow Audit can map the opportunities and costs. Proceed with a £10k+ build within 60 days and £1,000 is credited against the build.

A few practical questions

Before you send the spreadsheet

Do I need to replace my ERP?

No. The application sits around the existing systems. We can use spreadsheet imports, ERP exports or an agreed integration, depending on what the workflow needs.

Is this right for my business?

The best fit is a UK manufacturer with roughly 20–250 people, established systems and one awkward operational process outside them. I work directly with MDs, operations leaders and engineering teams.

What if an off-the-shelf tool would do?

I’ll say so. The initial discussion is free, and an audit is only needed when there’s real uncertainty about what to build.

Can I start without sharing the whole workbook?

Yes. Screenshots with sensitive details removed or a two-minute description are enough for the first conversation. We can agree how to share the detail later.

What happens after the sprint?

You get documentation and a handover, with support responsibilities agreed in advance. Another workflow can become another fixed-price sprint. Reserved monthly improvement capacity is available after a successful build.

Show me the spreadsheet

Tell me what’s broken

Send me the spreadsheet, screenshots or a two-minute explanation of the process. I’ll tell you whether I think it’s worth fixing.

I’ll tell you honestly whether this is something I’d build, something you can fix more cheaply with an off-the-shelf tool, or something that shouldn’t be digitised at all.

Use these prompts to prepare an email, then review and send it in your email app. You can attach a spreadsheet or screenshots there.

How is it done today?

Your answers stay in this page until you choose to email them. This form doesn’t upload files or send a message automatically.