Customer portal
Under NDA. A portal for an equipment supplier's clients: equipment, licences and service terms from 1C:ERP, renewals, tickets and requests with statuses.
The pain and the solution
The pain
- To find out when a licence or service contract ended, a client wrote to a manager and waited.
- Renewals and requests went through emails and calls, and managers spent time on look-ups.
How we solved it
- In the portal the client sees their equipment, licences and contracts with dates, straight from 1C:ERP.
- Renewals are priced by the rates and placed in the portal; tickets and requests follow a route with statuses.
- Documents are generated from the supplier's templates.
Recognise your task? We will solve it for you too.
Discuss a similar projectWhat we did
Data from 1C:ERP
Purchased equipment, licences and service contracts with their dates come from the supplier's accounting system; nothing is copied by hand.
Tickets and requests
Support tickets and requests follow an agreed route, and the client sees their status in the portal.
Renewals and documents
Service and licence renewals are priced by the supplier's rates, and documents are generated from its templates.
The project in detail
This project is under NDA, so the company is not named. An equipment supplier keeps everything in 1C:ERP, the most common Russian business accounting system: what was sold to whom, which licences and service contracts a client has and when they end. Clients could only learn this through a manager.
What we are building
A personal portal for client organisations. It shows purchased equipment, licences and technical support with their dates. The data comes from the supplier’s 1C:ERP, so the portal shows the same as the books.
The client prices service and licence renewals by the supplier’s rates and places them, files support tickets and requests. These follow a route agreed with the supplier, and the client sees which step they are at. Output documents are generated from the supplier’s templates.
How we build it
The work is split into four stages: the portal base and the link to 1C:ERP, viewing data, actions and sales (renewals, tickets, requests), then trial operation and launch. At each stage the client accepts the result on its own data.
Who it fits
Suppliers of equipment, software and services whose accounting is in 1C and whose clients regularly ask about dates, renewals and request status.
Discuss a similar project
Tell us about your task, and we will suggest how to build something like this for you.
- 01Analysis
We study processes, data and the points where value is lost, and fix the result we are working towards.
- 02Architecture and prototype
We design the system and build the first version on your real data. Stages and cost are agreed before work begins.
- 03Pilot
We launch in one area. Every stage is checked in a test version before it goes into operation.
- 04Scale and support
We connect the remaining areas, take responsibility for how the system runs and keep developing it.