Workflows

Start with the sales document lane that already repeats every week.

The first win should feel practical. It should turn inquiry, quote, proposal, follow-up, or CRM handoff work into reviewed packets without asking the business to reorganize around the automation.

Review guardrails

Trigger

One inbound event starts the lane

Action

Draft, classify, route, or update

Human gate

Review stays on riskier outputs

Mars used as the workflows page hero panel image

Workflow route

Lane

Routing, follow-up, inbox, intake, or support first

Grounding

Replies stay doc-backed

Record

Updates return to the source system

Expansion

Only after the first KPI loop holds

First-lane shape

One useful loop with enough context to stay sharp.

Each workflow needs a readable trigger, a narrow action, approved source material, and a clear path back into the system that owns the record.

Inbound signal stays explicit
Drafts stay grounded on approved docs
Approvals exist before risky actions

Choose by visible drag

Choose the route by the sales drag that already repeats.

This page is for picking the route itself. If two or three lanes still feel equally urgent, the scope is not ready for a clean first build.

New inquiries arrive, but no one wants to triage them manually.

Start with lead capture and routing when the drag lives in qualification, assignment, and record creation.

Open workflow detail

Export RFQs arrive, but quote context has to be rebuilt every time.

Start with RFQ response packets when buyer requests, product notes, MOQ, certifications, and lead-time assumptions need a reviewed answer fast.

Open workflow detail

Meetings happen, but recap and next-step admin still slips.

Start with meeting follow-up when the business already has calls, notes, and a repeatable recap pattern.

Open workflow detail

The shared inbox is really a queue with no clean first pass.

Start with inbox triage when sorting, summarizing, and owner routing are the main source of drag.

Open workflow detail

Records matter, but CRM hygiene still depends on memory and cleanup.

Start with CRM discipline when note quality, field freshness, and weekly visibility keep slipping.

Open workflow detail

Best first workflow

The first lane should be frequent, legible, and safe enough to review.

Good first workflows share the same shape: one clear trigger, one owner, one bounded action, one obvious record system to update or inspect afterward, and approved material that the AI can rely on.

Usually good first

Lead capture and routing

Strong first lane for founder-led services, lean sales teams, and small operators with one obvious inbound bottleneck.

Export RFQ response packets

Strong first lane for export suppliers and technical B2B teams where RFQs repeat, product source material exists, and a human still approves price, scope, lead time, and buyer commitments.

Meeting recap and follow-up

Best for teams that already run recurring calls and want cleaner recap, action extraction, and follow-up consistency.

CRM discipline and pipeline admin

Strong for small sales teams and founder-led pipelines where visibility matters but record maintenance keeps slipping.

Not first

Money movement

Payments, payroll, refunds, or anything that executes financial changes should not be the first automation lane.

Legal, medical, or compliance judgment

High-consequence interpretation work needs tighter controls than a day-one sales desk build should carry.

Multi-team orchestration

If the workflow crosses too many owners or departments, the first lane usually becomes unreadable before it becomes useful.

No templates, no docs, no rules

If the work has no approved source material and no review rule, the business is not ready to automate it responsibly.

Choose by owner

Once the owner is obvious, the first audit usually is too.

Use this layer when the drag is real but the lane still feels too broad. Sales admin, support queue work, and internal ops carry different review edges, proof expectations, and system constraints, so the first audit should start where the owning team can actually inspect outcomes every week.

Proposals, quote context, follow-up, and CRM cleanliness

Sales document desk

The goal is not autonomous selling. The goal is a calmer sales document desk: clearer inquiry routing, export RFQ response packets, faster proposal and follow-up drafting, and cleaner pipeline records inside the systems the team already uses.

First KPI

Proposal and follow-up turnaround with qualified handoff quality

System bias

Email or form intake -> routing logic -> CRM or sheet stays authoritative

Review edge

Pricing promises, unusual requests, and low-confidence qualification remain human-reviewed.

Lead capture and routing

Export RFQ response packets

Meeting recap and follow-up

CRM discipline and pipeline admin

View team page

Shared inbox triage and SOP-grounded drafting

Support queue automation

The first support lane should narrow the queue, not hide it. We focus on triage, draft quality, and escalation visibility so the team can move faster without pretending every reply should be automatic.

First KPI

Queue response consistency and escalation precision

System bias

Shared inbox or help desk -> triage and draft layer -> ticket record stays authoritative

Review edge

Billing, policy exceptions, refunds, and sensitive account changes stay reviewed before anything leaves the business.

Shared inbox triage

SOP-grounded support replies

View team page

Intake packets, onboarding prep, and recurring record discipline

Operations handoff automation

The first ops lane should create a calmer handoff surface: a readable packet, a visible review edge, and a defined path back into the record system that the team already trusts.

First KPI

Handoff completeness and time-to-ready for the next owner

System bias

Form, inbox, or meeting notes -> intake summary and routing -> project tracker, CRM, or sheet remains authoritative

Review edge

Missing docs, unusual scope, and irreversible status changes remain reviewed before the handoff is treated as complete.

Intake and onboarding admin

