Expand Beyond the First Workflow

Carry the architecture into other systems and teams.

View your context layer

The first workflow answers renewal questions. The architecture can support Sales, Marketing, Customer Success, Finance, and cross-system work, but expansion should reuse meaning without copying every rule.

Share organizational context

Fiscal dates, account segments, approved lifecycle definitions, and authority rules can serve many workflows. Keep one maintained definition and let each workflow load it. Copies drift.

Keep workflow boundaries local

A Customer Success workflow and a pipeline workflow need different fields, tools, and action rights. Share the meaning of “at risk,” then give each workflow its own allowlist and tests.

Add one system because the question needs it

Cross-system context is useful when a business question genuinely spans CRM, product, support, or finance data. Start with the join and definition needed for one answer. Do not turn the context layer into a warehouse or copy all source data into it.

Choose implementation plumbing after the model is clear

Rules can live in Salesforce, HubSpot, git, or a small database. The storage choice changes administration and retrieval, not the core contract. Platform-specific implementations live in Reference so this guide can stay general.

Extend the Acme risk definition into a bounded Customer Success workflow in the GTM Lab.

Implementation Reference

GTM Lab

Saved locally

The new workflow reuses your approved risk meaning while keeping its own permissions local.

Account segment

Customer Success renewals

SEG-0094

Accounts found: 46
Shared risk definition: No
Source workflow: Sales qualification
Field scope: All Sales fields
Write actions: Enabled
Owner: CS Operations

Extend the first workflow

Customer Success wants to use the same definition of “at risk” in a renewal workflow.

What happened

Customer Success Operations asked:

“Which high-risk customers need an intervention this week?”

Agent response

“I copied the Sales workflow and found 46 accounts. I also enabled its update actions for the CS team.”

Naive expansion: Customer Success copies the Sales prompt, every rule, and broad integration permissions into a second workflow.

How to complete this chapter

Reuse only durable organizational context.
Add a workflow-specific boundary.
Keep the first expansion small.

Build your decision

Reuse the approved risk definition
Shares the maintained organizational meaning.Add a Customer Success field allowlist
Limits the new workflow to what it needs.Copy every Sales prompt and rule
Creates a second library that will drift.Enable automatic renewal writes
Expands scope before the read workflow is proven.

Chapter 9 of 100 complete