A hundred and two service centers, seven of them ours
The network grew not by opening its own centers but by connecting other people's. I was given the mechanics: how a request finds the right center, and how that center runs it and gets paid.
A historical case: rus.support is a different business today. The shop window is reconstructed from the 2015—2020 web archive and press releases, the back end from my own account.
First I ordered signs, and the vendor came to inspect
From May 2013 I owned the visible side of openings: outdoor ads, print, halls, press. And the sign — from scratch in every new city.



The HP delegation on the steps of the St Petersburg center on 16 April 2015, the sign with HP Platinum Partner status and the side of a field-service van — one set of graphics on every surface.
- repair times
- repair quality
- engineer qualifications
What scaled was not the workshops but the authorisation
Independent repair shops across the country had premises, people and skilled hands. What they lacked was HP status: the vendor's requirements are expensive to maintain. The head of the service department proposed a trade.
- premises and people
- spare parts stock
- engineer training
- vendor audit
- a year of time
- premises and hands already there
- the network gives status and a standard
- the network gives a flow of requests
- the partner gives a pin on the map
- growth not paid with our money
- how a person in Magadan learns there is a network center nearby
- how a request reaches a specific partner
- how the partner runs it and gets paid
A request has to match on three axes at once
A person knows their city and their broken box. They don't know the words 'authorised service partner'.
All three axes in full, from the archived site map
Vendor and equipment
- HP Inc.: computing and printing equipment, commercial and home lines
- Wide-format printing DesignJet and PageWide XL
- POS terminals for retail points
- Cost-per-page contracts, MPS
- Hewlett Packard Enterprise: servers, storage, networking, 24×7 support
- Samsung: printing equipment
Geography
- 55 cities, 11 time zones
- Radius search from 20 km
- Geolocation lookup
- A map pinned with every center
- Own centers in seven cities plus regional partners
- A city email address for every location
Service level
- Repair: warranty, paid, on-site for printing equipment
- Original spare parts, warranty extension
- Contracts: service, HP Care Pack, HP Proactive Care, pay-per-page printing
- Infrastructure: monitoring, installation, upgrades, migration, outsourcing and outstaffing
The catalogue is what is left after routing
The May 2018 landing page — my last year at the company and the product's final state. It scrolls inside the screen.
- And — for a company: a center that fixes both the printer and the server
- Or — at home: any center that fixes printers
until 18:00
Status on the sign is worth nothing without a flow of requests
For a partner, the mechanics were what joining actually meant. I built them with the developers: described the logic, set the tasks, sorted out the integrations.
- a bank contract and requirements for the site
- test environment, refunds, reconciliation
- one center does the repair, while the network's legal entity takes the payment
The back end never made it into the web archive. Everything in this act, apart from the traces on the site and the press release, is my own account.
The network doubled without a single new center of our own
'50' and '100+' in my CV turned out to be two dates, not a mix-up. Both points are backed by archived snapshots.
The model outlived its author. The network did not
What follows happened without me, but the case would be dishonest without it.
The brief was about a catalogue of service centers. The job turned out to be about routing requests — and the whole product is built around that correction.
The case has no result in money: no data from that era survived, and I won't fill it in after the fact.
Outdoor ads and signs approved by the vendor and the city, halls and stands, print, regional press.
Routing across three axes, user scenarios, prototypes, development requirements, the 2018 landing page, the RUS.SUPPORT logo.
Request intake by connected centers, repair statuses on the site, online payment and the bank integration.
← Back to all cases