Crew Agent
v0.1 · proof of concept
MORNING DISPATCH FOR CONSTRUCTION CREWS
CONCEPT MEMO Drafted from one 7-min call

Your builder app,
at 7am,
as a text to every crew.

Every GC has the data, every job, every subcontractor, every punch list, sitting in his builder app. The crews don't. Crew Agent is a background worker that reads the app at sunrise, splits the day per crew, and sends each worker one text with their schedule and punch list. No login. No app. Just a text.

Subject · File 01
Mike
Ridgeline Builders
14
Active jobs
23
Crew members
21s
Per dispatch
READS THE BUILDER APP DISPATCHES AT 7AM ONE TEXT PER WORKER PER-CREW PUNCH LISTS WEATHER-AWARE BILINGUAL EMAIL FALLBACK NO APP TO INSTALL READS THE BUILDER APP DISPATCHES AT 7AM ONE TEXT PER WORKER PER-CREW PUNCH LISTS WEATHER-AWARE BILINGUAL EMAIL FALLBACK NO APP TO INSTALL
01 / DISCONNECT
Two hours every morning, lost to a problem that's pure logistics.

The data is in.
The crews are out.

Today · without the agent

The owner is the bottleneck.

06:45Mike wakes up, opens the builder app on his phone.
07:10Scrolls through 14 active jobs trying to remember who's where.
07:30Calls Hernandez, "you're at the Larson kitchen today, 8 sharp."
07:45Three group texts. Two follow-up calls. One forgotten subcontractor.
08:30Two crews still asking "where am I today?"
09:15Day already behind. Punch list still on Mike's phone.
Tomorrow · with the agent

Mike is on his second coffee.

07:00Agent reads the app. Jobs, crews, punch lists, weather.
07:00Resolves conflicts. Splits the day by crew.
07:0023 personalized texts hit 23 phones in 17 seconds.
07:01Mike gets one summary: "Day dispatched. 14 jobs. 1 weather flag."
07:30Every crew knows where to go, what to bring, what's overdue.
08:00First nail goes in on time. Every site.
"
The schedule isn't broken. It's just stuck in one person's head, and that person also has to swing a hammer.
Notes from the call · May 21 · 14 min
02 / MECHANISM
Four moving parts. One sunrise. Runs unattended.

Four moving parts.
One sunrise.

DAILY DISPATCH · DATA FLOW REV. A · 21 MAY 2026
BUILDER APP 14 active jobs 8 crews · 23 workers Punch lists by job Subcontractor schedule Material deliveries READ CREW AGENT DAILY · 7AM 1 ── Read the app 3.0s 2 ── Reason · split by crew 8.0s 3 ── Draft 23 messages 5.0s 4 ── Dispatch via gateway 2.0s 5 ── File the daily brief ~18s · BACKGROUND SMS MAIL SMS GATEWAY A REAL PHONE NUMBER EMAIL FALLBACK ONLY 7:00 7:00 Runs in the background. No laptop to leave open, no app to babysit. The owner just gets a one-line summary.
A · DATA SOURCE

The builder app

Whichever app you already pay for. The agent reads it just like the owner does, faster, and without forgetting.

B · THE BRAIN

Crew Agent

Reasons over the data: who's qualified, who's free, what's overdue, what the weather says. Drafts one message per worker.

C · THE MOUTH

A real phone number

Sends and receives real texts from a dedicated number. Crews save it as a contact. No app, no login.

D · THE CREW

23 phones

Workers don't install anything. They get a text from "Mike, Crew Agent." They text back if they have questions.

03 / MORNING RUN
Click play to watch the agent dispatch the day in real time.

21 seconds,
every day.

TUESDAY · MAY 21 · 07:00:00 EST
SPECIMEN RUN
07:00:00
Wake up
Agent boots itself. No human needed.
07:00:03
Pull the data
14 jobs · 8 crews · 23 workers · 47 open punch items.
07:00:05
Check weather
Brickell: 76°, rain by 2pm. Coral Gables: clear. Doral: 80°.
07:00:08
Resolve conflicts
Hernandez double-booked. Patel moved to 12pm, drywall isn't dry till 11.
07:00:11
Draft 23 messages
One text per worker. Address, time, punch list, materials, language.
07:00:15
Send the texts
23 dispatched in parallel. 2 fall back to email.
07:00:17
Brief the owner
One summary text: jobs, flags, deliveries, overdue invoices.
07:00:21
Done
~90 minutes back. Every. Single. Morning.
AGENT.LOG · LIVE +00.00s
Messages
0
Crews
0
Runtime
0s
04 / DISPATCHES
Three actual messages from one morning's run. No app required.

What three workers
see at 7am.

CREW AMarco Hernandez · Lead Carpenter
7:005G · 78%
Mike, Crew Agent
(305) 555-0142
Tue, May 21 · 7:00 AM
Tuesday · May 21
Marco, you're at the Larson kitchen today.

📍 1487 Tigertail Ave, Coconut Grove
🕗 Start 8:00 AM (Frank + Luis with you)

Punch list
  • Upper cabinets (delivery 9am)
  • Baseboards south wall
  • Verify outlet behind island
Bring: impact driver, level, cabinet shims. ⚠ Rain 2pm, exterior trim first. Patel moved to 12pm.
Delivered · 7:00 AM
CREW A · ESLuis Martínez · Carpintero
7:004G · 64%
Mike, Crew Agent
(305) 555-0142
Mar, 21 may · 7:00
Martes · 21 de mayo
Luis, hoy estás con Marco en la cocina Larson.

📍 1487 Tigertail Ave, Coconut Grove
🕗 8:00 AM

Trabajo
  • Gabinetes superiores (llegan 9am)
  • Retoques en zócalos
Traer: taladro de impacto. ⚠ Lluvia a las 2pm.
Delivered · 7:00 AM

Auto-translated to each worker's preferred language. Set once.

OWNEROwner · Daily brief
7:005G · 91%
Crew Agent
(305) 555-0142
Tue, May 21 · 7:00 AM
☀ Daily brief
14 jobs · 23 crew dispatched.

1 flag: rain Brickell 2pm. Exterior trim earlier.
🔄 1 conflict resolved: Hernandez Patel→12pm.
📦 2 deliveries: Larson cabinets 9am, Patel tile 11am.
💸 Overdue: Reyes $8,400 · 12 days.

Reply STATUS for check-ins.
STATUS
09:32 check-in
✓ 8/8 crews on-site
✓ Larson cabinets delivered
⚠ Patel tile delivery 30min late Want me to ping the supplier?
Delivered · 9:32 AM

The owner texts the agent back at any time. It pulls fresh data and answers.

05 / THE ASK
Three things from the owner. About twenty minutes total.

Three things
from the owner.

01 / APP
1

Which builder app he uses

The name of it, plus an admin-level login so the agent can read the same things the owner reads.

02 / CREW
2

His crew list

Names, phone numbers, and which language each worker prefers to read in. One spreadsheet is plenty.

03 / MORNING
3

One typical morning

Twenty minutes on a call. The owner walks through what they do at 7am, what he forgets, what falls through.

From there it's a short build, a single-day pilot on your real schedule, and then it's running every morning before he's out of bed. The hard part isn't the code, it's getting the messages right for your crews. That's what the discovery call is for.

NEXT STEP

Find out which app
your team uses.

That's the one variable. Once we know that, we know whether we're talking two weeks or four. Everything else in this memo is already battle-tested infrastructure.

Email Georg →