Before a lean professional team adopts a tool — really adopts it, not just pilots it — they ask two questions. Not always explicitly. Not always in this order. But always.

The first question: how long to go live?

This isn’t asking for a project timeline. It’s asking whether there is a project at all. A lean team has no capacity for an implementation project. If the answer is “a few weeks once we configure the integrations and train the team,” the tool doesn’t get adopted, regardless of how good it is. If the answer is “you can use it on your next deal,” adoption is possible.

The second question: can I trace the output back to the source?

This is a trust question, not a technical one. A professional’s reputation is tied to what they sign off on. If a tool produces a number, a summary, or a conclusion, and they can’t verify where that came from, they can’t use it in a deliverable. The output is unusable even if it’s correct, because correct isn’t enough — traceable is required.

These two questions are the filter that most AI tools fail. They’re designed by teams who optimized for capability and assumed the implementation would be handled by IT. The capability is there. The traceability is there if you dig into the settings. The time-to-first-value is measured in weeks.

A tool that passes both questions looks different. It works on the documents the team already has. It produces output with citations to the source text. It’s useful in the first session, not after a configuration sprint.

The deal-breaker questions are worth understanding because they reveal what lean teams are actually optimizing for. Not the best tool. The tool that fits their constraints — time, trust, and capacity.

Build for the constraints and the capability takes care of itself. +++