Operations studio · Bath, UK

We rebuild the busy work so you can think.

An operations studio for small and mid-sized businesses that have outgrown their spreadsheets. We replace the manual core of how you run, rather than adding another tool on top of it.

01 · Who we are

The people you meet are the people who build it.

We don’t bill a junior to you as a senior, and nothing gets handed offshore once the kickoff call is over.

Luke Hodges

Luke Hodges

Founder · ops & engineering

Based in Bath. Writes the systems, sits in the businesses, does the handover.

Book Luke →
Alex Stewart

Alex Stewart

Head of Commercial

Based in Bath. Runs scoping, keeps the engagement honest about what it will cost.

Book Alex →

Hi, I’m Luke. I keep Ironheart small on purpose. At most consultancies you meet a partner, and then a junior does the work. Here the person who takes your call is the one writing the proposal, and the one pushing the commits. We only take two or three companies at a time. You get a meeting and something shipped every week, and when the work is done we either wrap up or roll into a retainer.

Luke Hodges. Founder · luke@theironheart.org

02 · What we fix

Four places the work gets stuck.

Not industries. Symptoms. A haulier and a podiatry clinic both know what a week-late invoice run feels like.

01

Quotes rebuilt from scratch, every time

Every estimate starts at a blank email. The good version lives in one person’s head, and it leaves the building when they do.

→ we build: a quoting engine. same inputs, same number, minutes not days

02

Five systems, none of them agreeing

Spreadsheet, inbox, booking system, accounts: four different answers to “how did we do last month?” and no way to say which is right.

→ we build: one source of truth, synced both ways

03

Chasing that happens when someone remembers

Reminders, follow-ups, unpaid invoices. Goodwill is the scheduler, and goodwill goes on holiday, gets busy, moves on.

→ we build: chasers that fire themselves. day 8, every time

04

Month-end that eats a working day

Assembled by hand from four exports, every month, by the person whose day is worth the most.

→ we build: month-end as a live dashboard. open it any day

03 · What we build

Five systems we build again and again.

Every engagement starts with a look at the actual work. Then we build the smallest thing that removes the biggest constraint, and nothing more until that one has paid for itself.

/ 01

Process automation

The quote, the chase, the handoff, rebuilt as a system that runs without being remembered.

  • automation map
  • built workflows
  • monitoring
  • runbook
/ 02

Data & reporting

One number everyone trusts, instead of five spreadsheets that disagree.

  • source inventory
  • live dashboards
  • alerts on change
/ 03

Internal tools

The app your team needed, instead of the spreadsheet pretending to be one.

  • working app in weeks
  • role-based access
  • training + docs
/ 04

System integrations

Your booking system, your accounts and your inbox, finally on speaking terms.

  • integration spec
  • middleware
  • retries + monitoring
/ 05

AI-assisted ops

Drafting, triage and lookups handled before anyone opens the inbox.

  • use-case scoping
  • production agents
  • guardrails + audit
05 · How we work

A sprint, not a saga.

Five steps, six weeks, fixed price. You know the cost before we start and the number does not move.

Step 1 of 5

Week 1

Sit in it

We watch the actual work for a week. Not a workshop. The real thing, with the real mess.

  • stakeholder interviews
  • system inventory
  • workflow mapping
  • opportunity scoring
Week 1–2

Pick the one thing

One constraint, named, with the fixed price to remove it. No change-order roulette.

  • proposal + SoW
  • success metrics
  • fixed-price quote
  • kickoff date
Week 2–6

Build it

Weekly demos on your real data. You see it working before you trust it.

  • weekly demos
  • shared backlog
  • staged rollouts
  • observability from day one
Week 5–6

Try to break it

We run it against the ugly cases first. Anything that only works on a good day isn’t finished.

  • the ugly test data
  • failure drills
  • edge-case runs
  • sign-off criteria
Week 6+

Hand it over

Runbook, training, 90-day warranty. Then we keep it alive on retainer, or you do.

  • runbooks
  • team training
  • 90-day warranty
  • optional retainer
06 · Engagements

Three ways in.

Every price is fixed and quoted before we start. Scope changes the number, so we quote the scope, not a menu.

Not sure which one fits? That’s what the call is for.

Book the call →
07 · FAQ

The things people ask.

Who is this for?

Businesses of roughly 5 to 50 people who have outgrown the spreadsheet-and-goodwill stage. If one person leaving would break how you operate, that is us.

What does it cost?

It depends on scope, which is why we don’t print a menu. Audits and build sprints are fixed price, quoted before we start, and the number does not move. Book a call and you’ll get a straight answer inside fifteen minutes.

Do you build, or just advise?

We build. Every engagement ships working software, automations or infrastructure, not slides. We’ll advise along the way, but only alongside something real we’re delivering.

How fast can you start?

Usually within one to two weeks. The audit week is the fastest thing to book because it needs nothing from you but access.

What happens if it breaks?

Every build ships with a runbook, training and a 90-day warranty. After that most clients keep us on retainer, which is what the retainer is for.

We already have a developer. Does that matter?

No. We work alongside in-house teams often. We hand over source, documentation and access, and we do not hold anything hostage.

Do you need to be in the building?

For the first week, ideally yes, at least for a day or two. After that we are UK-based and remote-first.

08 · Book

Fifteen minutes, and you leave with a written answer.

No pitch. You describe what’s hurting, we tell you whether we’d take it on and roughly what it would cost.

  • no sales deck, no follow-up sequence
  • a written plan of attack, yours to keep
  • a straight no if it isn’t worth building

The calendar lives at cal.com; this page can’t frame it here.

Pick a time →

Or write to hello@theironheart.org · reply within 24 hours, usually 2

Bristol Upholstery · workshop

Quoting stopped being one person.

The manual version

Every quote priced from memory by the one person who knew how. Enquiries waited days for an answer, and the good version of the estimate lived in his head.

What we built

An intake form feeding a rules-based estimator: same inputs, same number, every time. Anything unusual routes to a human with the full context attached instead of a blank email.

What changed

Enquiries are priced in minutes without anyone touching them. Quoting is a system now, not a person. And the person got his evenings back.

Feet & Care · podiatry clinic

The diary stopped leaking.

The manual version

Bookings by phone, reminders when somebody remembered, and no-shows quietly eating clinic days that could never be sold twice.

What we built

Booking, reminder and no-show chasing chained into one flow that runs whether anyone is at the front desk or not.

What changed

The reminders go out on schedule, every time. Hours a month came back to the practice, and the diary holds what it is supposed to hold.

Cotswold Parties · events

Enquiry to paid, without a chase.

The manual version

Enquiry to invoice was a thread of copy-paste emails, and payment arrived whenever somebody found time to chase it.

What we built

One thread from first email to cleared invoice: quote, confirmation, invoice and chase, all generated from a single record of the booking.

What changed

Enquiry to paid runs without a human chase, and has kept running unattended for months.