BrickHouse / How we work
Fixed prices agreed before we start, a free Walk on your floor first, and an honest answer when the right recommendation is to do nothing.
The engagement
01
A free Walk on your floor, then a data export and three short interviews. You keep the signed report whether or not we build anything.
02
We design and build the system, connect it to what you already run, then put it in front of the people who’ll use it and correct it until they’d complain if we took it away.
03
If a system needs support, an upgrade, or its next version: a named certified engineering technologist, a response commitment, and tuning as your operation changes. Per system, quoted with or after the build. Never required.
The whole arc
What a complete engagement actually looks like, start to finish.
You can stop at any point. Roughly a third of Inventories end at day 14 with a report the customer acts on themselves, and that’s a legitimate outcome.
Timelines
Delivery
Data arrives by export. Interviews happen by video, scheduled around your operation. Implementation runs over APIs and a screen share with whoever looks after your systems.
We’re in Ontario and we’ll come and stand in your building if it helps — particularly early on, when you’re deciding whether to trust us. That’s our cost, not yours.
Ownership
Every account and every system we build is in your name — source, configuration, documentation. If you walk away tomorrow, it all keeps running.
All of it, always. We’ll export it for you on request, in a usable format, at any time — including if you’re leaving.
The system map, the Systems Inventory, the configuration record, and the reasoning behind every decision. Handed over so nobody inherits a black box, including whoever replaces us.
Our Inventory method, templates, internal tooling, and general-purpose components we wrote. The plumbing, not your business logic.
On benchmark data. With your written permission we keep anonymised, aggregated timing figures — never your name, your customers or your commercial detail — so we can tell the next operation how they compare. Entirely opt-in — decline it and nothing changes.
Boundaries
Fixed price, agreed before work starts. You never pay for our learning curve.
No percentage of your business, no attribution arguments, no ongoing claim.
An implementation nobody maintains stops being used. That’s what optional Support prevents — and why everything we hand over is documented either way.
If a process change fixes it, we say so — including when it costs us the project.
One conversation, no deck. Describe it in plain language and we will tell you honestly whether it is a tooling fix, a process fix, or something you should not spend money on at all.
Tell us what’s broken