Forest Way execution layer
The workbook wiring, translated into an implementation view.
This page shows the practical CRM/ERP structure underneath the Forest Way ecosystem: campaign blueprints, field mappings, workflow rules, asset IDs, and prospect list requirements.
Campaign Blueprint
Each campaign connects a persona/segment/stage decision to a CTA, required assets, and a follow-up action.
| ID | Campaign | Stage | CTA | Required Assets | Follow-up |
|---|
CRM/ERP Field Mapping
These are the fields the operating system needs so the journey can be segmented, routed, measured, and acted upon.
| Journey Field | CRM/ERP Module | Field Name | Type | Example Values | Purpose |
|---|
Workflow Rules
These rules turn behavior into next steps: campaign enrollment, stage updates, owner tasks, and asset recommendations.
| ID | Name | Module | Trigger | Conditions | Action | Notes |
|---|
Reusable Asset Queue
Assets are centralized by ID so the same approved content can support multiple personas, stages, and campaigns.
| ID | Asset | Type | Stage | Channel | Source References |
|---|
Prospect List Requirements
These fields make the import useful from day one instead of forcing manual cleanup after launch.
| Field | Required | Module | Type | Example | Reason |
|---|