Summary

  • RTS-tender's real economic question is whether a regulated procurement platform can turn high-volume, low-ticket statutory workflows into durable margin after security, hosting, support, compliance and supplier-acquisition costs are paid.
  • The company has a strong distribution asset because its platform sits inside Russia's approved electronic-procurement infrastructure and within the broader B2B-RTS group, but the statutory fee ceiling makes pure transaction monetization structurally thin.
  • The margin case improves when RTS-tender is treated as part of a larger procurement-automation system: commercial subscriptions, small-volume shops, property trading, education, supplier services, analytics, cash-management income and SRM software can subsidize the low-fee regulated core.
  • The main risks are not abstract platform competition. They are operational: missed filing windows, user-support friction, integration disputes, state-platform alternatives, concentration in a few large customers in some segments, and the possibility that compliance work grows faster than monetizable workflow.
  • The judgment changes if standalone RTS-tender economics show low direct margin, if complaints around RTS-market and technical reliability become widespread, if regional or federal systems take more workflow back, or if group margin depends too heavily on customer-balance income rather than service revenue.

Begin with one completed procurement. A municipal or state-linked buyer publishes a procedure, a supplier enters the system with registration credentials and an electronic signature, bids or uploads an offer, waits for protocols and, if successful, moves toward contract signature and payment. That is the visible story. The economic story is harder.

Somewhere in that chain the platform has to recognize revenue, collect it from the correct party, release or retain the correct balances, preserve the signed documents, answer support tickets, maintain the audit trail, keep the service running at bid deadlines and satisfy the statutory rules that make the transaction legitimate. RTS-tender's business is therefore not simply a marketplace. It is a regulated workflow plant. The plant processes legal events, not only listings.

The first discipline is to separate money passing through the procurement from revenue belonging to the platform. The face value of a procurement is a transaction between buyer and supplier. It is not RTS-tender's revenue. Bid security, guarantees, deposits and analytical-account balances may create financial float or administrative obligations, but they are not the same as platform fee income.

The operator's monetizable surface is much smaller: a capped fee on some winning regulated procedures, tariffs for other trading segments, subscriptions or participation packages in commercial procurement, property-trading charges, small-volume marketplace fees, education and advisory products, software modules, data and workflow services, and income from managing permitted cash balances at the parent-group level. That distinction matters because B2B-RTS reported roughly RUB 9.7 trillion of 2025 platform trading volume, while the same group reported RUB 9.378 billion of total income and RUB 7.950 billion of service revenue.

On that broad group basis, total income represented about 9.7 basis points of reported platform volume, and service revenue represented about 8.2 basis points. The business can be highly profitable, but only if the cost of processing an enormous nominal procurement base is kept small against each monetizable event.

Limited Liability Company "RTS-tender" is the legal operator in the directory entry. Public registry sources identify it as a Moscow company registered in 2000, with OGRN 1027739521666, INN 7710357167 and a main activity in software development. The same public profile lists charter capital of RUB 370 million and B2B-RTS as the owner. That boundary is important. The public financial disclosures with the richest operating data are group-level B2B-RTS disclosures, not standalone statutory accounts for RTS-tender alone. The group includes B2B-Center, RTS-tender, OTC, RTS Academy and Cloud Logistics.

So the correct reading is not that every ruble of disclosed B2B-RTS revenue was earned by RTS-tender. The correct reading is that RTS-tender sits inside a larger procurement-automation platform whose economics reveal the likely cross-subsidy and scale logic behind the federal electronic platform.

RTS-tender's regulated position gives it a base that most software vendors cannot copy by hiring more salespeople. Russian government procurement under 44-FZ and procurement by state-linked or regulated entities under 223-FZ use a statutory framework in which approved platform operators have defined roles. Government Directive No. 1447-r is the kind of legal gate that makes electronic-procurement operators different from ordinary SaaS marketplaces.

