This website uses cookies

Read our Privacy policy and Terms of use for more information.

We were busy. Then we weren't.

I've run Growth Forge Studio long enough to know the cycle well.

A stretch of good work comes in. Clients are happy. The team is heads-down delivering. Revenue is solid and the phone is still ringing. For a while, it feels like everything is working exactly the way it's supposed to.

Then one day you look up and the calendar is quiet.

Not because we did bad work. Because while we were doing great work, we stopped feeding the pipeline. Proposals sat. Social posting got inconsistent. Follow-ups fell off. Our own marketing — the thing we literally do for other businesses — got pushed aside while we took care of everyone else's.

The feast-to-famine flip. If you've owned a service business for more than a year, you know exactly what I'm describing.

For a long time our answer was simple: drop everything except client work. Clients first, always. That part was right. But "drop everything" also included the systems that kept new work coming in and every time things slowed down, we were essentially starting over.

The shift came when we stopped trying to find more time and started using AI to remove the thinking required to do the things we kept skipping.

Here's what that looked like in practice.

Proposals

We used to let incoming requests pile up when things got busy. By the time we had bandwidth to respond, the moment had passed.

The problem wasn't effort. Every proposal started from zero: blank page, scope, pricing, wording, formatting. That takes a cleared afternoon. Cleared afternoons don't exist during busy stretches.

We sat down with Claude and walked through every service we offer, every common variation, and every question clients typically ask. We built a simple service menu with base descriptions and custom options already written. Then we built a proposal template where the variables were clear and the boilerplate was done.

Now when a request comes in, we're filling in specifics, not writing from scratch. The thinking happened once. The system runs every time after that.

If you want to do this for your business, start here:

Prompt:
"I own a [type of business]. Here are the services I offer most often: [list them]. Help me write a simple service menu with a one-paragraph description for each, the most common variations or add-ons, and a standard response I can send when someone asks about pricing."

Do that once. Update it twice a year. Stop starting from scratch.

Social Media

The content was never really the problem. We had plenty to say. The problem was the decision: what to post, when, who handles it, where the files are.

Every time we sat down to post, we were making four decisions before we made one piece of content.

That's what made it easy to skip.

We used AI to remove the decisions.

We fed Claude a description of our business, our audience, the four content themes we rotate through, and a batch of past posts that had performed well. We asked it to build a 30-day content framework, not finished posts, but a calendar of angles, themes, and prompts that told us exactly what to make each week.

Then we built a simple file system. Past project photos organized by type. Video clips sorted by topic. When it's time to post, we're choosing from what's already there.

One session with AI to build the framework. One afternoon to organize the files. Now the weekly decision is almost eliminated.

Try this:

Prompt:
"I run a [type of business]. My four content themes are [list them]. Here are some examples of posts that performed well for me: [paste 3–5]. Build me a 4-week content calendar with a specific angle or post idea for each week, alternating between the themes. Keep it practical — things I can shoot on my phone or write from experience."

You don't need a content team. You need a plan that already exists when Monday comes.

Website and Ongoing Content

This one took us the longest to systematize because it felt the most optional. The website doesn't demand anything from you. It just sits there, quietly getting more stale.

What changed was building a capture habit. A simple checklist of what to grab from every active project. Not a production. Three photos of the work in progress. One note about the problem we solved. A sentence the client said that was worth keeping.

That's it. That's the input.

We then built a simple AI workflow around it. Drop the notes and photos into a prompt, get a draft blog post, a Google Business Profile update, and two or three social captions, all from the same project, all in one session.

Most businesses already have enough content. They just don't have a system for capturing it while the work is happening.

Here's the prompt that does most of the work:

Prompt:
"Here are my notes from a recent client project: [paste notes — what you did, what problem you solved, anything the client said]. Write me: (1) a short blog post for a local service business website, 200–300 words, focused on the problem we solved and why it matters to local customers, (2) a Google Business Profile update, 2–3 sentences, and (3) two social media captions for Facebook and Instagram."

Run that after every project. Three months from now your site looks like a business that's actually working.

We still put clients first. That hasn't changed.

What changed is that "clients first" no longer means our own business goes dark until the work slows down. The systems keep running. The pipeline keeps moving. And when the busy season ends, we're not starting over.

AI didn't suddenly make us disciplined.

It removed enough friction that the important things finally kept happening.

— Ryan
AI-Fueled Growth

Reply

Avatar

or to participate

Keep Reading