One shared surface. One trusted operator. Zero drift.
Ziel keeps a live model of your entire Revenue OS — CRM, meetings, product analytics, calendar, inbox. When you talk, dictate, or drop in a doc, the operator understands what to do across all of it, proposes the change, previews it, and waits for you.
How Ziel understands your business, remembers it, and keeps it aligned.
Ziel always knows what’s in your systems.
Continuously queries HubSpot, Gmail, Granola, Calendar, PostHog / Amplitude / Mixpanel. Keeps a fresh internal model of your workspace state — properties, pipelines, workflows, events, mailboxes. Nothing is guessed.
Every strategic decision is remembered — with rationale.
ICP shifts, pipeline redesigns, tracker changes, routing rule updates — all versioned in a living workspace brain with the WHY attached. Months later, you can ask “why is our qualification threshold at 70?” and get the real history.
One conversation moves everything downstream.
Tell Ziel you’re moving upmarket. Ziel identifies every affected part of your OS — ICP, routing, required deal properties, signal weights, sequence tone — sequences the changes, walks you through each one, and updates everything only after you accept.
Every surface. Same shape. One thing to learn.
Pipeline, deals, accounts, forecast, briefs, routing, connectors, settings — every surface in Ziel is built the same way. An artifact (the thing you're working on) in the center. The operator on the right. Talk, dictate, or drop in a doc. Watch the artifact change as you accept proposals.
┌──────────────────────────────────────────────────────────┐ │ Meridian Legal [⌘K ask, jump, or tell Ziel…] │ ← top bar ├────────────┬───────────────────────────────┬─────────────┤ │ DAILY │ │ Ziel │ │ Today │ │ │ │ Meetings │ │ You │ │ │ PIPELINE CHART │ split PLG │ │ PIPELINE │ (or Deal, Account, │ │ │ ● Flow │ Forecast, Brief…) │ Ziel │ │ Deals │ │ ⟳ reading… │ │ │ │ ⟳ checking │ │ MOTION │ │ ⟳ proposing│ │ Signals │ │ │ │ │ [proposed change · preview] │ [ your turn│ │ │ [Accept] [Revert] │ ▸ ]│ └────────────┴───────────────────────────────┴─────────────┘
Try it live at /demo/pipeline.
Propose. Preview. Accept.
Ziel never writes to your CRM without walking through the reasoning first. Every proposed change renders as a preview on the artifact. You accept, edit, or revert. Full audit trail on every action.
You tell Ziel what you want, in natural language. Ziel identifies what needs to change across your workspace — could be one field, could be six systems. It composes a structured proposal.
The proposal renders on the artifact in real time. Your pipeline chart re-draws with the new sources. Your deal card shows the new tracker values. Your forecast rolls up with the new weights. Nothing is saved yet.
Click Accept — Ziel writes the change to every affected system (HubSpot, Gmail, Slack, Ziel's own brain). Or click Revert and the preview vanishes. Every action lands in the audit log.
20+ skills. Every part of a great RevOps playbook, executable in natural language.
Each skill is a distilled operator capability — opinionated defaults, clear inputs and outputs. Invoke by clicking, by ⌘K, by ambient trigger, or just by talking. Same interaction shape every time.
- ICP Definition
- Motion Diagnostic
- Pipeline Design
- Deal Property Requirements
- Qualification Framework (MEDDPIC / BANT / SPICED)
- Routing Rules
- Signal Configuration
- Product Analytics Mapping
- Account Brief
- Deal Brief
- Deal Advice (next best action per deal)
- Follow-up Composition
- Deal Review Prep
- Notification Rule Setup
- Data Hygiene Audit
- Guardrail Recommendation
- Handoff Design
- AI Tracker Setup
- Forecast Methodology
- Risk Detection
- Pre-Meeting Digest
Modular. Bring what you already run.
Ziel doesn't build another database. It connects to whatever you already have — one tool or twelve — and keeps it clean. Tracker values write back to your CRM's custom properties. Digests land in whichever channel your team lives in. Nothing lives in a parallel system you have to keep synced. Connect one, add more later. The more Ziel sees, the sharper it gets.
Currently supported (and growing):
The operator has opinions. And limits.
Ziel only helps with GTM work — pipeline, deals, accounts, briefs, forecasts, routing. Ask it to write a birthday email and it'll redirect you warmly. This is an operator, not a general assistant.
Never writes to your CRM without walking through the why first. Every write goes through propose → preview → accept. Every action is audit-logged with the reasoning behind it.
Ziel says what it doesn't know. Doesn't agree just to agree. Doesn't invent evidence. When your data doesn't support a claim, it says so — and asks what to check instead.
Before proposing strategy, verifies the data actually exists in your systems. Won't stack a routing plan on top of a source taxonomy that isn't tagged in your CRM yet.