Consul Product Vision

One-Sentence Definition

Consul is an AI executive assistant that closes coordination loops across every channel and tool a professional uses, earning autonomy through trust, and scaling from individual operator to organizational platform.

The Core Belief

The bottleneck for busy professionals is not information. It is follow-through.

Every day, capable people lose hours to work that surrounds the work: scheduling meetings, triaging email, drafting replies, tracking commitments, remembering context, and following up on things that should not require their attention. The tools they use organize this work. They do not finish it.

Consul exists to finish it.

The product is built on a single operating principle: a loop is only closed when the real-world outcome happens and no further user attention is required. Drafts, summaries, reminders, and suggestions are not closed loops. Sent emails, confirmed meetings, completed follow-ups, and resolved commitments are closed loops.

Consul crosses the line from awareness to action.

What Consul Is

Consul is three things at once, delivered as one product.

An AI Executive Assistant

Consul is a personal executive assistant for people who would never hire a human one. It learns how the user works, operates across their existing tools, stays available across every channel they use, and executes coordination work on their behalf.

It is not a chatbot. It is not a search engine with a conversational wrapper. It is not a workflow builder. It is an assistant that takes ownership of the coordination tax professionals pay every day and gives them back the hours.

A Productivity Suite

Consul is also the workspace where professionals manage their operational life. Calendar, email, personal CRM, meeting recording and notes, scheduling, and contact management live inside one system with full awareness of each other.

This is not a dashboard that sits on top of disconnected tools. It is a unified operating environment where every surface shares context: the calendar knows the contacts, the email knows the calendar, the CRM knows the conversations, and the assistant knows all of it.

A Platform

Consul is the management layer for deploying, configuring, and controlling AI assistants across an organization. Administrators assign assistants, define what tools and data each assistant can access, monitor activity, manage billing, and enforce policies — all from a single control plane.

Who Consul Is For

Consul is built for professionals whose days are driven by meetings, relationships, inbox coordination, and scheduling. The product serves anyone with meaningful coordination load, including founders, executives, consultants, operators, fractional leaders, salespeople, and chiefs of staff.

The common thread is not job title. It is operating pattern. Consul is for people who spend too much of their day on communication logistics and not enough on the work that actually matters.

The ideal Consul user:

• Has a calendar full of meetings with different people and different contexts
• Manages relationships across multiple threads, tools, and stakeholders
• Loses time to scheduling back-and-forth, inbox triage, and follow-up tracking
• Needs coordination to be reliable, not just faster
• Would benefit enormously from an assistant but has never hired one

The Problem

Modern professional work is fragmented. Calendar lives in one place. Inbox lives in another. Relationship context is scattered across tools. Follow-ups are easy to lose. Meeting prep is manual. Scheduling is repetitive. And every AI tool on the market adds another place to check instead of removing something from the list.

The result is that busy professionals carry an invisible coordination burden that compounds throughout the day. Every open thread, unresolved commitment, and pending follow-up occupies cognitive bandwidth even when it is not actively being worked on.

Current tools do not solve this. Productivity suites lack agentic capability. AI-first apps feel magical at first, then fall flat because they stop at suggestion. No system pairs traditional work tools with a true AI executive assistant. And so professionals are left duct-taping their own stacks together and still feeling behind.

Consul solves this by collapsing the coordination layer into a single intelligent system that knows who matters, what is coming up, what needs a response, and what should happen next — and then acts on it.

How Consul Works

Channels: Meet the User Where They Are

Consul is channel-native. It operates as a full assistant surface in every channel the user already works in.

• Web and desktop — the full-fidelity experience with complete suite access, settings, and visibility
• iMessage and SMS — quick delegation, approvals, and conversational task handling
• WhatsApp — the same assistant, wherever the user's messaging lives
• Slack — team-integrated coordination and delegation
• Email — Consul has its own inbox and email address, enabling external parties and the user to interact with the assistant directly by email

Every channel is a first-class surface. There is no primary interface. The user works wherever they are, and Consul is already there.

Tools: Operate Across the Entire Stack

Consul is tool-agnostic. It integrates deeply with the systems that define a professional's workflow and operates across them as a single coordinated layer.

Core integration surfaces include:

