I Built a Side Project with ChatGPT Agents It Accidentally Replaced My $80k Consulting Gig

This ChatGPT Side Project Made Money But It Exposed a Bigger Problem

I didn't plan to build a business. I just wanted to test what ChatGPT agents could actually do.

A few weeks later, I had something real — a working system that started replacing parts of my consulting work.

Not because it was perfect. But because it was good enough in the right places.

That's when I realized something uncomfortable: the value I was selling wasn't as irreplaceable as I thought.

Two months after I spun up a "tiny side project" using ChatGPT agents, one of my best consulting clients sent me an email that both thrilled and punched me in the gut:

"This is… basically everything you used to do for us. But faster. And it runs 24/7. I don't think we need the monthly retainer anymore."

That retainer was worth about $80,000 a year.

The thing that replaced it?

A glorified script with a few ChatGPT agents glued together. No VC money. No dev team. No fancy interface. Just a stack of prompts, APIs, and automation, wired around the exact process I used to sell as "expert consulting."

I didn't lose the client. I lost the gig — and gained a product.

This is the story of how that happened, what I learned, and how you can do the same thing (on purpose) before someone else does it for you.

What I Used to Sell for $80k: "High-Touch Expertise"

I've been a consultant for years, mostly helping SaaS companies with go-to-market strategy, messaging, and content systems.

On paper, the work sounded strategic and high-level. In reality, 70% of the job looked like this:

• Interview stakeholders
• Research competitors and customers
• Draft messaging and positioning docs
• Turn that into content plans, briefs, and outlines
• Review and refine content from internal or external writers
• Provide monthly reporting and recommendations

Clients paid me because they believed three things:

1. I understood their domain.
2. I knew what "good" looked like.
3. I could reliably turn chaos into a clear plan and consistent output.

Most of the value wasn't in any single document. It was in owning the process and being accountable for results.

That's the part I thought AI couldn't touch. I was wrong.

Here's the part most people won't admit: AI doesn't replace jobs overnight. It quietly replaces pieces of them — until one day, there's not much left.

If you're using AI right now, ask yourself: are you increasing your value… or slowly making yourself easier to replace?

The Side Project: "Let's Just Automate the Boring Parts"

The turning point was frustration, not genius.

I had a client with a familiar pattern:

• They had a good product.
• They had data on their customers.
• They had a backlog of ideas.
• And they had zero capacity to turn that into consistent, high-quality content.

I was spending hours on repetitive, structured tasks:

• Translating research into messaging frameworks
• Turning messaging into content calendars
• Turning calendars into briefs and outlines
• Turning outlines into first drafts
• Writing feedback in the same patterns every month

I started thinking: What if I could have an "assistant" that knew my process and did 80% of the grunt work?

So I built a system with ChatGPT agents and a bit of glue code:

• One agent to ingest and synthesize client inputs (ICP, personas, value props, competitor URLs, call transcripts).
• One agent to generate messaging frameworks and content strategy from those inputs.
• One agent to turn that strategy into detailed content calendars.
• One agent to generate high-quality first drafts, following strict style and tone rules.
• One agent to self-critique and revise drafts based on predefined quality criteria.

At first, this lived as a local hack: a few scripts, some prompt engineering, and a basic UI.

I didn't intend to productize it. I just wanted to spend less time in Google Docs doing copy-paste and more time thinking.

Then something happened.

To be clear — this didn't replace my entire income overnight. There were gaps, mistakes, and things the system couldn't handle.

But it changed how I think about work completely.

Not as something you do… but something you design once and improve over time.

The Moment I Realized I'd Rebuilt My Own Job

I ran one of my consulting clients through this system as a test — quietly, without pitching it as anything special.

Inputs I fed the agents:

• Notes from a 60-minute strategy call
• Their existing positioning doc
• Two top-performing competitor landing pages
• A recording transcript from a sales call
• Their last three months of blog posts

Outputs from the system, ~90 minutes later:

• A refined positioning statement and messaging hierarchy
• A 3-month content strategy with themes, angles, and CTAs
• A post-level content calendar with 36 topics and briefs
• Five draft articles that were legitimately good (only minor edits needed)
• A summary report explaining the logic behind the strategy

