From the talk: Seguin Entrepreneur Club · Sep 1, 2026

Build your own personal OS

This is the actual recipe from the talk, not the demo version: the five automations you were promised, then the whole system behind the one page, level by level, from a free account tonight to a private dashboard with your name on it.

Bookmark this page; it’s the packet. If you weren’t at the talk, everything here still works.

The ladder · each level stands on its own

Start here · the five from the talk

The five automations

Exactly as promised: five you can start this week with a free claude.ai account, no code, no setup. Fill in the brackets, and read everything before it touches a customer. You are the last click.

01

Missed-call text-back

When you miss a call, get a text out fast so the lead doesn’t just call the next name on Google.

Then: Paste the three texts into your Notes app today. If your phone system or CRM can auto-text a missed call, drop the daytime and after-hours versions straight in.

I own [describe your business, e.g. "a residential plumbing company in Seguin, TX"]. When I miss a phone call, I want to text the caller back within a minute so they don't hang up and call a competitor. Write me 3 short text templates:
1. A missed-call text for daytime business hours.
2. A missed-call text for after-hours or weekends that sets clear expectations for when I'll call back.
3. A missed-call text for someone who's already a customer, versus a brand-new lead.

Keep each one under 300 characters, friendly and personal, not corporate. Use [Name] as a placeholder. End each with a simple next step (call back, text back, or visit my site).
02

Review requests, and replies that hold up

Ask happy customers for a review right after the job, and have a ready answer for whatever review actually shows up.

Then: Send the text version the next time you wrap a job. Save the replies in Notes so the next review notification never catches you staring at a blank box.

I own [your business type and city]. Write me:
PART A: 3 short review-request messages (one text, one email, one for a printed receipt/invoice) I can send a customer right after I finish a job, asking them to leave a Google review. Make them feel personal, not automated, with no corporate phrasing, no more than 2 to 3 sentences each. Include a placeholder for [Name] and [what we did for them].
PART B: 3 reply templates I can use when a review actually comes in: one for a genuinely glowing 5-star review, one for a lukewarm 3-star review that mentions something specific, and one for a 1-star review where the customer is upset. Keep every reply short, warm, and never defensive. The goal is to look good to the next person reading it, not to win the argument.
03

The front desk that never re-answers a question

Turn the ten questions you answer every week into ready answers your team or your website can use instantly.

Then: Paste the finished answers onto an FAQ page, or print them as a cheat sheet for whoever answers your phones. Same answer every time, in your voice.

I own [your business type and city]. Here are the questions customers ask me over and over (list as many as you have, rough is fine):
[paste your list, e.g. "Do you offer free estimates?" / "What areas do you service?" / "How fast can you get here?"]

For each one, write a clear, friendly answer in plain English: no jargon, 1 to 3 sentences, in the voice of a real person who knows the business, not a corporate FAQ page. Then group them into categories (pricing, scheduling, service area, etc.) and flag which 5 are the most important to have answered somewhere on my website.
04

Invoice reminders that don’t burn the relationship

Get paid faster without becoming the person everyone dreads hearing from.

Then: Most invoicing tools (QuickBooks, Square, Wave, Housecall Pro) can send these on a schedule. If yours can’t, three calendar reminders on day 0, day 7, and day 14 do the same job.

I own [your business type]. Write me a 3-step invoice reminder sequence for a customer who hasn't paid:
1. A friendly reminder sent the day the invoice is due.
2. A slightly firmer nudge for 7 days overdue.
3. A direct but still respectful message for 14 days overdue that makes clear next steps are needed.

