Sales and delivery admin / workflow lane

Convert meetings into action before the thread goes cold.

This lane fits when calls already generate manual recap work, founder memory debt, and uneven follow-up quality across sales or delivery conversations.

Scope Meeting recap and follow-up Back to workflow catalog

First KPI

Follow-up sent within one business day

Record 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.

Venus used as the meeting follow-up workflow marker

Scoped lane

Source material

Call note templates, approved follow-up examples, delivery SOPs, and meeting transcript samples.

First KPI

Follow-up sent within one business day

System pattern

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

Approval boundary

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

Lane summary

Meeting recap and follow-up

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

Call summary
Follow-up drafting
Next-step task capture

Why this lane fits first

This lane is strong when the workflow already exists and the drag is obvious.

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

Good fit signals

The business already has a recognizable meeting recap pattern.
Templates or strong examples for follow-up already exist.
The friction comes from speed and consistency, not deep research.

Not a first fit when

Every meeting requires custom strategic synthesis from scratch.
No one owns follow-up quality after the call.
The business wants the first lane to decide pricing or scope autonomously.

What the first build should leave behind

The lane should create artifacts an operator can inspect in minutes.

Better AI workflow work produces visible operating evidence. The buyer should be able to see the summary, the queue, the review edge, and the write-back pattern without needing a second explanation layer.

Structured recap with decisions, risks, and next actions

Draft follow-up message tied to approved tone and templates

Task capture log showing owner and due date proposals

Go-live review board

The lane should pass four checks before anyone calls it ready.

This is the practical review surface: the trigger is stable, the record path is visible, the source material is approved, and the human review edge is explicit before wider writes are even discussed.

Trigger and owner

The lane should already happen often enough to matter and have a named reviewer who can inspect weekly exceptions.

Record path

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

Grounding pack

Call note templates, approved follow-up examples, delivery SOPs, and meeting transcript samples.

Review edge

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

Take this into intake

The detail page should already tell you what to bring into the first scoping form.

Current drag

Describe where meeting recap and follow-up currently breaks, slows down, or creates avoidable cleanup work.

System path

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

Grounding source

Call note templates, approved follow-up examples, delivery SOPs, and meeting transcript samples.

First KPI

Follow-up sent within one business day

Next step

Scope this lane against your current stack.

Start the intake with this lane preselected, describe the current failure point, and keep the first conversation anchored to one KPI loop.

Suggested intake prompt: We need help with meeting recap and follow-up automation.

Best first KPI: Follow-up sent within one business day

Scope this lane See pricing