What if the best proof that an AI automation platform works is to use it to launch itself?
That was the question we asked in March 2026. JieGou had just completed a rebrand, migrated to new infrastructure, and had a working product with one paying customer. We had 300+ recipes, 90+ workflows, 20 department packs, and 13 messaging channels. What we didn’t have was a marketing engine.
No marketing team. No agency. No content calendar. No SEO strategy. Just a solo founder, a product, and an idea: use the product to build its own go-to-market.
Four weeks later, here’s what happened.
The Setup: Building Tools to Build Content
Before producing content, we needed GTM-specific tools inside JieGou itself. Using the Recipe Factory pipeline — the same catalog-generate-evaluate-promote workflow available to every user — we created 12 GTM recipes and 5 workflows.
The recipes ranged from gtm-blog-writer for long-form posts to social-content-repurposer for turning blogs into social content, to prospect-researcher for lead qualification. Every recipe was evaluated by LLM-as-judge scoring with an average quality of 85/100.
The workflows connected these recipes into pipelines. The most-used: gtm-blog-to-everywhere, which takes a single blog post and produces SEO metadata, social variants, and scheduling instructions in one run.
We also built a GTM Starter Pack bundling all recipes and workflows, and translated 234 entity strings across 6 locales. Even internal tooling ships in all 7 supported languages.
Time for foundation work: ~4 hours.
Phase 1: Running a Content Engine with 8 AI Agents
This is where the thesis was tested. We used JieGou’s Agent Teams to orchestrate 8 specialized agents — content-seo, competitive-intel, reddit, outbound, video-script, pitch-deck, support-docs, and dev-agent — each with task briefs and assigned recipes.
Four Weeks of Output
Week 1 produced the first blog (“Why Your Department Needs Its Own AI Pack”), 3 social post sets, a Reddit post on r/SaaS, a 25-keyword SEO strategy, competitive landscape analysis, subreddit map, ICP definition, 5 help articles, and a video script outline.
Week 2 delivered a governance-focused blog (“AI Approval Workflows — Not Just Guardrails”), a /vs/zapier comparison page built as an Astro component, 4 competitor briefs (Zapier, Make, n8n, Relevance AI), a pitch deck outline, sales one-pager, and 50 researched Taiwan SMB prospects.
Week 3 shipped two blogs — one on Claude Code integration, one on our own Week 1 dog-food results — plus a PSKin customer case study, 2 complete video scripts, and continued social/Reddit output.
Week 4 focused on outreach: 10 personalized emails, 3-vertical drip sequences (9 emails), and the outbound metrics framework.
Every blog post was published in all 7 locales simultaneously — English, Traditional Chinese, Simplified Chinese, Japanese, German, French, and Spanish. That’s 42 blog locale files from 6 blog posts.
Phase 2: Outbound Pipeline
While content was flowing, we built the outbound infrastructure in parallel:
- A
prospect-outreach-pipelineworkflow: Research → Score → Draft → Approve → Send - 50 Taiwan SMBs researched and profiled
- 10 personalized outreach emails with company-specific value propositions
- 3-email drip sequences for beauty/wellness, food & beverage, and professional services verticals
- A /get-started landing page (7 locale translations) as the conversion endpoint
The approval gate in the outreach workflow ensured no email went out without human review — exactly the kind of governed automation JieGou is built for.
Phase 3: Launch Week
With 3 weeks of content and outbound infrastructure ready, we executed the launch in a single Agent Teams session:
- Launch blog (“JieGou Is Live: Department-First AI”) in 7 locales
- 4 Reddit launch posts across r/SaaS, r/startups, r/smallbusiness, and r/artificial
- 5-day social campaign across Facebook and Instagram
- Video publish metadata for both demo videos
- Updated pitch deck with real campaign metrics
- Investor update for stakeholders
- Full competitive launch positioning document
The Numbers
What We Produced
| Metric | Value |
|---|---|
| Agent Teams rounds | 4 |
| Unique agents orchestrated | 8 |
| Recipes built | 12 |
| Recipes actively used | 10 |
| Workflows built | 5 |
| Blog posts published | 6 (42 locale files) |
| Social media post sets | 9 |
| Reddit posts | 7 |
| Video scripts | 2 |
| Case studies | 1 |
| Competitor analyses | 6 |
| Outreach documents | 3 (19 emails total) |
| Pitch deck / investor materials | 5 |
| Help articles | 5 |
| Marketing pages built | 2 |
| Total content pieces | 42 |
| Total files produced | 94+ |
Time Savings
| Category | Manual Estimate | With JieGou | Saved |
|---|---|---|---|
| Blog writing (6 x 7 locales) | 48 hrs | 6 hrs | 42 hrs |
| Social content (9 sets) | 9 hrs | 1.5 hrs | 7.5 hrs |
| Reddit posts (7) | 7 hrs | 1.5 hrs | 5.5 hrs |
| Competitive analysis | 20 hrs | 3 hrs | 17 hrs |
| Video scripts | 8 hrs | 1.5 hrs | 6.5 hrs |
| Outreach + prospecting | 27 hrs | 4 hrs | 23 hrs |
| Pitch deck materials | 16 hrs | 3 hrs | 13 hrs |
| Help articles + case study | 18 hrs | 3.5 hrs | 14.5 hrs |
| Campaign planning | 18 hrs | 3 hrs | 15 hrs |
| Total | ~171 hrs | ~27 hrs | ~144 hrs |
Efficiency multiplier: 6.3x. One person produced the equivalent of one month from a 3-person marketing team.
Cost comparison: A comparable agency engagement runs $15,000-25,000/month. JieGou’s Team plan is $149/month.
What We Learned
Recipes are the right abstraction. The difference between “write me a blog post” and “run gtm-blog-writer with these structured inputs” is dramatic. Recipes have input schemas, output schemas, quality benchmarks, and approval gates. Prompts are just text.
7-locale translation is a moat. Every blog post shipping in 7 languages simultaneously is something no marketing team does manually. For a platform targeting both US and Asia-Pacific markets, this multiplies content footprint by 7x at near-zero marginal cost.
Governance builds trust, not friction. The approval gates in our workflows weren’t overhead. They were the mechanism that let a solo founder trust AI output enough to publish it. Without them, every piece would need manual review in a separate process.
Agent Teams scale linearly. 4 rounds, 8 agents each, clear task briefs, specific recipes, defined output locations. The “department pack” model works: give the team tools, give them tasks, let them execute.
Workflows need simplicity. We built 5 workflows but actively used 2. The blog-to-everywhere pipeline was invaluable (used 6 times). The others were overengineered for our current scale. We’re shifting toward simpler 2-3 step workflows as the default.
The Recursive Proof
There’s something worth acknowledging about this case study: it’s recursive. We used JieGou’s Recipe Factory to build recipes. Used those recipes to produce content. Used that content to market JieGou. And this case study — itself produced using the platform — demonstrates the entire loop.
Every number here is derived from actual file counts, actual directory listings, actual campaign tracker entries. The 42 blog locale files exist in the repository. The 12 recipes are in the catalog. The 234 translations are in the i18n files.
The thesis was: “Can a department-first AI platform run its own marketing department?” The answer: 94+ files, 42 content pieces, 171 hours of equivalent work — in 27 hours, for one person, using the platform.
Try It Yourself
JieGou is available now. Start free, install a department pack, and run your first recipe in under 5 minutes.
- Install a Department Pack — 20 departments, ready on day one
- See Pricing — $49/mo Pro, $149/mo Team (unlimited users)
- Calculate Your ROI — See projected savings before you sign up
- Get Started — Free tier, no credit card required