Guided builds
Build something real, not a course
Each build gives you a problem worth solving, a plan, a testing checklist and proof for your profile.
Level 1 · Beginner
No code. Two to four hours. A first working automation and a first portfolio item in one evening.
Lead reply in one minute, with a score
Every form lead lands in a sheet with a score and a written reason, and the hot ones ping Slack.
Weekly ops report by email
Every Monday at eight the week's rows leave the sheet as a five-line report in your inbox.
Business FAQ assistant with no workflow tool
An assistant that answers only from your documents, names the section it used, and says when it does not know.
Review reply drafts with approval
Every review gets a drafted reply in the right tone, and nothing reaches the public page until a person clicks Approve.
Appointment reminders with confirmation
Every morning the diary sends tomorrow's patients a WhatsApp reminder, and their answer changes the calendar.
Content drafts from one idea sheet
One line of an idea becomes three finished drafts, and nothing reaches the posting queue until a person writes approved.
Level 2 · Intermediate
Integrations, APIs, retrieval and approvals. Four to eight hours. The builds businesses ask for most.
WhatsApp booking assistant
A customer books a real calendar hour over WhatsApp, and anything that is not a booking reaches a person instead.
Meeting notes to CRM
A finished call becomes a contact, a note on the timeline and a list of next steps, without anyone typing it up.
Document intake with validation
An invoice dropped into a folder is read, checked against five rules, and either filed by itself or sent to a person with the reason written out.
Order status and returns agent
Where is my order is answered from the shop's own data, a return inside the window is opened, and everything else reaches a person.
Support assistant on a help centre
A customer asks on WhatsApp, the answer comes back from the shop's own help-centre articles with the article named, and anything about money or anger reaches a person.
Internal knowledge assistant for a team
Anyone in the team types /ask in Slack and gets the answer from the company's own procedures with a link to the document, or a clear 'not in our documents, ask this person'.
Website lead assistant (chat widget)
A chat widget takes a name and an email, asks three qualifying questions, scores the visitor, replies in their own words and puts the lead in the CRM with the reasoning attached.
Level 3 · Advanced
Coded agents and deployed apps with Claude Code, Codex or Lovable. Eight to twenty hours. Portfolio pieces that stand out.
Agent evaluation harness
Forty cases with an agreed right answer, a script that runs them against a build you already made, a pass rate, and a GitHub Action that repeats it on every change.
Lead-scoring app with a dashboard
A public form anyone can fill in, a private dashboard only you can see, and a score with a written reason on every lead, decided on the server.
RAG assistant with citations, as code
A service you wrote yourself that answers questions from four pages of a business's own text, names the page it used, and says it cannot find the answer when the pages do not hold it.
Approval inbox with an audit log
A service any of your other builds can call when a person has to say yes: it posts the request to Slack with Approve and Reject controls, calls the caller back with the decision, and keeps a row saying who decided what and when.
An agent with tools for a real ops task
An agent that looks up contacts in the CRM, reads tomorrow's calendar and writes an email draft, with a ceiling on how many tools it may call, a list of what it may do at all, and a person who says yes before anything is kept.
Client results dashboard
A dashboard a client signs into and sees one number that matters, this month against a baseline, with a five-line note you write once a month and an email that sends it on the first.
Make it production-ready: a capstone on a build you finished
Take one automation you already built and give it what a paying client needs: an alert when it breaks, a retry when it can, a daily count of runs and failures with a cost line, and a page a second person can restart it from.