Kusa Studio

Concept demos

We're a new studio, so instead of client logos here are three systems we build, shown with synthetic data. Two of them work right on this page. Real client work will appear here only with the client's written permission.

Concept demo

Sales, stock and reporting for a distributor

The problem
Sales agents keep their own sheets, stock is counted weekly in another file, and the owner gets the weekly report on Wednesday, already out of date.
What we'd build
A single data pipeline that collects agent orders and stock movements as they happen, plus a dashboard with sales against the previous period, margin, reorder alerts and a Monday summary that writes itself.
What it could change
Decisions on fresh numbers instead of last week's. Reorders driven by actual sell-through rather than memory. The person who built the report by hand gets those hours back.

Inside the live demo

Runs in your browser with 180 days of synthetic orders.

  • Period, region and category filters
  • Sales trend against the previous period
  • Inventory with days of cover and reorder alerts
  • Add an order and watch stock and alerts react
  • Preview the automatic Monday summary email
  • Export the filtered data to CSV
Open the live demo
Concept demo

Chat orders into a clean order sheet

The problem
Customers order by WhatsApp, Viber, text and email in their own words. Someone retypes every message into the order sheet, guessing at product names and sometimes missing lines.
What we'd build
An order reader that matches messy item names to your product list, prices each line, and flags anything it isn't sure about for a person to confirm before it goes into the order sheet.
What it could change
Less retyping, fewer wrong items shipped, and every order captured in one place with a timestamp. The person stays in control of anything unclear.

Try it: paste or edit an order message

This version uses simple matching rules and runs entirely in your browser. Nothing you type is sent anywhere.

Concept demo

Collections tracking with automatic reminders

The problem
Receivables aging is worked out from invoice lists at month end. Reminders depend on someone remembering, so overdue accounts are noticed weeks late.
What we'd build
An aging view that updates as invoices and payments are recorded, with a polite reminder schedule that sends itself and stops the moment a payment is logged.
What it could change
Earlier follow-ups, fewer awkward phone calls, and a clear list each morning of who needs a personal call instead of an email.

Receivables by age

Sample figures for a fictional distributor.

Reminder schedule for one invoice

Stops automatically when payment is recorded.

  1. 3 days before due: friendly heads-up with the invoice attached
  2. On the due date: reminder with payment details
  3. 7 days overdue: second reminder, copy to the account's sales agent
  4. 21 days overdue: flagged on the morning list for a personal call

Have a version of one of these problems?

Tell us which one and what tools you use today. We'll reply with how we'd approach it.

Send a project brief About the diagnostic
Send a project brief See prices