One person. Two cards.
The decisions underneath a brand split that a logo never answers — designations, direct lines, mailboxes, and whose colours an internal tool wears.
The same director, under two brands.
A person working across two brands does not have one title, one number and one address. The people model treats all three as keyed by brand, because printing one card and hoping is how a firm ends up with a line nobody answers.
| The firm | The marketplace | |
|---|---|---|
| Designation | Director — Business Strategies | Director of Operations |
| Direct line | +91 92574 10057 | +91 62806 21215 |
| Mailbox | consult@savisonlife.com | hi@getpharm.in |
Nobody's name gets parsed.
- Before
- A visiting card has a “save contact” endpoint, so the system has to emit a structured name. The obvious implementation splits the display name on spaces.
- What forced it
- “Naming order varies by culture and guessing it puts the wrong string in someone's contact list.”
- The decision
- The display name and the structured name are written and stored separately — given, additional and family as explicit fields — rather than derived from one another.
- What it changed
- Two fields instead of one piece of string-splitting, in exchange for never addressing a person wrongly in their own phone. A four-line decision nobody would notice if it were made badly, which is what makes it a good measure of an operating model.
The operator console kept the firm's colours.
- Before
- Every customer-facing portal moved to the marketplace brand when the split shipped.
- What forced it
- The admin console is used by the firm's own staff, and after the split it administers both brands' content.
- The decision
- It stays with the firm. Branding resolves per internal route prefix rather than per deployment, so the exception costs one line in a map instead of a second application.
- What it changed
- An internal tool is where an organisation tells its own people who they work for. This one says: the firm.
This is not a fully automated marketplace, and the records say so.
The founder's own reference frames the admin role as real operating cost, under a heading that calls for honesty about it.
Every time
- Buyer drug-licence review.
- Manufacturer application and verification.
- Approved-product review, per factory.
- Manual payment confirmation.
- Disputes and contested ratings.
- Invoice adjustment and consultation scheduling.
Only the reversible
- Flag stale deals daily — never auto-reject.
- Expire carts and consultation slots.
- Complete delivered ready-stock orders.
Anything that could wrongly deny a business its livelihood stays with a human.
A lesson nobody wrote down is a lesson that happens twice.
Both of these were converted from an incident into a standing rule that survives the person who learned it. That conversion is the organisational design, more than any chart would be.
- Detach the website first, then edit DNS — written as an operating procedure after an attached hosting plan silently overwrote the apex record twice, once defeating four fix attempts.
- No chat history is load-bearing. The founder's reference carries the institutional knowledge so that the running system depends on no conversation — the succession plan for a small team working with AI collaborators.
- A missing portrait falls back to an initials tile, so a card page is safe to deploy before anyone has been photographed.
- The milestone-branch-per-feature workflow was adopted and then abandoned in practice. The records say so plainly rather than describing a process nobody follows.
- An operations hire is named as needed ahead of any volume push — scaling without it is recorded as the single most common way platforms like this break trust.
- The people model holds one person, so this study describes how a two-brand firm handles a person, not a staff.
It is the operating company's internal tool. Branding it as the product would be wrong for staff.
src/lib/constants/brand.ts
The full organisational study, panel by panel.
Ten rendered panels covering the two cards, the naming decision, the honesty enforced in code, the QR encoding constraint, the console exception, the unautomated work and the stated limits.