#1 leads
No enquiry slips through
Watches your CRM and call tracking, finds enquiries nobody answered, duplicates and spam. Output: a list of what was left untouched, and why an enquiry never became a deal.
CapyAgent - a program on your own computer.
Cloud · the cabinet is live
You write to it like any chat. From there it goes into your mail, your CRM, your ad account or the procurement platforms itself, does the work and brings back the result. Not advice on what to click - the finished thing.
Cloud prices are on the pricing page; how data is stored is in cloud data and security.
Honestly about the state: the cabinet works, but we deploy the agent ourselves - one-click self-service does not exist yet. The form starts a conversation about your task, not a purchase.
The price is fixed and known up front. You pay the model provider separately, about 2,000 RUB a month, so the total is about 3,600 RUB a month. Where compute and tokens are metered, nobody knows the monthly figure in advance. All prices are on the pricing page.
What it looks like
A real exchange, not a list of features. Two things to notice: it went into three systems on its own, and it stopped to ask before sending anything.
This week the ads spent 84,300 RUB and brought 61 enquiries. 44 turned into deals. Seventeen went unanswered for more than a day - the list is below. The most expensive one is the "Pumps Moscow" campaign: 12% of the spend and one deal.
Done, 17 drafts. I have not sent them - here is the first one, take a look. Say the word and I will send them all and note in the CRM that we got in touch.
In an ordinary web chat, the first question gets you instructions on how to work it out yourself. You would still be the one working it out.
What you get
Not a general-purpose helper, but specific work someone does by hand today. Next to each item is what actually comes out.
#1 leads
Watches your CRM and call tracking, finds enquiries nobody answered, duplicates and spam. Output: a list of what was left untouched, and why an enquiry never became a deal.
#2 tenders
On weekdays it watches your filters in Tenderplan, reads the first documents of each procurement and sends cards to Telegram. Output: a short list of procurements that matched your filters. A paid module, price on request.
AI tender search#3 ads
Matches ad spend against deals that actually closed. Output: where the money burns and which source brings revenue rather than enquiries.
#4 mail
Reads the mail, separates what matters, drafts replies. Output: a draft you edit and send. It will not send on its own - only on your word.
#5 calls
Transcribes calls and meetings, pulls out who promised what to whom. Output: a list of commitments with deadlines, instead of an hour of audio.
#6 reports
Every morning it walks the connected systems itself. Output: a briefing in your Telegram by the time you open the laptop.
How it goes
The difference from a chat is one thing: the answer is finished work, not text. Every step is visible, and you can step in at any of them.
In the cabinet, in Telegram or in your CRM chat. No commands to learn, no phrasing to guess.
Breaks the task into steps and shows them. If it misread the task, you see that before it has touched anything.
First it works out how your particular account is arranged: pipelines, fields, reference books. It does not assume someone else's naming.
Every action is recorded: what it read, what it changed, in which system. Irreversible actions ask for a separate confirmation code.
Not an instruction to go and export something, but the thing itself: a summary, a draft, a list - with the source of every number.
Connections
Nothing has to move: the agent comes to where you already work. You can disconnect at any moment and the access goes immediately.
Model
This is what the agent thinks with. You can change it whenever you like; the conversation and the settings stay put.
Limits
It does only what you allowed. Permissions are granted one at a time, never in a lump.
#1 confirmation
Sending a letter, changing a deal, deleting something - each of these is enabled separately, and enabling it sends a code to your Telegram. The cabinet password is not enough.
#2 trail
What it read, what it changed, in which system and how it ended. In plain lines you can actually read, not a technical trace.
#3 keys
Passwords and keys to your systems are stored encrypted and handed over only for the length of one request. Each client has their own: your agent cannot see anyone else's and cannot reach them.
Price
Some clouds charge by consumption: for machine time, for calls and for storing files. The monthly figure is not known in advance. We charge a fixed amount, known before you start.
| With us | If billed by a meter | |
|---|---|---|
| What the month will cost | known before you start | visible only after the fact |
| While the agent waits for work | included in the same 1,590 RUB | the meter runs anyway |
| How many systems and skills it has | as many as you like, the payment does not move | not charged as such, but every call eats money |
| A second agent | another payment like it, known in advance | another machine, the meter from zero |
| File storage | included | often charged separately |
| If the money runs out | we write to you and sort it out | depends on the provider terms |
Status
Promising what does not exist is easy right up to the first client. So the list of open ends is kept in plain sight instead of surfacing in week three.
Questions
Connect
Leave a request. We answer within a working day, clarify what the agent should do and send an invoice. There is no online payment yet.
While you wait: all prices and how data is stored.