Content studio

Most software tries to solve people problems by adding more rules. This electrical shop reminded me the smallest fix usually wins. Small residential jobs were finishing without anyone collecting, once or twice a week. One idea was to have the owner approve every excuse from his phone. He killed it fast. If his techs are waiting on him to hit a button, he's the new bottleneck. It didn't need a pile of extra steps. Just that little bit of friction of accountability. Now a tech can't close a job without collecting or picking a reason from a short list, and the owner still sees every reason.

An owner buying custom software named his biggest worry: a shop that can build anything will say yes to every question. The same owner later killed a feature idea on the spot, and that no made his build better.

So a manager from an inspection company reaches out. Different plants want their repair numbering to work opposite ways. Then he asks the real question underneath. Can his team flip that themselves, or does every new plant preference mean emailing us and waiting? That's fair to ask any vendor, custom or not. Which changes can you make yourself? Which ones need a ticket? He put that in writing before the next plant even asked for something different.

An electrical contractor asked us what happens if they ever want to run the system themselves. Basically, what if they fire us. He got the answer before he finished asking. They can host it, keep their domain, and keep their accounting system. He seemed surprised that was even an option. A lot of owners are stuck with a vendor who made leaving hard on purpose. If we can hold your business hostage, that's not morally right. So every account gets set up in the owner's name. Now he knows the door's open.

This tree service guy shows me his crew sheet situation. When someone accepted a job, he'd duplicate the estimate, then manually delete every price. Had to do it that way because anything typed on the estimate goes straight to the customer's copy. No place for internal notes, you know? They literally developed coded abbreviations and symbols that meant something to the team but the customer would just see random letters. After all, the customer doesn't need to know all the random logistical stuff. Now the work order builds itself the second the customer signs, and internal notes stay hidden from them.

So there's this inspection company I work with. They fly crews in two weeks before a plant shutdown. A big chunk of that window went to building tracking spreadsheets from scratch, every single job. Nobody questioned it. That's just what getting ready looked like. The work that's always been done the same way is usually where the hours are hiding. Now the scope imports straight into their app, and setup takes about two hours. The manager made a joke about his own customers: "We don't need to let them know that we can do it in about two hours."

So there's this supervisor at an inspection company. Same question keeps coming up in meetings. Out of all the equipment, how many initial inspections are done? Hard deadline too. His answer came from standing at a wall chart, reading it by eye. Most of them, except these two. What he needed was one sentence. Out of 162, deadline's tomorrow, we got 145 done. That's what a dashboard is for. Now that count just sits on his screen. He reads it off instead of counting the wall.

Most owners I talk to, they just lead with a job title. I need a secretary. I need a bookkeeper. I need a sales guy. Here's the thing though. AI doesn't work at the job title level, it works at the steps. Answer the phone. Figure out who called and what they want. Route it to the right person. Follow up. So before you post that job or buy some tool, grab a legal pad and write down what this person does all day. Step by step. Some of those steps need a human. Some don't. The list tells you which ones.

When you say you need help up front, you're asking for five different jobs. Some of them need a person and some of them don't. Here's how I break it down before anybody buys a tool.

Most owners try AI in a chat window, get a decent answer, and decide it's overrated. That's level one. In this video I walk through all three levels: what AI does on its own, what it does when it's wired into the email and CRM you already use, and what a full system looks like when one lead comes in and nobody touches it until the callback.

We closed a build a while back, and only afterward caught that the data it would hold came with strict federal privacy rules. Big miss on me. I asked questions up front. Lots of them. But I took the answers and just moved on instead of doing my own research. The person across the table knows their business. It's my job to know the rules for what I'm building. We caught it before anything went live and built it the compliant way. Cost us time and a ton of stress. Here's the thing. Asking isn't diligence. Now I research the rules before a proposal ever goes out.

One of my favorite clients got a starter price from me. Problem is, they're not a starter company. Didn't do my homework before the call. Didn't pull up the website, no quick search, nothing. Priced it off the conversation and my gut, and my gut guessed small. They're a great client and I'm stoked we work together. The miss was on me. Ten minutes of research would've shown me the real size of the job before I quoted anything. Research the company first. Then talk price.

On one of my first freelance jobs, things started breaking, I didn't know how to fix them, and I stopped checking. A month later I got a three-star review for poor communication, and I earned it. A quiet client is not permission to stop looking.

Early on I took a build that was supposed to take three weeks. Five weeks later I was still in it, with no deposit and no clear finish line. Every week the picture of the finished product grew a little. That wasn't the client's fault. I never pinned it down, so there was nothing to measure it against. So I made a list of my own misses. Scope. Early feedback. Payment. And the big one, I never defined what done looked like. That's the rule now. Half up front, and a written definition of done both sides agree to before any build starts.

Early on, my brother and I kept scope loose on purpose. Tell us your dream outcome, we'll figure out what that means as we go. Worked for a bit. We closed some deals, learned what local owners want, found out what we're good at. But that's a bad way to run a business. When done isn't written down, nobody knows when you're finished. You don't either. So now done is a checklist. The client reads it and approves it before we start building. Every box checked? We're done.

