Why We Start With a Half-Day Workshop, Not a Six-Month Project

Ask an executive director or a small-business owner what they're short on, and the honest answer is rarely just money. It's time. There is one of them where there should be three, the calendar is already full, and every new commitment comes out of something that was already load-bearing.

That single fact shaped how we built Breakwater Operations. Most consulting is designed around the consultant's economics — long engagements, big retainers, a scope that expands to fill the contract. We started somewhere else: what does an engagement look like if you take seriously that the client's time is the scarcest thing in the room?

The answer, for most organizations, is a half-day workshop. Not a six-month project. Here's why.

The Six-Month Project Asks You to Bet Before You Know

The standard model asks for a big commitment up front — months of work, a large budget, a lot of your team's attention — and delivers its verdict at the end. You find out whether it was worth it only after you've already paid for it.

For a well-resourced institution, that's a manageable bet. For a five-person nonprofit or a family-owned business, it's the opposite of manageable. You're being asked to wager scarce time and money on a promise, and the structure of the deal quietly transfers all the risk to you. If the recommendation lands flat, the consultant still got paid for six months. You got a binder.

We think that's backwards. The party asking you to commit should be the one carrying the risk that it wasn't worth it — not you.

Start Small, Go Deeper Only If There's a Reason

So we invert it. Most engagements start with the smallest useful thing: a half-day AI Literacy Workshop for your team or board. In one afternoon you get plain-language grounding in what these tools actually do, where they genuinely help, where they don't, and a live discussion of your real situations — not a generic curriculum.

At the end, one of two things is true. Either you've got a clearer head and enough shared vocabulary to make your own decisions — and you stop there, money still in the bank. Or you've found something specific worth examining, and you go one step deeper: a scan, an audit, whatever the actual question turns out to need.

Crucially, the depth is earned each time, not assumed at the start. Every stage is fixed-scope and stands on its own. You are never locked into stage four because you agreed to stage one. Plenty of organizations do the workshop and stop — and that's not a failed engagement. That's a good outcome.

Why a Half-Day Is Enough to Start

It's fair to ask whether meaningful work can happen in an afternoon. For the first step, it's not only enough — it's the right size.

Most organizations don't have an AI implementation problem yet. They have a clarity problem. The board can't agree because nobody shares a vocabulary. The staff is anxious or over-optimistic because nobody has separated what these tools really do from the headlines. The real first task isn't building anything — it's getting everyone in the room to see the same picture. That genuinely fits in a half-day, and stretching it to six months wouldn't make it truer.

There's a second reason. A workshop puts the people who actually do the work in the room. They know where the friction really is — better than any consultant arriving with a template. A half-day of structured conversation with them surfaces more usable signal than weeks of a consultant studying the org from the outside.

The Independence Underneath the Model

There's a reason most firms can't work this way, and it's worth naming.

If your revenue depends on selling long engagements or the software at the end of them, a half-day that might conclude "you're in good shape, go do it yourselves" is a threat to your business model. You need the big project. So the big project is what gets recommended.

We don't resell software, take commissions, or earn anything based on which tool you choose — so we have no structural need to grow the engagement. That frees us to recommend the smallest thing that actually helps, including nothing further. We'd rather earn the next step by making the first one genuinely useful than lock you into a scope you'll resent by month three.

This is also just how the two of us think. Barry spent fifty years watching organizations get sold sweeping transformation projects that arrived years before they were useful; the instinct to start small and prove value is hard-earned. Griffin's research runs on the same logic — narrow, testable, verify before you scale. A half-day pilot before a big commitment is that principle applied to the engagement itself.

What This Respects

In the end, the workshop-first model is a statement about whose constraints matter.

A model that demands a large upfront bet before proving its value is optimized for the consultant's certainty, not the client's reality. It treats your time as abundant when it's your scarcest asset. We'd rather build the opposite: a first step small enough that saying yes isn't a gamble, useful enough that you'd have wanted it either way, and honest enough that "you don't need the next stage" is a real thing we'll tell you.

Time is the one thing you can't get more of. The least a consultant can do is respect that.

Where We Come In

If getting your team or board on the same page sounds like the right first step, that's exactly what the AI Literacy Workshop is for — a half-day, fixed-scope, no product demo, no pressure to go further than it's worth. Most of our engagements start there, and a good number happily end there too.

Learn more about the AI Literacy Workshop or start a conversation.