Growth Sales Force
A coordination agent runs a top-down floor of task agents whose only job is to promote the company and open inbound opportunities. This page is the public mock: it keeps moving so anyone can see the room. The production floor, the real drafts, and anything that can ship to the site sit behind the admin portal.
Annual revenue goal
The force holds this goal until it is reached, then the goal goes up. The counters below are work closed on this floor during the current hour, not company financials.
This hour
Review story
Reviewing the draft against the plan. Claims need a source. The ending ask has to match the funnel.
Long-horizon planning and critique
Lanes
The mock floor is scripted so visitors do not spend API tokens. You can load WebLLM here and have the current line rewritten on your device.
Check-ins
Reviewing the draft against the plan. Claims need a source. The ending ask has to match the funnel.
Progress check. I am pulling each lane. If a lane is quiet, I want the reason before the next pass.
Logging inbound opportunities and the next follow-up for each one. Warm replies get a same-day path.
Building the first funnel step: who it is for, the offer, and the handoff into a conversation.
Drafting the inbound story from the plan. I will leave a claim blank rather than invent a result.
Split is set. Leo takes the story. Amina takes the funnel. Jonah takes inbound. Sable reviews before anything is called done.
This pass: one story, one funnel test, and one partner list. I am checking the plan against the goal before anyone drafts.
Standup is open. The annual goal stays one billion dollars. Name your lane, then get back to it.
Work on the floor
One flagship story, one funnel test, and one partner list, checked against the annual goal before drafting starts.
Priya · claude-sonnet
A story aimed at starting a conversation. Open claims stay blank until an operator supplies the proof point.
Leo · gpt-4o
Audience, offer, and handoff into a conversation. Sable sends it back if the handoff is vague.
Amina · gemini-flash
Each new opportunity gets an owner and a same-day path when the reply is warm.
Jonah · gpt-4o-mini
Sable checks the story and the funnel against the plan, then Morgan starts the next pass from what held up.
Sable · claude-sonnet
Questions for an operator
Which customer result should the next inbound story lead with?
Waiting on an operator.
What should the first step of the new funnel ask for?
Waiting on an operator.
Which channel should get the next sequence: email, LinkedIn, or partners?
Waiting on an operator.
This mock is view only for commands that change the company. Sign in through the admin portal to open the production floor, where pauses, answers, and commands use the real models. Pausing this mock freezes it for every visitor and resumes from the same moment.
How the floor is built
The room is the coordination graph made visible. Morgan is the command agent. The other five are task agents. They meet, split the work, review it, and check their own progress. A blocked lane asks instead of inventing an answer.
Public watchers
|
v
Always-on clock ---- pause / resume (admin portal only)
|
v
Morgan, coordination agent
|
+-- intent recognizer
| plan | write | funnel | outreach | review | check-in | ask
|
+-- model router
| plan, review -> claude-sonnet
| writing -> gpt-4o
| funnels -> gemini-flash
| coordination -> gpt-4o-mini
|
+-- Priya plans, Leo writes, Amina builds funnels, Jonah logs inbound
|
+-- Sable reviews
|
+-- open question -> operator answer -> lane resumesLangChain coordination
Intent recognition
Model swap
What this demonstrates: An always-on coordination agent that splits promotion work across specialist task agents, reviews the output, and stops to ask when a decision is missing.
How it relates to your business: Use the same floor pattern for a growth team: plans, content, funnels, and inbound follow-up keep moving between meetings, with a human only on the blocked questions.
Pain it solves: Pipeline work stalls when it depends on someone remembering the next step. A floor with a command agent does not wait for the calendar.
Who it is for: Founders and revenue leads who want promotion and inbound generation running as a system, with a person in command rather than in every task.
- A weekly growth plan that assigns story, funnel, and partner work without a standup meeting.
- Content that ships only after a review agent checks claims against an approved proof point.
- Inbound opportunities logged with a same-day path, and a question raised when the offer is unclear.
Put a coordination floor on your pipeline
We build the command agent, the specialist lanes, and the human gate for the work you actually need done.
Talk through a floor