As we maythink

AI adoption for organizations

AI that pays for itself on a real task.

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.

  1. Task
  2. Baseline
  3. Pilot
  4. Rollout
  5. Impact
Task diagnostic
from RUB 250,000
2 weeks + prototype in week 3
Pilot with a success threshold
from RUB 700,000
6–10 weeks

Prices exclude VAT. Work starts after 100% prepayment and receipt of the samples.

01 · The problem

Access ≠ adoption

Access to a model is not adoption.

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.

  1. There is a chat but no use cases: everyone invents their own reason to use AI.
  2. Good solutions stay personal tricks and never become a team tool.
  3. Pilots never reach production: no perimeter, no data access, no owner.
  4. The impact is never measured — so the next budget is impossible to defend.

We start with a task that has a price — not with a model.

02 · Approach

A cycle, not a one-off project

Six steps from a task to proven impact.

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.

  1. 01

    Find the tasks

    We map processes and look for repetitive work that eats specialists’ hours.

  2. 02 · 2 weeks

    Measure the baseline

    How much time, money and errors the task costs today.

  3. 03 · By week 3

    Build the solution

    A tool, an agent or a multi-agent system on your own data and systems.

  4. 04 · 6–10 weeks

    Run a pilot

    With a real team, against a metric and a threshold agreed in advance.

  5. 05

    Roll it out

    Inside your perimeter: access, security, training, support.

  6. 06

    Prove the impact

    Compare with the baseline and decide: scale, improve or stop.

Impact proven — on to the next task

Usually

  • A chat subscription
  • A prompting course
  • A pilot for its own sake
  • Impact “by feel”

With think

  • A catalogue of working use cases
  • A tool built for the task
  • A pilot with a success threshold
  • Impact in hours and money

03 · Where we start

Documents that follow your rules, not a universal AI lawyer.

AI prepares a draft and checks the document against a checklist. People retain responsibility and make critical decisions.

01

Contracts

Template-based drafts, checks for required terms and risks before approval.

02

Commercial proposals

Proposals assembled from source data and checked for completeness before sending.

03

Claims

A structured draft based on the facts, your policy and the supporting documents.

04

Supplier applications

Tender applications assembled and pre-checked against procurement requirements.

04 · Diagnostic → pilot → AI perimeter

Three steps. You can stop after each one.

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.

01 · 2 weeks + prototype in week 3

Task diagnostic

from250,000RUB per task

A baseline, impact and TCO assessment, a working prototype and a decision: pilot, refine or stop.

Included

  • Interviews and process mapping
  • 20–50 samples for measurement
  • Data and security constraints assessment
  • One-scenario prototype
  • Pilot metric and threshold

Stop with the report and a working prototype.

Discuss a diagnostic

02 · 6–10 weeks

Pilot with a success threshold

from700,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

  • One task and a team of 5–20 people
  • Up to one read-only integration
  • Configuration, support and iterations
  • Action logs and human review
  • Final measurement and recommendation

If the threshold is not met, the solution is not scaled.

Discuss a pilot

03 · timeline set in a commercial proposal

AI perimeter

no 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:

  • More than one task, process or team
  • More than 20 pilot users
  • Writes to accounting systems or more than one integration
  • On-premises deployment, GPUs and client infrastructure
  • Personal data or banking secrecy processed by Think; critical information infrastructure
  • Implementation, support and training beyond the pilot team

Make the decision only after the final pilot measurement.

Discuss the scope

100% of the diagnostic credited towards the pilot

The 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.

05 · Task diagnostic

Two weeks of work. A prototype in week three.

  1. Week 1

    Process and baseline

    Interviews, process mapping, and measurement of time, cost and errors, including human review.

  2. Week 2

    Scenario and business case

    One scenario selected, data and security constraints assessed, impact, TCO and payback calculated.

  3. Week 3

    Prototype and decision

    A demonstration of one scenario on anonymised data, a report and a pilot proposal.

What you receive