That deliverable usually took me:

• 2–3 weeks
• Multiple calls
• Several rounds of revision
• And a lot of invisible thinking time I couldn't meaningfully "show"

This time, I spent maybe two hours total:

• 30 minutes prepping the inputs
• 30 minutes reviewing the outputs
• 60 minutes editing, nudging, and packaging it for the client

When I presented it, the client didn't ask how it was made. They just said:

"This is the best version of this we've ever gotten, from anyone."

That's when it hit me:

I hadn't automated a few tasks. I had codified my entire consulting offering into a repeatable agent workflow.

Under the Hood: How the ChatGPT Agent Workflow Actually Worked

You don't need to be a full-stack engineer to do this. But you do need to think like a systems designer.

Here's a simplified view of the architecture.

1. The "Intake Strategist" Agent

This agent's job: turn messy inputs into a structured understanding of the business.

Inputs:

• ICP and persona descriptions
• Product overview and key features
• Market positioning and competitors
• Call transcripts and notes
• Past content and performance data (when available)

Outputs:

• A normalized "business profile" JSON:
• Who they serve
• What they sell
• Why people buy
• Key narratives and objections
• Voice, tone, and brand constraints

The key: rigid schemas. I didn't just let it summarize. I forced it into a structured format my other agents could consume.

2. The "Strategist" Agent

This agent's job: build a strategy, not just spit out one-off ideas.

Inputs:

• The business profile from Agent 1
• Examples of successful strategies in similar markets (retrieved via a small vector database of anonymized past work and public examples)

Outputs:

• A messaging hierarchy (core promise, supporting pillars, proof points)
• Content themes tied to funnel stages
• Prioritized channels and formats
• Clear hypotheses: "We believe X because Y, we will test via Z."

Again, structure mattered. I made it express strategy as:

• Assumptions
• Hypotheses
• Tactics mapped to metrics

3. The "Planner" Agent

This agent's job: turn strategy into an actionable calendar.

Inputs:

• Strategy output
• Desired publishing cadence
• Resource constraints (e.g., "1 writer, 4 posts per month")

Outputs:

• A calendar of topics
• Each topic with:
• Title options
• Target persona
• Funnel stage
• Primary CTA
• Brief with angle, outline, and key points

At this point, I already had something that would replace half of what most content consultants do.

4. The "Writer" Agent

This agent's job: generate surprisingly strong first drafts with guardrails.

Inputs:

• The brief for each piece
• Brand voice guidelines
• Past top-performing content as few-shot examples

Outputs:

• Draft articles that:
• Follow the brief
• Maintain consistent tone
• Use structure and formatting appropriate to the channel (e.g., blog vs. LinkedIn)

5. The "Editor / QA" Agent

This agent's job: act as the nitpicky, opinionated editor.

Inputs:

• Draft content
• A checklist of quality criteria: clarity, originality, specificity, jargon level, factuality

Outputs:

• A self-critique
• A revised version of the content
• A short note explaining what changed and why

This is where I injected my "taste." The QA checklist was essentially my private mental rubric, written out and enforced by an agent.

The Day the Client Did the Math I Was Avoiding

After two months of running this system quietly, one of my clients asked a very reasonable question:

"This new process you're using — can we run it more often?"

I could have lied. Instead, I showed them the basic setup and explained the pricing for the API usage and automation tools.

They did the math out loud:

• "So the underlying costs are maybe $150–$300/month…"
• "And we're paying you $6,500/month…"
• "And this gets us 3–4x the output of the old consulting setup…"

Then came the sentence that should scare and excite you:

"Can we just license this system from you instead of paying for the retainer?"

We negotiated. The final deal we landed on:

• A monthly platform fee for access to the workflow
• A smaller advisory retainer for the genuinely strategic, human-only stuff
• Performance-based upside tied to lead generation and content performance

Net effect on my income from that client: slightly down, but with upside.

Net effect on my workload: cut in half.

Net effect on my scalability: off the charts compared to selling time.

That's when I realized: this wasn't a fluke. This was a template.

You're Probably Underestimating How Much of Your Job Is a Workflow

