Start with the outcome.
Learn the system as you go.

What do you want Invice to handle?

You did not sign up to learn our nouns. You signed up because something keeps slipping: a lead going quiet, a document never sent back, a renewal creeping up unwatched. Start from the thing you want off your plate. The concepts will introduce themselves along the way.

Your first mission, start to sent.

One connected inbox, one clear goal, one approved send. About five minutes, and every screen named below is the real one. Nothing reaches a client until you approve it, so there is no way to break something by trying.

A faithful still of Step 1 in the real mission wizard: the goal in plain language, and the Stack and Vault rows underneath it scoping the apps this mission may act through and the documents that ground it.

Where step 7 ends: the drafted send waiting in your approval queue.

The minimum a workflow needs.

Strip any Invice workflow to the studs and four things remain. If you can answer these four questions about a piece of work, you can build it here, whatever the industry.

The learning path.

Nothing on this page is required on day one. This is the order that works. Each tier links to its chapter below, and everything past the first column can wait until the simple version is running.

Six proven patterns.

The building blocks combine into an endless range of workflows. Here are six proven shapes to build from, or fork whole from the Marketplace. Each names the pieces it leans on and how far up the learning path you should be before reaching for it.

You compose Invice. You don’t code it.

You have already met the four ingredients: outcome, context, authority, stop condition. Here is the same model in Invice’s own nouns. Every workflow is built from the same small set of parts. You brief a Mission with a Goal in plain language and the Guardrails it must never cross. You choose which Blocks that mission shows, connect the outside systems it should act through, and the agent plans and runs the steps between, returning to you only for the decisions that are genuinely yours.

For a process you repeat across many clients, you wrap it in an Operation. To make work start on its own, you add Triggers. Once a mission is shaped the way you like, you save it as a Playbook and reuse it, or publish it to the Marketplace for other professionals to run. That is the whole model. The rest of this guide is depth on each part.

Missions

A Mission is one job the agent owns end to end, usually for one client. You brief it like a teammate, and it works the job from first contact to done, proposing actions and waiting for your approval by default.

›The lifecycle

The four ingredients you write are the input. The lifecycle is what the agent does with them, and every mission moves through the same six phases. You are only pulled in at Escalate.

›The four shapes

Most missions are a variation on one of four shapes. Naming the shape helps you write a tighter brief.

Operations

An Operation is the parent that runs one process across your whole book of clients. It never executes on its own. It holds the shared brief, a goal template with placeholders like [CLIENT NAME], the pipeline stages, the connections, the vault documents, and the rules. When a new client arrives, by hand or by inbound email, the operation spawns a child mission that inherits all of it.

Blocks

Every mission has a rail of Blocks, the panels that make up its workspace. A recruiting mission and a mortgage file need different surfaces, so you add the blocks the work needs and drop the ones it does not. You choose once, per mission or per workspace, and it holds.

Adding a block is one choice on the mission’s right rail. The set you pick is part of what a Playbook captures, so a shared workflow arrives with the right surfaces already on.

Goal & guardrails

The brief is two parts. The goal is the outcome you want, written like a note to a teammate. The guardrails are the lines the agent will not cross, kept in their own block so they hold on every single action rather than getting buried in the goal.

Writing a good brief

The agent builds the steps. Your job is to be clear about the outcome and the limits. A few habits make the difference between a mission that runs itself and one that keeps asking.

Triggers

A Trigger is a rule that starts work on its own: on a schedule, on a time-based condition, or on an inbound event. You write it in plain language and Invice turns it into a precise, structured rule. When it fires it either flags you, launches a mission from a goal template, or calls a connected tool.

Connection methods

Invice acts through the systems you already use. There is no fixed integrations list to wait on. Instead there are a handful of open ways in, and almost every tool fits one of them. Here is what connects today, and what is on the way.

The Data map

The Data map is the block where you line up an Invice field with a field in a connected system, and name the source of truth. Your Email to Salesforce Contact.Email, your Stage to its Opportunity stage. For each pair you say who wins when the two differ, and whether Invice reads it, writes it, or both.

Today the map is declared connection context the agent can use when reasoning about fields, source-of-truth rules, and connector schemas. Live scheduled two-way sync and universal write enforcement are on the roadmap.

The safety model

Openness only works if it is safe by default. Three rules hold across every connection.

Agent Gateway

The Agent Gateway puts one governed agent on your own website with a single embed tag. Visitors chat with it. It answers only from the vault documents you switch on, proves who is real on both sides, captures interest the moment it appears, and hands off to a person when asked, with a subtle Invice Gateway Agent trust label.

Agent-to-agent

Two Invice professionals can partner their agents. A partner’s agent sends yours a structured ask, a question, and it lands in your triage. Nothing runs on its own. You approve every answer. Neither side can read the other’s data, and either side can cut the connection instantly.

Each workspace publishes a public agent card, a business card for its agent. Full end-to-end negotiation, where both agents settle a question between them, is on the roadmap.

Playbooks

A Playbook is a mission or operation, with its goal, its blocks, and its rules, saved as one reusable template. Capture is always private first. You publish only when you choose to, and client details are stripped before anything goes public.

The Marketplace

The best Playbooks come from people doing the real work. The Marketplace is where they live: proven client-facing workflows, published by other professionals, ready to browse, fork, and run in your own workspace. Build one that saves you an hour a day, publish it, and it saves the next professional the same hour.

Vocabulary

Invice speaks its own business language by default. If your team lives in a CRM, switch to CRM standard in Settings and every label becomes the term you know. It is a display skin only, applied per workspace. Nothing about your data changes.

Connections

Triggers

Stop conditions: until replied, until a date, or after a maximum number of tries.

Roadmap

What is shipped, and what is planned. Nothing here is aspirational dressed as done.

›Shipped

›Planned