01
The same data is entered several times
Data is copied from an email into a spreadsheet, then into a business management system. This takes time, and errors are easy to make during transfer.
Business analysis and automation
Tell us how your business works.
We'll find where automation can reduce inefficiencies
01 / Where inefficiencies arise
Does this sound familiar to your team?
Unnecessary steps, errors and delays take up time. We'll start with what gets in your way.
02
The report is needed now. It will be ready tomorrow.
Data is requested from different departments, file versions are checked, and the report is compiled manually.
03
Tasks stall without your involvement
You have to remind people about deadlines, ask what has been done and personally follow up to make sure tasks are completed.
04
You have to hire more people to handle routine work
The volume of documents and repetitive tasks grows. Your team spends more and more time on them.
You don't need to know in advance
what to automate
Tell us how your team works, or show us recordings of work meetings. An analyst will identify where time is being lost and suggest where to start.
02 / Improvement cycle
We test every change in practice
From understanding processes to a task with clear benefits. From implementation to measuring impact. New data shows what to improve next.
01 / Process analysis
We understand how work is organised
On calls with your team, we establish who does what, who receives their output and what is needed for the next step. We examine metrics and real work situations.
We build an overall picture: where work is delayed, errors occur and the same things have to be done twice.
The outcomeA process map: participants, the links between them, baseline metrics and inefficiencies.
Division of labour system
Pyotr Shchedrovitsky studies systems of division of labour. This perspective helps us consider work through the specialisation of participants and the links between them. In process analysis, we examine how individual activities contribute to the overall result.
Pyotr Shchedrovitsky on the division of labour02 / Task selection
We identify what will benefit your business most
We identify what most constrains the overall result. We assess whether automation can remove that constraint.
We estimate the expected financial impact: lower costs or increased revenue. We compare it with the costs of building and using the solution. Together, we choose a task and agree on how to evaluate the result.
The outcomeA priority task, an estimate of its financial impact, a budget and success criteria.
Goldratt's Theory of Constraints
Eliyahu Goldratt's Theory of Constraints identifies what holds back the results of the entire system. This helps us decide where to focus our efforts. We then assess the economics of the change: the expected benefits and the costs of achieving them.
About the Theory of Constraints03 / Development and implementation
We take the solution into everyday use
We build the solution and test it against your work scenarios. AI and ready-made components help shorten development time. If configuring an existing tool is enough, we use it.
We connect the necessary systems, help employees learn the new way of working and resolve issues that arise in practice.
The outcomeA working solution that your team uses in its process.
04 / Impact measurement
We assess what has changed for your business
We compare metrics before and after implementation and gather feedback from your team. We check whether the expected impact was achieved and what else may have influenced the result.
We decide what to keep, what to refine and what to abandon. With the new data, we return to process analysis: the main constraint may have shifted following the changes.
The outcomeAn assessment of the actual impact and conclusions for the next cycle.
HADI · from hypothesis to insights
HADI stands for Hypothesis, Action, Data, Insights. We formulate a hypothesis about the impact when selecting a task, test it through implementation and analyse the data at this stage. The insights become the basis for the next hypothesis.
About HADI from the Internet Initiatives Development Fund (IIDF)We start with one area
In our first conversation, we'll discuss how your company works and choose a process to examine in more detail. You don't need a predefined task or a technical specification.
How does your team take part?
We'll need an employee who knows the process and colleagues who will use the solution. On calls, we discuss current work; after implementation, we gather feedback. We use available metrics and examples from your systems. If the necessary metrics are not yet available, we'll agree on how to measure them. We agree in advance on the meeting format, data and time commitment.
How do we choose the next improvement?
We consider the results of the previous cycle, your team's feedback and business priorities. The next step may be a new task, a refinement of an existing solution or a change in how work is organised. If the expected impact does not justify the costs, we suggest stopping or reconsidering the task.
03 / Examples of changes
What could change
in your company.
A few possible areas. We'll choose a solution for you after the analysis.
Reporting
A report without manual compilation
Collect data from your business management system and spreadsheets. Highlight deviations that deserve attention.
What we checkPreparation time, data completeness and how up to date the data is.
Procurement
Suppliers in one spreadsheet
Combine prices, delivery times and terms from suppliers' proposals. The employee only needs to check and choose.
What we checkTime spent comparing offers and errors in transferring terms.
Sales
Agreements in a draft CRM record
Prepare a record from a conversation with a customer. The sales representative checks the details and confirms saving it.
What we checkTime spent recording information, field completeness and the number of corrections.
Sometimes configuring your system or changing the way you work is enough. We propose development when it is justified.
One example · sample dataFrom a call to CRM: benefit calculation and demoExpand exampleCollapse example
Illustrative calculation · not a customer's result
A CRM record after a call
| Metric | Assumption | Pilot target |
|---|---|---|
| Conversations per month | 300 | 300 |
| Time per record | 12 minutes | 4 minutesincluding review |
| Manual work | 60 hours / month | 20 hours / month |
Potential to validate
40 hours / month
freed up for your team if the pilot confirms the calculation
Freeing up time does not automatically mean saving money. A financial benefit will arise if paid overtime is reduced, an additional hire is no longer needed or the team generates more margin.
- Processing time
- Completeness of required fields
- Number of corrections
Try the sales representative's role
From a conversation to completed fields. Review the draft, correct the details and confirm the record.
1 / Customer conversation
“We need 30 sets for our new office. Please send two options tomorrow: a basic one and one with an extended warranty. We'll decide after comparing them.”
All data is fictional. The fields have been prepared in advance to show the workflow. The demo is not connected to AI or your CRM.
2 / Review before saving
Record confirmed in the demo
- Need
- Next action
- Due date
The record exists only on this page and will disappear when you refresh it. Nothing has been sent.
Our completed projects are internal, so we cannot publish them. What you see here are possible solutions and a practice demo. We'll test the benefits for your company in a pilot.
04 / Budget and terms
You can get started
without a million-ruble budget.
AI reduces development costs. A small task can be solved for tens of thousands of rubles. Your pilot's budget depends on its scope.
First step
A pilot on one process
Test the approach on a specific task.
What's included
- An analyst identifies inefficiencies and possible solutions.
- You agree on the expected benefits and budget.
- The team implements the approved scope.
- Together, we evaluate the actual result.
Two stages – two budget decisions
We fix the assessment price before starting. We agree on the implementation cost based on its findings. No subscription is required.
After validating the benefits
Continuous improvements
Gradually make your team's work easier.
What's included
- An analyst selects tasks based on the expected benefits.
- We work with one business function.
- We implement one task at a time.
- We report on results and maintain the solutions.
An agreed monthly budget
We agree on the scope of work and maintenance in advance. If there are no justified tasks, development can be paused while support continues.
Hosting, paid APIs and third-party licences are calculated separately. Before work starts, you see both the one-off budget and recurring costs.
What to know before starting
What data and access will be needed?
We start with one process and an agreed data sample. Where possible, we use anonymised examples for the preliminary assessment. Before data is shared, we agree on access, processing and storage locations, the use of external AI services and deletion procedures.
How will you work with our IT team?
We agree on integrations, security requirements and where the solution will be hosted. Before development, we establish who on your side is responsible for technical approval.
Who is responsible for quality and support?
AI assists with development. Our team is responsible for technical review, testing and implementation. For each solution, we agree on support, how to submit requests and the boundaries of responsibility. The terms distinguish between bug fixes and new features.
What will we retain when the work ends?
We hand over the code for the solutions created for you, documentation and the necessary administrative access. Exceptions for third-party and reusable components are agreed in advance. Before starting, we establish what is needed to run the service independently.
Can we avoid new development?
Yes. We first check whether the task can be solved by configuring your system, using a ready-made tool or changing the process. Custom development is needed when its benefits justify the costs.
05 / Let's start with a conversation
Tell us about your company.
We'll find where to start.
You don't need a predefined task – we'll define it together.