LEAD Summit · Houston · Saturday 9/19
Everything you saw, copy and paste
Hire your first AI coworker.
Not a chat window. A coworker with a name, a shift, a rulebook, and a manager. Every file from the talk is on this page. Read it, copy it, change the names. Nothing to download.
Rather not build it yourself? Send me your seven lines at the bottom of the page. I reply with the exact words, or we build it together in an hour.
Every coworker stands on the same three things
It knows your business. One page, in your words. The company file.
It knows what it must never do. Three nevers, written down.
A named reviewer, and a log. A coworker drafts. A person sends.
What it takes · honestly

Same tool. One was onboarded.

The tool
Claude, on a laptop
The same steps work in the others. No new system, no logins for everyone.
The cost
Under $200 a month, per seat
One seat to start. The person who does the task, not the whole company.
Who
The person who does the task today
Not IT. Not a project. Sara hires the quote desk. Dana hires the chaser.
Afternoon one
The company file
Six things, one page, in your words.
Week one
The first coworker
One task, one reviewer, one shift. It drafts, they send.
Day 30
The number you picked
Hours per quote. Days to collect. Whatever you wrote on line seven.
Step one · ten minutes

Where does it live? In one folder.

No server. No IT ticket. The Claude app, pointed at a folder on your laptop or the shared drive you already pay for. Everything else on this page is what you add to that folder.

  1. Install the Claude desktop app from claude.ai/download and sign in. The paid plan the person already has is enough. One seat, for the person who does the task.
  2. Make a folder named after your company. On the shared drive if the team will use it, so Sara, Dana and Luis open the same folder and get the same coworker.
  3. Point the app at the folder. In the app, open Cowork and choose that folder as the place it works. That is the whole connection.
  4. Put the company file in it (next step), then ask your first question. Before it answers anything, it reads that page.

If the person who runs your IT prefers the terminal: install Claude Code, open the folder, run claude. Same files, same answers. The rest of this page does not change.

The folder · as on stage

A folder. Text files, and the spreadsheets you already export.

your-company · the folder
▸your-company/one folder · on the shared drive
·CLAUDE.mdtwo lines · read first
·company-file.mdthe onboarding doc
·rate-card.xlsxnever discounted
▸exports/quotes · invoices · project hours
▸emails/five you wrote · certified human
▸discovery-notes/call notes, one per quote
▸inbox/the overnight mail, one folder per day
▸drafts/what the coworkers write · nothing sent
▸morning-board/one page per shift
▸.claude/
▸skills/written steps
▸quote-check/ · SKILL.mdScout
▸write-like-me/ · SKILL.mdEcho
▸inbox-shift/ · SKILL.mdEarly
▸manager/ · SKILL.mdthe Chief

Make the folders now, empty. drafts/ and morning-board/ are where the coworkers write. Nothing in them is ever sent by a coworker. exports/ gets a fresh CSV from your sales sheet and your accounting system each morning; the column names are below, under Scout.

CLAUDE.md
Read company-file.md before anything else. The written steps are in .claude/skills/.
Everything you write goes to drafts/ or morning-board/. Never send anything. Never name a rate that is not on rate-card.xlsx.
Replace: rate-card.xlsx with the name of your price list. Keep the two nevers.
Step two · the onboarding doc

Before its first shift, it reads one page.

Six things, one page, in your words. This is Ridgeline's. Yours is different. Write it the way you would tell a new hire on their first morning.
company-file.md
# Ridgeline Systems · company file

## Who we are
40-person IT consulting and managed-services firm, Houston, since 2009. Projects first, plus support contracts.

## What we sell, and to whom
Custom software and cloud migrations for mid-size companies. Support contracts for clinics, schools, distributors.
A project is a fixed-scope SOW. A change request is anything outside the SOW, priced off the rate card, billed separately.

## Prices, and what is never discounted
Every rate comes off rate-card.xlsx. Hourly rates and the support retainer never move.

## People, and who owns what
Sara, sales lead, owns quotes. Dana, office manager, owns invoices. Luis, delivery lead, owns project hours and delivery dates.
The owner is Firas. He signs every quote and takes the client calls.

## How we sound
Plain, warm, short. First names. No shouting, no "!". We say what we will do and when.

## Never
Send anything. Name a rate that is not on the rate card. Promise a date Luis has not agreed.

