Skip to content
alphonseautomation
All guides
Foundations · 6 min read

Start with one business problem.

A useful AI project starts with a specific piece of work that could go better. Choose something you can observe, explain, and evaluate. The first win is learning what makes a result useful in your business.

What you’ll take away

Leave with one clearly scoped experiment and a way to decide whether it helped.

Find the work that keeps coming back.

Look at a normal week. Where do you repeatedly retype information, chase missing details, interpret messages, prepare a first draft, or reconcile conflicting records? Ask the people doing the work. A recurring annoyance is often a more useful starting point than an ambitious transformation plan.

Be specific about the trigger and the result. “Help with customer service” is hard to evaluate. “Turn each new service inquiry into a complete brief for the person preparing the quote” gives you a bounded task.

  • What starts the task?
  • Who does it today, and what do they need?
  • What does a useful result look like?
  • Where does the current process break down?

Check whether the problem is actually clear.

Sometimes the delay comes from unclear responsibility, missing information, or an inconsistent policy. AI can help you investigate that. Adding automation before resolving the uncertainty can simply make the confusion happen faster.

Have the model restate the task and list its assumptions. Correct those assumptions before asking for a solution. If two people disagree about what “done” means, settle that disagreement first.

Choose a small, reviewable first result.

Start with a draft, summary, checklist, or comparison that a person can inspect before it changes anything. Use material you are allowed to share in the tool you choose. Remove details that are irrelevant to the experiment.

Choose one outcome to improve, such as fewer missed requirements or less time spent preparing a handoff. Also name a quality condition: the brief must include every customer requirement and must mark unknowns. Saving time only counts when the resulting work is good enough.

Compare against the way you work today.

Gather a small set of representative past examples, including an awkward one. Do the task manually and with AI. Record preparation time, review time, corrections, and the final quality. This is an exploratory pilot, not proof that the workflow works in every situation.

If the outputs look useful, try a limited live pilot with a clear owner. If they fail, inspect the failure. Was the goal unclear, the context incomplete, the source wrong, or the model unsuitable? Change one thing and try again.

Keep the useful learning.

Save the task brief, a strong example, and the corrections you made. Put the accepted result into a simple procedure another person can follow. The valuable asset is the combination of business understanding, instructions, examples, and review criteria.

Repeat the experiment before extending it. A successful draft does not automatically justify sending messages, changing records, or making commitments without review. Those are separate capabilities that need their own evidence.

Example: a service inquiry becomes a quote brief

An illustrative workflow for a service business. The model prepares the information; a team member decides what to quote.

Replace the bracketed fields before using this with AI.

Try it in your business.

  1. Write down one recurring task from the last week.
  2. Define one useful output and one quality condition.
  3. Choose three past examples, including one difficult case.
  4. Compare the work and the review effort before expanding the pilot.
Use the matching template

Further reading

Anthropic: Building effective agents