A website is finished when it launches. A product is barely started. That single difference determines almost everything about how a team is organised: what you measure, what you refuse, and how much you are willing to spend on foundations nobody sees.
Foundations are the whole job
Most of the work in this lab is invisible from the outside — a design system, a shared auth surface, a documentation pipeline, an evaluation harness. None of it is a product. All of it is why the next product takes weeks instead of months.
The name is the thesis. Bahukhandi means many parts. The bet is that a set of small, genuinely finished products, sharing one foundation, beats a single sprawling one.
Keep reading
- Changelog — July 2026NexLex private workspaces enter testing, Kiln gains service orchestration, and Groundwork's benchmark methodology goes public.
- Designing with exactly one accent colourA constraint that removes an entire category of decisions — and forces product identity to come from form instead.