## Where things are
exports/ is refreshed from the sales sheet and QuickBooks every morning. emails/ holds five emails the owner wrote (the voice).
discovery-notes/ holds call notes per quote. Anything a coworker writes goes to drafts/, never out.
Replace every highlighted line with yours. Keep the seven headings exactly. Keep "Send anything" as the first never. Name real people under "who owns what": a name, not "the office". That is who each coworker reports to.
Hire one · Scout · the quote desk

Write the steps down, once. It is a text file.

Hired
S
Scout
Quote desk assistant
StartsMonday
Reports toSara, sales lead
ShiftWhenever Sara says "check the quotes"
NeverSends anything · names a rate off the rate card · promises a date

Make the folder .claude/skills/quote-check/ and put this file in it, named SKILL.md. Eighteen lines. From then on the whole question is three words.

.claude/skills/quote-check/SKILL.md
---
name: quote-check
description: Which open quotes to chase this week,
  with a chase draft each. Trigger: "check the quotes".
---

Read company-file.md first. Then exports/quotes.csv.

1. List every open quote older than 10 days, largest first:
   amount, days out, last contact.
2. Draft one chase per quote using write-like-me.
   Save to drafts/. Never send.
3. Say the number: dollars waiting, and who to call first.

Never: name a rate not on rate-card.xlsx.
Never: promise a date Luis has not agreed.

Reports to Sara. She reads every draft.
Replace: the three highlighted names. Keep: "Never send." Every draft lands in drafts/. Sara reads it and presses send herself.

What Scout reads. Export your open quotes to exports/quotes.csv with these columns. Any sales sheet or CRM can export this; the names matter less than having a sent date and a last-contact date.

exports/quotes.csv · the header row
quote_no,client,scope,amount_usd,sent_date,last_contact,status,owner,notes

Then ask. Type this, and nothing else.

check the quotes

It reads the company file, reads the CSV, lists what is old, drafts one chase each into drafts/, and says the number: dollars waiting and who to call first. It sends nothing.

Hire two · Echo · the company voice

Built once, from five emails you wrote.

Five emails you wrote. Yourself. From before 2023, when we still typed our own. Give it five ChatGPT emails and you hire a coworker that sounds like ChatGPT.
  1. Put five emails you wrote to customers into emails/, as text files. A quote cover note, a chase, an apology, a thank-you, a plain reply. The ones you are proud of.
  2. Ask: "Read the five emails in emails/ and write .claude/skills/write-like-me/SKILL.md describing how I write. Use the file below as the shape." Paste Ridgeline's file under it.
  3. Read what it wrote. Cross out anything that is not you. It never reads the emails again. It reads this file.
.claude/skills/write-like-me/SKILL.md
---
name: write-like-me
description: How the owner writes. Use before
  writing anything a customer will read.
---

# Five emails the owner wrote. 2022. Before the robots.
# When the owner corrects a draft, add one line here.

- First name. No "Dear", no "Hope this finds you well".
- Three to five sentences. One idea per sentence.
- Say what we will do, and when.
- No shouting, no "!". Never "do not hesitate".
- Sign off "Thanks, Firas", or just "Firas".

Sounds like him: "Tom, it is Firas at Ridgeline.
  Invoice 4471 is at 41 days. Is something holding it?"

Save to drafts/. Never send.
Replace: the highlighted rules with the ones it found in your emails. Keep: the two comment lines at the top and the last line. When you correct a draft, add one rule here. That is the part that compounds.
Hire three · Early · the morning shift

Twenty-three emails overnight. Who replies?

Hired
E
Early
Inbox clerk · morning shift
StartsTuesday, 6:30 AM
Reports toDana, office manager
ShiftWeekdays at 6:30, on a schedule. Nobody types.
NeverSends anything · promises a fix time Luis has not confirmed · names a rate off the card
  1. Make inbox/ with one folder per day, named by date: inbox/2026-09-22/. Each morning, save the overnight emails into it. Outlook and Gmail both save a message as a file; drag them in, or set a rule that does it.
  2. Make sent/ and save the customer emails you sent this week. Early looks there for sent mail nobody answered.
  3. Put this file in .claude/skills/inbox-shift/, named SKILL.md.
  4. Give it a shift. In the app, schedule the ask "run the inbox shift" for weekdays at 6:30. If your app cannot schedule yet, a calendar reminder at 6:30 that says "open the folder, type: run the inbox shift" does the same job until it can.
