Whitespace AI

Whitespace Designs / automation

Your team should not spend Friday doing what a script can do by Tuesday.

I build automation for businesses with five to thirty staff — the ones where the same person doing the marketing is also doing the invoicing. Not chatbots. Working pipelines that take the repetitive production work off your team and hand back the week.

01

Marketing that ships without a coordinator

A motorcycle dealer near Whitby sends regular email campaigns. The products, the prices and the images all live in the storefront already, so a person copying them into an email is a person transcribing a database by hand.

The pipeline reads the storefront, builds the campaign against the approved layout, and leaves a draft waiting for approval. Nothing sends without a human saying so — that is deliberate. The same setup runs a racing team’s social accounts: clips cut, captioned, scheduled, and partner accounts tagged from verified records rather than from memory.

1 sourceThe storefront is the only place a price is typed. Email, social and the site all read from it, so they cannot disagree.
0 surprise sendsEverything lands as a draft. Automation does the assembly; a person still decides what goes out the door.
02

Footage that finds itself

If you have ever paid an editor, you have paid for the hours they spent watching. Scrubbing a card of 4K clips to find the eight seconds worth using is billable time that produces nothing on its own.

I built an indexer that watches it instead. It breaks each video into shots, transcribes the audio, reads numbers and text off the image, and writes the lot to a file you can search in plain language. A 604 MB 4K clip comes out the other side as a 1.3 KB index. You ask it where someone says a phrase, or where a number appears, and it hands back the timestamps.

604 MB → 1.3 KBOne 4K clip reduced to a searchable index of shots, transcript and on-screen text. Measured, not estimated.
0 uploadsRuns offline on an ordinary laptop. Client footage never leaves the building, and there is no per-minute cloud bill.
03

Built around how you already work

The automation that survives is the automation shaped to an existing process, not the one that demands you change to suit it. So I start by watching the job get done, find the part that is the same every time, and automate only that.

What I build checks its own work and tells you when it is unsure, because a pipeline that fails silently is worse than no pipeline. It runs on your hardware where it can. And you get the source — this is your process, not a subscription you rent back from me.

What takes your team all week?

Tell me the job nobody wants on a Friday afternoon. If it is worth automating I will tell you how I would do it, and if it is not, I will tell you that instead — it is a short conversation either way.