Our AI stack layer by layer, the nine decisions we run Redwater on, and a checklist of jobs AI can take in each part of a local service business. Hand the folder to Claude and it interviews you about your tools, writes the rules you pick into your AI's rulebook, and helps you choose the first job to hand off. Made in Lake Charles, Louisiana.
Whatever you sell, the work falls into the same four buckets, and each one is a string of small steps. Here's what AI can take in each one, and where a person still checks: wherever a price, a promise, or a relationship is on the line.
You record a short video or a voice memo. AI cuts it, captions it, and drafts the titles, posts, and review replies in your voice.
A new lead lands in one place and pings your phone. AI files your walkthrough notes and drafts the quote from your template.
AI drafts the crew schedule, the materials list, and the updates to your customer, and files the job photos.
Bank and card charges sync in, and AI sorts each one into a category. A routine labels and files the inbox several times a day. It never sends and never deletes.
What to automate first. Ask two questions about every job: how often does it happen, and how much is each one worth? High volume and low value goes first: reminders, follow-ups, data entry, and sorting the inbox. High volume and high value gets an AI draft and a person's check: quotes, proposals, and replies to customers. Big decisions, key relationships, and hiring stay yours. The download turns this into a checklist and a worksheet for your business.
Every tool on our stack passed one test: can our AI read it and work with it? The download explains each layer and suggests a simpler pick for a local business.
Claude reads and drafts across every tool below. We talk to it instead of typing, and Wispr Flow records our meetings, with permission.
Every note and rule lives in one folder on our computers, and in one private shared copy we both edit. If a laptop dies, nothing gets lost.
The screens, the database and logins, and the jobs that run on a schedule. They're the same three we build client apps on, because AI builds well on them and a client can keep them.
Every proposal carries its own payment link, so the deposit comes in when the client signs. We built it so AI sorts bank and card charges into categories, and our CPA gets clean books.
Email and calendar, team chat and alerts, the emails our apps send, and social posts that go out only after Nick approves them.
Software we built on the layers above, because nothing off the shelf fit how we work. Every lead, client, and request lands in one place and pings both our phones.
Some we chose on day one. Others came from a mistake we made once and wrote down. The download tells the story behind each one and gives you a line to paste into your AI's rulebook.
The download is a folder of plain text files. Your AI reads them, asks about your business a few questions at a time, and writes your own versions.
Unzip it and open the folder in Claude Code. The Claude desktop app's Code tab is the easiest way in. You can also upload the files to a Claude chat. Then type:
The setup file tells your AI to read and draft only. Nothing it connects gets the right to send, delete, or pay, and it shouldn't ask you for a password. No rulebook for your AI yet? Start with our AI memory setup, which builds one with you.
We're two brothers in Lake Charles who build AI tools for local businesses, and we run Redwater on the same tools. This is how we do it, written so a tree service, a roofer, an electrician, a cleaner, or a contractor can use it. Your AI rewrites the checklist in your trade's words, so it works wherever you are.
It pairs with our AI memory setup, which gives your AI a rulebook and notes on your business. Want to see what we build for paying clients? Look through our work.
Yes. No card and no trial. The files are yours to keep and change.
No. The download is a folder of plain text files. Your AI reads them and asks you questions in plain English, a few at a time. You answer, and you approve everything it writes.
A computer and a Claude account. Claude Code comes with the paid Claude plans, and the Claude desktop app's Code tab is the easiest way in. You can also upload the files to a regular Claude chat. If your AI doesn't have a rulebook yet, start with our AI memory setup.
No. The stack file shows what we use and why, then suggests a simpler pick for a local business at each layer. The test we held every tool to is the one that matters: can your AI read it and work with it? Keep the software you like and connect the rest to it.
Not on its own. The setup file tells your AI to read and draft only. If you choose to connect a tool, it starts read-only and you sign in yourself. Nothing gets the right to send, delete, or pay, and your AI shouldn't ask for a password in the chat.
The jobs that happen all day and aren't worth your time each time: reminders, follow-ups, data entry, and sorting the inbox. The worksheet in the download scores your jobs on value and volume and helps you pick one.
Yes. We're based in Lake Charles and build this kind of thing into local businesses. Book an AI audit and we'll tell you honestly whether it's worth it for you.
Start with an AI audit. We'll walk through how your business runs, bucket by bucket, and show you where AI would save you the most time. You keep the roadmap either way.
Book your AI audit →