Bargain Rani is a marketplace built for the Indian woman who has always negotiated in the local market and has never been allowed to online. The obvious product is a haggling game. The one I designed puts trust first and treats bargaining as the hook that gets her through the door, because women do not churn over price, they churn over a wrong-size kurti and a refund that never arrives.
An Indian woman negotiates without a second thought at a sari shop, a vegetable cart, a jeweller. Move her online and the same instinct is designed out. One fixed price, take it or leave it, and an unspoken message that asking for less is embarrassing. Meanwhile the things that actually decide whether she comes back, will it fit, is it genuine, will a refund arrive, are handled worst of all.
The strategic call that shaped everything: bargaining is the hook, trust is the job. If the platform wins the negotiation and loses the return, she never comes back, so the trust infrastructure was specified before the mechanic that gets attention.
The persona work refused the flattering version. She is not a deal-hunting gamer who wants to haggle for sport, she is time-poor, sceptical from experience, and quietly negotiating everywhere else in her life. Bargaining is only appealing if it costs her nothing when she cannot be bothered.
The palette and type ramp are declared once and consumed identically by the Next.js web build and the Expo mobile app. Warm ivory and parchment rather than the marketplace default of stark white; forest emerald and 18k gold to signal considered value rather than discount-bin urgency.
Colour, type, radius and shadow are declared in globals.css for web and mirrored exactly in lib/colors.ts and lib/fonts.ts for mobile. A change to the brand is a change in two files, not two codebases.
Buyer, seller, manager and admin each have distinct entry points, permissions and surfaces. Role transitions are enforced by a database function rather than client-side state.
A ten-step shadow scale including gold and saffron variants gives the interface depth without borders, which keeps the editorial feel intact at density.
The strategy inverts the obvious order. Trust mechanics are specified and built first; bargaining is layered on top as the thing that makes the platform memorable rather than the thing that makes it work.
Each of these had a more obvious option that would have shipped faster and demoed better. In every case the chosen path protected the trust promise rather than the pitch.
Five capabilities carry the product. Each one exists to make either the negotiation or the trust behind it legible to a buyer who has been let down before.
The build is a working marketplace against a live Supabase database. Authenticated pages render real orders, real carts and real seller catalogues rather than fixtures.
"I spent the first week designing the bargaining game, because it is the fun part and it is what the idea is named after. Then the persona work made it obvious that I was decorating the hook and ignoring the job. Women do not abandon a marketplace because the price was too high, they abandon it because the kurti did not fit and the refund took three weeks. So I stopped and built the trust layer first. The bargaining is still the reason anyone tells a friend about it. It is just no longer the reason the product works."
"Adding Name Your Price felt like hedging, and hedging felt like weak conviction. It is the opposite. Committing everything to live haggling would have been a bet that Indian women want to negotiate with a stranger in real time on their phone. I believe that is true for many of them. I do not know it, and the product should not need me to be right."
Every screen below is captured from the running Next.js build against a live Supabase database, so the authenticated pages show real data rather than placeholders.