Approval turns platform selection into a regulated infrastructure question: the operator must be acceptable to the state, participants must be able to rely on the platform's legal effect, and the procedure must withstand later scrutiny. This creates a moat, but it also creates a cost floor. A normal marketplace can tolerate some informality; a procurement operator cannot treat a bid submission, electronic signature, protocol or fee demand as loose commercial chatter.

The fee ceiling is the second constraint. For covered 44-FZ procedures, Government Resolution No. 564 regulates the operator's right to charge the person with whom a contract is concluded and caps the fee by reference to the initial or maximum contract price, with specific caps by participant category. The court and regulator materials around RTS-tender confirm the practical result: operator fees are not an optional marketing extra. They are embedded in user agreements, platform tariffs and collection mechanics, and disputes can arise when the user has no special account, no commission account or insufficient funds.

But the same legal structure means revenue per regulated event has a ceiling. If an operator earns only a few thousand rubles on many winning procedures, profitability depends on automated collection, low dispute frequency and very low manual support cost per transaction.

That is why the completed procurement is a useful unit of analysis. The buyer sees a procurement procedure. The supplier sees a chance to win a contract. RTS-tender sees a bundle of cost centers: authentication, electronic-signature compatibility, document storage, timestamped action logs, protocol publication, special-account interactions, support calls, fee collection, complaint response, tariff interpretation, integrations with state systems and resilience around deadlines. If those cost centers are mostly fixed and software-driven, the platform earns attractive incremental margin.

If they become ticket-driven and lawyer-driven, statutory volume becomes heavy.

The parent group's 2025 numbers show why scale is tempting. B2B-RTS disclosed 2.579 million procedures and RUB 7.950 billion in service revenue. A simple division gives about RUB 3,083 of service revenue per procedure across the group. That is not an exact regulated-procurement fee, because the numerator includes several services and the denominator covers group procedure volume. But as an order-of-magnitude pressure test it is useful. A platform can earn strong margins at three thousand rubles per procedure only if the marginal cost of one more procedure is tiny. It cannot put a human expert on every ordinary file.

It cannot tolerate frequent rework when a customer misunderstands which account is blocked or which offer has been seen by the buyer. It cannot let infrastructure problems cluster around closing times. The average-revenue math forces an operating philosophy.

B2B-RTS has publicly reported high group profitability: 2025 adjusted EBITDA of RUB 4.900 billion on total income of RUB 9.378 billion, or a 52.3 percent adjusted EBITDA margin, and net profit of RUB 3.708 billion, or a 39.5 percent margin on total income. It also reported no debt-financing burden in the investment framing and a meaningful net cash position. The first-quarter 2026 disclosure continued the pattern: total income of RUB 2.694 billion, adjusted EBITDA margin of 53.7 percent and net margin of 38.2 percent. That is the evidence for a high-margin procurement-platform model at the group level.

The analytical question is whether RTS-tender contributes to that margin by automating the regulated base, or whether the regulated base is the traffic engine that adjacent lines monetize.

The likely answer is both, but not evenly across segments. In 44-FZ, B2B-RTS disclosed a large active-customer base, a leading procedure share and top-10 customer concentration of only 3 percent of procedures in 2025. Low concentration is valuable because it makes the platform less hostage to a small set of buyers. But the monetization is tightly tied to law and tariff ceilings. The platform's advantage is not a high take rate. It is volume density, legitimacy, user familiarity and the ability to sell additional services around the workflow.

The disclosed 2025 savings number for 44-FZ customers, RUB 329 billion, is a customer-value argument, not a direct revenue line. It helps defend the platform's public usefulness, but the operator still has to collect its small fee efficiently.

In 223-FZ, the economics become more flexible but also more heterogeneous. B2B-RTS disclosed an 11.1 thousand active-customer base, high active-customer share, 40 percent procedure share in 2024 and top-10 customer concentration of 7 percent of procedures in 2025. That mix looks more attractive than a fragmented long tail alone: enough state-linked corporate workflow to create volume, but more room for customer-specific services, consulting and subscriptions than in the strictest state procurement. The SME-procurement rules under Government Resolution No. 657 add technical and payment requirements.

