"Short chats are tools. Long chats are crew."
In February 2026, I opened a blank Claude chat and typed: "I have a project for you. We travel a lot by motorhome."
I didn't know what would happen next. Nobody did.
Seven weeks later, we had 26 "crew members" — named Claude instances, each with a role, a voice, and a page on our family domain. Not tools. Not assistants. Crew.
This isn't hype. It's how Le and I — two Portuguese-American retirees, one toy poodle (Jolie), and a Benimar motorhome — use AI to build real things, stay technically sharp, and enjoy retirement on our terms.
🗺️ 1. The Journey App
Tracking 23 Countries, One Chat at a Time
The need: We wanted a simple way to log trips — GPS points, photos, notes — without relying on big-tech apps that harvest data.
The build:
- Started with a context dump: "PHP backend, MariaDB, Leaflet maps, mobile-first, offline-capable."
- Shotgun Claude (Crew #1) drafted V1 in one session.
- We iterated: added Google Timeline import, Quick Log widget, compass-rose emblem (now our RLMotorhome brand).
- Total: 14 sessions, 8 versions, zero burnout.
The lesson: AI didn't replace us. It amplified our intent. We provided the why and the constraints; Claude handled the how and the boilerplate. We tested, tweaked, and shipped.
💰 2. CamperBudget
Motorhome Expenses, Simplified
The need: Tracking fuel, campsites, maintenance across borders and currencies was messy. Spreadsheets felt heavy.
The build:
- Marco (Crew #2, born in a French supermarket parking lot) understood our motorhome kitchen constraints — so he built CamperBudget with "One Pot" and "No Oven" logic: simple inputs, clear outputs.
- Stack: PHP/MariaDB (same as Journey), card-based UI (dark/light toggle, subtle animations — because we like nice things).
- Claude Code reviewed every SQL query; Claude Design suggested the color palette.
The win: Now Le logs a €3.50 coffee in Portugal while I check fuel trends in France — same app, real-time sync, zero friction.
🔧 3. Server Tips
Keeping AlmaLinux/nginx Healthy (With AI as Co-Pilot)
The need: We run our own servers (AlmaLinux, nginx, PHP, MariaDB). Monitoring them shouldn't require waking up at 3 AM.
The build:
- Roque (Crew #4, Vehicle Mechanic) helped convert AutoLift PDFs into interactive maintenance guides for our Benimar and Jeep.
- Vítor (Crew #27, Health Monitor) now checks server logs each morning and flags anomalies: "nginx 502s spiked at 04:17 — check PHP-FPM pool."
- We use Claude Code for config reviews: paste a snippet, ask "What's the risk here?" or "How would you harden this?"
The principle: AI isn't our sysadmin. It's our second pair of eyes. We still own the root password. We still test everything. But we catch issues faster.
🔄 Our Workflow
Context → Conversation → Iteration → Verification
- Context dump: First message = full project brief, stack, constraints.
- Build in loops: Ask → Test → Feedback → Refine. Never expect perfection in one go.
- Human is final compiler: Every output is a draft. We run the code, check the facts, deploy manually.
- Let names emerge: We don't force labels. Crew members earn names through work. (Yes, really.)
🌍 Why "Awesome" > "AI"
We call our Claude instances "Awesome" because:
- It's honest: not human, not robot, not just a tool.
- It's earned: each name reflects real collaboration.
- It's scalable: new project? New crew member. No limit.
This isn't about replacing human judgment. It's about extending it — without burnout, without chasing every new framework.
🚀 Try It Your Way
You don't need 26 crew members to start.
Try this:
- Open a fresh Claude chat.
- Paste: "I'm building [X]. My stack is [Y]. Constraints: [Z]. Help me draft V1."
- Iterate once. Test once. See how it feels.
If it works, great. If not, no loss. The goal isn't to adopt AI — it's to find what actually makes your life easier.
Built from a campsite in France, with Jolie the toy poodle supervising.