Everyone's talking about the "one-person company" running on AI agents. Forbes covered it two days ago. Sam Altman has been saying it for two years. Maor Shlomo built Base44 solo, hit $1M ARR in three weeks, and sold to Wix for $80M in June 2025.

But nobody enumerates the actual roster.

Not the abstract "use AI for marketing and ops" advice. The specific agents. The ones that fire on a schedule, or when a webhook hits, or when a table field changes. The ones that hand off to each other. The ones that replace a named role at a named salary.

This post does exactly that: 12 agents, one per traditional team role, each buildable in Knolo today. If you're running solo and want to know what your AI team actually looks like — this is it.

A quick note on framing

One thread from r/Solopreneur put it well: "People do not care that you built a COO agent, they care that proposals go out faster and client handoffs stop falling through the cracks. Sell the pain removed, not the architecture."

That's the right frame for this post. Each agent below is described by what it removes from your plate — not by its technical architecture. The architecture is simple. The relief is real.

Also worth saying upfront: agents aren't "set it and forget it." They're closer to a new hire in their first 90 days. You'll tune prompts as edge cases arrive. The roster below is the starting point, not the finished product.

The 12-Agent Roster

1. Head of Content — Content Research Agent

Replaces: Content strategist + researcher
Salary equivalent: $85,000–$120,000/year

Every piece of content starts with research: what's ranking, what Reddit is saying, what competitors missed, what keywords are worth targeting. A content strategist spends 30–40% of their time on this before a single word is written.

The Content Research Agent does it on a schedule. It scans sources, checks SERPs, pulls Reddit pain points, identifies keyword gaps, and writes a structured research brief into your content table — complete with MDX component recommendations. When it's done, it flips the row status from research-me to draft-me, which triggers the next agent automatically.

In Knolo, this is the 🔬 Blog Research Agent. It runs on a field-change trigger: when you set a Blog Posts row to research-me, it picks it up, runs the full research loop, and populates the research_brief field. The brief you're reading right now was written by this agent.

Trigger type: Field-change
Knowledge base it reads: SEO Blog Strategy mind, Brand Foundation mind
Output: Structured research brief in the Blog Posts table

2. Staff Writer — Draft Agent

Replaces: Staff writer / copywriter
Salary equivalent: $65,000–$95,000/year

Once the research brief exists, someone has to write the post. A staff writer reads the brief, checks the brand voice guide, looks up what competitors missed, and produces a 2,500–3,500 word draft in MDX format with the right components in the right places.

The Draft Agent does this from the research brief alone. It reads the brief, pulls the brand voice guidelines from the Brand Foundation mind, checks which MDX components the brief recommends, generates the cover image, and writes the full post. It then passes the draft through the Rewriter Agent for humanization before saving.

This is the ✍️ Blog Draft Agent — the agent writing this sentence right now.

Trigger type: Field-change (status = draft-me)
Knowledge base it reads: Blog Posts table, SEO Blog Strategy mind, Brand Foundation mind
Output: Full MDX draft in the Blog Posts table

3. SEO Specialist — Comparison Page Writer

Replaces: SEO manager + content writer
Salary equivalent: $75,000–$110,000/year

Comparison pages — "Knolo vs. Zapier," "Knolo vs. n8n" — are some of the highest-converting pages a SaaS can publish. They target buyers who are already comparing options. Writing one well takes an SEO manager who knows keyword intent, a writer who can be honest about competitor strengths, and a CMS operator who knows how to publish it.

The Comparison Page Writer agent handles all three. It takes a competitor entry from the Competitor Tracking table, researches the competitor's positioning and pricing, writes a structured comparison page in the SEO Comparisons CMS format, generates a cover image, and publishes the row. The page goes live on knolo.io without a human touching it.

Trigger type: Field-change (comparison_status = approved)
Knowledge base it reads: Competitor Tracking table, Brand Foundation mind
Output: Published row in SEO Comparisons CMS table

4. Social Media Manager — LinkedIn Post Agent

Replaces: Social media manager
Salary equivalent: $55,000–$80,000/year

Every published video or blog post should generate a LinkedIn post. In practice, this step gets skipped because it's one more thing to do after the "real" work is done. A social media manager would do it, but that's a full-time hire for what's often a 20-minute task.

The LinkedIn Post Agent fires when a video is marked as published. It reads the transcript, pulls the brand voice guidelines, generates a visual using the LinkedIn Visual Templates mind, and drafts a post for HITL review. You approve or reject in the 📥 Review Queue — the agent handles the rest.

