This is how I think, build, decide, learn, and operate.

Six ways into the operating system. Not widgets — a table of contents.

1. 01

   Current Focus

   EQTY, Growing With Kid, Bolo Buddy, and teaching — the workstreams that set the week.

2. 02

   Active Products

   Founder products and the fintech OS partnership, held as one practice.

3. 03

   Current Experiments

   Hypotheses in motion — audio-first stories, constraint as editor, modular finance.

4. 04

   Teaching

   Curriculum, workshops, and mentoring as a way to test what actually works.

5. 05

   Advisory

   Enterprise systems and client work that still inform how the OS runs.

6. 06

   Writing

   Notes on decisions, trust, operating models, and building with less.

• AI product

  GWK Ghostwriter

  A personal LinkedIn studio: memory, source material, idea scoring, and a research-to-post workflow. Open the product from Work.

  Read case study →

• Community product

  Growing With Kid

  Newsletter, guides, and community for Indian parents. Constraint is the editor: one audience, one promise.

  Read case study →

• AI product

  Bolo Buddy

  Culturally rooted bedtime stories — Hindi, English, Hinglish, Tamil — built for children, not scaled down from adults.

  Read case study →

• Fintech OS

  EQTY

  Founding design partnership. Experience architecture sits inside the operating system, not after it.

  Read case study →

• Founder experiment

  Urban Prakriti

  A health brand built as a founder — positioning, identity, and D2C for city residents. Still running, still teaching how a venture stays honest.

  Read case study →

1. 01

   Start with evidence

   A screen is only the surface. The review starts with the decision the user must make, and what could make that decision fail.

2. 02

   Make thinking visible

   Products fail when the operating model stays invisible. Write the decision, the trade-off, and the lesson where the team can see them.

3. 03

   Build systems, not dependencies

   If the work cannot run without you in the room, it is not a system. It is a bottleneck. The deliverable is the system that generates the artefacts.

4. 04

   Ship useful versions early

   The smallest thing that answers who it is for, what they must decide, and what would make them stop trusting you.

5. 05

   Teach what works

   Teaching is not a second identity. It is how the practice is tested — students and teams as the fastest feedback loop.

Process and trade-offs. No invented results — only what the work taught.

1. 01 / Bolo Buddy

   Read entryClose

   Build bedtime stories as audio-first and screen-free, not as another kids’ app.

   Context

   Indian parents wanted culturally rooted stories. Existing platforms were Western-focused, screen-dependent, or mass-produced without cultural personalization.

   Trade-off

   Less visual theatre. Harder distribution in an app-store world that rewards screens. More work on voice, language, and trust.

   Outcome

   The product is defined by listening, not by a feed. Family voice-narration became a core idea rather than a feature bolted on.

   Lesson

   Children deserve tools built for them. Scaling an adult product down would have been faster and wrong.

2. 02 / Growing With Kid

   Read entryClose

   Let constraint edit the product — one job, not a catalogue of parenting features.

   Context

   Parenting advice is fragmented and overwhelming. A full app stack would have looked more ‘complete’ and said less.

   Trade-off

   Fewer surfaces to market. No theatre of process. The product has to be useful in a newsletter and a conversation first.

   Outcome

   The community product stayed small on purpose: essays, guides, programs — one voice, one audience, one promise.

   Lesson

   When the budget cannot buy another layer of process, the product has to say one thing well. That is still product work.

3. 03 / EQTY

   Read entryClose

   Join as founding design partner and treat experience architecture as part of the operating system.

   Context

   Financial products fail when trust, workflow, and business architecture are designed as separate layers.

   Trade-off

   Slower visible UI. More time in modules, states, and operator language before a marketing surface exists.

   Outcome

   The work is structured as a modular OS — how money, people, and decisions move — so new surfaces can join without a redesign each quarter.

   Lesson

   High-trust financial work is a workflow and language problem. The visual system stays quiet so the architecture can carry the product.

4. 04 / IIAD

   Read entryClose

   Teach design through decisions and production-bar critiques, not decoration.

   Context

   Studio traditions still reward polish. Practice now asks for systems, AI literacy, and the ability to defend a choice under constraint.

   Trade-off

   Less time on tool fluency as the headline. More discomfort in the room when a student cannot narrate the trade-off.

   Outcome

   Modules run as sprints. The critique is the curriculum: what they cut, what they kept, and what evidence moved the call.

   Lesson

   If juniors cannot apply the bar without a principal in the room, it is not a system. Teaching is how the operating model is checked.