• Email — read, triage, draft, send, label, archive, and follow up across the user's inbox. Consul understands writing style, detects action items, resolves recipients, and handles automated triage.
• Calendar — manage events, resolve conflicts, check availability, respect time preferences and buffers, and negotiate scheduling. Consul does not just add events; it handles the full scheduling workflow including multi-turn negotiation with external parties.
• Contacts and CRM — maintain a living relationship layer that starts as a lightweight enrichment of contacts and communication history and grows toward full CRM capability with pipelines, relationship scoring, and interaction timelines.
• Documents and files — search, create, move, share, and manage files across cloud storage and document systems.
• Meeting intelligence — Consul builds and owns its own meeting recording and note-taking capability, capturing what was discussed, extracting action items, and feeding meeting context back into the assistant's reasoning.
• Messaging platforms — read channels, fetch threads, send messages, and bridge communication context across team tools.
• Reminders — a dedicated system for commitments and follow-ups, distinct from calendar events, so nothing falls through the cracks.
• Connected third-party tools — expense management, travel, project management, and any other system the user connects. Consul treats every integration as another surface it can act on.

The vision is not to privilege any single ecosystem. Consul works across Google, Microsoft, Apple, Slack, Zoom, and whatever tools the user has. The more systems connected, the more valuable the assistant becomes.

Skills: Agentic Automation Through Natural Language

Consul does not make the user build automations. It does not expose a workflow builder, a drag-and-drop canvas, or a rule engine.

Instead, Consul treats automation as natural language skills that combine connected tools, events, and behavior to handle recurring work. Skills can be:

• Configured by the user — described in plain language. "When I get a receipt by email, add it to Expensify." "Every morning, summarize my unread marketing emails and archive them." "When someone RSVPs to a meeting, send them the agenda doc."
• Inferred from connections and behavior — Consul observes how the user works and suggests skills based on repeated patterns. If the user always forwards a specific type of email to the same person, Consul can learn to handle that.
• Inherently agentic — skills are not static triggers and actions. They are intelligent behaviors that use the assistant's full reasoning, context awareness, and tool access to complete work. A skill can involve multiple steps, decisions, and tool interactions without requiring the user to specify the logic.

This is the difference between a workflow platform and an assistant. A workflow platform makes the user think like a programmer. Consul makes the assistant think like a person.

The Daily Brief: Intelligence, Not Digests

Every day, Consul synthesizes the user's calendar, inbox, reminders, contacts, meeting history, and relationship context into a single decision-oriented briefing.

The daily brief is not a list of events and unread emails. It is an intelligence product that tells the user who matters today, what is urgent, what is connected, what needs a response, and what the day structurally looks like.

This is chief-of-staff behavior. It is the kind of work a great human assistant does in the first thirty minutes of the day — except Consul does it automatically, every day, and delivers it through whichever channel the user prefers.

Trust and Autonomy

The Trust Model

Consul earns autonomy. It does not start with it.

The product draws a hard boundary between read actions and write actions. Read actions — checking the calendar, scanning the inbox, looking up a contact — happen automatically. Write actions — sending an email, booking a meeting, sharing a file, messaging someone — require approval until Consul has earned the right to act independently.

This is not a limitation. It is the core product mechanic.

Earned Autonomy

Over time, Consul graduates to greater independence through a clear autonomy model:

1. Supervised — Consul proposes actions and waits for explicit approval before executing anything externally visible.
2. Trusted — after consistent approvals in a given domain, Consul can act and notify the user afterward. The user sees what happened and can correct course.
3. Autonomous — for well-established patterns where Consul has proven reliability, it acts independently. The user is always able to review, but does not need to.

Every approval and correction improves the system. Trust compounds. The more the user works with Consul, the more it learns their preferences, communication style, priorities, and judgment — and the more it can do without asking.

This creates a flywheel: usage builds trust, trust unlocks autonomy, autonomy saves more time, saved time drives more usage.

Safety as a Product Feature

An assistant that can send emails, book meetings, share files, and message people on the user's behalf must earn trust through discipline.

Consul makes risk visible. Important actions are previewed before execution. Write operations can be suspended for review. The user always sees what the assistant is about to do and can approve, edit, or reject. The system never silently mutates state on consequential actions unless the user has explicitly graduated that category to autonomous.

