A map of your own week
Your recurring work, sorted on paper into three columns: what an agent could carry now, what still needs your judgment, and what should never be touched at all.
A working lunch for business owners · New Braunfels, Texas
Two hours, one table, twelve owners. You leave knowing the two or three places an AI agent would genuinely change your week — and the places it would quietly cost you money, time, or a client.
Twelve seats, first come. Registration opens shortly — joining the list holds your place in line, takes no payment, and commits you to nothing.
Why now
You are not short on AI tools. You are short on a way to decide. The demos all work. What arrives six weeks later is an assistant nobody checks, wired into systems nobody scoped, doing work nobody can audit.
It ran correctly for six weeks. Then it ran correctly on the wrong record, and a person had to make the apology.
A vendor moved a button. Nothing errored, nothing alerted, nothing ran. The gap only showed up in the numbers.
Setup took an afternoon because it was handed the keys to everything. The blast radius outlives the convenience.
A month of follow-ups that were never sent, to leads who assumed you were not interested.
Built in a weekend, checked twice a day ever since. That is not leverage. That is a second job.
None of these are software failures.
Every one is a scoping decision made too early.
What you leave with
Your recurring work, sorted on paper into three columns: what an agent could carry now, what still needs your judgment, and what should never be touched at all.
What agents genuinely do well at your size today, with examples from businesses like yours — and the exact point where the impressive demos quietly stop working.
What to ask any vendor — us included — before you spend a dollar or a weekend. Enough to tell a careful build from an expensive gamble.
You take the paper home: the Map Your Week worksheet, the Doing It Right checklist, and the five questions card. Nothing else. It should stay short enough to actually get referred to.
One real job, start to finish
Not a chatbot answering a question. This is a scoped follow-up agent at a six-person roofing company, running its weekly job — every step it takes, everything it refuses to touch, and the exact moment it hands the work back to a person.
Hi Dana, You asked us to look at the roof after the hail came through on April 2nd, and we never got you on the calendar. That one is on us. If it is still on your list, I can have someone out Tuesday or Thursday morning. It takes about forty minutes and there is no charge for the look. If you have already had it handled, just say so and I will close it out. You will not hear from us again about it. — Marcus, Hill Country Roofing
Written from the note this lead actually left. Not a template with a name swapped in.
It runs on a timer at 4:00 pm every Friday. It cannot decide to run itself, and it cannot run early.
Any tool can write seventeen emails. What makes this one safe to leave running is everything it was never given: no send permission, no ability to edit a record, no guessing when two leads share a phone number.
Scoping that second column is the work. It is most of what the two hours are about, and it is the part almost nobody does before they wire something into their business.
Register interestThe session
Twelve owners, name cards with business names, and a whiteboard that fills up with your actual work. The instructor sits with the group, not in front of it.
Everyone names their business and the one task they would hand off tomorrow. It goes on the whiteboard, and that list becomes the spine of the whole session.
Chatbots answer. Agents act. Instructions, access, and memory in plain language — then a live build on something someone in the room just said. Deliberately unglamorous.
Four categories, one concrete example each, sized for a business with one to twenty people. Then we sort the room’s whiteboard list into them, live.
Food arrives. Fifteen minutes alone with the worksheet, then a go-round: you read your top item out loud and get a straight answer about it. This is the part people come back for.
Five failure modes, each tied to something actually said at the table. Then the checklist that prevents them: scoping, access boundaries, testing, monitoring, and a plan for the day it breaks.
Narrow scope, low risk, visible payoff, thirty days to earn trust. Everyone circles one item and says their first project out loud, which is how it stops being theoretical.
A recap, and one offer: a free thirty-minute audit built from your own worksheet, if you want it. Then twenty minutes of the instructor staying put for the questions people ask privately.
When & where
The first session is Wednesday, October 14. After that it runs on the second Wednesday of the month — same room, same table, twelve seats each time.
Wednesday, 12:00 – 2:00 pm
Wednesday, 12:00 – 2:00 pm
Wednesday, 12:00 – 2:00 pm
Wednesday, 12:00 – 2:00 pm
Who it’s for
Twelve seats means every person gets individual attention and the demo runs on someone’s real problem. It also means the wrong twelve people would waste the room. So — plainly:
Who’s running it
Robert builds careful, useful systems for real work — the unglamorous kind that still has to be running correctly in month six, when nobody is watching it any more.
This class is a compressed version of how he scopes an actual project: what the thing is for, what it is allowed to touch, and how you would know if it broke. Same questions, two hours instead of two weeks.
He also sells the thing being taught, so it is worth saying the quiet part out loud: the session is built to be useful whether or not you ever hire anyone. You leave with the worksheet, the checklist and the questions — including the ones that would let you say no to him.
No borrowed logos, no invented credentials. The work is at rblurrr.cloud — judge it yourself.
Practical details
An interest list, for now. The date is set — Wednesday, October 14 — but online payment is not open yet, so nothing is charged and no seat is formally held. Joining the list puts you in order of arrival, and we confirm your seat directly before the room fills.
It covers lunch and it does filtering work. A free class fills with people who are curious but not deciding, which ruins the go-round for everyone who is. The fee is credited in full against any work you later do with us, so if you hire us it costs you nothing.
No, and it is not an advantage. The session is about deciding what work should be handed off and what it costs you to get that wrong. There is no code, no setup, and no jargon that goes unexplained.
There is one short live build, on a task somebody in the room names, so you can see what the work actually looks like. You will not leave with a running system, and that is deliberate — an agent built in two hours in front of an audience is exactly the kind nobody ends up trusting.
Not in the class, and not in the demo on this page. We start at drafts, boundaries and explicit human approval. Anything that can act without a person signing off is a later decision, made on purpose.
Bring one recurring task and a rough sense of who handles it today. Leave confidential customer data at home — we work from examples and shapes, never from your records.
There is one offer, it takes about ninety seconds, and it comes in the last ten minutes: a free thirty-minute audit if you want one. The other hundred and ten minutes are the class.
That is the target. Every example is sized for one to twenty people. Small businesses tend to get more out of a first agent than large ones, because the recurring work is concentrated in fewer hands — usually yours.
Register interest
Four questions is enough to get you on the list for . The optional ones let the instructor walk in with an example that is already about your business — that is the whole reason intake gets read beforehand.