02/09/2026
What we got wrong building it
We’ve spent a good while building AI into The Brick Factory, and since I’ve spent five posts telling people how to judge other suppliers’ claims, it’s only fair to say what didn’t work in ours.
The first version of the quote was too clever. It tried to determine pricing from patterns in historical jobs. Impressive when it was right and quietly wrong in ways nobody could explain, which is worse than useless in a business where somebody has to defend a number to a customer. We rebuilt it to work from explicit rules the customer sets, with history used only to fill in what it already knows about that account. Less clever. Considerably more useful.
We underestimated how bad artwork actually is. We built the checker against the faults we expected. Then we pointed it at real files from real customers and found things we hadn’t imagined, including a logo somebody had scanned from a printed business card. The checker got a lot more paranoid.
We tried to automate approvals and had to pull it back. Routing a job automatically is fine. Approving one on somebody’s behalf is not, and the first time it went wrong it cost a customer a morning. Approvals go to a person now, faster than before, but to a person.
And the honest one. Early on we described this work in the way everyone describes it, as intelligence and automation, and it landed badly with exactly the people it was built for. Printers don’t want intelligence. They want forty minutes back on a quote and the artwork fault caught before the press. Same product, and we were selling the wrong half of it.
None of that is in a brochure, which is rather the point. Anyone who tells you their AI went in cleanly the first time either hasn’t shipped it or isn’t telling you about the bit that didn’t.
Ask us what went wrong. We’ll tell you, and then you can judge the rest of it properly.
30 minutes. www.brickfactory.uk