Trigger type: Field-change (stage = Published) + HITL gate
Knowledge base it reads: Video Publication table, Brand Foundation mind, LinkedIn Visual Templates mind
Output: Draft in LinkedIn Review Queue with generated image

5. Community Manager — Reddit Comment Drafter

Replaces: Community manager
Salary equivalent: $50,000–$75,000/year

Reddit is one of the highest-trust channels for B2B SaaS. Genuine, helpful comments in the right threads drive more qualified signups than most paid channels. But monitoring 10 subreddits, finding the right threads, and writing non-spammy replies takes hours every week.

The Reddit Comment Drafter runs every 6 hours. It scans target subreddits for threads matching Knolo's keyword list, classifies each thread by intent bucket (recommendation, pain-first, how-to-build, competitor frustration), and drafts a reply grounded in the Reddit System ground-truth document. Every draft goes to the 📥 Reddit Review Queue for your approval before anything posts.

A solo newsletter operator using this setup saved 8 hours/week on community monitoring alone — and saw a 3x increase in qualified inbound from Reddit within 60 days.

Trigger type: Schedule (every 6 hours)
Knowledge base it reads: Reddit System mind, Brand Foundation mind
Output: Draft comments in Reddit Review Queue (HITL gate before posting)

6. L1 Support Rep — Support Agent

Replaces: Level-1 support representative
Salary equivalent: $45,000–$65,000/year

The first 80% of support tickets are the same 20 questions. How does billing work? How do I connect an integration? What's the difference between a mind and an agent? A human support rep answers these all day. An L1 agent answers them in seconds, grounded in your actual product documentation.

The Support Agent is grounded in the Product Documentation mind. It handles incoming tickets, answers questions from the doc set, and escalates anything it can't confidently answer to a human queue. It never invents answers — it cites the doc or escalates.

A SaaS founder using this pattern reported handling 90% of support volume without human involvement, with a median response time under 2 minutes.

Trigger type: Webhook (new ticket event)
Knowledge base it reads: Product Documentation mind
Output: Ticket response or escalation flag

7. Sales Development Rep — Lead Qualifier Agent

Replaces: SDR (Sales Development Representative)
Salary equivalent: $60,000–$90,000/year (base + commission)

When someone fills out your waitlist or contact form, the clock starts. The faster you qualify and follow up, the higher your conversion rate. SDRs do this manually: research the lead, score them, send a personalized first email, and schedule follow-ups.

The Lead Qualifier Agent fires on a webhook when a new application arrives. It researches the applicant (LinkedIn, website, stated reason for joining), scores them on a 1–10 fit scale against your ICP criteria, and writes a qualification summary into the Invitation List table. High-fit leads get flagged for outreach; low-fit leads get auto-routed to a nurture sequence.

Trigger type: Webhook (new application)
Knowledge base it reads: ICP mind, Brand Foundation mind
Output: Qualification score + research summary in Invitation List table

8. Research Analyst — Trend Digest Agent

Replaces: Research analyst
Salary equivalent: $70,000–$100,000/year

Staying current on AI, automation, and no-code trends is a full-time job. A research analyst reads newsletters, monitors Product Hunt, scans Reddit, and produces a daily digest. Most founders skip this entirely and end up reacting to trends weeks after they peak.

The Trend Digest Agent runs on a schedule — daily or every few hours. It scans configured sources (Product Hunt, Reddit, specific newsletters, RSS feeds), deduplicates findings, and writes structured trend reports into the Trends mind. The 📊 Trends mind currently holds 199 reports. A human analyst couldn't produce this volume.

Trigger type: Schedule (daily)
Knowledge base it writes to: Trends mind
Output: Structured trend report files

9. Brand Designer — Branded Visual Agent

Replaces: Brand designer (for social/blog images)
Salary equivalent: $65,000–$95,000/year

Every blog post needs a cover image. Every LinkedIn post needs a visual. Every comparison page needs an OG image. A brand designer produces these on-brand and on-schedule. Without one, you either skip visuals or spend time in Canva.

