You’ve now read through eleven systems across seven go-to-market functions. If you’re anything like me, you’re simultaneously excited by what’s possible and overwhelmed by the amount of infrastructure to build.
That’s the right reaction. This is a lot.
But here’s what I want to say as directly as I can: you don’t build this all at once. Nobody does. I didn’t. The system I described across Part Two took me three years to build, and it’s still evolving. The first version was ugly, the second version was better but still had gaps, and the current version is the most complete, but I’m still finding things that are broken or missing every week.
A book about systems presents them in logical order, one chapter flowing into the next. Unfortunately, reality is messier.
- You build the content engine and discover you don’t have a tagging taxonomy.
- You build the outbound system and realize your value prop library is three bullet points copied from your website.
- You build the inbound processing workflow and find out that your enrichment data is 40% incomplete.
That’s normal. The system gets built by building it, not by planning it perfectly.
This chapter gives you three things: the site survey before construction begins (four audits that tell you what you already have and what’s missing), the recommended build order (so you start with the pieces that open up the most value soonest), and the minimum viable factory (what you can build in 30 days with one person and a Claude subscription if needed). Appendix B at the end of the book lays the 30-day plan out week by week.
§Before You Build: The Four Audits
Before you lay a single pipe, you need to know what you already have.
In Chapter 12, I introduced the Brand Brain: the structured knowledge layer that holds your messaging, your ICP definitions, your brand voice, your product truths, your quality standards, and your process documentation. The Brand Brain is what makes every workflow and every tool your team builds pull from the same foundation.
But the Brand Brain doesn’t populate itself. You have to fill it, just like you’d need to onboard a new intern (even if that intern was the smartest human in the world and had a photographic memory).
Before you can fill it, though, you need to know what exists, what’s missing, and where the institutional knowledge currently lives. That’s what these four audits are for.
I recommend spending two to three days on these before you touch a single workflow. It feels slow, I know. But it saves you weeks of rework later, because the most common reason systems produce bad output is that they were built on incomplete inputs. Every shortcut you take in the audit phase shows up as a quality problem in the production phase.
1. The Content Audit
What do we have that we want the Brand Brain to know?
Inventory every piece of content your company has produced that’s worth keeping. Blog posts, case studies, landing pages, one-pagers, competitive positioning docs, presentations, webinar recordings, podcast episodes. You’re not looking for everything; you’re looking for the assets that are accurate, current, and representative of who you are and what you sell.
For each asset, ask:
- Is this still accurate?
- Does it reflect our current product and positioning?
- Is it good enough that we’d want a workflow to reference it or a new team member to learn from it?
If the answer is yes, it goes into the library. If it’s outdated but salvageable, flag it for a refresh. If it’s outdated and irrelevant, archive it.
Most companies discover they have more usable content than they thought, scattered across more places than they realized. The audit brings it together. The tagging work from Chapter 12 (persona, buying stage, topic cluster, pain point, industry) gets applied to everything that passes the filter.
2. The Context Audit
What do we know about our product, benefits, and audience that we want the system to know?
This is where you capture the institutional knowledge that currently lives in people’s heads.
Your value propositions, your ICP profiles, and the specific language your best customers use to describe the problem you solve. The objections your sales team hears every week and the competitive advantages that are real (backed by data or customer evidence) versus the ones that are aspirational (listed on the website but never validated).
Interview your best salesperson. Interview your best customer success manager. Interview the founder or product lead. Ask them:
- When you’re explaining what we do to someone who’s never heard of us, what do you say?
- When a customer renews, what’s the reason they give?
- When we lose a deal, what’s the reason?
The answers to those questions are the raw material for the Brand Brain’s messaging framework and ICP definitions.
The output of the context audit is a structured document that captures your value props (tagged by persona and use case), your ICP profiles (with real language, not marketing language), and your competitive positioning (honest, not aspirational). This becomes the foundation that every workflow and every proprietary tool your team builds will pull from.
3. The Process Audit
How does each department’s work actually flow?
Map the actual processes your team runs, at a granular level. Not the org chart version or the quarterly review version that nobody really looks at. Map out the real, daily version.
- How does a blog post go from idea to published?
- How does a sales rep prepare for a call?
- What happens when an inbound lead submits a form?
- How does a case study move from customer agreement to published asset?
- How does a webinar get planned, promoted, recorded, and followed up on?
Document each process step by step, from start to finish. Where are the handoffs? Where are the bottlenecks? Where does the same work get done twice because two people don’t realize the other already did it?
This audit does two things:
First, it tells you which processes are candidates for workflows (the defined ones, where the steps are the same every time and only the inputs change) and which might eventually support agentic capabilities (the ones that require judgment between steps). That’s the defined vs. decides framework from Chapter 3 in action.
Second, it becomes the process documentation layer of the Brand Brain, so that when someone builds a tool on top of the system, they understand how it connects to what everyone else is doing.
4. The Quality Audit
For each thing we produce, who knows what “good” looks like?
This is the audit most teams skip, and it’s the one that matters most for AI output quality.
For every type of content or output your system will produce (blog posts, outbound emails, case studies, one-pagers, meeting prep briefs, follow-up emails, landing pages), identify the person on your team who knows what good looks like. Then capture their standard.
- What makes a blog post good enough to publish versus one that needs another pass?
- What separates a compelling outbound email from a generic one?
- What’s the difference between a case study that sales actually shares and one that sits on the website untouched?
The answers become quality templates: annotated examples of excellent output that your workflows use as pattern-matching references. This is the “good in, good out” principle from Chapter 4 made operational. The content engine from Chapter 5 doesn’t produce good output because the AI is smart but because you gave it an example of what “good” looks like and it uses that example as its quality benchmark. Without the quality template, the output is structurally competent and tonally generic.
With it, the output matches your brand and your brand’s unique point of view.
Every person who owns quality for a specific output type should produce one annotated example: here’s a good one, here’s what makes it good, and here’s a common mistake to avoid. Store those examples in the Brand Brain, and they’ll become the quality layer that every workflow references.
These four audits take two to three days:
- The content audit is the longest (half a day to a full day depending on how scattered your assets are).
- The context audit takes three to four hours of interviews plus two hours of structuring.
- The process audit takes a few hours per department.
- The quality audit takes an hour per output type, assuming the right person is available.
At the end of the audit phase, you have the raw material for your Brand Brain: tagged content, structured messaging, documented processes, and quality standards. Phase 1 of the build order starts from a foundation instead of from guesses.
§The Recommended Build Order
Not all pipes are equal. Some need to exist before others can work. I recommend you build in this order.
Phase 1: The Content Engine and Structured Library (Chapters 5 and 12)
This is the foundation. Everything else in the system either produces content for the library or draws content from it. If the library doesn’t exist:
- The outbound system has no proof points to include.
- The ABM system has no assets to assemble.
- The inbound system has no resources to surface.
- The event system has nowhere to store its derivatives.
Start here.
Before you build the engine, you need to know what it's producing and for whom. That means setting your content strategy across both traditional search and AI search (the dual-track approach from Chapter 5).
- Which keywords matter for your ICP?
- Which questions are your buyers asking ChatGPT and Perplexity?
- Where are the content gaps in the “competitive landscape” (an overused phrase by AI models, I know, but very accurate in this context) that you can cover better than what currently ranks?
This is Stage 1 human work. It takes maybe a day, but it's the day that determines whether your content engine produces pipeline content or noise. Then, set up your AEO monitoring alongside your SEO tracking from day one. You want baseline visibility numbers before the system starts producing, so you can actually measure the impact. If you don't know where you started, you can't prove what the system built.
Next, build the human-in-the-loop content engine (strategy, AI draft, human review, publish). Simultaneously, build the structured content library with your tagging taxonomy and populate the Brand Brain with the outputs from your four audits. Tag everything you produce from day one. Also, go back and tag your existing best content. Most companies already have 20 to 50 assets that are good enough to include (they’re just sitting in folders with no metadata).
Timeline: weeks 1 through 4.
Phase 2: Sales Enablement and Outbound (Chapter 6)
Once the content library has 30 to 50 tagged assets, connect it to your sales motion.
- Build the value prop library (this is human strategic work, not a workflow).
- Build the account intelligence enrichment workflow.
- Build the outreach generation workflow that maps enriched account data to value props and generates personalized emails with relevant content attached.
At this point, all you need is enough that the system can find something relevant for most account profiles. Thirty assets tagged across three to four industries and two to three buying stages is a workable starting point.
Timeline: weeks 3 through 6 (overlaps with Phase 1).
Phase 3: Inbound Processing (Chapter 7)
Once you have the enrichment workflow (built in Phase 2) and the content library (built in Phase 1), the inbound processing system is relatively fast to stand up. You’re assembling components that already exist: enrichment, scoring criteria, response generation from the content library, and routing rules.
The scoring criteria are the key human input here. Spend the time to define what a high-intent lead looks like for your specific business. Don’t copy someone else’s scoring model, but try to build one from your own conversion data: which attributes and behaviors have historically correlated with deals that close?
Timeline: weeks 5 through 7.
Phase 4: MOFU Repurposing (Chapters 8 and 10)
Now that the library, the outbound system, and the inbound system are operational, start feeding them from live conversations. Build the podcast or webinar repurposing workflow. Record your first conversation (a customer interview, a guest expert episode, an internal thought leadership recording).
Run it through the workflow. Review the ten outputs. Tag and store them in the library.
This is where the system starts to feel like a system rather than a collection of parts. One conversation produces ten assets that get distributed by the outbound system, surfaced by the inbound system, and referenced by the sales team. The compounding becomes visible.
Timeline: weeks 6 through 8.
Phase 5: ABM (Chapter 9)
ABM is the last system to build because it depends on all the others. It needs the content library for asset assembly, the enrichment workflow for account intelligence, the value prop library for message matching, the outbound infrastructure for multi-channel delivery, and the proof library for personalized landing pages.
If you try to build ABM first, you’ll end up with a sophisticated targeting system that has nothing relevant to say to the accounts it targets. Build the pipes first. Then connect them through ABM.
Timeline: weeks 8 through 12.
Phase 6: Case Studies (Chapter 11)
Case study production is ongoing, not a phase you complete. But the system for producing them (interview workflow, modular extraction, proof library tagging) should be built once the rest of the infrastructure is in place, because the modular outputs need the library to be tagged, the sales system to be surfacing content, and the ABM system to be assembling proof-based landing pages.
Start building your case study pipeline in Phase 1 (identify and reach out to customers), but don’t expect to produce the first finished case study until Phase 5 or 6. The customer approval process takes time regardless of how fast your internal system operates.
Timeline: ongoing from week 4, first outputs in weeks 10 through 12.
§The Minimum Viable Factory:
30 Days, One Person, and One Claude Subscription
The full system described in Part Two takes 10 to 12 weeks to build. But you don’t need the full system to start seeing results. You need the minimum viable factory.
Here’s what you can build in 30 days with one person:
Week 1: Audits and foundation
Run the four audits (content, context, process, quality). This is your site survey. In parallel, define your ICP personas (two to three maximum), write your value prop library (five to eight core value propositions, each tagged by persona and pain point), and create your tagging taxonomy (define the allowed values for each metadata category). Set up your content library (a Notion database, an Airtable base, or a Supabase instance with the right schema) and start populating the Brand Brain with the audit outputs. Tag your existing best content (you probably have 15 to 30 pieces worth tagging).
Week 2: Content engine
Build your first content workflow (topic brief to AI draft to human review to publish). Produce your first batch of ICP-focused content (five to ten articles). Tag and store each one in the library. This doesn’t need to be the full five-articles-per-day engine. Start with one article per day and iterate on the workflow until the output quality is consistent.
Week 3: Sales connection
Build the account enrichment workflow (company data, hiring signals, news, tech stack). Build a simple outreach generation workflow that takes the enriched account brief and a matched value prop and produces a personalized email draft. Test it against ten target accounts. Review the output. Refine.
Then, connect the outreach to the content library so the system can attach relevant resources.
Week 4: Inbound and repurposing
Set up your lead scoring criteria. Build the inbound enrichment and response generation workflow (even a simplified version that enriches the lead and generates a personalized response beats the 47-hour average by a mile). Record one conversation (a customer interview, a podcast pilot, or a structured internal discussion). Run the transcript through a repurposing workflow. Tag and store the outputs.
At the end of 30 days, you have:
- A Brand Brain with your messaging, ICP, and quality standards populated
- A structured content library with 30 to 50 tagged assets
- A content engine producing daily content
- An outbound system generating personalized emails for target accounts
- An inbound system responding to leads in under five minutes with personalized context
- A repurposing workflow that proves one conversation can become ten assets
That’s the minimum viable factory. It’s not the full system. It’s missing ABM, the case study production pipeline, the event segmentation workflows, and most of the connected workflow intelligence that makes the full system compound. But it’s enough to produce measurable pipeline results within the first 60 days, and it’s the foundation that everything else builds on.
§The Tool Stack
One thing I want to call out before I share my stack, because it matters for how you read this section.
I had the luxury of building inside Copy.ai for three years. That meant I had access to a workflow-building platform purpose-built for chaining AI tasks together, with structured outputs, team collaboration, and the kind of orchestration layer that makes multi-step workflows manageable without writing custom code.
That experience shaped everything in this book.
For enterprise teams (100+ people), I'd strongly recommend a workflow-building platform like Copy.ai or a similar solution. Here's why: the bigger the team, the harder it gets to maintain process consistency.
Individual contributors will build their own tools, use their own prompts, encode their own understanding of the brand. A dedicated workflow platform forces the process audit we talked about earlier in this chapter, gives you a shared environment where workflows are visible and editable by the team, and keeps everything organized in one place instead of scattered across personal Claude accounts and homegrown scripts.
For skeleton crews, though, enterprise workflow platforms aren't always priced for a team of one or two people with a startup budget. The stack I'm sharing below is what works at that scale. It's more hands-on than a dedicated platform, and some of it requires technical comfort (or a willingness to learn). But it gets the job done at a fraction of the cost.
The honest answer is that the best tool is the one that matches your team size, your budget, and your technical ability. The workflows matter more than what you build them in.
But people always ask me what tools I would use for smaller teams. I’ll share my stack, but with a caveat: tools change fast. What I’m using today might not be what I’m using in six months. The principles don’t change, but the specific software does, so pay more attention to the function each tool serves than to the tool itself.
1. AI backbone: Claude (Anthropic): This is where the workflows run. I use the Claude API for content generation, transcript processing, outreach drafting, and most of the multi-step workflow processing. I’ve used GPT-4 and Gemini for specific tasks, but Claude is my default for anything that requires nuanced writing, brand voice matching, and complex multi-step reasoning.
The quality of the output is noticeably better for B2B content use cases.
2. Workflow orchestration: FastAPI (custom): My content engine and several of my production workflows run on a custom FastAPI application. This gives me full control over the workflow steps, the prompts, and the quality checks. It’s more technical than a no-code solution, but the control is worth it for production-critical workflows. For teams without a developer, Make (formerly Integromat) or Zapier can handle most workflow orchestration at the cost of some flexibility.
3. Structured data: Supabase: The content library, the Brand Brain, the customer language database, the account intelligence records, and the tagged insights all live in Supabase. It’s a Postgres database with a nice API layer. Simple to set up, scales well, and the SQL access means I can run complex queries when I need to analyze the library’s coverage or identify gaps.
4. CMS: Webflow: Publishing layer for the content engine. I’ve used WordPress and others, but Webflow gives me the most control over the publishing workflow and the SEO technical layer without requiring a separate engineering team.
4. CRM: Salesforce and HubSpot (depending on the property): The lead scoring, routing, and deal tracking live here. I don’t have a strong opinion about which CRM is best. I have a strong opinion that your CRM needs to be connected to your content library and your enrichment workflows. If they’re disconnected, the inbound and outbound systems can’t function.
5. Enrichment: Apollo, LinkedIn Sales Navigator, and custom scrapers: Account intelligence comes from a combination of structured data providers and targeted scraping for specific signals (job postings, recent news, tech stack data). No single enrichment source is complete. You need at least two to three to get a reliable account picture.
6. Content distribution (native platform tools): LinkedIn publishing, email via the CRM’s built-in email, newsletter via ConvertKit or similar. I haven’t found a distribution tool that’s worth paying for beyond what the native platforms offer.
7. Automation glue: Zapier: The connective tissue between systems that don’t have native integrations. Post-call transcript to content library. New content published to sales team notification. Lead score change to Slack alert. Zapier handles the “when this happens, do that” connections.
This stack costs roughly $200 to $500 per month for a solo operator (Claude API, Supabase, Webflow, enrichment tools). That’s the cost of the entire factory’s infrastructure. Compare that to a single additional hire at $60k to $80k per year.
§The Build Mindset
I want to close this chapter with something philosophical, because I think the biggest barrier to building the factory isn’t technical. It’s psychological.
The first version of every system I’ve built was embarrassing. The content engine’s first output was generic and toneless. The outbound workflow’s first emails were over-personalized in ways that sounded weird. The inbound processing system’s first scoring model was miscalibrated and flagged tire-kickers as high intent. And the content library’s first tagging taxonomy had gaps and overlaps that took months to clean up.
All of that is normal.
Building systems is iterative. Like great writing, the first version is a draft, the second version is better, the tenth version is finally good, and the twentieth version is something you’re proud of.
The mistake I see people make is waiting to start until they have the perfect architecture planned out. They spend weeks mapping the ideal system on a whiteboard or they evaluate twelve tools. They need to read three more books or listen to a few more podcasts. They draft a detailed implementation plan with milestones and dependencies.
And then they never build anything.
I’ve had several people ask me what my “secret sauce” is over the years, and this is as blunt as I can be about it: my secret is a combination of stubbornness, optimism in technology, and the knowledge that the system only gets built by building it (and perfected by refining it, which is where the first two attributes come in handy).
Start with the content engine because it’s the foundation and it produces visible, tangible output from day one.
- Don’t worry about whether your tagging taxonomy is perfect. Tag it. You can fix the tags later.
- Don’t worry about whether your value prop library is complete. Write the first five value props. You can always add more when you learn what’s missing.
- Don’t worry about whether your scoring model is calibrated. Set initial thresholds based on your best guess. You can adjust them when you have conversion data.
That’s how the factory gets built. Not from a blueprint, but from the work.
I built my first workflow in a weekend. It was crude, but it worked. I iterated on it every week for six months until it was producing output I was genuinely proud of. If I’d waited until I had the full architecture planned out, I’d still be planning.
It’s all very formulaic: Lay the first pipe. Run water through it. See if it leaks. Fix the leaks. Lay the next pipe.
Eventually, you have a factory. Then you’re free to pour the chocolate and watch it become a river.