CRM discipline and pipeline admin

Meeting recap and follow-up

View team page

Workflow route

The first automation lane should still feel like one route through real work.

One inbound trigger, one approval point, one update back into the system of record. If the lane needs more than that to make sense, the route is still too wide for a first automation.

signal ingrounded draftreviewrecord update

Route matrix

A first workflow should read like one route through repeated work, not a miniature platform.

The useful pattern is stable: one signal arrives, one draft or routing action happens, one review edge remains visible, and one source system keeps the final record.

signal in stays explicit

review edge stays visible

record update stays narrow

exceptions stay separate

Thirty-day pattern

Every viable first lane should still move through the same four checks.

The lane can look different by department, but the operating rhythm does not change much: define the route, connect the source systems, test the risky edge, then keep or narrow the lane based on visible week-four evidence.

Week 1

Audit the workflow, confirm the owner, and establish the KPI baseline and no-go line.

Week 2

Build routing logic, prompts, and the first system connections with narrow permissions.

Week 3

Test edge cases, approvals, and exception handling against real business examples.

Week 4

Go live, review what failed or needed approval, and decide whether the KPI loop justifies continuation.

Full lane list

Only compare the full catalog after the owner and drag are already clear.

This is the decision shelf, not the starting point. Once you know where the repeated complaint sits and who reviews the outcomes, use the detailed lane cards below to decide what should go into the sales desk audit.

What the audit should settle

Which workflow lane hurts enough to justify a first build

Which system stays authoritative after every automation step

Which reviewer blocks low-confidence or risky outputs

Which KPI proves the lane earned a second month

Forms, inbox, and new inquiry flow

Lead capture and routing

Take new inquiries from forms or inboxes, classify the request, capture the important fields, and hand the lead to the right owner with a usable summary.

First KPI

First-response time and qualified handoff rate

System pattern

Form or inbox -> summary and routing logic -> CRM or spreadsheet record

Review edge

Human review stays on low-confidence qualification, unusual requests, and outbound promises.

Qualification summary
Owner assignment
CRM or sheet update

Open workflow detail

Supplier inquiries, quote context, and buyer follow-up

Export RFQ response packets

Turn overseas buyer RFQs, product notes, certifications, MOQ, lead time, and past answers into a reviewed quote-response packet before the thread goes cold.

First KPI

RFQ-to-reviewed-response turnaround and completeness rate

System pattern

RFQ email or form -> buyer/request summary -> quote context packet -> reviewed follow-up and CRM or sheet handoff

Review edge

Humans approve pricing, lead time, product fit, certifications, commercial terms, and any commitment before the buyer receives it.

RFQ field summary
Quote context packet
Follow-up and CRM handoff

Open workflow detail

Sales and delivery admin

Meeting recap and follow-up

Turn notes, promises, and next actions into recap drafts, owner tasks, and clean follow-up messages instead of another manual chase.

First KPI

Follow-up sent within one business day

System pattern

Meeting note or transcript -> recap and task draft -> CRM, docs, or project tracker

Review edge

Humans approve any commercial commitment, pricing statement, or edge-case response before it leaves the business.

Call summary
Follow-up drafting
Next-step task capture

Open workflow detail

Inbox admin and first-pass routing

Shared inbox triage

Classify repetitive inbound requests, surface the right operating context, and hand the item to the correct human or queue without losing the thread.

First KPI

Time to first triage and queue accuracy

System pattern

Inbox message -> category and summary -> owner or queue assignment

Review edge

Humans still handle escalations, unusual policy questions, and anything with unclear intent.

Inbox classification
Context summary
Queue or owner routing

Open workflow detail

Updates, notes, and weekly visibility

CRM discipline and pipeline admin

Keep fields, notes, and statuses current so the pipeline reflects what happened without forcing a founder or rep to do cleanup in batches.

First KPI

Pipeline freshness and note completion rate

System pattern

Call notes or activity feed -> structured recap -> targeted CRM updates

Review edge

Humans still approve stage changes, commercial commitments, and any update sourced from low-confidence notes.

Field updates
Weekly summaries
Cleaner pipeline state

Open workflow detail

Admin routing and handoff execution

Intake and onboarding admin

Convert raw submissions into a ready-to-work packet, route it to the next queue, and make the handoff legible for the human who receives it.

First KPI

Time from submission to ready-to-work handoff

System pattern

Form or inbox intake -> structured packet -> queue handoff and status update

Review edge

Humans still confirm unusual cases, missing details, and any handoff that changes scope or cost.

Structured intake
Queue routing
Handoff notes

Open workflow detail

Support, onboarding, and policy-backed answers

SOP-grounded support replies

Ground draft replies on approved documents, service notes, and policies so support stays faster without becoming generic or unsafe.

First KPI

Draft turnaround time and escalation accuracy

System pattern

Inbound support request -> grounded draft and escalation decision -> help desk or inbox record

Review edge

Humans still approve edge cases, sensitive claims, refunds, and any answer outside approved policy.

Doc grounding
Escalation path
Human signoff on edge cases

Open workflow detail