Trust is not a constraint on the product. Trust is the product.

The Three Stages

Stage 1: The Assistant

The core AI executive assistant that closes coordination loops across email, calendar, and messaging. This is the wedge: prove that Consul can reliably handle the most painful, visible, high-stakes coordination work — scheduling, inbox triage, drafting, follow-through — with enough trust that professionals delegate real work to it.

The assistant operates across all channels, connects to the user's existing tools, and delivers the daily brief. Skills and automations begin to learn user behavior. Autonomy graduation begins.

Stage 2: The Suite

The assistant expands into a full productivity workspace. Calendar management with AI-assisted conflict resolution. An integrated email client. Personal CRM with relationship scoring and enrichment. Built-in meeting recorder and note-taking. Scheduling links and public booking. Desktop and mobile applications.

The suite is not a replacement for existing tools by force. It is a better environment that earns adoption because the assistant works best when the user works inside it. Every surface in the suite shares context with every other surface, and the assistant has deeper visibility into everything.

Stage 3: The Platform

Consul becomes organizational infrastructure. Multi-assistant deployment across teams and companies. An admin dashboard for managing agents, users, skills, and permissions. Full access controls and policies. Audit logs and compliance. Consumption-based billing with organizational oversight.

At the platform stage, an organization can deploy specialized assistants — an executive EA, a team scheduler, a recruiting coordinator — each with defined tool access, data boundaries, and behavioral policies. The platform manages all of them.

The Business Model

Consul operates on a hybrid billing model: a base subscription that provides access to the assistant, suite, and platform capabilities, plus consumption-based usage for the agentic work Consul performs on the user's behalf.

This model aligns cost with value. Light users pay less. Power users who delegate heavily pay for the work being done. Organizations scale billing with actual usage rather than seat count alone.

The Moat

The Graph

The assistant is what the user touches. The graph is what the company owns.

Every interaction builds a richer model of the user: their preferences, priorities, communication style, relationship hierarchies, operational patterns, and recurring workflows. This graph makes Consul more useful over time and makes switching to a competitor mean losing an assistant that already knows exactly how the user works.

Cross-Tool Breadth

Every additional integration gives Consul more surface area to act. A scheduling assistant that can also check email, pull files, and message on Slack is categorically more useful than one that only touches the calendar. Integration breadth creates compounding value that narrows as competitors remain tool-specific.

Trust Compounds

Autonomy graduation means that long-tenured users have an assistant that operates with minimal oversight. New users start from scratch. This creates a retention mechanic rooted in earned capability, not switching costs.

Skill Network Effects

Every skill built for one user becomes available to all. Someone needs travel booking — now everyone has it. Someone needs receipt management — now everyone has it. The more people use Consul, the more it can do for everyone.

The Competitive Landscape

Consul occupies a unique position at the intersection of three established categories.

Against general AI assistants (ChatGPT, Claude, Gemini): they suggest, Consul acts. They tell the user what to do. Consul does it.

Against suite copilots (Microsoft Copilot, Google Gemini, Apple Intelligence): they optimize within their own ecosystem. Consul closes loops across the entire workflow, regardless of vendor.

Against scheduling and inbox tools (Calendly, Superhuman, Spark): they optimize one surface. Consul operates across all of them with shared context.

Against automation platforms (Zapier, Make, n8n): they make the user build automations. Consul owns the outcome.

Against point-solution AI agents: they solve one kind of loop. Consul is a general coordination assistant that handles the full range of professional coordination work.

Consul's differentiation is not a single feature. It is the combination of channel-native presence, cross-tool operation, agentic skills, earned autonomy, and a unified productivity suite — delivered as one coherent assistant experience.

The Vision

Every professional deserves an AI executive assistant that knows their world, works through their existing tools, operates across every channel they use, closes coordination loops with real-world outcomes, and earns trust by making every consequential action visible and reviewable.

Consul is that assistant.

It starts where action matters and success is legible. It earns trust through reliable execution. It expands from assistant to suite to platform. It builds a graph of how the user works that makes the product smarter every day.

The long-term ambition is not another productivity app, another chatbot, or another workflow builder. It is the operating layer between intention and action — the system that takes ownership of coordination work so professionals can focus on the work that only they can do.

Delegate the work. Keep the control.