Spohady — a complete digital service launched end to end.
We designed the customer website and the operating system behind it: office CRM / ERP, Telegram bot, field-worker PWA, routes, photo QA, subscriptions and finance.

The goal was not a standalone website but a service capable of accepting and delivering real orders
Customers needed a simple booking path. Office teams needed assignment, deadlines and control. Field workers needed addresses, routes and mobile proof submission. Every part had to behave as one product instead of a chain of manual hand-offs.
We connected the full journey from the customer website to execution and settlement
The website creates the order and sends it to Spohady Ops. The system assigns work, tracks status and history, Telegram delivers alerts, and workers complete routes in a mobile PWA. Photos pass quality control before finance and payouts close the loop.
03 · What the system includes
We connected the full journey from the customer website to execution and settlement
- 01
Customer website with service selection and ordering
- 02
Operations dashboard with deadlines, city workload and photo queue
- 03
Order kanban, detailed view, assignment and full event history
- 04
Daily routes, team schedule and multi-city control
- 05
Photo review before completion and rework handling
- 06
Services, subscriptions, finance, margin and worker payouts
- 07
Team roles, access rights, audit trail and alerts
- 08
Mobile worker workspace with PIN access, address, route and camera
- 09
PWA mode, unstable-connection support and push infrastructure
Service journey
Context moves forward without re-entry- 01Website→
- 02Order→
- 03Assignment→
- 04Field visit→
- 05Photo QA→
- 06Payout
04 · Business outcome
Customer, office and field teams work inside one connected service
Every order has an owner, next action, deadline and proof. Customers get a clear path, managers control delivery, and field workers see only what they need for the current visit.
Turnkey launch
One project covered the customer website, internal operations and field execution.
Focused workspaces
Customers get a simple booking path, office teams get control and workers get a mobile route.
Closed operating loop
From first contact to photo review, finance, payouts and audit history.
Discuss a similar process