Fulkram
Fulkram / work / the audit and the migration
Case study · my own business as the client

First I audited my own stack. Then I moved it.

Every money figure on this page comes from my own books. I ran this audit and this migration on my own business, where I could count everything and keep the receipts. Here's what an honest one looks like.

Not proven yet

No client money result appears anywhere on this site. None has been measured to my standard yet, and I won't invent one. When a client's number exists, it goes up the same way everything here does: with a method and a date.

Until then, the money on this page is my own. Which also means nobody rounded it up for a brochure.

Part one

The audit

I exported every automation from the old platform and counted what had actually run.

Automations that had run in the last 30 days

The dashboard looked busy. The export said otherwise. Everything else was furniture with a subscription attached, and I'd been paying for it for years.

The receiptSCREENSHOT The audit table, from the platform export

Zombie automations, still holding people

Holding 14,392 contacts mid-sequence: people who'd entered an automation that was never going to move them again. Nobody noticed, because nothing was visibly broken. I'd say that's the quiet failure mode of these platforms.

The receiptSCREENSHOT The zombie count, same export

A year of subscriptions, cut

6 tools replaced with small systems I own outright. Each cancellation sits in the ledger below with the tool named, and every line is a cancelled bill.

The receiptSCREENSHOT The cost audit ledger, below
The cost audit ledger showing six cancelled tools
The cost audit ledger. 6 cancelled tools, £12,000+ a year, from the real ledger.
Part two

The migration

The audit made this obvious: the old email platform was billing for a list most of which had already left.

Contacts archived from the old platform

The honest split: 9,468 still active, 26,997 unsubscribed, 661 bounced. The platform billed on the whole number. I only ever needed the first one.

The receiptSCREENSHOT Live query against the archive, aggregate counts only

Import errors

9,446 active contacts went into the new platform in one weekend, start to finish, and the import log is kept.

The receiptSCREENSHOT The import log

A month, before and after

Same list, same emails going out. about £7,000 a year saved on the email platform alone.

The receiptSCREENSHOT Billing records, both platforms

The archive, still queryable

Nothing was thrown away. The full history sits in a local database, 43 tables, that I can still query today, and it's mine outright.

The receiptSCREENSHOT File inspection, table count

Trapped in an expensive tool because moving feels too risky? That's the exact job I do without drama. Mine took one weekend, and the import log is kept.

The migration summary showing contacts archived and the monthly cost drop
The migration summary. 37,160 contacts archived, £650 a month down to £73.
What this means for you

Subtraction first, build second

Subtraction first. The build, if there is one, comes after.

No new tools, nothing for your team to learn. I audit what you're already paying for, show you what's actually running, and cut what isn't. In my own case the saving landed before anything new was built.

Then, if a build is worth doing, it's funded out of money you were already spending. And sometimes the answer after the audit is that you don't need a build at all. I'd rather tell you that than sell you one.

Paying for tools you couldn't list from memory? Send me the list you can remember. I'll find the rest.