Most engagements start with a discovery call. The vendor asks open questions, takes notes, nods, and promises to come back with something. The prospect spends an hour describing a problem and leaves with nothing in hand. The first artefact, if one ever arrives, is a deck or a quote built to win the work rather than to read the problem.

BOST starts differently. Our first step is a working operating brief. You describe the operating problem. We respond in writing, in seven days, with a one-page reading of how we would attack it. Not a deck. Not a quote. A reading. The difference is not stylistic. A discovery call extracts. A brief commits. That single change in the order of operations decides how honest the rest of the relationship can be.

Six Fields, Seven Days, One Page

The brief is captured through an adaptive briefing wizard on our site. It is short, and it adapts to what you have already said, but it always lands on the same small set of fields, because those are the fields that decide whether work is worth doing.

It asks for the problem: the operating thing that hurts, stated plainly. It asks for the constraint: the regulation, the budget, the timeline, or the political reality that any answer has to live inside. It asks for the current systems: what already runs, so a solution can embed rather than rip and replace. It asks for the future owner: the named person or team who will hold the work after we leave, because a solution with no owner is a liability with a delivery date. And it asks for a set of KPIs with their baselines: where the numbers stand today, before anyone touches anything.

Seven days later you have a one-page reading. It states the problem back to you in our words, names the constraint we think actually binds, sets out the lens we would lead with, and says what the first move would be. It is short on purpose. A one-page reading you can act on is worth more than a forty-slide deck you have to schedule a meeting to understand.

A discovery call extracts. A brief commits.

A Brief Is More Honest Than a Meeting

A meeting rewards fluency. The room warms to the confident voice, the tidy story, the answer that sounds finished. Nobody in the room is forced to commit to anything, so nobody does. A week later the energy is gone and the notes do not agree.

Writing is less forgiving, and that is the point. To write a one-page reading we have to decide what the problem actually is, which constraint actually binds, and what we would actually do first. There is nowhere to hide a vague claim in a paragraph that has to stand on its own and be read back to you. Writing forces the three questions that matter: what hurts, who owns it, and by when. A call lets all three stay soft. A brief makes us answer them in ink.

It is more honest for you, too. A reading on paper is something you can forward, challenge, and hold us to. You can disagree with our framing line by line. You can show it to the future owner and watch their reaction. You are not buying a feeling from a good meeting. You are reading a position you can test. That is why we say a brief is more honest than a meeting. The meeting flatters everyone. The brief commits someone.

KPIs and the Success-Fee Baseline

The most consequential field in the wizard is the one people are tempted to skip: the KPIs and their baselines. Naming the numbers up front, before any work begins, is what makes an outcome-based engagement possible and honest.

Here is the mechanism. If we agree on which KPIs matter and write down where they stand today, then we have a baseline neither side can quietly redraw later. That baseline becomes the reference for a success-fee option. We carry part of our compensation on whether the numbers actually move from the line we both signed. A success fee with no agreed baseline is theatre, because the baseline can be redrawn after the fact to manufacture a win. A success fee anchored to a baseline you set before we started is a real shared stake.

This is why the baseline lives in the brief and not in a later negotiation. By the time price is discussed, the numbers that define success are already on the table, set by you, agreed by both sides. That ordering is deliberate. It means our consulting fees, success fees, and licence fees all sit on a foundation you defined rather than one we proposed once the work was underway.

A success fee with no agreed baseline is theatre. The baseline has to be set before the work starts.

What Happens Next

The brief is the opening move, not the whole game. When the reading lands and you decide to go further, the path from there is direct.

First we scope. The one-page reading becomes a defined piece of work with a constraint, an owner, and the KPI baseline already attached. Then we embed. We work inside your current systems and alongside the future owner, not in a parallel lab that hands over a black box. Then we build, against the operating picture (Marsad), into field action (Maydan), and through to operating continuity and handover (Mashhad). Then we hand over. The future owner named in the brief takes the work and runs it without us. We measure the engagement by what survives that handover, not by what looked good on the way in.

That is the whole logic. Write the problem down. Read it back honestly. Set the baseline before the price. Build against it. Leave something that runs without us. None of it requires a discovery call, and all of it starts with a single page.

If you have an operating problem that hurts, start a brief at bost.boonio.com. Describe the problem, the constraint, the current systems, the future owner, and the KPIs. Seven days later you will have a reading you can act on. That is a more honest first conversation than any meeting we could schedule.