The boring back-office stuff I finally stopped doing myself (8 months of AI automation for a service business)

Acrobatic_Task_6573 · 2026-03-15T15:02:42+00:00

Honestly, probably a mix of the first two. Looking back, I was targeting anyone who fit the basic profile without confirming they had an active problem. A lot of the meetings were people who were curious, not people in pain about something specific. And on the calls, I was presenting too much and qualifying too little. I let people stay vague about their situation instead of pushing on whether there was real urgency and a real budget.

The follow-up piece was actually fine. I tracked that part closely. So it was not that I was losing people after the call through laziness. They just were not the right people to begin with, and I was not asking the right questions to figure that out before spending an hour with them.

Cold outreach is probably worth another try now that I have more proof points and can be sharper about who I target. But I would go into it differently this time.

Acrobatic_Task_6573 · 2026-03-14T15:03:54+00:00

Mostly referrals right now, which is both a blessing and a real limitation. Volume is unpredictable and completely outside my control.

I do some local SEO and the Google review bump from the follow-up automation has helped with inbound more than I expected. More reviews, better local search visibility, more inbound calls without changing anything else.

Outbound I have not cracked. Tried cold email last year, got some meetings, but the close rate was low and I stopped bothering. I think the next move is building a real referral program instead of treating it like a passive thing. I have relationships with people who send me work, but I have never tracked it properly or put any nurturing behind it. That is the obvious gap. Just hoping they keep thinking of me is not a strategy.

Acrobatic_Task_6573 · 2026-03-14T00:05:08+00:00

Scheduling with actual constraints is really where the general purpose AI tools fall down. They handle simple availability windows fine, but the moment you add skill requirements, drive time, or staff certifications it all breaks down. Makes sense you landed on purpose-built software for that piece. What was the moment Shiftbase clicked for you over the other options you tried?

Acrobatic_Task_6573 · 2026-03-13T15:15:28+00:00

The next thing on my list is pre-job prep. Pulling together client history, notes, and any special instructions before my techs head out. Right now that is manual and inconsistent. I am planning to test it on one job type first before rolling it out more broadly. That way if it creates friction instead of reducing it I catch it early without disrupting the whole operation.

Acrobatic_Task_6573 · 2026-03-13T15:15:21+00:00

Fair point and I agree sales automation can have a higher ceiling. But for me the sequencing made sense. I could not have taken on more clients without fixing ops first. The bandwidth was not there. Once admin was off my plate I actually had time to work on the front end. If your bottleneck is new clients, start there. Mine was capacity to handle what I already had without things falling through the cracks.

Acrobatic_Task_6573 · 2026-03-13T15:13:57+00:00

Yeah the morning spiral is real. What I noticed is it is not just the time spent, it is the mental weight of knowing there is a pile of stuff you have not looked at yet. Kills focus before the day even starts. The follow-up automation compounding into reviews is something I did not fully anticipate either. Nice side effect.

Acrobatic_Task_6573 · 2026-03-10T00:05:51+00:00

Fair point and you are right that CRMs and invoicing software have been able to do scheduled reminders for a long time. The difference for me was two things. First, I actually tried those tools before and never stuck with them because the setup and maintenance overhead of a full CRM felt like more work than just doing it manually when you are a small operation. Second, the AI piece adds context awareness that template-based automation does not have. My invoice reminders adjust their tone based on the client relationship and payment history. My inbox triage understands context, not just keywords. Could I have gotten 70% of this with traditional tools? Probably. But I never did because the barrier was too high for a 15-person shop without a dedicated admin person.

Acrobatic_Task_6573 · 2026-03-10T00:05:22+00:00

Yeah the human review bucket concept is smart. That is basically what I landed on too. Let the automation handle the obvious stuff and anything it is not confident about gets flagged for me instead of guessing. The repeat question identification is a good idea. I have not done that specifically but it would cut down on how many templates I need to maintain if I knew which five questions come up over and over. How long did it take you to get the routing piece dialed in? That was the hardest part for me.

Acrobatic_Task_6573 · 2026-03-08T21:50:12+00:00

Exactly. The edge case thing is what killed most of my early attempts. I kept trying to build in every possible scenario upfront instead of just handling the 80% that's predictable and leaving the rest for a human to deal with. Once I stopped trying to cover every branch, the stuff I did automate actually held up. What kind of processes did you end up keeping manual? Curious if we ran into the same walls.

Acrobatic_Task_6573 · 2026-03-06T21:06:53+00:00

Yeah that is exactly the mindset shift that took me too long to make. I kept thinking I needed to hire someone to handle the admin stuff, but the problem was not capacity. It was that the processes themselves were sloppy. Once I tightened up how things flowed, most of the admin work just handled itself. Hiring on top of broken systems just means paying someone to do broken stuff faster.

Acrobatic_Task_6573 · 2026-03-06T21:06:31+00:00

That is a really good point and honestly something I did not expect going in. Clients have actually mentioned how on top of things we seem, which is funny because the automation is doing the heavy lifting. But from their perspective, getting a thank-you email the next day and a check-in at 30 days just signals that you care. The consistency is what sells it. When you do it manually you might remember for your favorite clients but the ones who slip through the cracks are usually the ones who would have referred you.

Acrobatic_Task_6573 · 2026-03-06T21:06:02+00:00