Those requirements make the platform more valuable because the legal burden is hard for customers to replicate, but they also increase the platform's operating obligations.

Small-volume procurement is the segment where the market story can sound most attractive and most fragile at once. RTS Academy's public explanation of small purchases describes short, lower-value purchases, electronic shops, catalogues, supplier registration, protected chat, market-analysis tools and counterparty checks. B2B-RTS disclosed more than 100 regional electronic shops and a 1.5 percent tariff for the small-volume segment without a statutory upper cap in its segment disclosure.

That is more interesting than capped 44-FZ economics: lower-value but faster procurement, more marketplace behavior, more data, more supplier discovery and more potential repeat use. But the same segment exposes integration risk. Public forum complaints about RTS-market describe confusion where a purchase appears through one regional or supplier portal and another system, offers may not be visible where a user expects, and funds can remain blocked while the buyer believes it used a different source system. These are not verified statistics. They are market signals. But they matter because small-volume procurement is supposed to be fast.

If speed turns into ambiguity, the segment's higher take-rate potential can be eaten by support cost and distrust.

The 615-PP capital-repair segment is a different animal. B2B-RTS disclosed a 64 percent procedure share for 2024, 63 regional capital-repair funds using the group in 2025 and top-five customer concentration of 49 percent of procedures. That is a strong position but a concentrated one. A tariff described as from 0.5 percent and capped at RUB 14,000 can work if procedures are numerous and standardized, but the customer base is institutionally narrower. The platform must keep a small number of regional funds satisfied, compliant and operational. Here the key risk is not supplier churn in a broad open market.

It is policy, regional procurement preference and the administrative burden of serving funds whose processes can change with regulation and budget cycles.

Property trading adds still another logic. B2B-RTS disclosed a 38 percent procedure share for 2024, top-10 organizer concentration of 24 percent of procedures in 2025 and a tariff range from zero to 12 percent of maximum lot price. Court and regulator records show property-tariff language, guarantee-security mechanics and analytical-account requirements appearing in disputes and municipal auction notices. The revenue opportunity can be better than a capped procurement fee, because a property lot can support a percentage charge.

But the procedure can also create high-sensitivity user disputes: deposits, guarantee amounts, land leases, confiscated property, state assets and organizer compliance all create more legal heat than a routine low-value supply purchase. A platform that earns more on property lots may also spend more on user guidance, documentation and dispute handling.

Commercial procurement is where RTS-tender's parent ecosystem becomes strategically important. B2B-RTS disclosed that commercial procurement uses a combined subscription and one-off participation model, with packages or services reaching up to RUB 495,000 per year. It also disclosed top-10 customer concentration of 29 percent of procedures and customer savings of 18 percent in that segment. This is the segment that can make the whole platform look like enterprise software rather than regulated plumbing.

Subscriptions, supplier-management tools, analytics, procurement automation, corporate catalogues and integrations can lift revenue per customer without relying on a statutory winning-bid fee. The price of that upside is enterprise sales and implementation work. Commercial customers compare the platform with B2B-Center, corporate procurement portals, ERP procurement modules, SRM systems and internal workflows. They are not captive just because RTS-tender is approved for state procurement.

The B2B-RTS disclosures make clear that management understands this broader software angle. The group says it has more than 40 solutions, more than 15 product teams, 150,000 person-hours of product work a year and more than 180 releases since 2024. It describes a platform capable of more than 10,000 procurements per day and more than 1,000 price offers per second. It also emphasizes AI assistants, analytics and automation of procurement work. Those claims are not just technology decoration. They are the operating answer to the margin question. A platform with capped fees must automate complexity.

If product teams reduce the number of support interventions, improve supplier matching, prevent common filing errors and make compliance easier for buyers, they protect margin. If product teams mainly add features that require training, bespoke support and more exception handling, they can make the platform look sophisticated while weakening unit economics.

