OpenProse
GitHub1.2k
Browse outcomes/Write

AUTHOR NEW OUTCOME

Write the future as a sentence.

Write one outcome the system can judge true or false.

Draft sourcedrafts/trial-follow-up-loop.prose.md
01Sentence

Every qualified new trial account gets a useful follow-up before the buying window closes.

02Contract

Goal, continuity, requirements, and ensures become source.

03Review

Judge, fulfillment, triggers, and preflight stay inspectable.

DRAFT CONTRACT

Sentence to source

Mocked
drafts/trial-follow-up-loop.prose.mdworkspace/growth
---
name: trial-follow-up-loop
kind: responsibility
---

# Trial Follow-Up Loop

### Goal

Every qualified new trial account gets a useful follow-up before the buying window closes.

### Continuity

- New qualified trials should not pass the buying window without useful follow-up.
- Follow-up should stay grounded in current product behavior and account context.
- Duplicate outreach should be prevented unless new evidence changes the account's fit.

### Requires

- A connected mailbox that can send and read delivery history.
- A CRM source for trial qualification, owner, stage, and activity history.

### Ensures

- Each qualified trial has a useful follow-up before the buying window closes.
- The judge can cite the account, message, timing, and receipt for every pass.
- Missed, duplicated, or stale follow-ups become drift that OpenProse can repair.

REVIEW THE MACHINERY

Only the parts that affect the outcome.

JUDGE PLAN

How OpenProse judges true

Mocked

  1. Read qualified trial accounts created in the last business day.

  2. Confirm each account has one useful follow-up before the buying window closes.

  3. Flag drift when a qualified trial lacks a sent message, owner, or CRM note.

  4. Treat duplicate outreach as false unless new evidence changes fit.

FULFILLMENT PLAN

How OpenProse repairs false

Mocked

  1. Enrich account context from CRM, product usage, and public company metadata.

  2. Draft a short follow-up tied to the trial's first active behavior.

  3. Send through the connected mailbox only after dedupe and owner checks pass.

  4. Write the outcome receipt back to CRM with message id and judge evidence.

TRIGGERS

Events that can change truth

Mocked
New qualified trialStarts a run when lifecycle stage becomes qualified trial.
CRMCRM webhook
Buying window checkFinds accounts that are approaching the follow-up deadline.
CRONEvery business morning
Reply or bounceUpdates receipts so the judge has current delivery state.
GMAILMailbox event

CONNECTOR PREFLIGHT

Only what this outcome needs

Mocked
GmailNeeded to send useful follow-ups and avoid duplicates.
send mailread message history
Missing
CRMNeeded to find qualified trials and record receipts.
read trialswrite activity
Missing
StripeUseful when billing state becomes the source of qualification.
read trial status
Optional later

Connector setup opens with hosted authoring. Until then, this preflight is a static preview.

This preview is static until hosted authoring opens. Join the list and we will turn this sentence into a running outcome when the launch path is ready.