# AI tools: plan, compare, follow up

Free starter lesson from AI Superpower by Waymaker. Synthetic narration; fictional examples. Published November 7, 2026.

## Three practical tasks

Three practical tasks help you plan, compare, and follow up.

## Choose your result

Choose your result before choosing more software. An agent brief tells an implementer what should happen and where to stop. A fair comparison helps you decide which tool earns a place in your process. A follow-up decision keeps a quote visible without sending an automatic message. These lessons use fictional examples. Open the matching tools from the AI Superpower Launch Lab when you are ready to practice.

## Define the job

The agent's job should be small enough to check. In the Agent Launch Planner, the outcome is a weekly research brief. The trigger specifies the intended time and frequency. The inputs restrict the work to approved sources. The destination is a private draft. Entering a schedule in this planner does not activate a recurring job. It records the requirement for a later implementation.

## Set boundaries

The boundaries make the brief usable. The reviewer owns the decision to accept or revise the output. Approval is required before publishing or sending anything. The example limits give the implementer a spending ceiling and a retry rule; the planner itself does not enforce either. Quality criteria explain how the reviewer will check the result. Use role names and sample inputs, and leave passwords and confidential customer records out of the plan.

## Use the planner

Build, inspect, and keep is the practice sequence. Build my test plan creates the document after all eight fields are complete. Inspect the cases: a normal request, missing input, a duplicate trigger, an approval boundary, and a provider failure. Every case starts as not tested. Save or download keeps the work: a saved draft remains in that browser, while a download gives you a separate file. Pause here and build your own brief. Your deliverable is the plan, not a running agent.

## Set up a fair trial

A fair trial starts in the Tool Trial Lab. Choose one brief, such as turning fictional meeting notes into an action summary. Define the reference before seeing the answers: which decisions must appear, who owns each action, and which dates are actually present? Then use two candidates with the same input and requirements. If one tool gets extra context or more attempts, record that difference. The comparison should describe the work you actually did.

## Count review work

This fictional comparison shows why drafting speed alone can mislead. Candidate A produces a draft sooner, but an invented deadline adds checking and correction. Candidate B takes longer to draft and less time to review. The total is seven minutes instead of fourteen for this made-up case. No real product was benchmarked here. In your trial, record actual times, errors and corrections. For repeated use, also consider setup time, usage charges and how easily the output can be exported.

## Decide from evidence

Your decision applies to this task and the cases you tested. Keep a tool when its checked output meets the requirements at an acceptable cost. Revise when a specific input or instruction change may address the problem, then run the same cases again. Stop when errors or correction work outweigh the benefit. Download the report with the limitations included. Pause here and write your success criteria before trying another tool.

## Understand the next decision

An outstanding quote needs a decision before it needs another message. A customer may be waiting for an answer about access, timing or scope. The free Quote Follow-up Desk helps organize that review. It stores records in the browser and prepares drafts; it does not contact customers, synchronize a CRM or collect payment. Start with its fictional demo so you can learn the controls without using private records.

## Use the quote desk

Review one estimate all the way through. Explore the fictional demo and choose a record from the queue. Check contact preference before deciding whether outreach is appropriate. A quote's age is not permission to contact someone. Choose the next action, such as asking the estimator to confirm access requirements, and set a manual review date. Save the update so the reason is visible later. A review date is a prompt for a person to decide; it does not activate a notification or send a message.

## Know what the records mean

These records help with operations. Quoted value describes potential work and does not establish future income. Marked won records your update; confirm payments in the appropriate accounting or payment system. A full backup preserves the browser's records for later restoration. Browser storage can be cleared, and a local workspace is not a shared team database. Pause here: select one fictional quote, record a next action, and identify where you would keep an approved backup.

## Put it into practice

Choose one small next task. Practice for free in the AI Superpower Launch Lab and keep the brief, comparison or quote-review record you complete. Review the result: what is usable, what needs correction, and what still depends on a person? Get help when useful. A three-hundred-fifty-dollar working session can help with one agreed task; workflow setup starts at fifteen hundred dollars and requires a confirmed scope. The free tools and existing self-paced courses remain free. This lesson uses synthetic narration and fictional examples; it does not claim client results.

