INTERACTIVE DEMO · sample data only · nothing sends or changes production

RELATIONSHIP DATABASE

Creators

Find the right people and move them into outreach.

DA

Creator database

One record for fit, relationship, conversation, and lifecycle.

FilterMatch all conditions
CreatorFitNiche / marketSourcing statusEmailOutreachReview
Reply in original thread
Demo mode · sending disabled
Action neededAutomatedHeld
Illustrative cohort data

Each creator is counted once per reached step. Follow-up messages do not inflate conversion.

Monthly outreach cohort journey

Every outcome stays attributed to the month of initial outreach.

MilestoneReachedStep conversionLost here

Monthly cohort comparison

Compare mature cohorts without moving outcomes into a later month.

Outreach cohortReachedEmail openRepliedProduct sentPostedAffiliate

How to read this

Conversion and operational state answer different questions.

Cohort month is fixed by the first outreach send. A July creator who posts in August still counts in July.

Email opens are directional because privacy protection and image blocking can inflate or hide opens. Instagram has no equivalent open event.

Product sent means Shopify says fulfilled or shipped. A paid, unfulfilled order does not count.

Current-month outcomes are immature. Compare reply rate early, but wait before judging posts or affiliates.

Message rules

Triggers, timing, messages, and suppression in one place.

Versioned rule editor

Select a rule

Changes stay local in this demo.

Active

Demo only. Production publishing would create a new Supabase rule version. The worker and Iris would both read the same published version.

How a dashboard change applies to Iris

One authority, no duplicated prompts hidden in cron jobs.

1Dashboard saves draft
2Validate variables and guards
3Publish Supabase version
4Worker + Iris reload rule
5Audit every execution