Product development · SaaS and platforms · Backend, web, mobile

Software product development: from prototype to live operation

Software product development usually goes wrong before anyone chooses a framework: more features were built than testing the idea required, or a good-looking interface sits on an architecture that will not survive the second client. We start with what the product has to prove to the business, and build exactly the scope that proves it.

For companies that need to build or rebuild a software product: a SaaS product, a platform, a marketplace, an internal system, ERP or CRM, a mobile app. We build for live operation from the first release.

What is included

Architecture and MVP

We start with the minimum scope that tests the business hypothesis, and with an architecture that will survive growth. The point of an MVP is to test the idea before large investments.

Backend and APIs

Server logic, the data model, integrations and APIs that hold up under load and do not need rewriting in year two. We build the domain rules into the code and the database so that they cannot be bypassed.

Web interfaces

User accounts, dashboards and client applications in React and TypeScript: role-based access, data states, accessibility. The interface shows what the system can actually do.

Mobile applications

Cross-platform apps on top of your API. A thin client keeps pace with the web version, and the mobile channel does not turn into a separate second product.

Integrations with external systems

1C, CRM, payment and logistics services, marketplaces, internal APIs. We handle failures and timeouts in advance: sooner or later an external service will return an error, and the system must behave predictably.

Security and compliance

Access control, an action log, handling personal data under Russia’s personal data law (152-FZ), encrypted backups. We design all of this together with the system, before launch.

Operation and handover

Containers, deployment, monitoring, documentation and team training. We hand the product over so that your team can run it without us.

How we work

  1. Task analysis

    What the product has to prove to the business, and who needs it. We separate what the launch makes no sense without from what can wait for version two.

  2. Prototype and MVP

    We build a minimal working version with live operation in mind: the architecture, the core features, a plan for the next stages.

  3. Development

    In iterations, with demos and automated tests. At every demo you see the product itself.

  4. Production

    Load, fault tolerance, security, running costs, access rights and audit. We launch against measurable acceptance criteria.

  5. Growth

    New modules on the same architecture, without rewriting from scratch. The product grows as hypotheses are confirmed with real users.

Why us

Our methods in production

StudyNinja, the learning platform our methods run on, is in production (so far as a closed beta): a knowledge graph, telemetry, answers checked by code. We put the running cost of such systems into the calculation from day one.

Full cycle, one team

Architecture, backend, interfaces, infrastructure and acceptance in the same hands. Responsibility does not get lost where one contractor hands over to another.

Timelines you can check in the case studies

The timelines and figures in our case studies were checked against project artefacts, and where there is no confirmation, the case says so.

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

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

EdTech · Mobile app

In-house product

A mobile client for an AI learning platform, built without waiting on the backend

Flutter client for an exam-prep platform: adaptive micro-lessons, a streaming AI assistant, a knowledge map. The UI was built alongside the backend via a mock layer.

13 weeks
from first commit to a working app with sign-in, goals, lessons and AI chat
41 → 81 endpoints
API coverage doubled from MVP to the extended version, with 14 → 31 modules on the same architecture

IT consulting · Lead qualification

In-house product

A pilot plan for the visitor, a qualified lead for sales

We replaced the contact form with an AI consultant: it interviews the visitor, returns a pilot plan with KPIs and risks, and sales gets a lead with budget and timeline.

1 day
to build a working MVP: frontend, backend and deploy configs
16 days
from first commit to production with HTTPS and an issued certificate on its own domain

Frequently asked questions

How much does software product development cost?

The cost depends on the scope of the product, the number of integrations, the security requirements and whether an architecture already exists. Cheapest is a well-defined MVP with one integration. A platform with several roles, external systems and 152-FZ requirements costs more. We give a price range after analysing the task.

How is an MVP different from a “cut-down version”?

An MVP tests a business hypothesis on real users with a minimal set of features. A cut-down version is simply trimmed to fit a deadline. We build an MVP so that its architecture can take further development: a successful hypothesis can be built on without a rewrite.

Do you build on your own technology or on a standard stack?

We build client products on a widely used stack: Python and FastAPI, TypeScript and React, PostgreSQL. That way you do not depend on a single contractor. We use our own developments where they give the client a gain, and in a way that keeps the result yours.

What do we keep after the project?

The source code, documentation, deployment infrastructure and a trained team. By default the rights to the result belong to the client; the specific terms are fixed in the contract before work starts.

Can you improve our existing product rather than build from scratch?

Yes. We start with an audit of the code and architecture and say plainly which is cheaper: improving what exists or rebuilding the bottleneck. Sometimes the honest answer is “no rewrite needed”, and we give it.

Does the product need AI?

Not necessarily. Ordinary engineering often solves the task: a rules engine, integrations, a careful data model. That is cheaper and more predictable. We add AI where it pays off.

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