Omni × Brain Forge — Trial vs. implementation (one-pager outline)
Audience: Omni AEs, SEs, and CS; optionally customer economic buyer.
Purpose: Set expectations so trial length matches scope and reps know when to bring Brain Forge in as implementation partner vs. a light assist on a standard Omni trial.
Status: Outline — turn into designed PDF / Google Slides using your brand templates.
Headline options (pick one)
- Two ways to win with Omni + Brain Forge: 2-week pilot vs. implementation track
- Match the motion to the buyer: Omni trial vs. Brain Forge implementation
Above the fold (5 bullets max)
- Omni proves value fast in the product; Brain Forge shortens time-to-trust on data, semantics, and AI workflows sitting behind Omni.
- Standard Omni trial: validate product fit with a bounded scope — often ~two weeks when warehouse access, owners, and use cases are already clear.
- Brain Forge + Omni implementation track: used when the buyer needs discovery, modeling, pipelines, or agent/workflow build — typically 4–8 weeks to first production-grade outcome (can overlap with Omni trial/sandbox with explicit success criteria).
- Rule of thumb: If the customer cannot name warehouse access, metric owners, and 1–2 priority questions before day 1, do not promise a 2-week path to full implementation — start with prep week(s) or the implementation track.
- For AEs: We give you a single intro line and a qualification checklist so your customer hears one coherent story.
Section: “2-week value pilot” (Omni-led, Brain Forge optional)
Best when
- Warehouse (or agreed source) and read access are available or scheduled within days.
- Owner for metrics/definitions is assigned.
- 1–2 use cases are scoped (e.g. executive KPIs, one operational workflow, one self-serve slice).
What “good” looks like at day 10–14
- Omni connected to agreed sources; 3–5 canonical questions answered in the UI or agreed artifacts.
- Success criteria written on day 1 and reviewed on day 7 (adjust or declare implementation track).
Brain Forge role (light)
- Office hours, semantic/metric alignment, prompt/workflow patterns — not net-new pipeline build.
What we explicitly do not promise in 2 weeks
- Full semantic layer from scratch, heavy ETL, multi-team data discovery, or custom agent productionization.
Section: “4–8 week implementation track” (Omni + Brain Forge joint)
Best when
- Discovery is still open (sources, definitions, politics, security).
- Multiple stakeholders or net-new data work is required.
- Buyer wants Omni + AI/automation tied to governed metrics and workflows.
What “good” looks like
- Agreed phase 1 dashboards/questions/workflows live; handoff doc for customer team; Omni remains the front door for analytics.
Brain Forge role (primary)
- Discovery, implementation sprint, documentation, enablement; tight loop with Omni SE/AE.
Reference deals (internal — name only if approved externally)
- Elements, Eat in Health: longer cycles reflected scope (discovery + build), not product drag.
Section: Qualification checklist (for AEs — copy into CRM note)
| Question | If “no” or “unknown” |
|---|---|
| Is warehouse / primary source identified and is access realistic in <1 week? | Prefer prep or implementation track |
| Is there a single accountable owner for metrics/definitions? | Schedule stakeholder alignment first |
| Are 1–2 use cases written in one sentence each? | Joint scoping call before trial start |
| Is this mostly “connect and explore” or build net-new data/AI? | Explore → 2-week pilot; build → implementation track |
| Does customer expect production outcomes inside 2 weeks? | Reset to implementation track or narrow scope |
Section: How to introduce Brain Forge (email snippet for Omni reps)
We’re bringing in Brain Forge as our implementation and AI partner for this account. They’ll help us get from connected data to trusted answers in Omni faster — especially when we need metric alignment, workflows, or a scoped build, not just a product trial.
On this deal we’re running [2-week pilot | 4–8 week implementation] so expectations stay aligned.
Section: Call to action
- Omni: [Name] — book 30 min with Brain Forge on [link] for deal qualification and motion selection.
- Brain Forge: [Name] — single owner per opp; respond within 1 business day on AE threads.
Design notes (for whoever lays this out)
- One visual: two tracks (timeline bars: 2 weeks vs. 4–8 weeks) with overlapping “Omni trial” where applicable.
- Footer: Omni + Brain Forge logos; link to partner control center / internal hub (internal version only).
Copy for Max (follow-up — edit names/links)
90-day goal (one sentence, if you want it in writing):
We want the next ninety days to be about one joint motion: a clear 2-week Omni pilot path when scope is tight, and a 4–8 week implementation track when discovery and build are real — so your customers and our team hear the same story and we earn more implementation intros from Omni.
Short message:
Hey Max — following up on our chat about cycle length on the Omni + BF deals. I’m formalizing a trial vs. implementation one-pager and qualification checklist for your team so a standard 2-week trial doesn’t get conflated with a heavier build (like we saw on Elements / Eat in Health).
Can we do 30 min this week to pressure-test the framing and pick 1–2 live opps to pilot it? If there’s someone on your side who owns partner / rep enablement, happy to loop them in so this lands where reps actually work.