Each one under 5 sentences, no threats, no legal language, no shame, just clear and professional. Use [Name], [Invoice #], and [Amount] as placeholders.
05

Quote follow-up, so silence stops costing you jobs

Turn the quotes you sent and never heard back on into booked work.

Then: Set three calendar reminders for every quote you send (day 2, day 7, day 14), or paste the sequence into your CRM’s follow-up automation.

I own [your business type]. I send quotes/estimates and often never hear back. Write me a 3-touch follow-up sequence to send after a quote, spread over about two weeks:
1. A check-in 2 to 3 days after sending the quote: low-pressure, "just making sure you got this."
2. A follow-up about a week later that adds one small piece of new value (answers a likely objection, offers to walk through the numbers, or mentions availability).
3. A final, brief message around day 14 that respectfully closes the loop: "still want this done, or should I close this out?"

Keep the tone warm and low-pressure throughout, never pushy, never salesy. Use [Name] and [Job/Project] as placeholders.

You now have: five working automations, and the habit that matters more than any of them: reading the draft before it goes out.

Level 1 · Tonight, on the couch · no code · ~20 minutes

Your first morning brief is tomorrow

The unlock at this level is a file: everything your assistant needs to know about your business, written down once, read every day. The difference between a chatbot and an employee is that the employee was onboarded.

Before you start, list every pane of glass you touch daily, just like in the talk: email, calendar, Google reviews, Facebook, the stats, the form fills. Keep it nearby; the interview will ask, and at Level 3 that list becomes the spec for your page.

Step 1: open Claude or ChatGPT.

Start a Project (Claude) or a custom GPT / persistent chat (ChatGPT) named after your business.

Step 2: don’t fill out a form. Get interviewed.

A blank template invites blank answers. Paste this instead and answer its questions like you’d answer a sharp new hire on day one. It writes the file for you, house rules included.

You are my new business assistant, and this is your onboarding
interview. Interview me about my business so you can write the file
you will work from every day. Rules for the interview:
- One question at a time. Short questions, plain language.
- Twelve questions at most. Skip anything I have already answered.
- When my answer names a customer, a lead, or a promise, dig one level
  deeper: what do I owe them, and by when?
- If I do not know a number, write "no data." Never estimate for me.

Cover: what the business sells and where; what only I can do; every
customer I owe something right now; every lead in play and its next
step; what a good month looks like in dollars; what is overdue; the
promises I would hate to drop; the fixed points of my week.

When the interview is done, output one file titled MY BUSINESS,
ending with these HOUSE RULES, word for word:
1. Never claim something you can't point to in this file or in what I
   paste you. If you don't know, say "no data."
2. Never draft anything as already done. Drafts say DRAFT.
3. You draft. I send. Never tell me to assume something was sent.
4. Dates: if I didn't give you the date, ask. Never guess a day of week.
Then tell me to paste the file into this project's instructions, and
ask me nothing else today.

Rather write it yourself? This is the file the interview produces. Fill in the brackets and paste it into the project’s instructions:

MY BUSINESS: the file my assistant reads first

Business: [name, what you sell, service area]
Me: [your name, what only you can do in this business]
Customers right now: [name, what you owe them, when]
Leads right now: [name, where it stands, next step]
Money: [what a good month looks like; what's overdue]
Promises I've made: [the things you'd hate to drop]
My week: [the fixed points: market days, school pickup, league night]

HOUSE RULES: not optional
1. Never claim something you can't point to in this file or in what I
   paste you. If you don't know, say "no data."
2. Never draft anything as already done. Drafts say DRAFT.
3. You draft. I send. Never tell me to assume something was sent.
4. Dates: if I didn't give you the date, ask. Never guess a day of week.

Step 3: every morning (or the night before), paste this.

Read MY BUSINESS. Give me today's brief:
1. NOTICED: one thing in what I've told you that deserves attention,
   with the reason (the receipt) stated.
2. TRENDING: one thing getting better or worse across the week.
3. THE MOVE: the single highest-value action for today, and draft
   whatever it needs (the email, the quote, the list). Mark it DRAFT.
Then: today's promises and fixed points, shortest list possible.
End with: one question you need answered to be smarter tomorrow.

Answer its question each day and it compounds. You’re not chatting. You’re running a standing meeting with an employee who never forgets what you told it.

You now have: an assistant that actually knows your business, and a morning brief whenever you ask for one.

Level 2 · This weekend · ~1 hour

It runs without you asking

Goal: the brief shows up on schedule instead of when you remember to ask. This is also where you graduate from the chat window to the terminal. The chat window can only talk, but Claude Code can read and write real files on your machine, and that difference is the whole level.

Claude: install Claude Code (claude.com/claude-code, included in the paid plan) on the computer where your files live. Make a folder for the business, save MY BUSINESS in it as my-business.md, and ask Claude Code in plain English: “Create a scheduled task that runs every weekday at 7 AM, reads my-business.md in this folder, writes today’s brief to brief.md using the house rules, and never sends or posts anything.” It sets the schedule itself.

ChatGPT: use Scheduled Tasks (in the app) with the Level-1 prompt as the task, or the same folder approach with their desktop tooling.

Add one evening task the same way: “At 8 PM, ask me what actually happened today, update my-business.md with facts only, and prep tomorrow’s brief.”

Now it briefs you at 7 and closes the books at 8. You approve; it remembers.

You now have: a standing 7 AM briefing and an 8 PM close-out, running on a machine you own, with nothing going out the door but drafts.

Level 3 · The build · a weekend, after two weeks at Level 2

One private page with your whole business on it

This is the level from the demo: the brief, your promises, your leads, your panes of glass, and your wins: one password-gated URL only you can see. You will not write a line of code. You will answer an interview and approve a build, which is exactly how the system you saw on stage was built.

Do Levels 1 to 2 for two weeks first. The dashboard is only as good as the files behind it, and two weeks of real briefs is what makes the files real.

Step 1: the accounts. All free, fifteen minutes total.

  • github.com

    Where the code lives. Vercel deploys straight from it. Sign up free; you will never have to read the code it holds.

  • vercel.com

    Turns your folder into a live private URL. The Hobby plan is free and is all you need. Sign up with your GitHub account so the two are already connected.

  • supabase.com

    A real database, for later. Skip it on day one. Your files are the database until they genuinely aren’t, and the build prompt below tells Claude to say so before reaching for it.

  • Claude Code

    Included in the paid Claude plan you already have. Download it at claude.com/claude-code and open it in a terminal. This is the tool the whole level runs on.

Step 2: the setup interview. This is the part everyone skips.

Open Claude Code in a new empty folder and paste this. It interviews you, then writes the three files that make every future session smart: the standing instructions, your business file, and your pane-of-glass list. The build reads these; that’s why it comes out as your system and not a template.

This folder is about to become my business operating system, and
you are setting it up. Interview me first, one question at a time,
fifteen questions at most:

- My business: what we sell, where, and who buys it.
- My panes of glass: every place I check every day (email, calendar,
  Google reviews, social, the bank, form fills, the job board). Get
  the complete list. This is the spec for everything you build.
- My rhythm: when I want the morning brief, when I close out the day,
  what a normal week looks like.
- My rails: what you may draft on your own, and what only I may send.
  Assume nothing leaves this machine without me.

Then, without further questions, write three files and show me all
three before doing anything else:
1. CLAUDE.md: the standing instructions for this folder: who I am,
   what this system is, my rails, and the house rules from
   rjdigitaltx.com/seguin/toolkit written in as law. Add one more
   rule: every number the dashboard shows must trace to a file in
   this folder.
2. my-business.md: everything from the interview, structured.
3. panes.md: my pane-of-glass list, one line each: what it is, what
   I check it for, and what "needs attention" looks like there.

These three files are the system. The dashboard is just the window.

Step 3: the build.

Read the three files it wrote. Fix anything wrong. That file is your employee’s brain, and this is the cheapest moment to correct it. Then paste this:

Read CLAUDE.md, my-business.md, and panes.md in this folder. Build
me a private, password-gated dashboard that puts my whole business
on one screen: today's brief on top, then promises and leads, then
one short section per pane from panes.md showing what I told you
"needs attention" looks like there, and a running wins list at the
bottom.

Next.js, deployable on the Vercel free tier. Storage: the markdown
files in this folder ARE the database. Do not add a real one until
the files genuinely can't do the job, and when that day comes, use
the Supabase free tier and tell me why before you touch it.

Then wire my rhythm from CLAUDE.md as scheduled tasks: the morning
brief written to brief.md, the evening close-out that asks me what
actually happened and updates my-business.md with facts only, and a
redeploy whenever the files change.

House rules apply to every pixel: the page only shows what the
files can prove.

Step 4: put it on the internet, behind a password.

Tell Claude Code: “Deploy this to Vercel and walk me through connecting my GitHub account as you go.” It handles the pieces and tells you when it needs a click from you. When the URL is live, test the password from your phone. That phone check is the moment this becomes real.

Cost check

~$20/mo
AI (already paying)
$0
Hosting
$0
Database
~$12/yr
Optional domain

That’s the whole bill.

You now have: one URL with your whole business on it, briefed at 7, closed out at 8, visible to exactly one person. The same shape as the system from the talk, because it is the same system.

The rules that make it safe

Tape this up. The AI isn’t the hard part. The rules are. Start with the rules.

  1. Receipts or it didn’t happen. Every claim traces to a real email, event, or number.

  2. It drafts. You send. Every time. No exceptions, ever.

  3. The calendar is the only truth for dates.

  4. “No data” beats a confident guess.

The living page

This page keeps growing

This packet is the system I actually run, scaled down to a weekend, and I keep building. New automations, deeper levels, and the ready-made starter app all land here, at this same address, as they’re finished. Bookmark the page and you have them. If you’d rather be told when something new lands, leave your email. No catch, no card, no sales call.

The gazebo in downtown Seguin glowing under string lights at night
Downtown Seguin

New here? The Seguin page has five more fixes you can make this week, and a free 60-second visibility check.