nikam.dev ← All cases Telegram →
nikam.dev / Cases / Command centre for marketplaces
Live · Telegram bot + Mini App

Team control and store signals on the marketplace - in Telegram.

Sellbridge / Löva. Telegram bot and Mini App for sellers on Wildberries. Two loops in production: team discipline (a daily checklist, reminders, an evening report to the director with money and a «Nudge» button) and store signals (bad reviews and buyer chats into the team chat, stock every 4 hours, ad budget with a «runs out by HH:MM» forecast). The product is growing into a multi-store command centre.

What
Telegram bot + Mini App
Market
Wildberries
In prod
Team control + signals
Status
Live · 2 loops in production
Open sellbridge.nikam.dev →
- The problem

The owner doesn't know whether the team does the daily work - and learns about problems after the fact.

The WB cabinet is powerful, but it's a place you have to walk into. The manager should answer reviews, handle questions, watch stock and ads every day. Whether they do - becomes visible when the rating dips or the item runs out. There's no control in the moment.

Pain 01
The manager's work is invisible until something breaks
Did the manager answer the reviews, handle the questions, check the stock - the owner finds out after the fact. Between «doing it» and «not doing it» sits a whole day of invisible work nobody is answerable for by name.
Pain 02
To see what's new - you have to open the cabinet
A new bad review, a buyer's question, a chat - all of it sits inside the cabinet and waits for someone to open the tab. Reaction speed suffers proportionally - and the store rating with it.
Pain 03
The ad budget burns out mid-day
The ad balance ran out at lunch - promotion stopped, and everyone learned by evening. Topping up «by eye» is bad too: money arrives from WB on a payout schedule, and the ad account should get exactly what survives until the next payout.
Pain 04
The day's profit is unknown
The cabinet shows revenue, but «how much did we earn» - no: ads, commission, cost of goods are scattered across sections and spreadsheets. The owner sees profit once a month from the accountant, not every evening.

Two loops in production: team discipline and store signals.

The product runs on a real WB brand. The owner's task was manager control; a second loop grew around it: store events come to Telegram by themselves, with a forecast, not after the fact.

L
Löva · WB control director + manager · bot connected
⋯
today
daily checklist Good morning. Tasks for today:
1. Answer reviews < 4★
2. Handle buyer questions
3. Check stock on top SKUs
4. Reconcile the ad budget
10:00 · bot
ads Ad balance - runs out by 16:40
At the current burn rate the budget dies today. Recommended top-up - accounting for the WB payout schedule.
12:05 · bot
Kirill · manager Topped up, reviews handled.
12:30
reminder By 18:00 - 2 of 4 unmarked
Stock on top SKUs, ad reconciliation. Will you make it by tonight?
18:00 · bot
report to director
End of day: 3 / 4 done · ad spend, ad-share and revenue in the report. Day's profit: computed from SKU costs.
23:00 · bot

A bot that makes the work and the money visible

The manager gets a daily checklist at 10:00 and marks completion. During the day the bot reminds about the unmarked. In the evening the director gets a report: what's done and how much was earned - with a «Nudge» button if the day was missed.

1
Daily checklist to the manager - at 10:00 Every morning the manager gets the store's daily task list and marks completion right in Telegram: «changed the bids?», «what did you find in reviews?» - with preset answers. The work stops being invisible. Weekends are skipped automatically.
2
Reminders by day, a director's report by night Unmarked by 18:00 - the bot reminds the manager. By 21:00 - reminds harder. In the evening the director gets the day's report with a «Nudge» button: a reminder goes to the manager in one tap, no conversations. The report live-updates if the manager finishes late.
3
A report with money, not just checkmarks The evening report carries ad spend, ad-share of revenue, revenue and the day's gross profit. The profit is honest: until the cost of every sold SKU is entered, the bot shows a dash - not an invented number.
4
Bad reviews and buyer chats - into the team chat 1-3★ reviews land in the team chat with SLA control - «this one has been unanswered for 12 hours». Buyer questions and messages go there too. You can reply right from the bot, without opening the cabinet.
5
Stock - every 4 hours, in days of cover Not «100 units left», but «less than 14 days of cover - red». Plus a daily warehouse-diff check and a sales anomaly detector: an SKU suddenly selling 60% above or below its usual pace is a signal.
6
Ad budget - with a forecast, not after the fact The balance is checked every 15 minutes. The bot computes the burn rate and warns ahead: «runs out by 16:40». The top-up recommendation accounts for the WB payout schedule - how much money actually survives until the next payout.

This is the live loop in production. Where the product grows next - below.

Where it grows: a multi-store command centre.

The product's core is a tenant-agnostic library: the same modules that run in production plug into any seller. What's in development is labelled honestly.

live · skeleton
Owner's Mini App
The app and billing are deployed: onboarding, WB-token connection (encrypted), subscription. The dashboard runs on demo data for now - the live alerts API is in the works.
in development
Multi-store
Several stores per owner, a team with «director / manager» roles per store. The core is already multi-tenant - the worker polls stores in parallel.
in development
Other marketplaces
Today the product lives on Wildberries. Ozon and Yandex.Market are the next adapters over the same signals-and-control core.
in development
Per-SKU and per-campaign metrics
Today the money is counted store-wide. The next step - profit and ad-share broken down by each SKU and ad campaign.
- Outcome

What changes for the owner from day one.

10:00 → 23:00
The discipline loop: a checklist in the morning, reminders by day, and in the evening - a director's report with money and a «Nudge» button.
1-3★
Bad reviews and buyer questions land in the team chat with SLA control. The reply goes from the bot, without opening the cabinet.
15 minutes
The ad-balance control cycle: a «runs out by HH:MM» forecast and a top-up recommendation that accounts for the WB payout schedule.

Is the team working - or just reporting?

If you have a seller team on a marketplace and you learn about misses after the fact - let's talk. In a 30-minute call we'll figure out what in your store should be made visible and manageable first.

Message on Telegram → nick@nikam.dev