Skip to content

Pricing · 2025

Priced for the cost shape of a CEE service operation — not a per-seat SaaS meter.

Every plan is built around the actual economics of dispatching crews across Ukraine, Poland, Romania, and the Czech Republic. Predictable per-technician rates. No surcharge for offline mode, multi-language call handling, or marketplace ingestion. No nickel-and-diming for the parts of the job your dispatcher already does.

Book a Demo See how operations teams use Sluzhba
  • 4.3 moAverage customer payback, 2022–2024 cohort of 412 deployments
  • 94%First-month technician adoption, measured across 28,000+ field users
  • 99.97%Trailing-12-month platform uptime, third-party audited
Sluzhba dispatch console showing a CEE job board

Two tiers · Built around your crew size

Pick the tier that matches today's operation. Add modules as you grow.

Pricing is per active technician, billed monthly. Active means logged a route, a job, or a status update inside the billing period — not a seat that exists on paper. Plans can be co-termed or anniversary-aligned at signature.

Tier 01

Growth

For a single-trade or single-city operation running 10–80 technicians.

€42 per active technician / month

10 – 80 technicians

  • Dispatch & routingTerritory-aware job board, drag-to-reassign, travel-time model calibrated for CEE traffic patterns.
  • Mobile field appOffline-first Android & iOS, sync on rural 3G, photo capture, signature on glass.
  • Customer comms11 CEE languages incl. Ukrainian, Polish, Romanian, Hungarian, Bulgarian. SMS + WhatsApp inbound.
  • Cash & invoice hybridCash-on-completion reconciliation built in, not a plugin. Privat24, LiqPay, Stripe.
  • Job board ingestionOne marketplace integration of your choice — Prom.ua, Rozetka, Allegro, or eMAG.
  • ReportingSingle-location dashboards: first-time-fix, SLA, technician utilisation, revenue per route.
  • Onboarding14-day structured rollout with a named implementation lead.
Book a Demo

Tier 02 · Most chosen by ops directors

Scale

For multi-trade, multi-city networks running 80–250 technicians across regions.

€64 per active technician / month · volume bands drop to €54 at 200+

80 – 250 technicians

  • Everything in GrowthPlus the modules operations directors ask for once they cross the second branch.
  • Multi-location reportingRoll-up by region, branch, trade. Drill into one location without leaving the parent view.
  • All four marketplacesProm.ua, Rozetka, Allegro, eMAG — lead ingestion into a shared pipeline.
  • Advanced SLA engineCustomer-tier promises, time-windowed commitments, escalation rules, breach alerts.
  • TelematicsOptional. Native bridge to Wialon, flespi, and GPS-Trace for fleet telemetry.
  • Custom API & webhooksREST endpoints, signed webhooks, sandbox tenant. ERP and BI hooks documented.
  • Onboarding30-day rollout with a solutions architect. Migration from clipboard, WhatsApp, or legacy ERP included.
  • Customer successQuarterly business reviews, named CSM, SLA-backed response times.
Book a Demo

Both tiers contractually waive the per-seat meter for dispatchers, owners, and accountants — we sell against field coverage, not browser tabs.

Add-on rail

Flat-rate modules. No usage-based metering.

If you need one of these you should be able to budget it on a single line. Every add-on is priced per active technician per month, and contractually will not switch to a per-event meter.

  • Telematics & fleet bridge

    €6 / tech / mo

    Native ingestion from Wialon, flespi, GPS-Trace, and 14 additional CEE-grade fleet systems. Live route replay, geofence alerts, fuel/idle reporting — surfaced inside the same job board your dispatcher already lives in.

  • Marketplace lead ingestion

    €4 / tech / mo

    Plug into Prom.ua, Rozetka, Allegro, eMAG, OLX, and Allo. Inbound chats and orders land as draft jobs with the original lead attached — your team quotes without copy-paste, and the marketplace conversation history stays in the same record.

  • Advanced SLA & escalation

    €5 / tech / mo

    Customer-tier promises (VIP, contract, retail), time-windowed commitments, breach alerting to dispatchers and to the customer via SMS/WhatsApp, and post-incident root-cause reports for the QBR conversation.

  • Custom API & webhooks

    €8 / tech / mo

    REST endpoints for jobs, customers, technicians, invoices. Signed webhooks. Sandbox tenant for staging. Documentation written by the engineers who answer your integration tickets, not an auto-generated OpenAPI dump.

