← Field notesStrategy

How to make AI work for you in the next 30 days

Ryan Walker7 min readUpdated May 27, 2026

How to make AI work for you in the next 30 days

The people getting real results from AI are not smarter or more technical than you. They have a bias toward shipping. They pick one thing, run it, measure it, and move on. This 30-day framework gives you the same structure: four weeks, one task at a time, with a feedback loop built in from the start.

No tool shopping. No prompt libraries to browse. Just a repeatable process you can start this Monday.

Week 1 — Audit, do not add

Before you touch any AI tool, spend this week watching yourself work.

List every task you completed in the past five working days. Be specific: “wrote three client emails,” “reformatted the weekly report,” “pulled data from the CRM into a spreadsheet.” Then mark each one against three criteria:

  1. Repetitive — you do it more than once a week
  2. High-volume — it takes meaningful time in aggregate
  3. Rule-based — there is a right answer, or at least a clear standard

Tasks that hit all three are your AI candidates. Tasks that require judgment, relationship context, or creative originality are not — at least not yet.

Do not add any new tools this week. The audit is the work.

By Friday you should have a ranked shortlist. The top item is your Week 2 target.

Week 2 — Build one thing

Take the top candidate from your audit. Build the simplest possible prompt or agent for it. Not the best one — the simplest one that could plausibly work.

Then run it on five real pieces of work. Not test cases. Real ones.

Time yourself doing the task manually. Time yourself using the AI output. Write down the delta. If you saved 12 minutes per instance and you do this task 20 times a week, that is four hours. If you saved nothing, that is also useful data.

Do not expand scope this week. One task, five runs, one number.

Week 3 — Add the evaluation layer

This is the step most people skip, and it is why most AI workflows quietly degrade.

Without evaluation, you are shipping noise. The output looks plausible, you approve it, and over time your standards drift toward whatever the model produces.

Build a simple check: does the output meet your standard? Options include:

  • A checklist of five criteria the output must satisfy
  • A second prompt that reviews the first output and flags issues
  • A human spot-check on every fifth output

The form does not matter. What matters is that you have an explicit standard and a mechanism to catch drift. Run your Week 2 workflow through this evaluation layer. Fix the prompt where it fails. By the end of the week, you should have a workflow that produces acceptable output at least 80% of the time without manual correction.

Week 4 — Document and expand

Write down what works. Not in your head — in a document.

Record the prompt, the evaluation criteria, the workflow steps, and the time delta you measured in Week 2. This is your system. It is now repeatable by you, and eventually by someone else or another agent.

Now pick a second task from your Week 1 shortlist and repeat Weeks 2 and 3. You already know the process. The second cycle will be faster.

By the end of Week 4 you have two working AI workflows, both evaluated, both documented. That is a foundation — not a finished product, but something you can build on.

We send a monthly AI workflow template and prompt pack to Field Notes subscribers. Get it at avakata.agency/contact.html.

What this looks like at Avakata

We ran this exact process when building the engine.

Week 1: Audited every manual task in a client engagement. The highest-volume, most rule-based task was copy rewriting — taking raw product claims and reformatting them to match brand voice and SEO structure.

Week 2: Built a copy-rewrite agent for that task. Ran it on five real client briefs. Measured the time delta: 40 minutes of manual work reduced to 8 minutes of review.

Week 3: Added a critic gate — a second prompt that reviewed each output against a rubric of brand voice rules and flagged deviations. Output quality stabilized within the week.

Week 4: Documented the loop and expanded to GEO optimization — structuring content for AI citation, not just search ranking.

That was 18 months ago. The engine now runs 160+ agents across engineering, content, data, and client delivery. It started with one audit and one prompt.

If you want to run this process with support, we offer a short discovery call to map your highest-value AI candidates and build the first workflow together. Book a call at avakata.agency/contact.html.

Frequently asked questions

How long does it take to get real results from AI?
30 days if you ship. Most people spend 30 days evaluating tools and see no results. The ones who pick one task, build one prompt, run it on real work, and measure the output in week one are seeing time savings by week two. The variable is not the tool — it is the bias toward action.
What task should I automate with AI first?
The task that is repetitive, high-volume, and rule-based. For most solopreneurs that is content drafting, email responses, or social scheduling. Audit your last week of work, mark every task you did more than three times, and pick the one that took the most total time.
What is an evaluation layer and why does it matter?
An evaluation layer is a check that runs after AI generates output — before you ship it. It can be a checklist, a second prompt that reviews the first, or a human spot-check. Without it, you are shipping AI output without knowing if it meets your standard. Most AI failures in production are evaluation failures, not generation failures.

Related reading