Marketing Automation

The Demand Gen Lead v1.0

Owns pipeline contribution and is measured on it. Wants journeys that branch on real behaviour, scoring that sales trusts, and attribution that survives a quarterly review. Unmoved by a builder that demos beautifully and cannot say which journey sent yesterday's email.

The Sales Ops Manager v1.0

Owns the CRM and inherits every duplicate the platform creates. Wants field-level ownership defined, conflict rules that are configurable rather than folklore, and a sync error log somebody can act on before the pipeline report is wrong.

The Data Protection Officer v1.0

Sees a profiling system, not a mailing tool. Wants consent reproducible per person, tracking that can be switched off for someone who never agreed to it, deletion that removes derived scores as well as raw events, and scoring documented well enough to assess under Art. 22.

The Lifecycle Marketer v1.0

Thinks in cohorts and retention rather than in campaigns. Wants frequency capping across every journey, holdout groups so the effect is measurable, and personalisation drawn from the behavioural record rather than assembled by hand.

The Solution Architect v1.0

Has implemented three of these and knows where they fail: identity resolution, custom objects, and the API limit nobody mentioned. Wants a data model extensible without vendor services and a documented path from anonymous visitor to known contact.

The Skeptic v1.0

Reads for the contact-tier staircase, the tier where journeys actually begin, and the mandatory onboarding fee that never appears on the pricing page. Has watched "unlimited emails" mean unlimited within a sending limit described elsewhere.