Found a bug in an app we built. A salesman uploaded photos to an estimate, and every line item edit he'd just made got wiped. He had to go back out and re-quote the whole job. He didn't mind that much, and he still likes the app. But that shouldn't happen. The fix wasn't complicated. If you're building custom apps or dashboards, have some sort of autosave. Now every screen where people type real work saves as they go.

At [event name] this week, someone across the table asked me: [the question, paraphrased]. It's a good question. [One sentence on the worry underneath it.] Here's how I answered. [Two or three sentences. If it was which workflow to start with: the one that makes you sigh. The most pain is where the payoff is.] So on Monday, [the one thing an owner should do differently because of this].

At [event name], someone asked me if AI is going to take their people's jobs. [Their exact angle, paraphrased, if it was different.] Here's the thing: not if you do it right. The person already sitting in your office knows your business and your customers. That took years. You can't just hire that. What you want is one person getting through the work of five without working five times harder. We work with an electrical contractor, and he put it roughly like this: almost nothing changes for the guys in the vans, but a lot changes for the office. Better tools for the people you trust. Nobody gets fired. That's it.

At [event name], someone stopped the talk to ask about the ethics of AI: [their question, paraphrased]. Here's the car comparison I gave, and why the tool itself has no morality.

Every week at my referral group, each of us gets about 60 seconds to say who we are, what we do and what kind of referral we want. This week I said: [paste your 60-second intro, word for word]. And I asked for one thing: [the one kind of referral you asked for]. Not anyone with a business. [Why that kind of business, this week.] A narrow ask is easier to act on. When people can picture exactly who you mean, they can think of a name.

At the end of every talk I give, I ask the same thing, word for word: "Who runs a group or organization that would benefit from hearing this? Can you make an email introduction?" I don't ask who they know. That question's too big. People just go blank. So after [event name] this week, that ask turned into [real number of introductions, including zero]. [One line on what came of it, or what you'd change.] Here's the thing though. It works the same with your own people. Ask for something specific and someone can act on it. Ask for something vague? You get a nod and nothing else.

Went to my first local referral group back in late April. Wasn't feeling ready, honestly. Didn't think my offer was that solid either. Seven out of twenty people came up after. We swapped contact info and booked three meetings before the day was done. I'd been grinding on applications online for months. One room of real people beat all of it. This week I was at [this week's group or event]. [One line on how it went.] The lesson's the same though. Show up before you feel ready.

A tree and land clearing company here in South Louisiana was running on the owner's memory, his phone and a whiteboard. To make a crew sheet, he'd duplicate the accepted estimate and zero out every price by hand. Testing our first build on his phone, he typed out what he wanted: always know what step a customer is in once they call. So that's what we built. Work orders that create themselves when a customer signs, the schedule and the invoices, all in one place. Per customer, estimate to invoice went from about 4 hours down to 20 minutes. Now he knows what step every customer is in.

This is the talk I give in local rooms around Lake Charles, start to finish. Workflow thinking over role thinking, why nobody needs to get fired, three demos that climb from capability to connection to system, and one piece of homework for Monday.

A tree and land clearing company in South Louisiana ran everything from the owner's head, his phone and a whiteboard. This is the whole build: the problem, the spec he typed on his own phone, the system, what broke in testing, and how estimate to invoice went from about 4 hours down to 20 minutes per customer.

I'm Nick Rougeau. My brother and I run Redwater Revenue out of the Lake Charles and Lafayette area. I lead the building side. Custom CRMs, dashboards and automations, the software a local business runs its day on. Tree services, electricians, inspection crews. Most of our clients come from rooms, not ads. Talks, local events, and people who know somebody we've built for. This feed is field notes. What we're building, what went wrong, faith, and what tools should and shouldn't do for your people. If we met at an event, say hi here.

When I talk to local business owners about AI, it's always the same fear. People getting fired. Everything feeling fake. So I lead with this: I have no intention of getting people fired, destroying the earth, or ruining society. AI is a tool, I'd love you to use it responsibly. Then I draw a comparison to the car. It expands on the gift of movement you've got naturally. If you never move, you get obese, not good. AI expands on productivity, creativity, and intelligence. If you castrate that human gift, not good. In either case, the tool just is. It's got no morality. Up to the user. That's how we build. People keep their jobs and get better tools. What's one part of your week you'd hand off?

People talk about kids like they're gonna kill your life. No freedom. No ambition. Forget travel. I don't buy it. I got to be part of God's creative work and help bring a brand new, eternal soul into the world. That's not a burden. That's the coolest thing I've ever been part of. So on our last trip, he came up the trails with me. Out of 25.1 trail miles, I carried him for 20.9. Your kids don't end your life. They're the best part of it.

Someone stopped me mid-talk to ask about the morals of AI, and I compared it to a car. A car can extend your natural gift of movement, just like AI extends productivity, creativity and intelligence. You can also end up ceasing all movement, get obese, and die 10 years earlier, just like you can castrate your humanity by outsourcing everything to AI. The tool just is. Whether it grows the gift or shrinks it is up to you.

