Commerce and campaigns

Campaign research and copy: Carry client research all the way into campaign copy.

Campaign research and copy connects intake and call context to market research, offer planning, script development and downstream drafting. The finalized script becomes the shared handoff, so website and email copy inherit the campaign’s direction instead of starting over.

Historical campaign research output — About this view
Historical recording
Original recorded document library with local field-level anonymization, not a wide black patch.

Original intake and research workflow — About this view
Local import only
85-node archived source imported locally. Inactive; no credentials or executions.

Intake and research branch — About this view
Local import only
Native local source detail; not current client activity.

Original finalized-script copy workflow — About this view
Local import only
56-node source imported locally. A source graph does not prove native approval enforcement.

Finalized-script handoff branch — About this view
Local import only
Native local source detail. No publication or delivery was performed.

Historical research document detail — About this view
Historical recording
Source text and displayed values retained; identifying fields locally anonymized.

Historical script and copy output — About this view
Historical recording
Recorded document excerpt with local privacy masks.

Historical downstream output — About this view
Historical recording
Original document output, not a live generation or acceptance receipt.

What it does

Intake and call-context handoff into linked client research and offer planning.
Research-to-script workflow with client references and revision context.
Finalized-script handoff into website and email-copy drafting.

Why it matters

Keeps campaign direction coherent across research, scripts and downstream assets while giving reviewers a shared reference point.

intake/research, script development and finalized-script copy handoff: 3 workflow stagesStages represented by original source exports; local views do not prove production execution.

Under the hood

Onboarding to research and offer planning - archived source

85 nodes · 85 non-note nodes

Open read-only HTML explorer →Download explicitly sanitized review JSON

Approved script to website and email copy - archived source

56 nodes · 55 non-note nodes

Open read-only HTML explorer →Download explicitly sanitized review JSON

Technology stack

n8n
Airtable
Google Docs
Anthropic
OpenAI
JavaScript
HubSpot
Fathom

Build note

One approved script, then website, funnel and email copy.

Source & context

Historical operating documentation and recorded workflow views.

Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.

Capture the context once

The documented process starts with intake and call material. The source archive includes the eighty-five-node onboarding-to-research and offer-planning workflow, rather than only the document-library screenshot.

Carry research into the script

Market research and offer planning support the script-development stage. Historical document outputs are retained as outputs, with identifying fields locally anonymized instead of covered by a single wide black strip.

Let downstream copy inherit the finalized script

The finalized-VSL source workflow feeds the website and email-copy stage. The documented process uses a finalized-script handoff; the local import is not proof that every native approval gate or destination was independently tested.

Show the whole handoff, not a collage of tools

The source canvas, a readable branch and the recorded research/output views show different parts of one operating process. The benefit is less context reconstruction for the next writer; time savings remain unmeasured here.

Inside the system

Client and call context Links intake and transcript before research begins.
Research and scripts Carries the same source material into reviewable drafts.
Finalized-script gate Uses reviewed direction for downstream drafting.
Revision context Retains feedback and references against the client.

The handoff

Intake and transcript handoff
Linked research and script drafts
Finalization decision
Downstream drafting and revision requirements

Technology stack

Workflow source and integrations

n8n
Airtable
Google Docs
Anthropic
OpenAI
JavaScript
HubSpot
Fathom

Recovered intake/research/copy graph and documented intake context.

Not established

Production hosting is not established.

Source & context

View	Provenance and limitation	Evidence class
Fig. 1	Historical campaign research output Original recorded document library with local field-level anonymization, not a wide black patch.	Historical recording
Fig. 2	Original intake and research workflow 85-node archived source imported locally. Inactive; no credentials or executions.	Local import only
Fig. 3	Intake and research branch Native local source detail; not current client activity.	Local import only
Fig. 4	Original finalized-script copy workflow 56-node source imported locally. A source graph does not prove native approval enforcement.	Local import only
Fig. 5	Finalized-script handoff branch Native local source detail. No publication or delivery was performed.	Local import only
Fig. 6	Historical research document detail Source text and displayed values retained; identifying fields locally anonymized.	Historical recording
Fig. 7	Historical script and copy output Recorded document excerpt with local privacy masks.	Historical recording
Fig. 8	Historical downstream output Original document output, not a live generation or acceptance receipt.	Historical recording

Historical operating documentation and recorded workflow views.

Reviewed: 2026-10-27

Map one workflow handoff

Bring one workflow and the output the next person needs. Define its inputs, review decision and completion check before agreeing implementation scope.

Discuss a workflow →