Lesson 1 · 10 min

Scope a tool that does one job well

By the end

A one-page scope for your tool: one user, one task, one measure of success.

1Learn
2Try it
3Human check
4Quick check

Learn · 4 min

Small tools fail by being big

First AI tools often fail the same way: they try to do a whole job. “Handle customer emails” sounds like one task, but it’s really several: reading, sorting, looking things up, deciding, writing, chasing. A tool that tries all of them does each one a bit badly, and when something goes wrong, you can’t tell which part broke.

One job looks like this: turning a bakery’s wholesale order emails into rows on the order sheet, or a design studio’s call notes into a project brief. A tool that does one job well is quicker to build, easier to test and easier to trust. If it works, you add the next job. If it doesn’t, you’ve lost a week, not a quarter.

One user, one task, one measure

If you can’t name the user, you’re building for nobody in particular. If you can’t say where the task starts and ends, you can’t test it. If you can’t count the measure, you’ll never know whether it worked. So before anything gets built, write three lines:

One user: the person who will use it every week, by name. Not “the team.”
One task: a verb and a thing, with a clear start and end. “Draft a first reply to each new quote request, from our price list” is a task. “Help with sales” is a wish.
One measure of success: a number you can count from records you already keep, like “quote requests answered the same business day.” Note where it stands today.

Find the step that actually hurts

Ask the person who does the work to walk you through the last time they did it, not the official process. Write the steps as they really happen, workarounds included. Then mark the one step that eats the time or causes the mistakes. That step is your tool.

Next, ask whether that step needs AI at all. AI is good at reading messy text and drafting language. Plain rules are better for anything with a fixed answer: if the address is outside your service area, the answer is no, and a form or a spreadsheet formula gives it every time. And check whether software you already pay for does the job before you build anything.

Draw the edges

The most useful part of a scope is the list of what the tool won’t do. For a plumbing firm’s quote-reply tool, that might be: no firm prices for jobs that need a site visit, no replies to complaints, nothing sent without the office manager reading it first.

Add who approves the output and what happens to anything unusual. A good default: the tool drafts, a named person approves, and anything it isn’t sure about is marked “Needs a person” instead of guessed. Keep the whole scope to one page, so the person who’ll use the tool can read it in two minutes and tell you whether it’s the job.

Try it on your business

6 min

Turn the tool you have in mind into a one-page scope, and let the AI push back if it’s really three tools.

1
Pick a task you or a teammate do every week in roughly the same way, and think of the last time it was done.
2
Fill in the brackets from how that last time really went, not the official process, and run the prompt in your assistant.
3
If it says you’ve described more than one job, pick the smallest useful one and ask for the scope again, for that job only.
4
Check the measure: can you count it from records you already keep, and do you know roughly where it stands today? If not, change it.
5
Paste the scope into a shared doc and send it to the person named as the user, with one question: “Is this the job?”

I look after a workflow at [TYPE OF BUSINESS] and want a small AI tool for it. What I have in mind: [THE TOOL, IN A SENTENCE OR TWO].
The person who would use it every week: [NAME OR ROLE].
How the work happens today, step by step, including workarounds: [THE STEPS].
The step that takes the most time or causes the most mistakes: [THAT STEP].

Act as a skeptical operations advisor. First, tell me plainly whether this is more than one job, and which single job to start with. Then write a one-page scope for that job with these headings: User; Task (where it starts and ends); Input; Output; What it won’t do; Who approves; Measure of success. Flag any step where a simple rule, form or spreadsheet formula would do better than AI. Where you need a fact about my business, ask me instead of guessing. Keep it under 250 words.

Open ChatGPT Open Claude Open Gemini

Human check: before you use it

The person named as the user has read the scope and agrees it describes the job as it really happens.
The “won’t do” list keeps a person on anything involving money, prices, contracts or promises, anything sent to a customer and anything you can’t undo.
Every fact the AI added about your business (a price, a policy, a step) is one you’ve confirmed, not one it assumed.
You described the work instead of pasting customer emails or records, unless your plan’s data settings and your AI policy allow it.
You can count the measure of success from records you already keep.

Quick check · question 1 of 2No grades

Which of these is a well-scoped first tool?

Your notes · private, saved on this device

Ask the Distillery

Answers come from The Distillery’s own pages, with sources.

If the Distillery doesn’t know, it says so and points you to a person.