R&D · Research · Development

Research and development (R&D) in software and artificial intelligence

We carry out R&D in software and AI: we research and build an algorithm, a model or an architecture when no ready solution exists yet. In Russia, R&D is more often associated with instruments and design documentation. Our subject of research is different, but the order of work is the familiar one: hypothesis, experiment, report, acceptance.

For companies that need something the market does not offer: their own algorithm, a model for their own task, a test of a technical hypothesis before investing in a product.

What is included

Research work (NIR)

A review of the field, hypotheses and tests of them on your data. The result is a reasoned answer: whether the problem can be solved, and at what cost.

Experimental development (OKR)

From a confirmed hypothesis to a working prototype: architecture, implementation, testing, documentation.

Algorithms and models for the task

We develop algorithms and models when ready-made solutions do not fit on accuracy, licensing or deployment requirements.

Specification and reporting

The technical specification, the test programme and methodology, stage reports. Documents that pass acceptance and are needed to account for the work.

Technology transfer

The result stays with you: source code, documentation, team training. We do not build in a dependence on us.

How we work

  1. Framing

    We turn a vague goal into a testable hypothesis with a success criterion. Without that, research can go on forever.

  2. Research

    A review of the field, experiments, early checks. We take on the research risk and report a negative result at once.

  3. Prototype

    Building the solution and testing it to an agreed methodology.

  4. Documents and handover

    Stage reports, source code, training for your team.

Why us

Research you can check

Some of our work is open: the Balansis numerical library on PyPI and the Agent Native Universe agent runtime under MIT. For the Balansis model, 153 theorems are proved in Lean 4 with no gaps (as of 05.10.2026). They prove the algebra of the model over the real numbers, not the behaviour of float64.

We report a negative result early

If a hypothesis is not confirmed, we say so at an early stage, while that is still cheap. We publish our own negative results too: the open Agent Native Universe repository records that the relationship graph between agents gave no advantage on these tasks.

Through to a working system

If you need it, we take the prototype to a service in operation. That is what happened with sandwich-panel specifications from CAD drawings: on one real project, 784 of 784 panels matched the manual specification line by line.

Case studies

Manufacturing · Building materials

MVP in operation

Panel specs from CAD drawings in seconds, not hours

Reads DWG/DXF layouts and builds the Excel spec: 10–⁠30 seconds instead of 2–⁠15 hours by hand. All 784 panels of one real project matched the manual spec line by line.

784/784 and 189/189
panels on one project and wall panels on another matched the manual specs line by line, size groups included; area within 0.001 m²
2–15 h → 10–30 s
to produce a project spec: manual work vs app processing, measured on real projects

Real estate · PropTech marketplace

MVP in operation

Land-plot marketplace with a next-step plan: MVP in 2 months

From a mock-up to a working platform: plot → works → contractor → request. Rule-based next-step engine, three dashboards, personal-data compliance. MVP in 2 months.

2 months
from approved spec to a pre-release MVP on an HTTPS stand: week 9 against the plan’s own 10–13 week estimate
7 days
from spec to the first full-implementation commit: 168 files, 21.5k lines, then two months of hardening to pre-release

Marketplace e-commerce · Pricing

Pilot

Rule-based repricing: a pilot whose contract terms are enforced in code

Competitor prices tracked per SKU, a price computed by rules inside an agreed corridor and applied only after confirmation. Pilot: 10 SKUs, setup within 14 days.

10 SKUs · 2 scenarios
pilot scope; the SKU cap and both scenarios are enforced in code and verified by contract tests, so the cap cannot be exceeded
up to 14 days
contractual setup window from client inputs to launch, then a 1-month pilot; the service tracks the dates and closes access when the period ends

EdTech · HR-tech

MVP in operation (demo stand)

From business canvas to a student-work marketplace demo in about six weeks

The client had a business model and no product. We built a student-task marketplace MVP where the server enforces legal and platform rules, and put a demo stand live.

~6 weeks
from first commit to a deployed demo with all workspaces; 7 working days in commit history
3 checks
run by the server before a contractor is assigned: data consent, self-employed status, mentor; each with a plain refusal

AI infrastructure · multi-agent systems R&D

Research project

A multi-agent environment where the rules are code

In four days we built and open-sourced (MIT) an agent environment where code enforces the rules: cryptography, a PBFT-style agreement protocol, reproducible experiments.

same hash
a repeated run and a replay of the log give a byte-identical final event hash; anyone can check it on the MIT-licensed code
187 of 187
engine tests passing; master branch, commit 625b81d, as of 05.10.2026

EdTech / AI research

Research project

Long-term student memory: from hypothesis to a working service

A research neuromorphic memory core and a student model, taken to a service in 10 days: 32 REST endpoints, 368 tests, 21 Lean 4 statements. The code is open.

10 days
from first commit to a release with formal verification, measured by commit dates
368
test functions across 37 files, counted from code

Scientific computing / R&D

Research project

From mathematical theory to a verified numerical library in 9 months

Compensated-computation library: precision loss is visible and checkable, the model’s algebra is proved in Lean 4, each numeric claim has a reproducible benchmark.

1.0 instead of 0.0
residual preserved on the [1e16, 1, −1e16] sum that float silently drops; reproducible benchmark generated by a script in the repository
6 of 6
scenarios of the published benchmark in which the exact dot-product kernel matched the exact reference; numpy.dot matched in 0 of 6. The C kernel is not yet released on PyPI, and the cancellation scenario was built on purpose

Frequently asked questions

What is the difference between research (NIR) and development (OKR)?

Research (NIR) answers the question “is this possible, and under what conditions”. Its result may turn out negative, and that is a normal outcome. Development (OKR) takes a possibility confirmed by the research and brings it to a design or a working sample.

Is there such a thing as R&D in software?

Yes. R&D is defined by the nature of the work, and the industry plays no part: there has to be scientific or technical uncertainty that standard design cannot remove. Developing a new algorithm or model for a task with no ready solution meets this criterion.

What if the result turns out negative?

That is a regular outcome of research, and it has value: you get a reasoned answer that the path does not lead to the goal before you invest in developing a product. We plan the stages so that such an answer comes as early and as cheaply as possible.

Who owns the results?

The contract sets the rights to the result. By default we assume they belong to the client. The terms on exclusive rights are fixed before work starts.

Work it out on your own figures

The AVA calculator works out the economics of your process from your own figures, with no form and no price from us. If automation does not pay off, it says so.

Estimate the payback

Tell us what you are dealing with

Describe the problem in your own words. If it can’t be solved or won’t pay off, we’ll say so before any work starts.

In the reply we will say what we understood, what we need to clarify and whether it is worth doing.

or email us directly: hello@xteam.pro

See case studiesNew write-ups on Telegram