logo

IT System Support and Development

We take on a running system — ours or someone else's. Good support is invisible: our team hears about an outage before your customers do, and improvements ship on a plan rather than in a panic.

Formats and terms
Service desk
SLA
Incident resolution
Восстановлено
Improvements and development
v1.4v1.5
Monitoring and alerting
99,9%
Upkeep and optimisation
Профилактика
Taking over from another team
Аудит кода
We work under an SLAwith agreed response times and monthly reporting

When you need a support vendor

Support isn't for when everything is already broken — it's for when downtime costs more than maintenance. One sign is enough:

Failures get fixed in panic mode, with no procedure

There are no agreed response and recovery times (SLA)

The in-house team is overloaded and can't close everything

You need improvements and development, not just bug fixes

The previous team left and nobody maintains the system

The system slows down as the database grows and needs upkeep

«Good support means our team hears about the problem first, not the users.»
Evgeny Ramazanov — CTO, PROFSOFT

What support covers

Six areas of work. The exact scope is fixed in the contract, based on the system and how critical the processes are.

Service desk

A single entry point for every request: logging, classification, prioritisation and routing.

Result

No request is lost in a thread — each has a status, a priority and a deadline.

Incident resolution

Diagnosis and service recovery by procedure, followed by root-cause analysis.

Result

First the service runs again, then the cause is closed for good rather than until next time.

Improvements and development

New features, interface changes and enhancements requested by the business, shipped in planned releases.

Result

The product keeps developing without turning every release into a risk to stability.

Monitoring and alerting

Availability, error and performance monitoring with alerts to the on-duty team.

Result

Our team is the first to know about a problem, not your users.

Upkeep and optimisation

Work on database growth, performance, dependency updates and technical debt.

Result

The system doesn't degrade as data and load grow.

Taking over from another team

Audit of code, infrastructure and technical debt, documentation recovery and a stabilisation plan.

Result

A clear picture of the system's state and a plan: what to fix now, what can wait.

Ways to work together

Three formats for different levels of criticality and workload. We recommend one after auditing the system.

Warranty support

For projects we built, right after launch.

Terms

  • Free of charge
  • For 6 months after release
  • Only for projects developed by PROFSOFT
  • Incident-based work
  • Transparent reporting

Capped hours

When work comes up irregularly and a standing team makes no sense.

Terms

  • Billed on hours actually spent
  • Fixed hourly rate
  • For any project, including ones we didn't build
  • Preliminary system audit
  • Incidents and product improvements

Retainer

When the system is business-critical and under constant development.

Terms

  • Quarterly or annual billing
  • Fixed cost
  • Dedicated team
  • Unlimited improvement requests
  • Release and capacity planning
  • Monthly reporting

How we take a system on support

Six stages from audit to routine work. By the time the first incident arrives, we already know how your system is built.

1

Audit

Code, infrastructure, technical debt and risks

2

Procedure

SLA, priorities and escalation channels

3

Knowledge transfer

Documentation, access, architecture walkthrough

4

Monitoring

Metrics, alerts and on-duty rotation

5

Stabilisation

Closing the critical findings from the audit

6

Routine work

Incidents, releases and reporting

What we track and report on

Support quality should be visible in numbers rather than claims. These figures go into the monthly report.

Response timeRecovery timeSLA complianceRepeat requestsSystem availabilityRelease stabilityMonthly reportOpen backlogHistory for every requestIncidentsImprovementsUpkeepConsulting

Projects we support

Business car
Business car

Business car

Mobile app for one of Russia's largest car dealers

View case
Protector
Protector

Protector

Built an app to protect children in dangerous situations with live location sharing and fast help escalation

View case
Maria
Maria

Maria

Built and launched a mobile app to automate processes for the largest furniture factory in Russia and the CIS

View case
ORGHIM
ORGHIM

ORGHIM

Internal app for optimizing company business processes

View case
Samberi
Samberi

Samberi

Mobile app for a hypermarket chain

View case
Athletes Academy
Athletes Academy

Athletes Academy

A mobile app and admin panel: athletes earn a sports rank on video and get the award by post

View case

IT support FAQ

Yes, that's a large part of our work. We start with an audit: code, infrastructure and the scale of technical debt, plus recovering documentation where none exists. We then give you a stabilisation plan and say honestly what risks the current state carries.

It depends on the format: billed hours against a cap, or a fixed quarterly or annual retainer. Criticality, required response time and the volume of improvements all move the price. We give an exact figure after the audit — before that, any number would be invented.

An SLA is the agreed response and recovery time for each type of request. A critical outage blocking the business and a small interface annoyance get different priorities and different deadlines. The actual figures are fixed in the contract, based on how critical your processes are.

No. Improvements and development sit alongside incidents: new features, interface changes, optimisation. That's why we keep a shared backlog and plan releases rather than only reacting to breakage.

We hand over the code, documentation, access and the open backlog. We run projects so they can be handed over — without that, support turns into vendor lock-in.

Yes, and ideally before the first incident. An audit shows where the system is fragile as load and data grow, and lets us commit to a realistic SLA. Taking on a system whose internals we don't know would be unfair to you.

Discuss support for your system

Tell us what the system is and what's happening with it now. We'll propose a format and the scope of an audit.