What Actually Happens on a 30-Minute Bottleneck Audit

The first call with Brightline Labs is thirty minutes. It is titled “bottleneck audit” and it happens before anything is scoped, priced, proposed, or committed to. Most partners I meet arrive at the call expecting some version of a sales pitch — slide deck, case studies, pricing matrix, soft close. That is not what the call is. This piece describes what it actually is, in more detail than the book page does, so anyone thinking about booking one knows exactly what they are signing up for.

I wrote this down because a depressingly common piece of feedback I get from partners after a discovery call is something along the lines of “that was refreshingly different from how I thought it was going to go.” The fact that it has to be refreshing is an indictment of the industry, not a credit to me. Every consulting call should feel this way. The only reason it usually does not is that most consulting calls are really sales calls wearing a different badge.

What I do before the call

Before we speak, I read whatever is public about the firm. Practice areas, attorney or partner headcount, office locations, any press or writing the firm has put out, the shape of the website. If you have sent me a sentence about the workflow in question, I read that three or four times. The goal is not to arrive with a plan. The goal is to arrive with enough context that the thirty minutes gets spent on you, not on me asking questions Google could have answered.

I do not prepare a deck. I do not prepare a demo. I do not prepare case studies to leaf through. I prepare a blank page of questions and a few intuitions about what the firm’s situation is likely to be, which I then mostly throw out during the first three minutes of the call, because reality is always more specific than the intuitions.

The three questions the call actually turns on

Every discovery call I run is built around three questions, in this order. They sound simple. They are not, and the answers are the whole audit.

These questions are not warm-up questions. They are the audit. Everything else we discuss is a consequence of what you say in response.

Why these three, in this order

Question one is the most important, and it is the one most partners answer wrong on the first try. The word is specifically, and it is load-bearing. “Document review” is not a workflow. “The first-pass review of deposition transcripts for a case captain, the week after a deposition” is a workflow. Ninety percent of the value of this question comes from the follow-up questions that drag the answer from the first shape to the second. If I do nothing else useful on a call, getting the firm to state its problem at the right resolution is worth the thirty minutes.

Question two is the question partners are least prepared for, because it flips the perspective. Most partners describe the workflow from their own vantage point: what lands on their desk, what theyapprove, what they bill against. The person who actually does the workflow every day almost always has a different mental model of it — different pain points, different edge cases, different sense of what “working” would even mean. If a build ever happens, that person is who the build is for, and the call is more useful if their voice enters the room early, through the partner’s recollection of what they actually say.

Question three is a reality check on the ROI math. Firms underestimate how hard it is to convert reclaimed hours into P&L impact. If the answer is “we would do more of X” and X is something the firm is genuinely capacity-constrained on, the ROI is real. If the answer is “we would have a calmer August,” the ROI is real but harder to put on a spreadsheet. If the answer is an uncertain shrug, I say so, and we talk about how to convert the answer into a real one before we discuss building anything.

What comes out of the call

The deliverable from the call is not a proposal. It is a verdict. There are three possible verdicts.

Verdict A: a real build candidate exists.This happens on roughly half of the calls. The firm has a repeating, structured, measurably-painful workflow that is a strong fit for a bespoke AI module, and the person who owns the workflow day-to-day is available to participate in the build. When the call ends I tell you what I would scope, what it would likely cost, and what an early demo would look like. You decide whether to move to the scoping step. Most partners want a day or two; that is fine, and expected.

Verdict B: the right answer is not custom software. This happens on about a third of calls. The firm has a real workflow problem, but the problem is better solved by renegotiating a vendor contract, reorganizing a team, switching practice-management systems, or, in a few memorable cases, sending the partner to a different accountant. I say so. I suggest the alternative if I know one. Nobody tries to close anyone. The call ends having saved the firm a hundred thousand dollars of false starts, which I think is the correct way to measure the value of a discovery call that concludes this way.

Verdict C: the information is not there yet.Sometimes the firm knows there is a bottleneck but has not yet named it specifically enough to build anything. That is fine, and common. When this happens I usually suggest a one-week self-audit exercise: track the workflow, who touches it, how long each step takes, where the waste is. We reconvene after that, for free, with real data. A surprising number of these second calls produce verdict A within twenty minutes, because the firm now has the resolution the first conversation was missing.

What the call is not

A few things the call is specifically not, for the avoidance of doubt.

It is not a slide deck. There is no deck. There is never a deck. If you want one for internal circulation I will write a paragraph after the call that captures what we discussed, and you can share that however you like, but the call itself has no visual aids and no screen-share.

It is not a demo. Custom work is poorly represented by demos, because every piece of work is firm-specific. What looks slick in a demo is someone else’s firm-specific work, which is exactly the thing your firm should not buy off the shelf.

It is not a multi-round sales cycle. There is no follow-up call scheduled in advance. There is no nurture sequence. If the call ends with verdict B, we part amicably and I refer you to the right specialist when I know one. If the call ends with verdict A, the next step is a written scope and a fixed price; the scoping work is billable but small, and I will tell you what it costs before we start.

It is not binding. Booking the call does not commit you to anything. Receiving a scope does not commit you to a build. Signing a scope commits you to the fixed price of that build, and the scope is deliberately short and written in plain language, not in MSA boilerplate.

Why it is structured this way

The whole structure of the call is designed to surface the honest answer fast. The reason most consulting calls don’t end with an honest answer is that the person running the call is compensated for a different outcome. They are paid to advance you down a funnel, or to generate a statement of work, or to book a second meeting. None of those incentives select for telling you the truth.

Brightline Labs is structured so I can afford to tell you the truth on the first call. Engagements are fixed-price, two weeks each, and delivered to your repo. I don’t have a quarterly quota. I don’t have a retention target. What I have, instead, is a pattern I care about: firms that complete one Sprint and decide it was worth it tend to come back for a second. Firms that complete one Sprint and decide it was not, tell two other partners why, and two other partners never call. The only way to win that game is to be right about the first call. So the first call is engineered to be the most honest conversation the firm has had about this subject in a year.

If you are weighing whether to book one, the simplest test is this: do you have a workflow in mind you could describe to me in two sentences, and do you have a specific person inside your firm who owns it? If yes, the thirty minutes will be well spent regardless of which verdict we land on. If no, take fifteen minutes this afternoon to write those two sentences, identify that person, and then book the call. That fifteen minutes is the difference between a discovery conversation that gets to something useful and one that politely circles.

I read every booking note personally and reply within one business day. Most calls happen within the following week. There is no assistant, no qualifier call, and no pitch phase — just the call, and the verdict it produces.