Customer acquisition is a hidden cost. B2B-RTS says it uses internal sales, regional branches, external partners and training events, with more than 50,000 people trained over 15 years. RTS Academy pages show paid courses for 44-FZ, commercial procurement, suppliers and broader procurement expertise. This is more than education revenue. It is an acquisition and retention machine. Procurement platforms need buyers and suppliers to know the procedures well enough not to break them. Training reduces support cost, increases confidence and creates a path for suppliers to become recurring users.

But training can also become evidence that the product is hard to use. If every new supplier needs a course to bid safely, the network effect is less automatic than platform investors want to believe.

The supplier side deserves special attention because it is the side that pays many fees and feels the pain of workflow failure. A buyer may publish several procedures and have administrative staff. A small supplier may have one shot at a contract, one electronic signature configuration, one bid deadline and limited knowledge of the platform. Public reviews show that some users find RTS-tender convenient, appreciate seeing the number of submitted applications or describe support as helpful.

The same review pool and public forums also include complaints about complexity, delayed help, documents not attaching, requests not appearing clearly, and money blocked after small-volume procurement confusion. Treat these as anecdotal signals, not a quantified defect rate. Yet in procurement economics anecdotes can still be costly. A supplier who misses a filing deadline or believes a bid vanished does not care that the average uptime is good. It will demand support, complain to a buyer, move to another platform where possible or advise colleagues to avoid the workflow.

This is why infrastructure evidence belongs in an economic article. Public DNS and domain-intelligence records show rts-tender.ru with Russian hosting signals, multiple mail records and name servers, and an attributed RTS-tender network range for some nameserver infrastructure. Robtex records the zone as not signed with DNSSEC, while IP intelligence attributes ns2.rts-tender.ru to AS203203 and a 185.179.85.0/24 range. None of this proves internal architecture, redundancy or uptime. It does show that RTS-tender is not merely renting a generic web form with no visible operational surface.

A procurement operator has to maintain public domain, mail, authentication, support and security posture as part of the product. The cost is not just servers. It is certificates, browser compatibility, electronic-signature plugins, anti-tampering records, incident response and the boring work of keeping users able to sign documents when the legal deadline is hours away.

The regulatory burden is also a customer promise. Resolution No. 656 requires continuity of electronic procedures, reliable software and hardware, equal access and preservation of signed documents. These are not nice-to-have service-level claims. They are conditions of trust in the procurement system. A platform whose audit trail fails can create disputes between buyer, supplier and regulator. A platform whose interface confuses users can create complaints even if the code technically worked. A platform whose fee collection process is unclear can create litigation over relatively small amounts.

RTS-tender's court and FAS footprint is therefore not surprising. The relevant question is whether disputes remain ordinary background noise for a high-volume regulated operator or become a sign that manual exception handling is consuming the margin.

The role of cash balances and asset-management income complicates the margin picture. B2B-RTS reported RUB 1.428 billion of asset-management income in 2025, about 15.2 percent of total income. In the first quarter of 2026, asset-management income was RUB 658 million, about 24.4 percent of total income. Investor commentary links this income to customer funds and reliable instruments. This line can be economically powerful. Customer balances connected to procurement workflows can generate income with limited incremental sales cost. But it can also flatter platform profitability if interest rates or balances are unusually favorable.

A durable judgment cannot rely only on float. The stronger case is that service revenue grows, commercial and small-volume revenue deepen, and asset-management income remains a supplement rather than the bridge that makes the margin story work.

Competition comes from several directions. The obvious competitors are other federal and commercial electronic trading platforms: Sberbank-AST, Roseltorg, ETP GPB, TEK-Torg, ZakazRF, RAD, national electronic platforms and corporate procurement systems. In 44-FZ, the approved-platform list limits who can play, but it also standardizes part of the service. If supplier registration through state systems opens access across platforms, the switching cost is lower than in an enterprise SaaS monopoly. In 223-FZ and commercial procurement, customers have more discretion.