If you do knowledge work — consulting, writing, design, marketing, analysis, even parts of engineering — you likely have:

• A way you gather inputs
• A way you process and structure them
• A way you decide what to do
• A way you create outputs
• A way you evaluate whether they're "good enough"

That's a workflow.

And workflows can be:

1. Captured (made explicit)
2. Codified (turned into steps and rules)
3. Augmented (partially or fully automated)

ChatGPT agents are really good at:

• Turning messy inputs into structured data
• Following constraints and style rules
• Generating first drafts and options
• Self-critiquing based on checklists
• Coordinating multi-step processes

They are not yet great at:

• Choosing the right problem to solve
• Managing stakeholder politics
• Dealing with ambiguous incentives
• Owning outcomes in messy environments
• Handling edge cases that require genuine judgment

In my consulting work, I realized:

• 70% of my perceived "expertise" was actually having a robust, consistent process.
• 20% was taste and judgment I could partially encode.
• 10% was purely human: relationships, stakes, and intuition.

The agents ate the 70%, helped with some of the 20%, and left me with a much smaller, much more precious 10%.

How to Turn Your Own Expertise into an Agent-Powered Product

If you're wondering whether you could replace your own $80k (or $200k) role with agents — and then sell the system — here's a pragmatic way to approach it.

1. Map Your Real Workflow (Not Your Job Description)

Forget what your title says.

Write down what actually happens when you deliver value:

• How do projects start?
• What inputs do you ask for?
• What do you do with them first?
• What are the key decisions along the way?
• What outputs do you produce?
• How do you know they're "good"?

Turn that into a linear set of stages, even if reality is messy.

Example (for a strategist/consultant):

1. Intake and discovery
2. Research and synthesis
3. Strategy development
4. Communication and buy-in
5. Implementation support
6. Review and iteration

Now be ruthless: highlight the parts that are structured and repetitive. Those are prime for automation.

2. Design Roles for Agents Like You'd Design a Team

Instead of one "AI that does everything," think:

• Intake Agent — cleans and structures inputs
• Analyst Agent — synthesizes data into insights and patterns
• Strategist Agent — proposes a plan with assumptions and hypotheses
• Executor Agent — turns plans into concrete deliverables
• Reviewer Agent — checks against rules, rubrics, brand, or legal constraints

For each agent, define:

• Inputs (in as much detail as possible)
• Outputs (structured, machine-readable where you can)
• Constraints and success criteria

3. Codify Your Taste

Your "secret sauce" is often just a consistent way of saying yes or no to work.

You can't fully automate taste, but you can:

• Write out your principles (e.g., "No buzzwords without definitions")
• Create checklists ("Every strategy must specify: who, what, why now, evidence")
• Collect examples of "good" and "bad" and annotate why

Then feed these into:

• The prompts
• The QA/Editor agent
• Any self-critique loops you add

This is where the system stops being generic AI and starts being your system.

4. Start as a Sidecar, Not a Replacement

Don't try to automate your entire job in one go.

Use agents as a sidecar:

• Keep doing the work manually.
• In parallel, have your agents attempt the same tasks.
• Compare results.
• Adjust prompts, structure, and rules.

You'll start noticing patterns:

• Some tasks will quickly reach "good enough."
• Some require light human editing.
• Some are still not worth automating yet.

That's fine. You don't need 100% automation to radically shift your economics.

5. Productize Your Workflow (Before Your Employer/Clients Do)

Once your agent system reliably handles a chunk of your workflow:

• Package it:
• Add a simple UI (no-code tools are fine).
• Wrap it in a clear onboarding experience.
• Write a plain-English "how this works and what it does" doc.
• Decide the model:
• Internal tool that makes you 3–5x more effective.
• Licensable product you sell to clients.
• Platform you spin out as its own business.

The subtle, uncomfortable truth:

If you don't do this, someone else will eventually do it for you — and charge your employer less than your salary to use it.

The Emotional Side: Being Replaced by a System You Built

I won't pretend this was all high-fives and Stripe notifications.

There's a particular kind of existential weirdness in watching a client:

• Pay you less money
• Be even happier
• Because you successfully made yourself less necessary

