A brand that did not exist, and the storefront that had to sell it
Naming, identity, site, tracking, assistant, hosting and ads for an artisanal food business, built from an empty page.
- Naming
- Identity
- Website
- SEO and AEO
- Tracking
- Chatbot
- Hosting
- Ads
Orree began as a decision that had not been made yet. There was no name, no mark, no palette, no site, and no idea how any of it would be measured. Everything on this page came after that, in order, from one pair of hands.
That sequence matters more than any single piece of it. A name chosen without knowing how it will look set in type, a site built before anyone has decided what a sale is, an ad account switched on before the tracking exists: these are the ordinary ways a launch quietly wastes its first six months.
Read the rest
Starting with the word
The name had to survive being said aloud in a shop, typed by someone who had only heard it, and read by a customer who speaks Bangla at home and types in Latin letters. It also had to leave room for the business to grow beyond the first product, which is the mistake almost every food brand makes when it names itself after what it happens to sell first.
The palette, the voice and the mark followed from that, not the other way around. One decision at a time, each one narrowing the next.
The storefront
The site was built for the conditions the customer is actually in, not the conditions the demo is recorded in. An old phone, a connection that dips, a thumb rather than a mouse. Product photography is the heaviest thing on the page, and everything else steps aside so those images arrive first.
It was also built to be found by machines that never run JavaScript. Structured data, a clean heading order, direct answers near the top of the page, so an assistant asked about artisanal food in Bangladesh has something to quote rather than a shell to guess at.
Where the measurement had to go
Cash on delivery breaks every assumption commerce tooling is built on. There is no card, no payment webhook, no clean moment where a sale becomes a sale. Someone taps an ad on Tuesday, a courier knocks on Friday, and some of those knocks come back undelivered.
So the events were split by meaning. The order is sent when the order is placed, from the browser and from the server, carrying the same identifier so it is counted once. The confirmed delivery is a separate event, sent later, when the outcome is finally known. The ad platform learns from the second one, because that is the one that pays salaries.
The assistant, and then the ads
A chatbot sits on the storefront and on the messaging apps, answering from the real catalogue and the real prices, and handing over to a person the moment money or a complaint enters the conversation.
The ad account came last, deliberately, and I still run it. That is the part of this list I would defend hardest. The person spending the money can read the tracking that reports on it, because the same person built both. There is nobody to blame and nowhere for a bad number to hide.