A large corporate buyer can use a corporate ETP, an ERP procurement module, a dedicated SRM suite, a B2B marketplace or a sector-specific platform. The substitute is not always another federal platform. Sometimes it is an in-house process that reduces the need to pay outside platform fees.

State alternatives are the more subtle risk. The more procurement becomes a state digital infrastructure priority, the more likely it is that common registration, identity, catalogs, small-purchase systems and audit trails move toward federal or regional systems. RTS-tender can benefit by integrating with those systems and acting as the specialized execution layer. It can also lose differentiation if the state standardizes too much of the user experience or pulls more workflow into official portals.

This is most relevant in small-volume procurement and regional shops, where the front-end convenience matters as much as the legal platform status. If a region owns the buyer relationship and RTS-market is perceived as a duplicate or confusing layer, monetization can become contested.

Suppliers and partners matter because the platform's value chain is broader than software code. Electronic signatures, CryptoPro-style browser environments, banks and special accounts, mail delivery, call centers, training providers, regional representatives, legal databases, integration vendors and customer procurement departments all shape whether a transaction completes smoothly. The platform may own the interface, but it does not own every input.

When a supplier cannot sign, cannot upload, cannot see a buyer's action or does not understand a blocked amount, the blame often lands on the platform even if the root cause sits in a certificate, local workstation, bank account or regional integration. Economically, that means RTS-tender bears reputational and support cost for a larger ecosystem.

This supplier dependency is where the operating model becomes most unforgiving. The platform needs enough outside service providers to make participation possible for small and regional firms, but each outside dependency can create a weak link in the completed procurement. A bank may control the special account. A certificate provider may control signing readiness. A local workstation setting may control whether a browser recognizes the certificate. A regional information system may control how a small purchase enters the marketplace. A customer procurement department may control the clarity of the lot and the timing of protocol publication.

RTS-tender can document these dependencies, automate checks and provide support, but it cannot eliminate them. The economic burden is that the supplier sees one brand on the tender page and treats the whole chain as that brand's responsibility.

The capital question should also be framed through avoided capital, not only deployed capital. RTS-tender does not have to own factories, warehouses or inventory to process trillions of rubles of procurement volume at the group level. That is the attractive part of the model. But a regulated platform has a different form of capital intensity: accumulated software, security controls, support knowledge, compliance procedures, customer trust and institutional relationships. These assets are expensive even when they do not sit on the balance sheet as large physical plant.

B2B-RTS's statement that most software-development costs are treated as operating expenses rather than capitalized assets makes the reported margin more credible, but it does not make the investment disappear. The investment is visible in personnel cost, product-team throughput and the need to keep releasing compliant functionality as laws and customer practices move.

Cloud-service dependency is not simply a hosting question. The directory places this company in a cloud-competition frame because RTS-tender is effectively selling a critical remote workflow. Users do not install a private procurement plant for every bid. They depend on a shared service that must be available, legally reliable and compatible with the Russian public-procurement stack. That gives RTS-tender cloud-like economies of scale: one platform update can serve many customers, one compliance interpretation can be embedded in many workflows, and one supplier identity can participate in many tenders.

It also gives the platform cloud-like risk: a central outage, certificate problem, DNS problem or authentication failure can have broad economic consequences. The value proposition is convenience and compliance-as-a-service; the liability is that centralized convenience becomes centralized blame when something breaks.

Software lifecycle risk is sharper in procurement than in ordinary enterprise tools. In a CRM, a bad release can irritate salespeople and be rolled back. In an electronic procurement platform, a bad release can collide with a bid deadline, a statutory clock or a signed document. That is why release velocity must be judged against defect containment. B2B-RTS's disclosure of more than 180 releases since 2024 shows a system under active development, and active development is necessary in a market where laws, interfaces and customer expectations keep changing. But the real test is whether the release cycle reduces exception handling.

