In-scope / out-of-scope drafter

Packaged know-how that tells an agent how to do a job well.

You might say…

“The scope document I send isn't defensive paperwork — it's the first test of whether we actually agree on what I'm here to do.”

What it does

Turns a loose description of the remit into an explicit in/out scope statement — decisions the advisor has a voice in, functions touched, domains owned versus reserved for others.

Trigger: Use to convert a vague brief into a crisp boundary the client can react to, before terms are set.

I/O: Loose remit description + known exclusions → structured in-scope / out-of-scope statement

Recognise the problem?

The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.

Start a conversation