Product
Wizard — an autonomous sales-operations team on top of your CRM.
Five specialist variants for five revenue roles. One shared architecture. Sits on Salesforce and HubSpot; owns no data; acts only under the autonomy tier you set.
What Wizard is
Most AI copilots for revenue teams are generic. They understand "sales" in the abstract; they don't understand your ICP, your naming conventions, your attribution model, or the fact that your renewals move through the CSM and not the AE.
Wizard is different by construction. A three-layer architecture: a shared core of primitives, a substrate of your reference data (ICP, voice, playbook, product catalog, competitive set), and a family of signed skill packs — one per role. When a rep talks to Sales Wizard, they get a specialist that knows how their team sells. When a CSM talks to CSM Wizard, they get a specialist that knows how their renewals move.
Wizard learns your business at install time from your actual data — not a questionnaire. Every deployment sharpens to its environment over time, without that data ever leaving your tenant.
Five variants, five Tuesday mornings
What actually happens when Wizard runs.
Every variant has a different daily shape. Concrete examples beat taglines — here's what Tuesday 9:02 AM looks like for each seat at the table.
For reps and AEs
Sales Wizard
Works the queue a rep already has open. Prospect research, next-best-action, pipeline hygiene, attribution captured at the moment it happens.
Tuesday 9:02 AM
Tuesday 9:02 AM — a rep opens Salesforce. Sales Wizard has already triaged the 27 accounts in the queue, written one-paragraph research briefs on the three new inbound leads, flagged two deals where the economic buyer went silent, and drafted follow-up emails for each. The rep reviews, edits one, sends three, and starts their first discovery call ten minutes ahead of schedule.
For content, demand-gen, and PMM
Marketing Wizard
Drafts in the brand voice it learned from approved content. Campaign planning, lifecycle sequences, competitive positioning — grounded in your reference data.
Tuesday 9:02 AM
Tuesday 9:02 AM — the content marketer opens their editorial calendar. Marketing Wizard has drafted three blog variants against this week's topic, a lifecycle email sequence for the new segmentation that shipped Friday, and a competitive positioning brief against a competitor launch announced overnight. Each draft is in the team's approved voice, sourced from the reference library, with citations.
For RevOps, VPs, CROs
Leader Wizard
Reads the pipeline, spots the dying deals, writes the exec summary you would have written on a good Friday afternoon. Ad-hoc reporting on demand.
Tuesday 9:02 AM
Tuesday 9:02 AM — the RevOps director asks "is mid-market EMEA slipping?" Leader Wizard returns a one-page read: seven charts, the three segments driving the drift, the two reps whose forecast calls have diverged most from commit, and a draft note for the VP. No dashboard-toggling. The answer beats the question to the finish line.
For onboarding specialists and implementation consultants
Onboarding Wizard
Walks a new tenant through deployment without a consultant on retainer. 30/60/90 playbook per account, milestone tracking, stakeholder maps, risk flags.
Tuesday 9:02 AM
Tuesday 9:02 AM — the onboarding specialist has 14 concurrent accounts. Onboarding Wizard has already posted the morning stand-up digest: account 3 missed its day-30 milestone (risk flag raised), account 7's champion stopped attending meetings (stakeholder health dropping), accounts 9 and 11 hit first-value overnight (ready for CSM handoff). The specialist moves down the list in order.
For customer success and renewals
CSM Wizard
Retention signals, renewal risk, expansion opportunity. Pulls from product telemetry, support history, and the CSM's own notes — without asking the CSM to re-enter anything.
Tuesday 9:02 AM
Tuesday 9:02 AM — the CSM opens their account list of 18 renewals within 120 days. CSM Wizard has pre-scored health for each, surfaced two accounts where product usage dropped below the save-playbook threshold, drafted QBR decks for the four meetings this week, and flagged one expansion opportunity that matches a known attach pattern. The CSM approves the save-playbook fire on one account in under a minute.
Add-on modules
Stack what the team needs. Skip what it doesn't.
Four first-party modules extend every Wizard variant through a unified interface. Every module ships with real connectors and a native fallback, so nothing blocks deployment.
Product analytics
Usage signal unified across Pendo / Mixpanel / Amplitude / Heap, with a native fallback scorer.
Read the design →
Contracting
Documenso self-host + DocuSign/Adobe BYO. Typed-field templates. No injection surface.
Read the design →
People research
Prospect and account research, ICP-anchored, citations required.
Read the design →
Competitive intel
Continuous monitoring of competitors in your segment, surfaced where it belongs: your deal review.
Read the design →
Integrations
Built into the systems around the Wizard.
Salesforce
Full adapter at launch. Standard + custom objects. Read-only OAuth until HITL approves a write path.
HubSpot
Full parity with the Salesforce adapter. Covers Growth and Enterprise tiers. Same HITL posture.
Contracting
Documenso (self-hosted, primary) for Starter; bring-your-own DocuSign or Adobe Sign for Enterprise. Typed-field templates, no HTML merge.
Product analytics
Pendo → Mixpanel → Amplitude → Heap adapters, plus a Wizard-native fallback scorer. Every tenant gets usage signal.
Next step
See Wizard against your actual pipeline.
Beta walkthroughs are 30 minutes on your org. No slide decks. We'll show you exactly what Wizard sees and what it can do — then talk about whether Starter, Growth, or Enterprise fits your shape.