Proposal automation: build it, then follow up
The agent builds a proposal from your company template using Bitrix24 and amoCRM data, adds a competitor comparison and follows up after it is sent.
Scenarios for this job
Every scenario is a ready brief for the agent: the steps, the connected systems and the output. Open one and run it on your own data.
The agent builds a client proposal from your template: CRM data, current prices and terms filled in — the document is ready to send.
The agent finds clients who went quiet after receiving the proposal and writes each a personal follow-up informed by the conversation history.
The agent builds a competitor comparison: features, pricing and positioning for each — a table you can base strategy on.
A sales proposal is the most expensive routine a sales team runs. Every one of them is assembled out of the same parts: the company template, the current price list, terms shaped for this particular customer, a paragraph or two about why you beat the alternatives. An hour of a manager's time per document — and only about ten minutes of that is an actual decision. The rest is copying fields out of the deal card, pasting company details, straightening the table and re-reading formatting that broke on paste. And when the client asks to re-price the volume or change payment terms, the whole document is rebuilt from scratch — by Friday a manager is sitting on five near-identical files with different numbers in them.
Then comes the second half of the job, and it is done worse. The proposal goes out and hangs there. No answer, nudging feels awkward, and a week later the deal is forgotten. The Bitrix24 pipeline shows twice as many proposals sent as conversations held afterwards. Follow-ups get written for the customers a manager happens to remember rather than the ones most likely to close. And every manager rebuilds the competitor comparison from scratch in their own way, so two proposals from the same week describe the product differently.
The agent covers both halves. It takes the deal data from Bitrix24 or amoCRM, drops it into your Google Docs template together with current prices and terms, and hands back a document ready for a read-through. A separate scenario assembles the competitor comparison by feature and plan — a table the proposal can point at. After sending, it watches the deals that went quiet and writes each customer a personal follow-up informed by the email history and what was discussed on the call. Prices, discounts and the final wording stay yours: the agent fills in only what your price list and your template already hold, and invents no terms of its own.
Common questions
Is the proposal built from our own template?
Yes. The agent works inside your Google Docs file: it keeps the structure, the sections and the formatting, and drops deal data, line items and prices into their places. It invents no new design — it fills the one you have already approved.
Where do prices and terms come from?
From the systems you connect: the price list and stock from 1C or MoySklad, the deal's line items and the agreed discount from the card in Bitrix24 or amoCRM. If an item is missing from the price list, the agent leaves a flag instead of inventing a number.
Are follow-ups sent automatically?
The agent finds deals with no reply after the proposal went out and drafts an email for each, based on the email and call history. You confirm sending; if you want, the first routine reminder can be put on a schedule.
Where does the competitor comparison come from?
From public sources and your own materials: competitor plans and features are collected into a table along the criteria you name. Every data point is shown with a link to its source so you can verify it before the proposal reaches a customer.