A platform built out of a working service business
RepairCore Cloud generalises the process that has been running in real workshops and fleets since 1998 into a platform other organisations can use. This page shows what already runs in production, what does not yet exist, and how to start a conversation.
by Muto · Automotive Technology
Investment thesis.
Three things that separate this from another workshop system drawn from scratch: where the product comes from, the shape of its data, and how it earns.
Pillar
What it rests on
Generalised, not greenfield
The product is built by generalising a process that genuinely runs - in the eCarService workshops and in FleetPoint fleet coordination - rather than by designing a system away from the workshop floor and selling it into the industry afterwards.
One shared record
The workshop, the fleet and the network work on the same work order and the same vehicle card, instead of three separate systems stitched together after the fact. That is an architectural decision a competitor cannot copy with a single feature.
A revenue model already published
Four subscription plans with public prices and a published work-order limit, with three deliberately separate layers above them: add-ons, usage and individual rollouts. We do not sell "everything, unlimited, in the top plan".
The platform is developed by Muto sp. z o.o. The operator’s registry data and the product’s origin are set out on the Company page.
Go to the Company pageWhat already runs.
The maturity of each item is stated plainly. What is a pilot we call a pilot - and what runs in production is not talked down just to sound careful.
Element
State and scope
ECS Cloud
The current SaaS platform, actively developed towards RepairCore Cloud - with a working core of work orders, estimates, subscription billing and a full audit trail of decisions.
Claims
The damage-estimate decision inside an existing work order, with deadlines and a decision trail - today in pilot with one insurance partner, developed towards the full process.
Partner API
Data exchange with technical partners, piloted today case by case with the first partners; the broader partner platform remains a direction, not a state.
RepairCore Network
Service relationships built since 1998, today in a requalification programme - activated with further partners after verification, contact and consent.
The network does not start from zero.
We are not starting with an empty partner base. We are starting with a quarter-century of service relationships, which we turn into a network through a controlled requalification process.
500+
Historical service records for requalification
16
Regions in the historical relationship base
118
Records from the earlier eCar structure
Historical data. Current partner status requires renewed verification, contact, consent and confirmation of the scope of cooperation. Historical network relationships do not represent active RepairCore Cloud subscriptions.
We publish anonymised aggregates only. We publish no workshop names, addresses or contact details, and every entity may update its data or opt out at any stage.
See the full network registerRevenue model.
Four separate monetisation layers. Separate on purpose - blending them is the most common way vertical SaaS loses its margin to rollouts.
Layer
Scope
Subscription
Four plans with a published price and a published monthly work-order limit, billed per organisation.
Add-ons
Specialist technical data, advanced automation and additional communication channels - a separate product and a separate licence, never "included in the plan".
Usage
Messages sent and paid external lookups, billed on actual consumption.
Individual rollouts
Service networks, large fleets, CFM, insurers and enterprise integrations - priced per contract.
Subscription plans
- BASIC
- 299 PLN net / month200 work orders / month
- STANDARD
- 599 PLN net / month500 work orders / month
- PREMIUM
- 1 199 PLN net / month1500 work orders / month
- FLEETPRO
- 1 999 PLN net / month5000 work orders / month
There is no public signup or checkout today - every plan path leads to a conversation. That is a known gap in the funnel, not a product feature.
See the full pricingMarket context.
We deliberately publish no TAM or SAM figures here. The market model, with its assumptions and sources, goes into the pack - the page keeps the observations you can check.
Observation
What it means for the product
The market is fragmented
Independent workshops run on a mix of separate tools, spreadsheets and paper. What wins is not another feature, but joining the process into a single record.
No dominant vertical player in Europe
The strong vertical products grew primarily in the US market. Europe has no equivalent covering workshops, fleets and networks at once.
Regulatory and digitisation pressure
Documentation and settlement obligations grow faster than a small organisation’s capacity to handle them by hand. That turns software from a convenience into a requirement.
Fleets are the second segment of the same process
The same work-order record serves an individual customer and a fleet, but a fleet contract carries higher value and a longer horizon. One product, two sales motions.
Technical foundation.
Mechanisms that are a constant of the architecture, not a parameter of one rollout. We describe them by what they do rather than by vendor name - stack details go into the technical pack.
Mechanism
What follows from it
A separate database per organisation
One organisation’s data is separated at the architectural level, not merely by a filter in a query.
Separation of organisations and locations
A multi-site network sees its locations separately and together, with no data mixing between entities.
An audit trail of decisions
Vehicle and work-order history can be reconstructed: who decided on a cost, when, and on what basis.
Identity confirmation on financial decisions
Sensitive operations require an additional confirmation - and when verification is unavailable, the operation is held rather than let through.
Interface abuse protection
Traffic to programmatic interfaces is rate-limited and monitored, which contains the blast radius of a faulty or malicious integration.
Gradual feature rollout
A new capability can be enabled for one organisation ahead of the rest, so it can be piloted without risk to every customer.
We publish no certifications we do not hold and no infrastructure diagrams. Architecture, stack and technical due-diligence material go into the pack.
What is still ahead of us.
This list is here on purpose. Every one of these points will surface in due diligence anyway - better that it surfaces from us, together with what we are doing about it.
Open point
What we are doing about it
No self-service path
There is no public signup or checkout today - a conversation carries the sale. Closing the path from website to subscription is the first direction for capital.
Plan-limit enforcement
The entitlement engine runs in observe mode today: it measures and reports before it starts refusing. That is why we publish exactly one numeric limit and confirm the rest of the boundaries at onboarding.
E-invoicing in pilot
Support for the national e-invoicing system is functionally complete but runs in a single-environment pilot. Extending it to further organisations is planned, not done.
Partner platform on architectural hold
The broad "any audited partner plugs itself in" programme is deliberately on hold in favour of case-by-case pilots. We do not sell it as available.
Concentration on one operator and one market
Today the product grows out of a single operating environment in Poland. That is the source of its credibility and, at the same time, a concentration risk - diversifying needs capital and partners.
The network requires requalification
Historical relationships are not active partners. Every record goes through verification, contact and consent before it becomes part of a working network.
Forms of cooperation.
Four different conversations, each with a different first step. Choosing a path in the form below lets us answer with specifics instead of a generic deck.
Path
What the first step looks like
Equity investment
An introductory call, then the materials pack: financial model, operating indicators, company structure and pilot status.
Strategic partner
A shared use case on one concrete process - a fleet, an insurer, a network - before we discuss the shape of an agreement.
Technology or data provider
A technical conversation about the scope of data exchange and a pilot on a limited scope, ahead of any public communication.
Service network
Verification of the scope and terms of cooperation, followed by entry into the network requalification programme.
What we share in a conversation.
We do not publish financial data on the site - not because we lack it, but because a public page is the wrong place for indicators that change every month.
Investor pack
- Financial model and operating indicators
- Platform architecture and technical due-diligence material
- Product roadmap, separating what runs from what is in pilot
- Company structure and the operator’s full registry data
- Pilot status and the network requalification programme
We share materials individually, after a short introductory call. We sign a non-disclosure agreement at the other side’s request.
Contact
Arrange a meetingRepairCore Cloud is developed by Muto sp. z o.o., Poland.