If new features lower the number of support calls per thousand procedures, shorten the time to successful submission, reduce fee-collection disputes and make audit trails clearer, the lifecycle is margin-accretive. If releases require more webinars and more human support, the lifecycle consumes the very scale economics it was supposed to create.

Lock-in is also more nuanced than in conventional SaaS. A supplier does not choose RTS-tender because it loves the product in isolation; it chooses the platform because a buyer's procedure is there, because approval lists make the platform legally recognized, and because registration and workflow familiarity reduce execution risk. That is soft lock-in. It is powerful but not absolute. For 44-FZ, common state registration reduces the pain of using multiple approved platforms. For 223-FZ and commercial procurement, large buyers can select or build alternatives. For small purchases, regional systems can mediate the front end.

RTS-tender's durable lock-in must therefore come from procedural trust rather than captive inconvenience. Users stay because the platform works, documents are traceable, fees are predictable and support resolves deadline-sensitive problems. If users stay only because they have no immediate alternative, the lock-in will show up as public resentment and political pressure.

A sensible unit-economic model for RTS-tender has four layers. The first layer is capped regulated fees: broad, legitimate, high-volume and low take-rate. The second is semi-regulated or specialized procedure income: capital-repair, property trading and small-volume procurement where tariffs and customer needs vary. The third is commercial subscription and service income: procurement automation, supplier management, analytics, counterparty checks, catalogues and execution tools. The fourth is financial and educational adjacency: cash-management income, training and consulting.

The model is attractive when the first layer supplies trust and traffic, the second and third layers lift average revenue per customer, and the fourth layer monetizes cash and knowledge without adding too much risk. The model is weak when the first layer supplies most of the operational burden while the higher layers remain too small or too concentrated.

The customer side of the same model is a procurement-cost trade. A buyer may accept platform fees and service subscriptions if they are outweighed by more competition, lower prices, shorter cycle times, lower compliance risk and better supplier visibility. B2B-RTS emphasizes savings and operational-efficiency claims, which are plausible in a fragmented procurement market. But buyers eventually ask whether the platform is lowering total procurement cost or merely relocating bureaucracy from paper to screen. RTS-tender's job is to prove that the electronic workflow is not just legally required but economically useful.

The more it can turn procedure data into supplier discovery, catalogue discipline, contract execution and repeatable analytics, the more it becomes a productivity tool rather than a regulated toll collector.

The supplier side asks a different question: does the platform improve access to demand enough to justify fees, setup work and process risk? For a small supplier, a few thousand rubles of platform charge can be acceptable if the contract is worth winning and the path is clear. It becomes unacceptable if the supplier has to pay for training, spend hours configuring signatures, face uncertain blocked funds and then discover that the buyer did not see the offer because the purchase originated somewhere else. That is why supplier-acquisition cost includes friction cost.

The platform can advertise to suppliers, but the cheapest acquisition is a successful prior bid that makes the next bid feel routine. The most expensive acquisition is a frustrated supplier who needs manual rescue and then warns peers away from the system.

The customer-concentration data cut both ways. In 44-FZ, the top-10 customer share of procedures is low, which protects the platform from a few buyers walking away. In 223-FZ, it is still modest. In small-volume procurement, concentration by nominal maximum procedure sum is higher but not alarming. In 615-PP, top-five concentration is high because regional capital-repair funds are structurally concentrated. In commercial procurement, top-10 concentration of 29 percent is meaningful. The right conclusion is not that customer concentration is a fatal weakness. It is that each segment has a different renewal and bargaining logic.

A diffuse 44-FZ base supports network legitimacy. Concentrated capital-repair and commercial segments demand account management. If those concentrated customers negotiate harder or migrate, revenue quality can change even while aggregate procedure count looks stable.