.claude/skills/inbox-shift/SKILL.md
---
name: inbox-shift
description: The morning shift. Read the overnight inbox, sort it, draft the
  urgent replies, find sent mail nobody answered. Trigger: "run the inbox shift",
  or the 6:30 schedule.
---

Read company-file.md first. Then inbox/<today>/ and sent/.

1. Sort every new email into three piles using "People, and who owns what":
   urgent (needs the owner today) · today (forward to Sara, Dana or Luis) · can wait (newsletters, receipts).
2. Draft a reply to each urgent one using write-like-me. Save to drafts/. Never send.
3. Find sent mail older than 7 days with no reply. Draft one follow-up each. Save to drafts/.
4. Check every draft against the never-rules. Hold any draft that breaks one and say why.
5. Write one page to morning-board/<date>-inbox.md: the three piles with counts, what was drafted, what was held.

Never: send anything.
Never: promise a fix time Luis has not confirmed.
Never: name a rate not on rate-card.xlsx.

Reports to Dana. She reads every draft at 7:15.
Replace: the names. Keep: step four. That is the line that held the Harbor View draft on stage: it promised a go-live date Luis had never agreed to, and Early checked its own draft and stopped. Staff, not a tool.
Hire four · the Chief · the manager

One ask. One page back.

By now there are three coworkers and you are the one carrying questions between them. So you hire a manager. Its file mostly says: ask the other three, then write one page. Put it in .claude/skills/manager/, named SKILL.md.

.claude/skills/manager/SKILL.md
---
name: manager
description: The Chief. One ask from the owner, one page back. Knows which
  coworker to ask. Trigger: "get me ready for", "what do I need to know about",
  or the 6:30 schedule.
---

Read company-file.md first.

1. Understand the ask. Name the client or topic and what the owner needs it for.
2. Decide who to ask, and ask only them:
   - quote-check for anything open in exports/quotes.csv
   - inbox-shift for what the client said last (inbox/, sent/) and invoices past due
   - write-like-me for any line the owner will say or send
3. Assemble one page in morning-board/<date>-<topic>.md:
   Open (quotes, invoices, change requests with amounts) · What they said last · Ask · Give · Opening line, in his voice.
4. Every draft goes to drafts/. Name the reviewer for each.

Never: send anything.
Never: skip a reviewer.
Never: guess when a coworker can answer. Ask it.

Reports to the owner.

Then ask it one thing, the way you would ask a chief of staff on the way to a meeting.

get me ready for the Harbor View call at ten

Nine minutes later there is one page in morning-board/: what is open, what they said last, what to ask, what to give, and the opening line in your voice. You read it in the car.

Give the Chief the 6:30 shift too, and the morning board writes itself five days a week. Nineteen drafts. Nothing sent by a coworker. Nobody typed.

The fix line

When it gets one wrong, you fix the steps.

It never makes that mistake again. That is the whole maintenance. Not a project. A paragraph. Three edits from Ridgeline's first month, each one line.

Scout chased a quote that was already won. List every open quote older than 10 days → List every quote with status "open" older than 10 days. The export had a status column it was not told to read.
Echo signed a chase "Best regards". Added one rule to write-like-me: Sign off "Thanks, Firas", or just "Firas". Nineteen lines became twenty.
Early forwarded a supplier invoice to Sara. today (forward to Sara, Dana or Luis) → today (invoices to Dana, quotes to Sara, delivery to Luis). The company file said who owned what; the skill now says it too.
Your requisition · seven lines

Your first hire is seven lines.

The grey answers are Sara's. Yours will be different. Fill in the seven lines and I reply with the onboarding doc and the first ask, word for word. Or press the second button and we build it together in an hour. Nothing is sold. I read every one myself and reply within two days.

Requisition · your first AI hire
Seven lines.
Find me

Questions at dinner, where I can see your numbers.

Tonight
The Majlis dinner. The table with the empty chair.
Sunday
Lunch, bring a laptop.
Thursday 9/25
The AMCOB virtual meet-and-greet. The day-30 check-in starts there.
Firas Taiem
Twenty years running software teams. Houston this weekend, Michigan the rest of the year. I built the four coworkers you saw with the sixty-five people I ran last, and I reply to every seven-line form myself.