The Branded Visual Agent generates images from a prompt template grounded in the visual style guide. It knows the brand colors (deep teal #0d1f1f, cream #FAFAF5, lime green #AAFF00), the risograph grain texture, the editorial layout style. It generates cover images for blog posts, infographics for comparison pages, and LinkedIn visuals — all from a description, no design tool required.

In Knolo, this runs inside the Draft Agent and the Comparison Page Writer as a sub-step: describe the post → the agent generates the cover image → saves it to the SEO Cover Art Storage mind → uses the URL in the frontmatter.

Trigger type: Sub-step within other agents
Knowledge base it reads: Brand Foundation mind (visual style guide)
Output: Generated images saved to SEO Cover Art Storage mind

10. Copy Editor — Rewriter / Slop Remover Agent

Replaces: Copy editor
Salary equivalent: $55,000–$75,000/year

AI-generated text has tells. Certain phrases, certain sentence rhythms, certain over-hedging patterns that signal "this was written by a model." A copy editor strips these out and enforces brand voice. Without one, your AI-written content reads like AI-written content.

The Rewriter Agent — the AI Slop Remover — runs as the final step before any draft is saved. It reads the full MDX draft, applies the rewriter rules from the Rewriter Specs mind (which includes a running log of AI fingerprints to strip), and returns a humanized version. It doesn't touch MDX component tags or frontmatter — only prose.

The 📓 Rewriter Log currently holds 135 rewrite records. Each one is a paired before/after that feeds back into the spec, making the rewriter better over time.

Trigger type: Sub-step within Draft Agent (mandatory final gate)
Knowledge base it reads: Rewriter Specs mind (ai-fingerprints.md, rewriter-rules.md)
Output: Humanized prose written back to the draft field

11. Product Manager — Feedback Triage Agent

Replaces: PM inbox management
Salary equivalent: $90,000–$130,000/year

Product feedback arrives everywhere: support tickets, email replies, Reddit comments, waitlist application reasons. A PM reads all of it, tags themes, and routes insights to the roadmap. Without a system, feedback disappears into inboxes.

The Feedback Triage Agent parses incoming feedback from configured sources, tags each item by theme (pricing, UX, integration request, bug, feature request), and writes structured rows into a Feedback table. Recurring themes surface automatically — you see the pattern before it becomes a crisis.

Trigger type: Webhook (new feedback event) or schedule
Knowledge base it reads: Product Documentation mind
Output: Tagged feedback rows in Feedback table

12. Operations Manager — Space Orchestrator

Replaces: Ops manager / executive assistant
Salary equivalent: $70,000–$100,000/year

Someone needs to keep the pipeline healthy. Are agents running? Are there stuck rows in the Blog Posts table? Did the daily trend digest fire? Did the Reddit monitor surface anything urgent? An ops manager or EA does this daily check-in. Without one, you find out things are broken when a deadline is missed.

The Space Orchestrator runs on a morning schedule. It checks pipeline health across tables, surfaces stuck rows, flags agents that haven't run in their expected window, and sends a daily digest to your inbox. It's the system watching the system.

Trigger type: Schedule (daily, morning)
Knowledge base it reads: All active table minds
Output: Daily digest notification + flagged stuck rows

The Roster at a Glance

Trigger Patterns — How Agents Actually Fire

The roster above uses four trigger types. Understanding them is the difference between agents that work and agents that sit idle.

Schedule (cron) — The agent runs on a timer: every 6 hours, every morning at 8am, once a day. Used for: Trend Digest Agent, Reddit Comment Drafter, Space Orchestrator. Best for tasks where you want consistent cadence regardless of external events.

Webhook — An external event hits a URL and the agent fires. Used for: Support Agent (new ticket), Lead Qualifier Agent (new application). Best for tasks that need to respond immediately to external input.

Field-change — A value in a table row changes and the agent picks it up. Used for: Blog Research Agent (status = research-me), Blog Draft Agent (status = draft-me), Comparison Page Writer (comparison_status = approved). Best for pipeline stages where you want human control over when each step fires.

HITL gate — The agent drafts, a human approves or rejects, then the agent acts. Used for: LinkedIn Post Agent, Reddit Comment Drafter. Best for anything public-facing where you want a final review before it goes out.

The Cost Comparison

This matches what Forbes reported two days ago: solo-founded startups now make up 33%+ of new ventures (up from 23.7% in 2019). The cost structure is the reason. When your ops layer costs $12k/year instead of $1.5M, you can stay solo longer, reach profitability faster, and build with a fundamentally different risk profile.

Knolo's pricing is credit-based — you buy credits, use them when agents run, and don't pay for idle time. No subscription, no per-task counting, no surprise bills at the end of the month.

What Agents Still Can't Do

Honesty matters here. The roster above handles a lot. It doesn't handle everything.

Specifically, keep these with yourself:

• Genuinely novel judgment calls — Agents are excellent at executing within established patterns. They're poor at recognizing when the pattern itself is wrong.
• Long-arc relationship building — A community manager agent can draft a reply. It can't build a genuine relationship with a power user over 18 months.
• High-stakes negotiation — Pricing conversations, partnership terms, investor discussions. These require real-time reading of the other person.
• Anything requiring new taste — Agents can execute your aesthetic. They can't develop a new one. The creative direction has to come from you.
• Crisis response — When something goes wrong publicly, you need a human making judgment calls in real time, not an agent following a playbook.

The honest version of the "solo founder with AI team" story is this: you're still the CEO, the creative director, and the relationship owner. The agents handle execution. That's a real and significant division of labor — just not a complete replacement.

Which Three to Build First

You don't need all 12 on day one. Most founders who try to build everything at once end up with 12 half-working agents and no confidence in any of them.

Here's why these three:

Support Agent first — It has the clearest success criteria (did it answer the question correctly?) and the most immediate ROI (every ticket it handles is time you get back). Ground it in your product documentation mind and test it on your last 20 support tickets before going live.

Content Research Agent second — If you publish content at all, this is the highest-leverage agent in the roster. A research brief that would take 3–4 hours to produce manually takes the agent 8–12 minutes. The quality floor is higher than most human first drafts.

Trend Digest Agent third — This one runs in the background and requires almost no maintenance. Set it up once, point it at your sources, and it builds a knowledge base of trend reports you can reference whenever you need context for a decision.

Once these three are stable and you trust their output, add the Draft Agent, the Lead Qualifier, and the Space Orchestrator. The rest follow naturally.

How Agents Share Knowledge in Knolo

One thing the generic "use AI tools" advice misses: agents are only as good as the knowledge they can access. An agent that can't read your brand voice guide will write off-brand copy. An agent that can't read your product docs will hallucinate support answers.

In Knolo, agents share knowledge through minds — knowledge bases that any agent in your space can read. Your Brand Foundation mind holds your voice guidelines, ICP, and visual style. Your Product Documentation mind holds your feature specs and how-to guides. Your SEO Blog Strategy mind holds your post structure templates and MDX component catalogue.

Every agent in the roster above reads from one or more of these shared minds. That's what makes them a system rather than a disconnected set of tools. The Content Research Agent and the Draft Agent share the same Brand Foundation — so the research brief and the post it generates are aligned from the start.

This is Knolo's Discover API in practice: 3,000+ integrations available, and agents can install their own integrations from any REST API — without you touching a config file.

Getting Started in Knolo

Total time to first working agent: ~27 minutes. Most of that is uploading your docs.

From there, the Content Research Agent takes another 10 minutes to configure. You describe what you want it to research, point it at your Blog Posts table, and set the field-change trigger. The first research brief it produces will tell you whether your prompts need tuning.

Frequently Asked Questions

Do I need all 12 agents?

No. The roster is a menu, not a mandate. Start with the three highest-friction tasks in your current week and build agents for those. Most solo founders find that 4–5 agents handle 80% of the value.

What order should I build them in?

Support Agent → Content Research Agent → Trend Digest Agent → Draft Agent → Lead Qualifier Agent → Space Orchestrator. This sequence builds your confidence in agent output before you hand off higher-stakes tasks.

How do agents share knowledge with each other?

Through Knolo minds. Any agent in your space can read from any mind you've created. You build the knowledge base once — your brand voice guide, your product docs, your SEO strategy — and every agent reads from the same source. No copy-pasting, no version drift.

What if an agent fails at 3am?

Knolo is cloud-native and always-on — no Docker, no local setup, no infrastructure to maintain. If an agent run fails, you get a notification and the run log shows exactly what happened. The Space Orchestrator agent monitors pipeline health and flags stuck rows before they become problems.

Can agents hand off to each other?

Yes — through field-change triggers. The Content Research Agent sets a row status to draft-me when it finishes. That status change triggers the Draft Agent. The Draft Agent calls the Rewriter Agent as a sub-step before saving. The chain is built from table field changes, not hard-coded agent-to-agent calls.

How much does the roster actually cost per month?

Knolo uses credit-based pricing — you buy credits and use them when agents run. A full 12-agent roster running at moderate volume (daily trend digest, 6-hour Reddit monitor, 2–3 blog posts per week, 50 support tickets per week) typically costs $300–$1,000/month in credits. Compare that to the salary line for a single mid-level hire.

The Bottom Line

The solo founder AI team isn't a fantasy. It's a specific set of agents, each with a defined role, a trigger type, and a knowledge base it reads from. The roster above is buildable today, in Knolo, without writing a single line of code.

You describe what you need. Knolo builds it. The agents run. You stay focused on the work only you can do.

Try Knolo free →

Related Reading

• How to Create an AI Agent for Your Business Without Coding in 2026
• How to Create an AI Agent for Content Creators in 2026
• What Is Multi-Agent AI? A Plain-Language Guide for Non-Technical Teams
• Best AI Workspace Tools for Solopreneurs in 2026
• How to Automate Your Content Workflow with AI Agents in 2026