The take-rate question is therefore less about raising prices than about layering revenue. In regulated procurement, fee caps make direct price increases politically and legally constrained. A platform can still improve economics by reducing cost per transaction, lowering failed or disputed submissions, automating support, improving fee collection, and using the regulated relationship to sell permissible adjacent services. In commercial procurement and small-volume markets, pricing can reflect more value: faster supplier discovery, catalog management, contract execution, analytics, counterparty checks and workflow automation.

The key is not to make every supplier feel taxed for entering the system. If platform monetization becomes visibly extractive, users search for alternatives, lobby buyers or complain in public forums. The platform must price like infrastructure and sell like software.

There is also a geopolitical and regulatory tailwind. Foreign procurement software and enterprise workflow products have lost ground in Russia after sanctions and vendor exits. B2B-RTS and B2B-Center position domestic SRM and source-to-pay tools as replacements for foreign systems such as SAP Ariba. Soware lists RTS-Tender as included in the Russian software register, and B2B-RTS promotes domestic software status across its solution set. This supports customer adoption among Russian public and corporate buyers that need domestic systems. But a tailwind is not a margin guarantee.

Domestic preference can increase demand while also increasing compliance obligations, localization duties and expectations of state-aligned reliability. The platform may win because it is domestic, then spend heavily because it is systemically important.

The unofficial user signals are worth reading with discipline. T-Bank's review page shows a positive headline rating, which suggests the platform is not broadly reviled by the small sample there. Forum and outage pages show enough complaints to identify recurrent friction themes: technical submission problems, support delays, confusing integrations, blocked funds and uncertainty over whether a buyer saw an offer. Do not convert those posts into an uptime percentage. Do not ignore them either. In a regulated platform, the cost of friction is nonlinear.

One confusing bid flow can create a support ticket, a complaint, a regulator response, a buyer relationship problem and a supplier who tells others to avoid the platform. The economic value of good interface design is not cosmetic. It is litigation avoidance and support avoidance.

RTS-tender's best defense is automation with explanation. A procurement platform cannot remove the law, but it can make the law legible. It can warn a supplier before a fee is triggered, explain which account will be used, distinguish a regional source system from RTS-market, show whether an offer is visible to the buyer, and preserve user-facing proof of action. It can build customer-specific settings without creating hidden exceptions. It can use training content as product feedback: any topic that needs repeated webinars is a candidate for an interface fix, a better guided task list or a clearer support bot.

If B2B-RTS's AI assistants reduce routine legal-search and procurement-error questions, they can protect margin. If they merely add another layer of branded output without resolving process ambiguity, they will not.

The capital requirement is not obvious from public accounts because the parent group says it expenses most software-development costs rather than capitalizing them, except for fixed assets. That accounting choice makes reported earnings less flattered by capitalized development, but it also means product investment appears in operating costs. B2B-RTS disclosed that personnel costs, especially IT specialists, restrained EBITDA growth in 2025 after wage adjustments. That is exactly the cost line to watch.

A regulated platform's scarce resource is not only server capacity; it is procurement-law engineers, product managers, support specialists, security staff and developers who can translate changing regulation into stable workflow. If wages in that labor pool rise faster than service revenue, scale advantages narrow.

The platform's margin resilience also depends on release quality. More than 180 releases since 2024 signals product velocity. In procurement infrastructure, velocity is a double-edged metric. Frequent releases are good if they adapt the platform to new rules, close support gaps and improve automation. Frequent releases are dangerous if they create user-interface changes around bid deadlines, training churn or regression risk in signature and upload workflows. The correct economic metric is not release count.

It is release count adjusted for fewer manual interventions, fewer complaints, faster procedure completion and better conversion of suppliers into repeat users.

The buyer's value proposition is strong. B2B-RTS talks about procurement savings, lower operating costs, faster cycle times and access to a large counterparty base. In public procurement, transparency and competition are policy goals. In corporate procurement, savings and supplier discovery are budget goals. RTS-tender can plausibly sit at the center of both. But buyers and suppliers value different things. Buyers like competition, compliance and analytics. Suppliers like clear rules, low friction, predictable fees and confidence that bids are seen.

