Contracts
Template-based drafts, checks for required terms and risks before approval.
As we maythink
AI adoption for organizations
We start with document preparation and checks based on your company’s templates and checklists. First we measure the process and show a prototype; only then do we propose a pilot.
Prices exclude VAT. Work starts after 100% prepayment and receipt of the samples.
A company rolls out a chat and buys licenses. Three months later a handful of enthusiasts use it — and nobody can say what it has earned.
We start with a task that has a price — not with a model.
Every solution goes through the same path. The metric and the success threshold are fixed before we build — so a pilot ends with a number, not an impression.
We map processes and look for repetitive work that eats specialists’ hours.
How much time, money and errors the task costs today.
A tool, an agent or a multi-agent system on your own data and systems.
With a real team, against a metric and a threshold agreed in advance.
Inside your perimeter: access, security, training, support.
Compare with the baseline and decide: scale, improve or stop.
Impact proven — on to the next task
Usually
With think
AI prepares a draft and checks the document against a checklist. People retain responsibility and make critical decisions.
Template-based drafts, checks for required terms and risks before approval.
Proposals assembled from source data and checked for completeness before sending.
A structured draft based on the facts, your policy and the supporting documents.
Tender applications assembled and pre-checked against procurement requirements.
The price is clear before we start. The impact comes from measurement. First a diagnostic and prototype, then a pilot with a written success threshold.
from250,000RUB per task
A baseline, impact and TCO assessment, a working prototype and a decision: pilot, refine or stop.
Included
Stop with the report and a working prototype.
Discuss a diagnosticfrom700,000RUB per task and one team
The solution works with a real team on a real workflow; impact is measured against a threshold agreed in advance.
Included
If the threshold is not met, the solution is not scaled.
Discuss a pilotno starting priceBy proposalpriced in a commercial proposal
Implementation, integrations and support under a separate commercial proposal.
When a separate proposal is needed
Implementation has no public starting price. Additional scope is assessed after the diagnostic or pilot:
Make the decision only after the final pilot measurement.
Discuss the scopeThe full diagnostic price is credited if the pilot covers the same task and the contract is signed within 90 calendar days of the diagnostic acceptance certificate. The credit does not apply if the task changes or that period has passed.
If you start directly with a pilot, the diagnostic stage takes place during its first two weeks. The starting price remains unchanged.
Prices exclude VAT.
The diagnostic starts after 100% prepayment and receipt of the samples. Pilot payment terms are fixed in the contract.
Website prices are starting prices provided for information only. This website does not constitute a public offer under Article 437 of the Russian Civil Code. The scope, timeline and final price are determined after a brief and fixed in a commercial proposal and contract. The pilot success threshold is agreed in writing before the pilot starts; if it is not met, the solution is not scaled.
Week 1
Interviews, process mapping, and measurement of time, cost and errors, including human review.
Week 2
One scenario selected, data and security constraints assessed, impact, TCO and payback calculated.
Week 3
A demonstration of one scenario on anonymised data, a report and a pilot proposal.
A decision package, not a presentation of promises:
from RUB 250,0002 weeks + prototype in week 3 · Prices exclude VAT.
Discuss a diagnosticThe pilot threshold comes from the diagnostic and is fixed in the contract before work starts. We do not promise a percentage in advance. Total time includes human review, and quality must not fall below the baseline.
If the threshold is not met, we refine or stop — we do not scale the solution.
This shows the mechanics, not a result. The success threshold is fixed before the pilot; if the pilot misses it, we do not scale.
Not a chat but a catalogue: employees see where AI already helps in their work, who is behind each tool and what comes next. The hardest scenarios run as multi-agent systems, and ideas for new ones come from the employees themselves.
Multi-agent system
One agent gathers requirements from the tracker, wiki and repositories, a second lays them out in the company template, a third checks completeness and contradictions. A person gets a draft and signs off.
Taking apart a contract, a project or a codebase: the weak spots and what to fix first.
In development
Tasks, decisions and agreements from meetings, chats and files become clear next steps.
Teams plug AI into their systems with the same sign-in as the chat — inside the perimeter, with a usage log.
Path of an idea
We find the processes where AI delivers measurable results, build tools and multi-agent systems for them inside your perimeter, and bring them into everyday work — measured before and after.
One task, one tool with a clear input and result: a document in your company template, a risk review, an answer from your knowledge base.
A complex process is split between agents: one gathers data from your systems and knowledge bases, another checks it, a third prepares the result for a person.
A single entry point: models, access keys for services, a tool catalogue, rules and a usage log — all inside your perimeter.
Employees see what already works, vote for ideas and build tools themselves. Adoption grows from within instead of being pushed from the top.
In the AI perimeter
10 · Who it is for
11 · Questions
Yes. You receive the measurement, business case, prototype and recommendation. A decision to stop is a valid diagnostic outcome, not a failure.
In full, if the pilot covers the same task and the contract is signed within 90 calendar days of the diagnostic acceptance certificate. The credit does not apply if the task changes or that period has passed.
Yes. The diagnostic stage then takes the first two weeks of the pilot, and its starting price remains unchanged.
One task and one agreed scope. A pilot covers one team of up to 20 people and no more than one read-only integration. Infrastructure, implementation and additional scope are priced separately.
We record the result and its causes, then choose refinement or stop. The solution is not scaled.
Get started
Tell us which documents your team prepares or checks. We will discuss the process and whether a diagnostic makes sense.
Who to talk to: Dmitry Krechman, business development director — dimak@aswemay.ru
Think first. Then automate.