EN
SENDOWEB
AI

AI for small businesses: Start with one workflow

When I bring AI into a workflow, I start with a job I can describe in one sentence. Turning call notes into a project brief makes a useful first test: the inputs, expected output and person responsible for review are all clear.

Start with one handoff

Try turning a discovery call into a short brief. Give the assistant the outcome you want, the questions it needs to answer, and one example of a brief you’d actually use. For the first pass, pick five sets of fictional or anonymized notes. Keep the same brief structure for each so you can compare results fairly.

Give it a way to say “I don’t know”

Ask it to flag missing details rather than filling gaps. Keep customer data out of test prompts unless you know how the tool handles it and have permission to use it. Check names, figures and commitments against the source. A confident sentence that invents a delivery date is a failure even if the rest reads well.

Count the review time

Compare the old process with the new one, including editing and rework. If checking the output takes longer than writing it, tighten the task before expanding the pilot. In a sample run, the manual brief takes nine minutes. Drafting by AI takes two, and review takes four. That saves three minutes, as long as the brief has the same quality and completeness.

A prompt I’d try first

“Turn these notes into a project brief with four headings: Goal, Deliverables, Deadlines and Open Questions. Use only the notes. Write ‘not agreed’ if a deadline is missing. Don’t add commitments.” If you would still have to reread the entire call transcript to trust the result, test a shorter input or a narrower task before putting it into use.

Seed a mistake before the pilot

I give the assistant two fictional notes: “The owner prefers June” and “Launch date pending.” In the brief, June belongs under preferences; it is not an agreed deadline. I try the same test with a quoted budget and a spending ceiling. If the draft merges either pair, I change the headings before testing with another team member.

Decide what stays manual

My handoff has three columns: draft, source and reviewer. A colleague should be able to point to the sentence behind each price or promise. I keep sending the client email outside the automation. If nobody is available to check it, the draft waits. That boundary matters more to me than how polished the first version sounds.

Read next: Website launch checklist: The five-minute smoke test All articles

Display & accessibility

Adjust this site for the way you read and navigate.

Accessibility