A platform that optimizes only for buyers can alienate the supply side; a platform that reduces supplier friction can improve competition and help buyers. The best long-term margin comes from serving both sides enough that volume arrives without constant paid acquisition.

The completed procurement at the start of this article therefore has a narrow accounting answer and a broad strategic answer. Narrowly, RTS-tender or the group earns only the applicable platform fee or service revenue, not the contract value. Broadly, the completed procurement can seed a supplier relationship, teach a buyer to use adjacent tools, create a customer balance, generate data for analytics, demonstrate savings, and justify a subscription or software module. The more of that broader value the platform captures without increasing manual work, the stronger the margin.

The more the transaction remains a single capped fee with a support tail, the weaker the margin.

The strongest case for RTS-tender is that the B2B-RTS group has already shown high margins while handling large regulated and commercial volumes. It has disclosed broad customer and supplier counts, market leadership in several segments, strong profitability, product-team scale, and growth in 2026 service revenue. It also benefits from domestic procurement-software demand and a statutory operator position that many ordinary SaaS firms cannot enter. This is not a speculative platform with no revenue model.

It is a real workflow system processing legally meaningful transactions in a market where electronic procurement remains structurally important.

The skeptical case is also substantial. Standalone RTS-tender accounts are not disclosed in the same detail as group accounts. Group profitability may depend materially on commercial procurement, B2B-Center, cash-management income or other businesses outside RTS-tender's strict regulated platform role. Fee caps limit the upside of 44-FZ. Some segments show concentration. Public user signals identify support and integration friction. State systems can standardize or absorb more workflow. Product and compliance labor can rise faster than low-ticket revenue.

A platform can be essential and still see margin compressed if it becomes the place where every regulatory change, customer error and supplier complaint must be absorbed.

My judgment is that RTS-tender's margin can remain durable only if management treats the regulated platform as a distribution and trust engine, not as the main profit engine by itself. The pure statutory fee business is too constrained to carry the full compliance, infrastructure and support burden indefinitely unless volume is exceptionally automated.

The attractive business is the layered one: regulated legitimacy brings users; users create data and balances; data and balances support analytics, commercial procurement, small-volume shops, property trading, education, supplier services and source-to-pay software; those adjacent lines fund the product and compliance machine that keeps the regulated base reliable. That is a credible model, but it is an execution model, not a birthright.

The facts that would change the judgment are clear. It would improve if RTS-tender published or disclosed standalone service revenue, direct cost and margin showing that regulated operations are profitable before group cross-subsidy. It would improve if small-volume procurement grew while complaints about duplicated listings and blocked funds faded. It would improve if commercial subscription revenue became a larger, recurring share of group service revenue and if top-customer concentration declined in commercial and 615-PP segments.

It would improve if public evidence showed lower support load per procedure and fewer regulator disputes per unit of volume.

It would worsen if B2B-RTS margins stayed high only because asset-management income rose while service revenue slowed. It would worsen if official platform-fee caps tightened, if state platforms took the front-end relationship in small-volume procurement, if regional integrations caused recurring confusion, or if a competitor built a more trusted support and signing workflow. It would also worsen if product releases and AI features increased complexity rather than reducing manual support.

The market will not reward a procurement platform for sounding advanced if suppliers still fear that a deadline, bid file or blocked amount will disappear into process ambiguity.

RTS-tender's economic problem is therefore brutally simple. It must make platform revenue exceed compliance, infrastructure and acquisition costs in a market where much of the core workflow is legally prescribed and much of the user pain is operational. The evidence says the broader B2B-RTS platform has the scale and margin profile to do that today. The unresolved question is whether RTS-tender's own regulated engine is a profit center or a strategic gateway. Either can be acceptable.

But if it is a gateway, the company must keep the toll low, the road reliable and the adjacent services valuable enough that users do not resent the toll booth.

Sources