Writing
Things I've learned building products, teams and a company — written down so I remember them, and in case they help you.
- Stop Asking for 20% More. Think in Multiples.
Percentage targets quietly lock you into the system you already have. Asking "what would 3x look like?" forces you to question the system itself — and that is where real growth hides.
- Self-Hosting AI Taught Me That Architecture Beats Model Choice
We compared a lot of speech models for Indian languages. The biggest wins came from how we fed audio to the model, not which model we picked.
- The Library Is Free. The Risk Isn't.
How I now choose open-source dependencies for anything we plan to run for years — license, ownership, and the cost of leaving, before features.
- Writing the Hard Messages: Feedback, Increments, and Goodbyes
Years of writing performance feedback, increment letters and exit communications taught me that clarity is the kindest thing a leader can offer.
- Being Cheaper Isn't the Same as Being Ready
What I learned about taking a SaaS product into new countries — and why a good price is often the least important part of the plan.
- Everything You Subscribe To, You Must Unsubscribe From
What a slow memory leak in a long-running chat application taught me about lifecycles, ownership, and the bugs that only appear after hours of use.
- How I Read a Vendor Proposal Now
Agencies and vendors are good at writing proposals. Here is the checklist I use to read past the presentation and see the actual deal.