It gets the meeting notes
Notes, a transcript or a voice memo with a few sentences after the call. They do not have to be tidy.
After a meeting you hand the agent your notes or a transcript. You get back the agreements, the tasks, a draft follow-up and, when needed, a draft proposal. You read, correct and send them yourself.
The first meeting takes about an hour. We go through your proposals and follow-ups process and agree where to start.
From the end of the meeting to the message that goes out, step by step.
Notes, a transcript or a voice memo with a few sentences after the call. They do not have to be tidy.
What the client wants, what we promised, who does what and by when. It records this with the client in the shared company knowledge base.
An email summing up the agreements and the next step, in the tone you use with clients.
From the agreements, the price list, templates and earlier proposals. It flags whatever the agreements do not settle instead of guessing.
You read, correct and send them. We record your corrections as rules, so the next draft is closer to what you would have sent yourself.
The agent writes from knowledge the company already has. We put it in order during the deployment.
This is what you receive after a meeting. We show the structure of the drafts, because the agent writes their content from the agreements of a specific call.
The drafts come to you, not to the client. The agreements and tasks stay recorded with the client, even if you send the message some other way.
Always a person. A proposal commits the company and a follow-up tells the client what you agreed, so a specific person is responsible for both. The system measures how many drafts pass without correction, so you can see how well the agent already knows the company.
We run this process in our own company: agents draft our proposals and follow-ups, and one of us sends them. Client deployments are just starting, and for each one we say plainly what stage it is at.
Where the system runsProposals and follow-ups after meetings are the most common first process of a deployment, and the lowest-cost scope when the company’s knowledge already exists. The price covers system configuration, documentation and team training. We set the final price after the meeting.
On your side: a Claude Team subscription for every person who works in the system.
No. The agent prepares a draft, and a person reads, corrects and sends it. Every step that cannot be undone needs approval.
From the price list, the service descriptions and earlier proposals in the company knowledge base. If there is no price for a given scope, the agent flags it in the draft and you set the price.
To start, notes and company files are enough. We add integrations with a CRM, mailbox or calendar when the process really needs them, and quote them separately.
We do not give one number, because it depends on how many meetings and proposals you have. Count the hours a week your team spends on follow-ups and proposals today. The agent takes over the writing; reading, correcting and sending stay with you, so the saving also depends on how many drafts pass without correction.
The first meeting takes about an hour. We go through your proposals and follow-ups process and agree where to start.
Prefer to write?hello@200iqlabs.io