Services / Day One
The first version exists to produce information, not to be finished.
A first store is not a smaller version of a mature one. Its job is to generate the first real data about what people will actually pay for, which means the correct scope is the smallest thing that can transact honestly and be measured, shipped fast enough that the market answers before the budget runs out.
The canon
The principles this rests on, named.
Each with who established it, so the claim can be checked rather than taken on our word.
Build the smallest thing that produces a real signal.
Eric Ries, The Lean Startup; and Steve Blank's customer development before it
Not a rough thing. A small, complete, honest thing. The distinction is what separates a minimum viable product from an excuse for poor work.
Speed of learning is the actual constraint, not speed of building.
Boyd's OODA loop, applied to product
Fifteen working days is not a marketing number. It is chosen because a launch that takes four months has burned the runway before the first honest data arrives.
Trust signals decide the first transaction, because nothing else is available.
Stanford Web Credibility Project (B.J. Fogg); Sillence et al. on staged trust
A new brand has no reviews and no reputation. Contact details, a clear returns policy, real photography and a working payment flow are the entire credibility budget.
Measurement is installed before launch or it is never accurate.
Analytics practice
Retrofitted tracking loses the first weeks, which are the only weeks where the baseline exists.
Indian D2C converts at roughly 1.6% on average, against about 2.2% in the US.
Published India D2C benchmark data; cart abandonment 30-45%
It sets an honest expectation for a first store, and it is why COD, payment method coverage and delivery clarity get more attention here than a US playbook would give them.
Launch with the catalogue you can photograph well, not the one you can list.
Practical constraint, learned the expensive way
Twelve products with real imagery outsell sixty with placeholder photographs, and they are far easier to learn from.
Method
What actually happens, in order.
One question, written down. Everything not needed to answer it is out of scope for launch and goes on a list for later.
Mark, palette, type and the rules. Enough to be consistent, not a full manual, which is a later purchase for a reason.
Home, collection, product, cart, checkout. Every other page is secondary and is built after the path that takes money works.
UPI, cards, netbanking, wallets, and a decision on cash on delivery made with its return economics understood, not by default.
Analytics, events, and the pixel, tested with real transactions rather than assumed to be working.
The build is not the deliverable. The first read of real behaviour, and what to change because of it, is.
What goes wrong
The failure modes nobody advertises.
The blog, the loyalty programme, the quiz. All reasonable later; all reasons the store did not launch.
The first four weeks are the only true baseline you will ever have, and they are unrecoverable.
It lifts conversion and it carries a return and RTO cost that can exceed the margin. It is a decision, not a default.
A catalogue that looks unfinished and teaches nothing, because no product got enough attention to be a fair test.
Six weeks of identity refinement on a product nobody has yet been asked to buy.
What we refuse
A studio is defined as much by this list.
- We do not launch without analytics and conversion tracking verified against a real order.
- We do not add scope during the build; it goes on the list for after launch.
- We do not ship placeholder photography.
- We do not enable cash on delivery without showing the client its cost.
Measured, not felt
How anyone can tell whether it worked.
Time from approved wireframe to live, against the fifteen working day commitment.
First order, and the time it took to arrive.
Conversion rate baseline established in the first four weeks.
Checkout completion rate by payment method, so the method mix is a decision.