Cycle Conductor pairs your members — and never repeats.
A recurring-engagement engine that generates no-repeat member pairings, drafts brand-voice outreach, and renders on-brand connection pages — re-theming live across any number of tenants from a single config file. The matching is fully deterministic; the AI only writes the emails.
The live engine, in your browser.
This is the real matching logic — same cost weights, seeded randomness, odd-count doubling, and dropout repair as production. Change the inputs and run it: the same inputs always produce the same pairings.
Seven steps, every cycle.
Read the roster
Pull the current participant list and each member's pairing history from the system of record.
Score every pairing
Build a cost matrix: a repeat pairing is penalized so heavily it only happens when nothing else is left; same-org and same-region clashes carry smaller penalties.
Seed the randomness
A seeded shuffle makes tie-breaks deterministic — the same roster and history always produce the same result, so the output is reproducible.
Select pairs greedily
Walk the sorted cost list and lock in the lowest-cost valid pairings first, removing matched members as it goes.
Handle odd counts
If the count is odd, one member is doubled into a group of three rather than left out — chosen by the same rules, so nobody is dropped.
Repair dropouts
If someone leaves mid-cycle, only the affected pair is re-matched; every unaffected pair is frozen, so a late change doesn't reshuffle the whole cohort.
Draft & render
The AI layer drafts each intro email in the tenant's brand voice and renders the on-brand connection page. The matching never touched the AI.
One engine, every brand.
The same matching engine re-themes across any number of tenants from a single config file. Each tenant defines its own voice, palette, and connection-page theme — the logic underneath never changes.
Warm & editorial
Forest tones, serif voice, a calm members-first connection page.
Cool & precise
Glacial slate, technical voice, a directory-style connection layout.
Bold & brass
High-contrast accents, confident voice, a spotlight-style page.
This page shows no time-saved or ROI statistics, on purpose. Cycle Conductor's primary role is capability proof — the clearest demonstration of the ethos that AI belongs on the writing and rules belong on the matching. Any ROI figure here would be a borrowed metric from a context that isn't yours. When we scope your engagement, we model the time saved against your actual cycle cadence and headcount — real numbers, not a brochure's.
What people ask about the engine.
How does it guarantee no repeat pairings?
Every possible pairing is scored, and a previously-seen pairing is penalized so heavily that the engine only repeats a pair when there is genuinely no alternative. Because the same inputs always produce the same pairings, the no-repeat behavior is verifiable rather than random.
What happens with an odd number of members?
One member is deterministically doubled into a group of three rather than left out, so nobody is dropped from a cycle. Who doubles follows the same scoring rules, so it's consistent and explainable.
What if someone drops out mid-cycle?
Only the affected pair is re-matched. Every unaffected pair is frozen, so a late dropout never reshuffles the whole cohort — the repair is surgical, not a full re-run.
Can it serve multiple brands?
Yes — it's multi-tenant from a single config file. Each tenant defines its own brand voice, colors, and connection-page theme, and the same engine re-themes live across all of them without changing the matching logic.
Want an engine like this for your members?
Cycle Conductor is one shape this takes. If you're pairing, introducing, or rotating people by hand each cycle, the same engine can carry it — your members, your voice, your cadence, no repeats.
Start a project ↗