Skip to content

We build digital systems a business can own

Rapoport Studio designs and ships digital platforms, internal systems and AI infrastructure for businesses already in operation. First we find out where the business is losing time, money or control. Then we describe the solution, agree it with you, and only then start building.

Discuss your project on Telegram →See our work
WHO WE ARE

A small studio with undivided responsibility

Pavel Rapoport leads the project — from the first conversation and the architecture through to checking the result. Rapoport Studio builds the system, bringing in vetted specialists as the work requires: designers, engineers, researchers and domain experts.

You know in advance who is on the project, what each person is responsible for, and who decisions are made with. There is no layer of account managers between you and the person answerable for the result.

Pavel Rapoport

Founder · diagnostics and architecture

Rapoport Studio SRL · Chișinău, Moldova IT Park resident · working with businesses in Moldova, Romania, Israel and the EU

Pavel Rapoport, founder of Rapoport Studio

Who does the work

The studio's core is small. Network specialists join per project and are named in the case studies where they have agreed to be.

WHAT WE BUILD

Not another website or AI feature — a working system for your business

We take on work where picking a ready-made template is not enough:

  • data, processes and several existing services have to be joined up;
  • AI has to do the work, not just generate text;
  • a product already in use has to move to a new architecture without a risky full rewrite;
  • a business process is held together by spreadsheets, messages and manual checking;
  • a system needs clear rules, clear responsibility and room to grow.

If an off-the-shelf product would solve it more reliably and for less, we will say so before the project starts.

HOW THE WORK STARTS

First we establish what actually needs building

The work starts with a growth diagnostic — the first paid step, three to four weeks. We study the problem, the existing processes, the constraints and the data. What you get:

  • a map of the current system and where it is constrained;
  • a description of the proposed solution;
  • the architecture of the key components;
  • the order of implementation;
  • the boundaries of the project and what counts as done.

It is a result in its own right. You can continue with us, hand it to your own team, or use it when choosing another supplier.

More about the diagnostic →
HOW DEVELOPMENT RUNS

You see the result before it turns into code

Every significant change is described in plain language first: what problem it solves, what exactly will change, which decisions are already settled, what is deliberately out of scope, and how we will check it is done.

You read the description and agree it. After that the team and the studio's AI tools do the work in small, checkable stages. Nothing significant reaches your project without human review. When plans change, the agreed description is updated first — then the code.

More about the process →
WHAT STAYS WITH YOU

A project should not depend on its supplier

The documentation and the code sit in your repository. So do the decisions taken and the reasons the system is built the way it is.

When the work is finished you can carry on with us, hand the project to your own team, bring in another supplier, or stop without losing the knowledge. We do not hold a client through a closed tool, a proprietary file format or documentation they cannot reach.

EVIDENCE

Work you can check

Client systems in production. Timelines and confirmations come from the clients themselves.

  • Senzo

    • Trilingual site live within three weeks
    • In daily production since June 2026

  • VSThermo Moldova

    • Eight days from kick-off to production
    • Full catalogue published from day one
All projects →
WHY THE METHOD IS OPEN

Our way of working is open to inspection

We run our own studio by the same rules we offer clients. A large part of our working documentation is published: the decisions taken, the history of changes, and the rules the studio's people and AI tools follow. It is evidence of transparency, not a document a client has to study.

See the working documentation →

You do not need a finished technical brief — describing a process, a constraint or a task that eats too much time is enough. In the first conversation we will work out whether we can help, which first step makes sense, and what does not need building yet.

[ CLT ]

Tell us about your project.

Message us on Telegram — it's the fastest route: it reaches us directly, and voice notes are welcome. We reply within 48 hours with an honest fit assessment and a proposed next step — or a pointer to someone better suited.

Message us on Telegram →
Fill in the structured brief

5–10 minutes, if you'd rather write it out point by point.