A decision package, not a presentation of promises:

  • a baseline measured on 20–50 documents or requests;
  • a business case based on hours × rate, API/GPU costs and payback;
  • a working prototype of one scenario without integrations;
  • the pilot metric, baseline, threshold and measurement period in writing.

What we need from your team

  • A process owner with decision-making authority and a named contact.
  • 3–5 practitioners available for interviews of up to one hour each.
  • 20–50 real or anonymised samples, templates and checklists.
  • Time-measurement data and a security contact.

from RUB 250,0002 weeks + prototype in week 3 · Prices exclude VAT.

Discuss a diagnostic

06 · Success threshold

Measured before the start, not after

First we write down what counts as a result.

The 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.

Baseline
Time, cost and quality of the task today — measured, not estimated.
Metric
One headline number the process owner understands.
Threshold
The value below which we do not scale the solution.
Period
The pilot length, after which the decision is made.

If the threshold is not met, we refine or stop — we do not scale the solution.

Sample · illustrative dataPreparing a document from a template
Impact per monthRUB 180,00090 h

This shows the mechanics, not a result. The success threshold is fixed before the pilot; if the pilot misses it, we do not scale.

07 · Internal showcase

An AI tool showcase for employees.

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

  1. Employee idea
  2. Colleagues vote
  3. An author takes it on
  4. Beta
  5. In production
4
tools already in daily use
2
in development, requested by teams
8
employee ideas in the queue

08 · What we build

From a single tool to an AI perimeter

We build what the task needs — nothing more.

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.

01

Applied AI tools

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.

02

Multi-agent systems

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.

03

Your company’s AI perimeter

A single entry point: models, access keys for services, a tool catalogue, rules and a usage log — all inside your perimeter.

04

A showcase and an author’s path

Employees see what already works, vote for ideas and build tools themselves. Adoption grows from within instead of being pushed from the top.

09 · Data and perimeter

The environment follows the constraints, not the other way round.

Diagnostic
Anonymised or synthetic samples. The prototype runs on a Russian LLM or open weights, with no writes to your accounting systems.
Pilot
A Russian cloud API or an agreed client perimeter; action logs, input and output filtering, and human review for critical steps.
Separate proposal
On-premises deployment and GPU infrastructure, personal data or banking secrecy processed by Think, critical information infrastructure and production integrations.

In the AI perimeter

Sign-in
Through corporate SSO, with roles and access rights.
Log
Who used which tool, and with what data.
Rules
Your security team decides what data may go to a model — we build those rules into the tools.

10 · Who it is for

A good fit

  • A repeatable document task with a clear owner.
  • Templates, checklists and enough document volume for measurement.
  • A person reviews the output and owns critical decisions.
  • You are ready to start with one task and one team.

Not a fit

  • You need a fully autonomous AI lawyer or a guaranteed saving before measurement.
  • There is no process owner, document samples or access to practitioners.
  • You want every department and accounting system covered immediately.
  • You need certified standards compliance or decisions without human review.

11 · Questions

Questions before you start

Can we stop after the diagnostic?

Yes. You receive the measurement, business case, prototype and recommendation. A decision to stop is a valid diagnostic outcome, not a failure.

Is the diagnostic credited towards the pilot?

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.

Can we start directly with a pilot?

Yes. The diagnostic stage then takes the first two weeks of the pilot, and its starting price remains unchanged.

What does the starting price include?

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.

What happens if the pilot misses the threshold?

We record the result and its causes, then choose refinement or stop. The solution is not scaled.

Get started

Don’t adopt AI “in general”. Start with a specific task.

Tell us which documents your team prepares or checks. We will discuss the process and whether a diagnostic makes sense.

  1. Bring the process that takes up the most hours.
  2. Diagnostic: 2 weeks. Working prototype: by week 3. Pilot: 6–10 weeks.
  3. The decision to scale rests on the pilot’s numbers.
What to discuss

Data processing consentPrivacy policy

Contact us

Who to talk to: Dmitry Krechman, business development director — dimak@aswemay.ru

Think first. Then automate.