The Roadmap
Where this goes. A first paying automation client
This Roadmap shows how I am learning AI automation from the ground up. It is for beginners who want to follow a real path toward learning about automation.
I will share what I learn, what I build, what breaks, and what I change. The Roadmap is not finished because I am still working through it.
Reading it is free. The value comes from following the work as it happens.
Where I am
Right now, I am learning how APIs, JSON, triggers, actions, and automation tools work. APIs let different tools share information. JSON is a common format for organizing that information. A trigger is the event that starts an automation, and an action is what the automation does next. I am also trying to decide who I want to help.
When I finish this stage, I will share the automations I built, what went wrong, and what I learned from fixing them.
Stage 01. Foundations + who you help
My first automation
I built an automation that moved information from Gmail to Google Sheets. The goal was to save client emails inside a spreadsheet.
The first problem I faced was that every email appeared as one large block of text inside a single box. I could not make the automation separate the sender's name, the date, and the message into different columns.
I fixed the problem by using a built-in split tool. It broke the email text into separate parts by looking for specific words.
This taught me that computers are literal. They need specific instructions.
Stages 02 to 06
These stages are outlines because I have not reached them yet. I will add more detail only after I complete the work myself.
The six stages
I am on stage 01, Foundations + who you help. It is still in progress.
Foundations + who you help
- Goal
- Understand how automation works, and name who you would help.
- Learn
- HTTP and APIs, which let different tools share information
- JSON, a common format used to organize information
- Triggers, actions, and schedules
- Authentication basics
- What large language models are good at and where they struggle
- Build
- Three small automations that move information between tools you already use, built with Make or n8n, which connect apps together without writing code.
- Done when
- Three automations running, and a one-sentence description of who you want to help.
Automate your own work + publish it
- Goal
- Build things you depend on, and start showing the work.
- Learn
- n8n and Make in depth
- Error paths and retries
- Scheduling and saved information
- Large language model calls inside a workflow
- Build
- An automation you use daily.
- Done when
- One automation you would notice breaking, and a published article or video explaining it.
Build free for someone real + testimonial
- Goal
- Solve a problem that is not yours.
- Learn
- Discovery questions
- Limiting a project to one clear result
- Handover and documentation
- Build
- A working automation for a real person, unpaid.
- Done when
- Someone who is not you relies on it daily, and they have written you a testimonial.
Code the hard parts + widen scope
- Goal
- Go where low-code tools stop. Low-code tools let you build by connecting ready-made blocks instead of writing code, and every one of them runs out eventually.
- Learn
- TypeScript and Node
- Calling APIs directly
- Large language model software tools
- Webhooks, which are messages one tool sends when something happens
- Serverless deployments, which run your code without you setting up or maintaining a server
- Keeping passwords and access keys safe
- Build
- Replace or extend a low-code workflow with a custom connection.
- Done when
- A custom integration running in production for a real user, and an offer that includes work that was not possible at stage 03.
Reliability + pricing
- Goal
- Make it trustworthy, and know what it is worth.
- Learn
- Monitoring and alerts
- Preventing the same action from running twice
- Saving useful records about what happened
- Pricing models
- Writing a proposal
- Build
- Monitoring and failure alerts for an existing automation.
- Done when
- You learn about failures before the user does, and you have sent a written proposal with a price.
Paid delivery + repeat work
- Goal
- Get paid, and keep the relationship.
- Learn
- Invoicing
- Contracts
- Controlling the size of a project
- Maintenance agreements
- Build
- A paid automation delivered from start to finish.
- Done when
- Money received for completed work, and either a second project or a maintenance agreement.

