SYSOISYSOI Run it on your event

The product

Five layers. One throughline. Every signal in real time.

SYSOI runs five owned-IP modules end-to-end across the event lifecycle, each one feeding the next. Define the strategy. Unify the data. Watch for drift. Score readiness. Score content. The whole stack is live, grounded by the Sandbox Brain, and built modular from day one.

Event Brain · North-Star

Define the event once. Measure everything against it.

Every SYSOI event starts with a North-Star — goals, KPIs, target audience, brand voice, key themes. Draft it from a brief with AI, rebuild it from your website, or paste in your existing strategy doc. Once it's set, every downstream layer is measured against it.

How it works. Opus drafts the North-Star from a brief or scrape, then writes it to a versioned profile. Every signal the Consistency Engine emits, every CFP score Marquee returns, and every readiness model the scoring layer runs reads from this profile. When the North-Star changes — a pivot to a different KPI, an audience refocus — every downstream signal re-scores against the new truth.

Connectors: Web scrape via ForgeScrape; document upload (PDF / Markdown / text); manual brief.

[ North-Star screenshot ]
North-Star profile · versioned · live

Unified Record · Golden Record

Six tools' worth of attendees. One sales-ready record.

Connect your registration platform, your matchmaking tool, your mobile app, your lead capture, your CRM. SYSOI resolves identity across all of them — deterministic on email and phone, probabilistic on name and domain — rolls contacts up to accounts, advances the lifecycle stage from registered through meeting-held to opportunity, and enriches every registrant with real firmographics from LinkedIn.

How it works. Each provider pushes (webhook) or is pulled (REST) into one canonical adapter. The adapter resolves identity, applies survivorship (email is identity-anchor; name/title are last-write-wins so a CRM correction propagates), and lands the row. Re-imports refresh, never stack — the lifecycle-state engagements are unique per (contact, event). The record gets cleaner the more tools you connect, not messier.

Connectors: Sandbox-GTM (owned, live), RainFocus (built), HubSpot (live, two-way), Salesforce (connected), Attio (handoff live), Mailchimp (live), Cvent (live, self-hosted OAuth), Google Sheets (live), Excel / CSV (live).

[ Records · identity resolution ]
229 of 230 contacts enriched · 1 day ago

Consistency Engine · Forensic drift signals

A forensic analyst watching your event. Not a chatbot.

SYSOI's Consistency Engine reads the live unified record against your North-Star and emits drift signals across five dimensions — KPI, audience, voice, content, context — with severity ratings, evidence cited inline, and a recommended fix. Every signal is human-reviewed. Every dismissal teaches the system what to ignore.

How it works. Opus runs a forensic scan over a structured snapshot of the event (goals, KPIs, audience composition, session content, brand voice). Outputs are typed signals with severity (info / warn / critical), evidence (the data point that triggered it), and a recommendation. The reviewer queue is human-in-the-loop: acknowledged signals stay open; dismissed signals write to the per-tenant playbook so the same false positive doesn't recur. The Brain-First Protocol weighs prior patterns and prior mistakes before reasoning.

[ Consistency · signals queue ]
5 open · 2 critical · last scan 14m ago

Sales Readiness · Engagement-weighted scoring

Every attendee scored. Every score auditable. Every hot contact handed off.

SYSOI scores every contact's sales readiness from the live engagement stream — lifecycle stage, engagement intensity, recency, ICP fit, meeting outcome, session-cluster bonus. Every score carries its math. RevOps can audit every number. Hot contacts hand off to HubSpot or Salesforce with an AI-generated mini-dossier stamped on the record.

How it works. Scoring is deterministic and additive: lifecycle stage base (registered = 5, meeting_held = 75) + engagement kind weights + recency decay + ICP fit + meeting-outcome modulation (from the post-meeting survey via the connector). Session attendance is track-aware: relevant tracks × dwell-ratio multiplier, with a topical-cluster bonus when an attendee hits three sessions on the same track. The handoff push upserts by email into the CRM, self-provisions the four sysoi_readiness_* custom properties, and stamps an AI-written ≤110-char dossier so the AE sees the load-bearing context at a glance.

Connectors: HubSpot (live, full loop incl. inbound contact sync + last-touch attribution + back-stamp), Attio (handoff live), Salesforce (connected).

[ Readiness · handoff push ]
Brian Morgan · 100 hot · handed off to HubSpot · meeting_held → opportunity

Marquee · CFP fit

Score every session against the event's strategy. With the deck.

Marquee scores every CFP submission, every track topic, and every speaker against the event's North-Star themes, audience ICP, and brand voice — additive math across pillar alignment, audience fit, strategic fit, technical depth, voice fit, and delivery readiness. Upload the actual presentation deck and SYSOI re-scores against what's built, not what's promised.

How it works. Sonnet runs a fixed-additive rubric (six capped factors → 0–100) over each submission. Rationale is the recommendation — accept, accept with revisions, decline. Deck-grounded re-score attaches the PDF as a Claude document and re-evaluates technical depth, voice fit, and delivery readiness against what's actually built. Promote-to-sessions one-clicks accepted submissions into the live agenda the Consistency Engine reads.

[ Marquee · scorecard ]
CFP scored · deck-grounded · accept

Run it on your event

Bring a past event. We'll show you what it actually generated.