
The Short Version
Most articles about small business marketing mistakes are written by someone who would like to sell you the fix. This one is a list of things we got wrong building this site, with the receipts.
Want this built for you?
Animus Engine installs the marketing brain and the engine that runs on it. A human hand on every gate.
Five mistakes, each with a number attached:
- We bought pictures before we checked where they would appear.
- We paid for pictures before we agreed what they should say. Forty credits, five images, all rejected.
- We bought data we did not need. One keyword pull cost 1,936 units. The next one cost 64.
- We wrote a spending cap and broke it the same day. Forty allowed. Forty-eight spent.
- We built a monitor that slept whenever the machine slept.
The pattern underneath all five is the same, and it is the only real lesson here: we spent money on the assumption that something was true, when ten minutes of checking would have told us it was not.
Tell Us the Task That Eats Your Week
Name one marketing job you’d hand off tomorrow. We’ll send back how we’d run it with AI — the steps, the tools, and where a human stays in charge. A real reply from Chris within one business day.
Mistake One: We Bought the Picture Before We Measured the Wall
We commissioned cover images for every post at 2400 by 1260 pixels, saved as WebP, on a documented standard. Then somebody checked where they actually appear.
On the individual post page, the cover does not appear at all. The theme does not place it. It is present in the page’s metadata, which is what social platforms and search engines read when they build a preview card, but a reader who lands on the article never sees it. On the blog index and the category pages it does appear, in a thumbnail box 200 pixels wide by 125 tall. The file the theme serves into that box is 300 by 158, cropped to fit.
So we were producing an asset twelve times the width of the largest box the site ever shows it in, on the theory that it was a banner at the top of the article. It never was.
The part worth sitting with is that the specification turned out to be defensible anyway, for a reason we had not thought about. Two thousand four hundred by 1260 is exactly twice the standard size of a social preview card, which is the surface the cover genuinely serves. We got a reasonable answer by accident, and an accident that lands well is still not a method.
What We Did Instead
We now check the destination surface before commissioning the asset, and we say which surface we checked. “The image is on the post” and “the image is in the post’s metadata” are different sentences, and only one of them is about something a reader sees.
The general version, and the one that costs small businesses real money: before you pay for an asset, open the place it is supposed to live and look at it. Logo files, headshots, brochure photography, video cut for a platform that crops it square. The brief is usually written from an idea of the destination rather than the destination itself.
Mistake Two: We Paid for Pictures Before We Agreed What They Should Say
On 31 July we generated five images in a single batch. Forty credits. Every one was rejected.
They were not broken. They rendered cleanly, they matched their prompts, and there was nothing technically wrong with any of them. They were simply the wrong pictures, because we had never agreed what the pictures were supposed to argue before we paid to make them.
The check we had in place tested whether an image had rendered correctly. It had no opinion on whether the image said anything. So the check passed all five, and a human looked at them and cut all five.
It happened again in a smaller way a few days later, for a different reason. One concept went through two attempts and 32 credits and never produced anything usable, because the idea depended on the picture repeating an identical object across four columns at a consistent size. That is a thing image models are known to be poor at. The concept was not badly written. It could not be rendered at all, and no amount of rewording was going to fix it.
What We Did Instead
We separated two questions that we had been asking as one: is this image correct, and is this image the right image. The second question now gets asked before generation, in one sentence, and it gets asked again afterwards against what actually came back.
If you are buying creative of any kind, the equivalent is cheap. Write the one sentence the asset is supposed to make a viewer think, before anyone opens a design tool. If you cannot write the sentence, you are not ready to buy the asset, and a supplier will happily produce something beautiful that argues nothing.
Mistake Three: We Bought Data We Did Not Need
Our first serious keyword pull cost 1,936 metered units for 44 keywords. That is about 44 units per keyword.
The next pull cost 64 units for 32 keywords. Two units per keyword.
The work was not twenty times smaller. We had simply learned that the tool prices each field separately. The identifying fields are cheap. The interesting-looking columns are ten units each, and we had been requesting all of them by default on every row, including for a pull whose entire purpose was to check one relationship that needed none of them.
Nothing was wrong with the first number at the time. It is what the work costs when you do not know what you are buying. It became a mistake only when we kept doing it after the information to do better was available.
What We Did Instead
We now decide which fields a question actually needs before running the query, and we record the measured cost of every run rather than estimating it. That record is the only reason we can tell you the difference between 44 and 2, and it is the reason the third pull did not cost 1,936 units again.
For a small business the same shape shows up in software subscriptions and in agency scopes. The bill is rarely one big wrong decision. It is a default nobody revisited, running monthly.
Mistake Four: We Wrote a Spending Cap and Broke It the Same Day
On 4 August we ratified a daily limit on image generation of 40 credits, precisely to stop a bad day from becoming an expensive one.
That same day, we spent 48.
The ledger records it plainly, in two batches of 24, with the running balance dropping through both. The cap was real, it was written down, and it did not stop anything, because it was a number in a document rather than a check inside the thing doing the spending.
What We Did Instead
The limit now has to be read at the start of a run, before spending, by the process that does the spending. A cap that depends on somebody remembering it is not a control. It is a preference.
This is the most portable mistake on the list. Most small businesses have a marketing budget in the same condition: a real number, agreed by real people, sitting in a document that nothing checks before the invoice is approved.
Mistake Five: We Built a Monitor That Slept When the Machine Slept
On 6 August, two scheduled jobs did not run. Nothing failed loudly. There were no error messages, because nothing got as far as producing one.
We found out the following morning, and only because the log for that day was empty rather than wrong. The machine that runs the work had been closed through the window when the work was supposed to start, and the watchdog that was supposed to notice lived on the same machine. When the machine slept, the alarm slept with it.
A day of scheduled output was lost. That is a small loss for us because the queue was thin that day. It is not a small loss for a business whose one weekly email did not go out and whose reporting tool cheerfully showed no errors.
What We Did Instead
The fix is an external check that expects a signal and complains when it does not arrive, rather than an internal one that reports problems it is still awake to see. It is a small piece of plumbing, and it is worth more than most of the dashboards we could have built instead.
The general rule, which is worth stealing: anything that watches for failure must be able to fail independently of the thing it watches. If your alerting lives inside the system it monitors, you have a system that is confident right up until it is not.
The Mistake Everyone Writing About This Makes
When we measured the search results for this topic, the pattern was consistent. The pages ranking are forum threads, an insurance company’s learning centre, and small agency blogs running numbered lists. Every one of the vendor pages tells small businesses what they are doing wrong. Not one of them shows a single number from its own operation.
That is not dishonest, exactly. It is just advice with nothing behind it, and it is the reason so many owners have learned to read this entire genre as marketing rather than as information.
We are not neutral here either. We sell marketing operations, and this post exists partly so that you can judge us. The difference we would ask you to weigh is not tone. It is whether the person telling you about mistakes is willing to name their own, with a date and a figure attached, in a place you can check.
What to Check in Your Own Marketing This Quarter
This is the diagnostic version of the five mistakes above. It costs nothing and it takes about an hour. Most small business marketing problems that look like strategy failures turn out to be one of these.
- Take one asset you paid for and open the place it is supposed to appear. Not the brief. The live page, on a phone. Assets that live nowhere are more common than anyone admits.
- Write the one sentence your next piece of creative is meant to make someone think. If you cannot, do not commission it yet.
- Open your last three vendor or software invoices and find one line you cannot explain. There is almost always one, and it usually recurs.
- Find your marketing budget and ask what actually checks it. If the answer is a person remembering, the number is a preference.
- Ask what would tell you if your marketing stopped running. If the answer is that you would eventually notice, that is the same gap we had.
If the honest answer to most of these is uncomfortable, that is the normal result. It was ours.
Where We Actually Are, Starting From Zero
So that this sits on something checkable rather than on modesty, here is the state of the thing these mistakes were made building.
You can read this site’s entire archive in an afternoon, this post included. The last time we measured our domain rating, on 30 July, it was 0.0, and we have not re-measured it since because doing so costs metered units we would rather spend on research that changes a decision. Every figure in this article came out of our own cost ledger, run log and seed queue, which we keep because a claim we cannot trace is a claim we will not print.
We are not going to tell you that these mistakes made us wiser. They cost time and a small amount of money, and we would rather have had both. What they did produce is a record specific enough to be useful to somebody else, which is the only thing that makes a post-mortem worth publishing.
If you want the longer version of how this content operation runs and what a single post consumes, that is in what content marketing actually takes — including a section on when something else comes first, which is a genuinely different question from this one and gets a fuller answer there. The system these mistakes were made inside is described in building the system before you buy the tool, and the shape of the team that runs it is in marketing operations team structure.
If you want to check the operating context for small businesses against something neutral rather than something we wrote, the SBA’s Office of Advocacy publishes independent research, and the Census Bureau runs a business trends survey that tracks technology adoption among small firms. The Census survey is labelled an experimental data product, which is worth knowing before anyone quotes it at you. For the mechanics of how search actually treats a site, Google’s own documentation is the primary source and costs nothing.