When I get up in front of a room to talk about AI, I don't lead with what it can do. I lead with what I won't do with it. I have no intention of getting people fired, destroying the earth, or ruining society. AI is a tool, and I'd love for you to use it responsibly. First time I did that, you could feel the room just relax. People stopped bracing and started asking real questions about their business. Here's the thing. Owners need to hear where the line is before they hear about the tool. Once they know it, they can listen.

I met with someone local who'd been told their own domain couldn't be moved. It can. It always can. It just takes someone willing to walk you through it. Here's the thing though. If a vendor can hold your business hostage, that's not a tech problem anymore. It's a moral one. You should own your domain, your accounts and your data. In your name. And you should know exactly how you'd leave any vendor you work with, including me. Can't say who owns what? Find out this week. It's your business. Keep it that way.

Led a trip recently. Midway through, something came up I couldn't fix. I'm keeping the details private, but here's what it taught me. You're not the main character. Bad stuff happens to you and the people you love, and sometimes no amount of skill or prep changes that. At all. As a husband, a father, a friend, and the guy leading the group, I had to sit with that. Then do what I could, when I could, anyway. Control was never mine. Showing up for the people in front of me was.

Carried my son up almost every trail on our last trip. Had someone else's 20 pound pack on me for 3.2 of those miles too. I'll be honest, my ego loved it. Had to check that. Being stronger, faster, or more capable doesn't put you at the top. It puts you at the bottom. You get the honor of serving everyone in the group. So get stronger. Get smarter. Max your stats. Then use all of it to carry more for the people next to you.

"I'm a detective trying to piece together a crime scene of what is going on." That is an electrical contractor describing how he finds out what happened in his own business last week. He has a calendar and a general idea. Everything else gets reconstructed by hand, job by job, after the fact. He was not complaining about software. He was describing memory as a business system.

Tree service we work with had no work order for the crew. So they made one out of the customer's estimate. They'd duplicate the accepted estimate and zero out every price by hand. Had to be a copy, because anything you type on the estimate shows up on the customer's side too. Their software was built for the salesman. Nobody had the crew in mind when they built it. Now the work order builds itself the second the customer signs, with notes only the crew sees and no prices on it.

A plant wants to know how many repairs were damage versus normal wear. They bill another contractor based on that number. Here's how it gets made. A man scrolls through the repair log and counts rows by hand. Out of 105, there's 27. That number goes in a report. Money moves because of it. Not a formula. Not a report. A person counting.

An inspection company we work with did the same setup for 8 years. They'd copy the last job's folder, copy thousands of rows of spreadsheets, then retype everything by hand until it matched a new plant. It didn't feel clunky in the moment... That's just what setting up a job looked like. Now they import the scope of work, and the wallcharts, spreadsheets, to-do lists and inspection progress are all right there. No more 1200 row shared spreadsheets

When someone tells me AI writes flat copy, I think about a real estate office I met with. An agent's listing copy for a pricey dining room came out flat. She'd asked the tool to describe an elegant dining room. The broker typed her own ask into the same tool, same minute, and described how the room should make someone feel and what the reader should do next. The agent read both and asked why the broker's was so much better. Same tool. Same minute. The difference was how they asked.

Met an owner once who told me why he was nervous about hiring a software guy. It wasn't the price. He'd asked his last web vendor for an emergency services button, because he was starting to push emergency tree removal. The vendor told him he was the professional and he'd handle it. The owner's take: maybe he tried to make me feel inferior, like I was an idiot, just because I wanted to make a simple change. I think about that a lot. He wasn't difficult. He got talked down to, and it stuck with him. Now he asks for a change, and it gets made.

A landscaping owner I talked with gets calls from software companies every other day wanting to demo him. His answer: "I don't have time to sit down and do it. And I don't want to." He's right. A demo asks you to change how you work, and his truck is his office. He doesn't have an afternoon to learn somebody else's system. So we watched how he already works and built around that. The software fits his day, and he didn't have to change anything.

A roofing company we're working with sends work orders to its crews on WhatsApp. Not because they love group chats. Adding crews to their software costs extra per seat, so they're not on it. Someone copies every work order into the chat by hand instead. They're paying for a system. The crews are working out of a text thread. Now every crew member's on the new software. No per-seat costs when you own it.

If your best estimator went back to paper, he's not the issue. At a roofing company we're working with, the salesmen skip the tablet. Too many steps, too many screens. Even the owner would rather write it out by hand. That's not people refusing to change. That's software nobody wants to open. So we're building estimates they'll open, on the device they're already carrying.

A tree service owner was spending his mornings typing accepted estimates into a spreadsheet, just so the job existed somewhere. He knew what that time was worth. His words: "I can make myself a lot more money by going out and meeting with people and bidding on bigger jobs." The retyping wasn't hard. It just ate the hours he sells. Now accepted estimates land in the app on their own, and his mornings go to bidding instead of retyping.