How you pay

Pay the way your finance team already pays vendors.

Procurement friction is the most common reason a good demo becomes a stalled deal. Sluzhba is built so that finance can sign off without restructuring their rails.

  • Privat24

    UA · corporate & individual

    Native business-account debit and standing-order support. Receipts reconcile back to invoice line.

  • LiqPay

    UA · card & tokenised

    Tokenised recurring billing. Card data does not touch Sluzhba infrastructure; PCI scope narrowed to the payment step.

  • BLIK

    PL · six-digit mobile

    Six-digit mobile authorisation, including PolishSpzoo VAT-correct invoices. Covers 90%+ of Polish retail payment flow.

  • Stripe

    EU/EEA · card & SEPA

    Card and SEPA Direct Debit with webhook reconciliation into the same invoice record used by your finance team.

  • SEPA

    DE / AT / NL / FR

    EUR-denominated standing orders across the SEPA zone. Monthly invoice net-14 standard; net-30 on request.

  • Cash-on-completion

    All CEE markets

    Built into the technician mobile app. Cash collected on site reconciles to the job at end-of-shift; branch-level variance report at end-of-day.

ISO 27001 · continuously certified since March 2022 99.97% trailing-12-month uptime · third-party audited VAT-compliant invoicing in UAH, PLN, RON, CZK, HUF, EUR

The math, in plain numbers

From 1 dispatcher per 8 routes to 1 per 22, in 90 days. That is where the payback comes from.

The most expensive line item in a CEE field service operation is almost never software. It is the dispatchers between the jobs and the crews. Sluzhba is built to compress that ratio without losing the human judgement that resolves edge cases.

1:8 → 1:22 Dispatcher-to-route ratio, before vs. 90 days after
−37% Average drive miles per completed job, measured cohort
4.3 mo Customer payback period, 412 deployments (2022–2024)
Book a Demo

Procurement questions

The five questions operations directors ask before booking a demo — answered honestly.

If your question isn't here, [email protected] reaches a person in Lviv within four business hours.

  1. Is there a contract minimum, and how long is the commitment?

    Annual commitments are standard. We also offer 6-month commitments for operations running a pilot, and quarterly contracts during the first 90 days of a phased rollout. The 4.3-month average payback shown above is computed against annual pricing — shorter terms have a 12–18% uplift to cover our own prepayment risk, and we will say that in writing before you sign.

  2. What does onboarding cost, and what does the implementation actually include?

    Onboarding is fixed-fee and quoted against technician count, branch count, and data-source migration complexity. Growth deployments start at €4,800 one-off; Scale deployments are scoped against a 30-day plan and typically run €9,000–€18,000. The fee covers data import from your existing tool (Excel, 1C, SAP B1, or a legacy FSM), dispatcher training, technician onboarding, and a 30-day post-go-live window with a named implementation lead.

  3. How do we migrate from clipboards, WhatsApp groups, or four overlapping spreadsheets?

    Our migration team has seen all of these and worse. The pattern is the same: we import your customer master, your inventory master, and your last 90 days of completed jobs as a baseline, then run a parallel period (you operate both systems) for 14–30 days until the numbers reconcile within 1%. Branch-by-branch cutovers are normal — we do not insist on a single big-bang go-live.

  4. Do you offer multi-location or multi-trade discounts beyond the published tiers?

    Yes, published as a flat percentage once you cross 200 active technicians or 3 branches in different oblasts/voivodeships. The Scale tier drops from €64 to €54 per active technician per month at that band, and we will commit that ceiling in writing against the actual headcount you operate at signature. We do not run quarterly volume rebates — they reward complexity we are not selling.

  5. What happens after a pilot ends?

    If the pilot produces the headcount, SLA, and reporting outcomes we agreed on, the contract moves to the full tier at the published rate — no renewal uplift. If the pilot does not produce those outcomes, you keep everything you built, we write off the implementation fee, and we part as professionals. We have lost three pilots in six years; the reference calls we share are 100% opt-in, including the conversations where a customer decided not to proceed.

Ready to scope a deployment? Most operations directors book with one calendar invite and a list of three pain points.

Book a Demo