Cerebrium
Cerebrium Consulting ← Back to homepage
Brain · online
Book discovery →
Brain Tom Olakitan Trained on Tom's methodology

Ask honestly.
Get the same advice I'd give on a call.

Brain is trained on my methodology, frameworks, and the reasoning behind them. It will tell you when you're not ready, when a tool you've mentioned is wrong for your situation, and when the answer is "call me instead."

We're a 32-person distribution business in Surrey. Our competitors are talking about AI non-stop. I feel behind. Where do I actually start?
Parsing: org size 32, industry = distribution, geography = BC, stated emotion = "behind"
Flagging: question is about starting point, not tool selection
Pulling: Education stage framework, FOMO-driven engagement heuristics
Cross-checking: Tom's prior notes on SMB urgency paradox

Reading between the lines

Before anything else — "I feel behind" is the most important sentence you wrote. It's also the most dangerous. Most failed AI engagements start with that exact feeling, because it pushes you toward doing something fast rather than doing something right.

So the honest answer to "where do I start" is: you start by not starting with a tool.

What I'd actually do in your situation

A 32-person distribution business is almost always better served by three unglamorous things before any AI conversation:

1 · Honest data audit. Where does your customer, inventory, and fulfilment data live right now? If the answer involves three spreadsheets and a shared drive, AI won't fix that — it will amplify it.

2 · One specific pain, not "AI strategy". Pick the single most expensive repeated decision or bottleneck in your week. That's the candidate — not "let's use AI."

3 · Readiness, not roadmap. Know your score on data, strategy, tech, people, governance before anyone sells you a platform.

Concrete next step

Take the 5-minute readiness assessment. It will give you a diagnostic across the five dimensions above — free, no login. If the score comes back in the yellow or red, we should have a conversation before you spend a dollar on AI. If it's green, we have a very different conversation.

Drawn from
The SMB Urgency Paradox
Article · 2,400 words
Readiness > Roadmap
Method · Stage 02
This is where Brain stops. The readiness conversation is too specific to your business for a chat to finish. If you want the real version of this answer — with your actual data, your actual people, and your actual P&L — book a 30-minute discovery call. The first one is free.
A vendor just quoted us $80,000 for a 12-week "AI transformation pilot." They said we need to act now because our competitors are ahead. Is this reasonable?
Parsing: vendor quote $80k, timeline 12 weeks, pitch mechanic = urgency + FOMO
Flagging: "transformation pilot" is a category error — transformation ≠ pilot
Cross-checking: SMB vendor-pricing norms, scope-vs-outcome red flags
Pulling: Tom's notes on vendor pushback, discovery-before-delivery

The short answer

No. And it's not the number that's wrong — it's the shape of the deal.

"$80k for a 12-week AI transformation pilot" is three red flags in a single sentence:

1 · "Transformation" and "pilot" don't belong together. A pilot is a scoped experiment against a single hypothesis. Transformation is a multi-year organizational change. If a vendor uses both words in one sentence, they're selling the romance of one and the scope of the other.

2 · "Your competitors are ahead" is a sales tactic, not a diagnostic. It's impossible for them to know what your competitors are actually doing. Urgency is the oldest tool in the B2B sales playbook — treat it as information about them, not about you.

3 · No outcome is named. Ask them: "What specific decision or process will be measurably different at week 13?" If they can't answer in one sentence, you're buying activity, not impact.

What a reasonable engagement looks like

For a business your size, a credible first engagement is usually $8k–$20k for 3–4 weeks, outputs a readiness assessment and a single prioritized use case with a business case. Then — then — you scope build.

If this vendor can't restructure their proposal into that shape, they're not the right vendor. That's not negotiation advice — that's a compatibility signal.

What I'd do tomorrow

Send them three questions in writing: (1) What business outcome is this measuring? (2) What happens if the pilot fails — do we keep anything? (3) Who owns the data, the model, and the IP at week 13? Their answers will tell you everything. Most vendors will not respond.

Drawn from
Vendor Red Flags
Article · 1,800 words
Discovery Before Delivery
Method · Stage 01
If they're pressuring you to sign this week, that's the answer. Send me the proposal if you want a second pair of eyes — happy to do a 20-minute read-through free. book a vendor review →
My leadership team is pretty skeptical about AI. Half think it's hype, half are scared of it. How do I bring them along without forcing it?
Parsing: split team sentiment — hype-skeptics + fear-skeptics
Flagging: these are two different problems, opposite solutions
Pulling: change-readiness frameworks, Stage 04 people dimension

First — you have two teams, not one

"Hype skeptics" and "fear skeptics" sound similar but they need opposite things. Treating them as one group is where most leaders lose the room.

Hype skeptics think AI is overblown. They'll be persuaded by evidence — a small, real result inside your own business. Not a demo, not a case study. Something they watched work.

Fear skeptics think AI is coming for their role or their team. They'll be persuaded by agency — being the people who choose, scope, and evaluate it. The fastest way to make them hostile is to hand them a finished tool.

A sequence that usually works

Week 1 · Ask, don't tell. Individual 20-minute conversations with each skeptic. One question: "Where do you spend time on work that doesn't feel like yours?" You're not selling AI. You're collecting candidates for what AI could remove.

Week 2 · Pick one boring thing. Not the flagship process. Something tedious and low-stakes — meeting notes, invoice categorization, report summaries. Boring protects you from big-bet failure.

Week 3–4 · Let a skeptic lead the pilot. The person most skeptical should run the small experiment. If it works, they become your most credible advocate. If it doesn't, they trust the rigor.

Week 5 · Share honestly. Present what worked, what didn't, what you'd do next. Not a celebration — a field report.

What not to do

Don't run a lunch-and-learn with an external speaker. Don't buy a platform "for the team to try." Don't announce an AI strategy at an all-hands. Every one of those makes skeptics more skeptical, because each one skips the thing they actually want — to be consulted before a decision is made.

Drawn from
Two Kinds of Skeptic
Article · 1,600 words
People Dimension
Method · Stage 04
Change work is where engagements succeed or fail. If you want help running the first round of skeptic conversations without it feeling like a setup, that's something I help with often. book a change session →
⏎ send · ⇧⏎ new line

Brain is a demo of the advisory tooling Tom builds for clients. Your conversation isn't stored or trained on.