Selected work / Compass

Compass

An operations product for supplier onboarding, built around clearer handoffs and less manual coordination.

Client

Compass

Domain

Operations

Use case

Supplier onboarding

Compass

Structured onboarding flow, internal workflow logic, status handling, and operator-facing product surfaces.

The work

The product supports supplier onboarding as a structured workflow instead of a loose chain of messages, files, and manual status checks.

What mattered

Operational tools need clarity more than flash. The system had to make next steps, status, and responsibility visible to the people running the process.

What shipped

We built onboarding flows, workflow logic, status handling, and product surfaces for the internal team operating the process.

Case study

Compass

Compass runs a network of fuel stations in Kazakhstan with a sprawling supplier ecosystem around it — stores, express markets, cafés, services. Onboarding new suppliers used to live in a chain of spreadsheets, WhatsApp messages and price lists scattered across personal chats. We replaced the chain with a WhatsApp agent. A supplier scans a QR code at any Compass site, lands in chat, and a structured intake walks them through everything Compass needs — company details, contacts, category, files. The output is a clean Bitrix24 card, not another forwarded message.

Problem

Suppliers came in through every door at once.

Compass talks to a large number of suppliers across many product and service categories, and every application arrived in its own shape: a phone call, a WhatsApp file, a forwarded message, an email. Nothing was structured, half the data was missing, and finding "all stationery suppliers in Almaty" was a manual job. The team needed a single intake door that any supplier could find — and a CRM card on the other end with the fields actually filled in.

Solution

One QR code, one chat, one clean record in Bitrix24.

Every Compass site carries a QR code with a city or location identifier baked in. A supplier scans it, opens WhatsApp, and the agent already knows which region the application is coming from — no need to ask. Then a structured intake walks them through the rest. The agent categorises the supplier on the fly, validates IIN/BIN, accepts price lists in PDF, Word, Excel or photo, and writes everything into a Bitrix24 card. The procurement team works from CRM, not from chat history.

Technical work

A bilingual WhatsApp agent wired straight into Bitrix24.

The agent is a Python backend talking to suppliers over the WhatsApp Business API via Whapi. Language is detected automatically — the intake runs in Russian or Kazakh — and the conversation state is driven from our side rather than from a no-code builder. Validation, categorisation and file handling all happen before anything reaches Bitrix24, so the CRM card lands populated, not as a stub for someone to fill later. QR routing is done via per-station identifiers, which let the architecture scale without changing intake logic.

Related work

Running supplier onboarding (or any intake) out of WhatsApp and spreadsheets?

We help operations teams move that pipeline into a single agent — one channel, one structured intake, one CRM record on the other end.

Brief (optional)