Your network's command centre.
A chain is not a big outlet. It is a franchisor with a finance function, a supply chain, a legal clock and forty partners whose money is not its money. Slotwise was built for the network first — then scaled down to the chair.
What needs you today, ranked by rupees.
Five money-first tiles
Network revenue MTD, money lost this month, royalty collected, outlets at risk, approvals waiting — each with trend and cause.
Brief me
Your day in three sentences, written by the system from the network's signals.
Signals with actions
Every row carries rupees at stake, outlet count, age, an owning function and a one-click action.
Network health index
Cash share, NPS and capacity on one dial, with twelve weeks of history.
Seven moments a COO recognises from their own week.
Not a module list. The routines that change how a network is run.
What needs me today
Every morning, ranked by rupees at stake, with the action one click away.
Where the money went
No-shows, discount leakage, idle hours, stock variance — named, priced and owned.
Royalty without arguments
Live royalty on platform revenue, cash-share anomalies flagged, a settlement ledger both sides can see.
Every franchisee, 360°
Health, compliance, contract clock and open items per partner — before the relationship sours.
Supply chain you can trace
From tender to chair, with OTP handover and batch recall — the retail-grade backbone this industry never had.
Open the next 100 outlets
Franchise development as a pipeline, not a spreadsheet — from lead to first-month ramp.
Ask the network
Ask a question in plain language, simulate the policy, roll it out with holdouts, and log the decision.
…and 100+ live modules
Across Overview, Money, Govern, Operate, Grow, Expand, Intel and Settings.
Every leak named, priced and owned.
Supply chain, Collections, Brand pricing, Growth, Compliance, Marketing — a money problem becomes someone's queue with a deadline, and HQ sees the age of every item. That is governance, not reporting.
- Stock variance — third consecutive shortfall, same SKUs, same shift: Review variance
- Receivables — overdue beyond 30 days, credit-block line crossed: Open receivables
- Discount overrides — manager cap bypassed: Review overrides
- Campaign attribution — HQ campaign bookings, contribution invoice not raised: Contribution ledger
Royalty on platform revenue, not self-declared revenue.
Cash share above the cluster median, royalty pending or overdue, and open items per outlet surface as signals with an owner — before the relationship with a franchisee sours.
- Outlet league — FOFO / FOCO, revenue vs cluster median, health score, cash share, royalty status, open items — one row per outlet
- Zone performance — revenue, outlets at risk and health per zone, month on month
- Settlement ledger both sides can see; FOCO payouts; HQ contribution
Eight command areas. 100+ live modules.
A selection from each area. Live in production, enabled per your operating model. Full dated module list available for due diligence.
Overview
Command centre · Network map · Action queue · End-to-end chains
Money
Royalty & settlements · Receivables & arrears · Money lost · Consolidated P&L · FOCO payouts · Cash & banking · E-invoicing & TDS · Statutory payroll
Govern
Approvals & SLA inbox · Contracts · Expiry & renewal clock · Legal & signing · Evidence & audit trail · Audit log centre
Operate
Outlets · Warehouse · Sourcing & tendering · Batch trace & recalls · OTP handover · Cycle counts · Quality & audits · Field ops · Chair yield · HRMS & payroll
Grow
Campaigns · Template distribution · WABA fleet · Messaging health · Consent register · Customer equity · Retention missions · Prepaid liability
Expand
Development pipeline · Site selection · Fit-out & ramp · Prospectus · Territories · Resale & transfer · Distress watch
Intel
Network intelligence · Findings queue · What-if simulator · Benchmarks · Ask the network · Scenario studio · Rollout & holdouts · Decision log
Settings
Business type & modules · Rules & workflows · Brand setup & theme · Workspaces & personas · Privacy & consent (DPDP) · Security & trust · Access control · Integrations & payments hub
Before Slotwise
- Check the franchisee’s Excel.
- Check WhatsApp for the royalty reply.
- Call the area manager.
- Argue about self-declared revenue.
After Slotwise
- Open the command centre.
- Royalty on platform revenue, already computed.
- Every outlet at risk, ranked by rupees.
- Done.
Security and data
288 permission switches with per-outlet scoping. Evidence and audit trail on every change. Privacy and consent built for DPDP. Your data stays yours — export any time.
Migration and rollout
Legacy data migration, store provisioning and a rollout-with-holdouts tool so you can prove a policy on twenty outlets before four hundred.
Support
Named customer success manager and a direct escalation path. Onboarding by a team that has done franchise rollouts, not a ticket queue.
Better visibility. Better decisions. Better business.
A 30-minute walkthrough of the HQ command centre on illustrative data — then a Revenue Control Audit on your own export if you want the real number.
