Blueprint
Cycle-aware re-engagement engine
The full Cuely operating spec is now packaged as a markdown source document with segment timing logic, onboarding flow, response handling, and all 18 ready-to-use client emails.
Segment Logic
Six segment configs with explicit trigger definitions, timer anchors, reset rules, and 2x-window escalation behavior.
18 Email Templates
Three real templates per segment: initial check-in, no-response follow-up, and a longer-gap low-pressure touchpoint.
Onboarding Flow
A five-step setup flow covering segment selection, imports, timer assignment, email preview, and go-live confirmation.
Engine Rules
Cycle detection starts from project completion, resets on new work, tracks positive replies, and surfaces high-value silent clients.
Segment Timers
Timing by creative segment
Cuely schedules the first check-in at the start of each segment window, then follows up at +7 and +14 days. If the client stays silent through 2x the normal window, Cuely sends a final low-pressure note and moves them to manual review.
| Segment | Window | Initial | Follow-ups | 2x Window |
|---|---|---|---|---|
| Wedding Photographers | 10-11 months | Day 304 | Day 311, 318 | Day 670 |
| Motion Designers | 60-90 days | Day 60 | Day 67, 74 | Day 180 |
| Podcasters / Audio Producers | 30-45 days | Day 30 | Day 37, 44 | Day 90 |
| Graphic Designers | 60 days | Day 60 | Day 67, 74 | Day 120 |
| Video Editors | 45-60 days | Day 45 | Day 52, 59 | Day 120 |
| Animators | 90 days | Day 90 | Day 97, 104 | Day 180 |
What's Inside
Deliverables in the spec
The markdown file includes a shared data schema, detailed trigger-event definitions for all six segments, reset conditions, escalation rules, and onboarding requirements.
It also includes every email template Cuely needs for MVP: one initial re-engagement email, one no-response follow-up, and one "been a while" email per segment.
Response tracking rules cover positive, neutral, and negative replies, plus a recommended way to flag high-value silent clients without making the engine overly complex in the first release.
Use It
Source-of-truth markdown
The raw document is meant to be implementation-ready. Product, design, and engineering can all work from the same file without translating the rules first.
View the full spec