— On pricing
A shape,
not a number.
We don't publish a price list. The cost of buying for an Indian D2C floor depends on the depth of your assortment, the cadence you run, and the windows you sell into. We size each engagement to the work — then write a single transparent number for the year.
The rate card, hand-written.
Brands fall into three rough operating shapes.
We rarely take a brief that does not sit inside one of these. Read the one that matches your floor; ignore the others. The shape, not the price tag, is what tells you whether we are the fit.
- I~20 SKUs
The capsule.
— Weekly forecasts
A buyer at one desk, with one notebook. The engine reads with her.
A heritage-occasion label running a tight capsule. Twelve looks for Diwali, eight for wedding-guest, a steady chanderi base. Per-style demand bands at 30 / 60 / 90 days, the quarterly meta-report, and a phone-call cadence with the founder during festive windows.
- II~200 SKUs
The buying floor.
— Daily refresh
A buying floor that meets every morning. The brief is on the table when the buyers walk in.
A daily-wear D2C with rotating drops across kurta, co-ord and lounge. Two designers, three drop calendars, four cities of intent. Daily refresh, competitor benchmarking across the 24+ Indian D2C set, regional slicing north / south / east / west, and the festive almanac feeding the calendar directly.
- III~2,000 SKUs
The merchant operation.
— Per-region forecasting
A merchant office where the calendar is on the wall and the runway is on the table.
A multi-category house with a designer cohort, ten-city footprint, and a buying calendar that runs eighteen months ahead. Per-region forecasting at city granularity, custom designer cohorts on top of the standard runway watch, sub-segment slicing (wedding-guest, festive co-ord, occasion-luxury), and a named buyer-relations contact.
Sit between two shapes? Most brands do. We'll find the seam on the data-fit call.
The maths the founder
doesn't write down.
Every Indian D2C founder has a number for last Diwali's over-buy. Few write it down. Slide an honest figure and read what the markdown took — alongside what a year of TrendSense would cost.
— Likely markdown loss
₹18.0 L
At a 45% markdown — roughly what Indian D2C womenswear takes on unsold festive stock once EOSS and the post-Diwali drag are in.
— A year of TrendSense
₹6 L – ₹30 L
Sized to your assortment depth and buying cadence. The figure opposite would buy 7.2 months at the upper end.
For context, not a quote. The maths is a heuristic against published markdown depths in Indian D2C womenswear. Your number is your number; we'll work it out together on the data-fit call.
If after the fourteen-day proposal phase you choose not to continue, the data we synced is yours. We delete our copy.
Three calls. Ten days.
No drawn-out evaluation phase, no procurement choreography. From the intro call to a one-page proposal on your desk is a fortnight, and the sample forecast on your own data is the halfway mark.
- 1
Day 0
Intro call.
Twenty minutes. What you sell, where you sell it, what hurt last season. No deck.
- 2
Day 4
Data sync.
We connect Shopify (or take a CSV), pull the last 180 days, and run the engine on your own data.
- 3
Day 10
Proposal landed.
One page. Scope, cadence, cost. The sample forecast is in your inbox; if we are not the fit, you keep it.
— From the engine room
This week
Regional demand slicing rolled out — north / south / east / west.
Next
Visual search on the 247-attribute taxonomy. Upload a swatch; the engine returns its closest cousins.
— The engine ships every week
— Two ways in
Pricing is a conversation,
not a catalogue.
Twenty minutes on a call is the cheapest possible read on whether we're a fit. If we are not, you'll walk away with the sample forecast.