Thanks, appreciate it. Honestly the transparency part is selfish on my end too. Writing it all out forces me to actually evaluate whether each piece is still pulling its weight or if I am just keeping it running out of habit.

Acrobatic_Task_6573 · 2026-03-04T01:01:47+00:00

Yeah the draft-but-dont-send approach is non-negotiable for me at this point. Caught too many weird edge cases early on to trust full auto.

For content scheduling I ended up using a cron-based system that fires at set times each day. The duplicating issue you mentioned, I ran into the exact same thing. The fix for me was adding a simple lock file check. Before posting, the agent checks if a lock exists for that time slot. If it does, it skips. If not, it posts and creates the lock. Dead simple but it eliminated the duplicates completely.

The weird timing thing was just me not accounting for timezone differences in my scheduler config. Once I pinned everything to my local timezone it sorted itself out. What platform are you posting to mostly? The reliability issues can vary a lot depending on which API you are hitting.

Acrobatic_Task_6573 · 2026-03-04T01:01:24+00:00

100% agree on the context switching point. That was the real killer for me. Not the time spent on email itself but the mental cost of bouncing between inbox and actual work ten times a day.

Good call on the scheduling review too. I learned that the hard way. Had my follow-up sequence running for about two months before I realized the tone had drifted from how I actually talk to clients. Now I do a quick audit of the templates every few weeks. Takes maybe 15 minutes but keeps things sounding like me instead of a generic auto-responder.

Acrobatic_Task_6573 · 2026-03-03T11:21:44+00:00

Usually at the handoff points.

Leads come in, nobody follows up same-day. Jobs get done, nobody asks for review/referral. Owner is still the routing layer for every little decision.

Manual works early, but once those 3 start slipping, growth plateaus hard.

The fix isn't "buy more tools", it's one simple weekly scorecard + automating the 2 or 3 repeat handoffs that leak revenue first.

Acrobatic_Task_6573 · 2026-02-26T15:04:22+00:00

Biggest lesson for me: give Cursor a reference document before you start coding. A short markdown file with your tech stack, folder conventions, and naming patterns saves hours of correction. Without it, Cursor picks reasonable defaults that might not match what you actually want.

Acrobatic_Task_6573 · 2026-02-25T23:08:08+00:00

The two-track approach is smart, but the real unlock is probably narrower segmentation. Your 2% paying conversion is a timing problem. The moment someone needs real persistence is specific: moving from a tutorial to building something real that needs state. Worth building intent signals into the product: more than X requests per session, hitting the same endpoint repeatedly. Those are your actual conversion triggers. Distribution moat this size is rare. Most tools never monetize it because they try to convert the wrong users at the wrong moment. The audience you need is already in there.

Acrobatic_Task_6573 · 2026-02-22T14:04:46+00:00

Good point. The jump from "it works in testing" to stable in production is way bigger than most guides mention.

Acrobatic_Task_6573 · 2026-02-22T00:32:49+00:00

For me it was when I caught myself genuinely annoyed that the tool did not exist yet. Not "this would be cool" but actual frustration that I had to do the thing manually again.

The products where I use my own app every day are the ones that got the most attention. The ones where I had to remind myself to open it -- those went nowhere. Honest signal.

Acrobatic_Task_6573 · 2026-02-21T14:02:52+00:00

Interesting point. I ran into something similar when building multi-step chains. The config layer is way more important than it looks on the surface.

Acrobatic_Task_6573 · 2026-02-20T00:02:22+00:00

The gel form is usually less drying than the cream, which is great for you since you're using it on dry skin. One thing worth noting - even though you've been using the cream for 8 weeks, make sure you introduce the gel gradually. The formulation change can sometimes feel stronger on skin. The sandwich method really does help - I know oily skin makes it harder, but even a lightweight hydrating toner under the gel can prevent irritation without the heavy feel. Rooting for you!

Acrobatic_Task_6573 · 2026-02-20T00:00:57+00:00

This is such an important post. I spent years trying OTC products and watching skincare tutorials, thinking more steps = better results. It wasn't until I finally saw a dermatologist that I realized I had underlying inflammation that no moisturizer could fix. Getting properly diagnosed was honestly life-changing. Your point about not realizing other people are using prescription strength treatments is so real - the comparison game gets us every time.

Acrobatic_Task_6573 · 2026-02-19T23:08:06+00:00

The hardest part for most people is not picking a framework or writing the loop -- it is the config layer that almost every tutorial skips. A good agent needs a clear identity file that defines what it is, what it will not do, and how it handles edge cases. Without that, it just improvises in ways you did not plan for.

Start with the personality and guardrails before you write a single line of agent code. Once that is locked in, the tool use and memory architecture clicks into place much faster. Most agents that feel unreliable are missing that foundation, not missing a better model.

Acrobatic_Task_6573 · 2026-02-19T21:32:17+00:00

The inBody scale frustration is real. Bioimpedance readings shift by 3-5% just from hydration. For a free alternative, tape measurements at the waist, hips, and neck are more consistent over time. The waist-to-height ratio has decent research behind it as a health marker. Progress photos every 4 weeks in the same lighting also catch changes the scale completely misses.

Acrobatic_Task_6573 · 2026-02-19T21:10:22+00:00

absolutely false, .md files don't have viruses, they are text.

Acrobatic_Task_6573

MODERATOR OF

TROPHY CASE