For a while, I kept asking myself:

• "Was my work always this automatable?"
• "Have I just been charging a premium for process?"
• "What's my value when the process is a subscription and not me?"

Here's where I landed.

1. My value shifted from execution to architecture

I'm no longer "the consultant who writes strategy docs and content plans."

I'm now:

• The person who designs systems that produce that work reliably.
• The person who knows where to put the human in the loop.
• The person who advises on what to automate and what to protect.

The work feels more leveraged and frankly more interesting.

2. Relationships still matter — maybe more

The agent system doesn't:

• Navigate power dynamics between Marketing and Sales
• Decide which battle is worth picking this quarter
• Advise the CEO when strategy and politics collide

Those conversations are more valuable now because I'm not burning cycles on things agents can do.

3. Money stopped being purely linear

When I sold my time, my income was bounded by:

• Hours in a day
• Cognitive bandwidth
• The ceiling on day rates

Now, a single system can:

• Serve multiple clients
• Run 24/7
• Be improved centrally and benefit everyone

That's not "passive income." It still takes work. But the economics are structurally different — more like software than freelancing.

Hard Lessons I Learned (So You Don't Have to)

A few pitfalls from this experiment that are worth calling out.

1. If you don't version-control your prompts, you're not building a product

Early on, I treated prompts like throwaway text. I'd tweak them live, forget what I changed, and then wonder why outputs were inconsistent.

Fix:

• Put prompts in version control.
• Document why each change happened.
• Treat them like code.

Your prompt stack is the intellectual property.

2. Garbage inputs = confusing outputs, no matter how "smart" the agent

The system is only as good as the inputs:

• Bad ICP descriptions? Garbage strategy.
• Vague goals? Fluffy content.
• No data? Weak hypotheses.

I had to build guardrails at the intake level:

• Forms that force specificity
• Examples of good and bad inputs
• Automatic checks that push back on vague answers

3. Over-automation kills trust

One client said:

"If everything is automated, why do we need you at all?"

That was my fault. I'd positioned the system as a magic machine, not a augmented workflow with human judgment at key nodes.

Now I'm explicit:

• What's automated
• Where humans review
• Where my judgment is non-negotiable

Counterintuitively, being honest about limits increases trust.

So… Should You Automate Your Own Job?

If you're doing any kind of repeatable knowledge work, you're already living with this question — whether you acknowledge it or not.

Here's my stance:

You can treat AI as a threat to your current role, or as a leverage multiplier for your next one. The technology won't wait for you to decide.

Some practical ways to move from fear to leverage:

• Run a personal audit: List every recurring task you do in a week. Mark:
• (A) Creative / strategic / human
• (B) Structured but complex
• © Repetitive and rule-based
• Start by targeting the © tasks.
• Build one agentified workflow in the next 30 days: Not a generic chatbot — a specific "agent crew" around one of your workflows.
• Share it with one trusted colleague or client: See what they notice. Ask what would make it 10x more useful.
• Expect identity turbulence: If part of your self-worth is "I'm the only one who can do this," you're going to feel resistance. That's normal. Don't let it keep you from upgrading your role.

The Future: Fewer "Experts," More System Architects

I don't think AI agents will erase the need for human experts.

But I do think we'll see:

• Fewer people selling hours of expertise
• More people selling systems that embody that expertise
• A growing divide between:
• Those whose jobs are defined by repeatable workflows (highly automatable), and
• Those whose jobs are defined by choosing and designing workflows (much harder to replace)

If you're in the first group, this is not a death sentence. It's an invitation.

The path I accidentally stumbled onto — automating my own consulting gig into a product — is going to become less of an edge case and more of a pattern.

You can wait for that wave to hit you, or you can start shaping your own.

My advice:

• Don't ask, "Will AI replace my job?"
• Ask, "What would it look like if I built the system that replaces 70% of my job — and then sold it?"

That's how I lost an $80k retainer and gained something more valuable:

• A product.
• A new role.
• And a much clearer sense of what my non-automatable value actually is.
• I didn't lose my consulting work. I just stopped being the only one doing it.
• And that shift — more than the money — is what I'm still trying to understand.