← back to all work
01
distributor-management-system.case

Distributor Management System

Built and shipped a modern DMS to replace legacy workflows — designed for distributor operations, admin governance, and finance compliance. Adopted by four enterprise customers in the first year.

Role
Product Manager · 0→1 owner
Timeline
Apr 2025 — 2026
Team
2 designers · 8 engineers · QA
Status
Live · 4 enterprise customers
Distributor Management System product screenshot
The product The DMS console — built workflow-first, with role-based access from day one. Each screen is scoped to admin, sales head, finance, or field rep.

Legacy DMS tools didn’t fit modern distributor operations.

Salescode.ai had no internal DMS — but our SFA and eB2B customers were repeatedly asking for one. Existing tools in the market were built for a different era: rigid order flows, no audit trail, minimal governance, and unusable on a phone for field ops.

Users: distributor admins, sales heads, finance teams, and field reps — mostly non-technical, often working in low-connectivity environments.

Pain points: manual order tracking in spreadsheets, schemes invisible to the field, no clear approval flow, and reconciliation taking days each month.

Business objective: complete the enterprise sales-tech suite, unlock new revenue, and protect existing accounts considering competitors.

Constraints: no domain expertise in-house, parallel SFA roadmap commitments, and a 4-customer rollout target inside the first year.

Workflow-first. Role-based. Adoption-led.

  • Discovery. Spent four weeks shadowing distributors, sales heads, and finance teams. Mapped real-world order flow, exception patterns, and the spreadsheets people actually used.
  • Prioritization. Ranked features against two questions — does it move the adoption metric, and does it survive a finance audit? Cut anything that didn’t.
  • Delivery. Broke the system into shippable slices: orders, schemes, approvals, reporting. Each slice rolled out behind a feature flag and validated with one pilot customer before wider release.
  • Validation. Defined the adoption metric as % of orders fully processed in DMS, not logins. This forced us to fix workflow friction, not vanity metrics.

The trade-offs that shaped the product.

  • Invoice integrity over editability. Finance teams wanted free-form edits; we shipped immutable invoices with a corrections log instead. Slower for ops at first, but it survived the first audit cleanly.
  • Role-based by default, not as an add-on. Every screen was scoped to a role from day one — admin, sales head, finance, field rep. No “view-all” backdoors.
  • Phone-first for field, desktop-first for admin. Two distinct UI paradigms instead of one responsive compromise. Cost more to build; produced two products people actually wanted to use.
  • Adoption metric = orders processed, not logins. Aligned the team with the customer’s real outcome and prevented us from celebrating empty engagement.

Live with four enterprise customers in year one.

The DMS is now used by Coca-Cola, Cavin Kare, Nllne, and App Passeo — supporting onboarding, order management, schemes, and reporting in production. Adoption metrics have held above target for two consecutive quarters.

30–35% Reduction in manual tracking
+40% Lift in scheme & sales visibility
4 Live enterprise customers

From DMS to intelligent distribution.

The roadmap now folds in AI/ML enhancements — sales forecasting, outlet attrition prediction, and field insights surfaced directly in the rep’s daily flow. The thesis: a DMS that tells you what to do next beats one that just records what happened.

next case study · 02 / 03 Reducing cart abandonment in quick commerce