Every week without AI
is a week your competitors are pulling ahead.
This isn’t a “learn at your own pace” situation. The gap between teams that use AI and teams that don’t is compounding right now. Not in 2 years. Now.
Build Your First
AI Agent.
One weekend — Sep 11–13, Fri to Sun in Austin. Walk out Sunday with a working agent running on your own data. No time off work, no boss to ask.
Two more weekends. Same promise.
Hands-on, small group, led by a MakerSquare co-founder. Every workshop ends with a working system built on your own work — demoed live on Day 3.
For founders, operators, and product people who want AI doing real work for them. You pick a problem from your own work on Day 1. You spend 3 days building an agent that solves it. You demo it live on Day 3.
- Your first agent — a personal digest that finds what you care about — running on a schedule by end of Day 1
- An agent working your real data — email, docs, sheets — through Composio
- The judgment that matters: when a problem needs an agent, and when a simple automation wins
- A working agent solving your actual problem, demoed on Day 3
For operators and business owners whose week is eaten by recurring work. Three days automating it: meeting notes that file themselves, reports that assemble from live data, documents read and extracted, inbox triage — taught by the co-founder who runs a live AI ops command center inside his own company.
- Your most repetitive workflow, automated by end of Day 1
- Documents — invoices, forms, transcripts — extracted to structured data
- A weekly report that writes itself from your live sources
- Everything running on your real accounts, demoed on Day 3
For founders and owners who’ve been waiting for a technical co-founder. Describe it, build it, ship it: three days from idea to a live app with a real database behind it — the “vibe coding” skill everyone’s talking about, done properly with production tools. Last workshop before the January cohort — attendees get $200 off the 2-week program.
- Your app live on a real URL by end of Day 1
- A real database behind it — live forms writing real rows, with the safety rules that keep your data yours
- Day 3: polish, your own product decisions, and a live demo
- The skill that compounds: you can keep shipping after you leave
Pick a workshop.
See exactly what your three days look like.
- ✓What an agent actually is: a goal, tools, and a loop — taught visually, so it clicks
- ✓The ladder: when you need an agent, when a simple automation wins — run on your problem before lunch
- ✓Build the Personal Scout: an agent that searches, judges, and emails you a digest
- ✓Deploy it on a schedule — it runs itself every Monday, long after the workshop
- ✓Break it on purpose — and learn to read why an agent decided badly
- ✓Flowchart your real task — trigger, steps, decision points — confirmed 1:1 with the instructor
- ✓Build the core on your real data and tools from minute one — no toy data
- ✓Spot-checks and visible reasoning, so you can trust what it tells you
- ✓Access without the keys: least privilege, drafts-not-sends, and prompt injection shown live
- ✓Memory between runs — so it never sends you the same thing twice
- ✓From “works when I run it” to “runs without me”
- ✓Wire it to where it lives: a schedule, a button, or straight into your inbox, Slack, or sheets
- ✓Know what it costs to run — real numbers, no surprises
- ✓A runbook you wrote — so when it breaks in three weeks, you know where to look
- ✓Demo it live to the room — and explain the loop in your own words
- ✓The recurring-work audit: your actual week on paper, every repeating task ranked by hours × dread
- ✓What to automate and what to leave alone — the boring middle is the target; the judgment stays yours
- ✓Connect your real accounts — safely
- ✓Build automation #1 from the top of your list — running before you leave
- ✓The review step: it drafts, you approve — until it’s earned autonomy
- ✓Read a pile — invoices, forms, transcripts — and get clean, structured records
- ✓The matching problem: connecting what it reads to records you already have — where the time always goes
- ✓When the extraction is wrong — and how you catch it before it matters
- ✓Meeting notes that file themselves
- ✓The weekly report, assembled from your live sources
- ✓Put it all on a schedule — the work happens whether you’re there or not
- ✓When it breaks — and it will: reading what went wrong
- ✓What it costs to run — real numbers
- ✓Show your work: demo the full system live to the room
- ✓Decide what you’re actually building — cut it to what ships in three days, pick its one job
- ✓Something people visit, or something you work in — picking the simpler side, deliberately
- ✓Write the real content first — real words, not lorem ipsum, so it never reads as a template
- ✓Build it in plain English: one change at a time, be specific
- ✓Deployed to a live URL before you leave
- ✓The aha: your app remembers — live forms writing real rows
- ✓Why a database and not a spreadsheet
- ✓The tiny bit of SQL you’ll ever need
- ✓The data-safety rules you leave with
- ✓See it back: live data flowing through your own product
- ✓Polish where it counts — the details users actually notice
- ✓Your product decisions: what’s in, what waits
- ✓Handle the ugly cases — empty states, bad input, missing data
- ✓What it costs, and what to do when it breaks
- ✓Keep shipping after you leave — then demo your live app to the room
Every day ends with something running — and Day 3 always ends with you demoing it live to the room.
701 Brazos St, Downtown Austin — the center of Austin’s startup world, the same building where our Demo Days run. Doors 8:30am, we start at 9 sharp. Parking garages and street parking nearby.
A painful, repeating task from your actual work — and the real data it runs on. That’s what you build on from Day 1. No coding background needed: you’ll be working in the terminal before lunch, even if you’ve never opened one. The week before, we send a ~90-minute guided setup — you arrive connected, so Day 1 is all building.
“Just getting over the barrier of using Claude Code through a terminal was worth the time and expense.”
Ted Kilgore · Cohort 1, on LinkedIn
“The most valuable part was building the base — then taking that base to build the agent.”
Cameron Dowd · built his agent at MakerSquare, Cohort 1
You’ve tried tutorials.
This is different.
The reason people finish AI courses and still can’t build anything: they learned on fake data with fake problems. We don’t do that.
Earlier is cheaper. Same seats, same instructor.
Price is based on when you register, not who you are. No negotiating — just book the early bird before it closes.
Workshop Seats
Open to individuals and companies. Buy multiple seats at the same tier — no special process needed.
Invoice available on request. Email hello@makersquare.ai for PO-based payment.
Private Team Session
Your team only. Your dates. Content adapted to your tools and use cases.
Email hello@makersquare.ai — proposal within 24 hours.
Want to train your whole team?
Same 3-day curriculum, built around your team’s tools, industry, and specific use cases. You pick the topic. You pick the dates. We bring the instructor and the curriculum to you — in Austin or on-site.
Questions people ask before booking.
The 2-week MakerSquare program is the full build — 3 complete AI products, shipped and presented at a public Demo Day in Austin. Workshop alumni get $200 off with code WORKSHOP200.
See the 2-week programBuild Your First AI Agent — Sep 11–13.
$999 early bird closes Aug 21.
Small cohort. After Aug 19 it’s $1,199. After it sells out, it’s gone. 3 days in Austin — you leave with a working AI agent that runs without you.