A project manager who builds systems from the work.

Manufacturing, automotive, heavy engineering and refinery work in India — on the contractor side and on the client and PMC side. Currently a head-office project manager running a multi-project portfolio: planning, execution, quality, materials, site administration and project documentation, with the commercial function as the core.

The scope is the whole factory package, not just the production shed — admin block, canteen, utility buildings, internal roads, drainage and boundary wall get priced and measured too.

Within that, the sharpest part is the commercial side: tendering, rate analysis, and checking and certifying other people's bills. Most material written about commercial control comes from people who have only ever prepared a claim. This comes from someone who has also sat on the side that cuts them — which is a different, and more useful, view of why things get rejected.

Every system on this site started as something I needed on a Tuesday, not as a product.

The billing system exists because I run bills. The finance system exists because I wanted to see every asset class in one place. The assistant exists because I wanted one. None of them began as something to sell, which is why none of them goes out before it works.

That is also why the systems page carries the word "planned" against four rows instead of a launch date. A date I cannot keep is worth less than an honest blank.

The same problem turns up in a billing month, in a portfolio, and in a week of admin: work that repeats, is badly recorded, and goes wrong quietly.

Each time the fix is the same — write down the sequence, compute what can be computed, and check it before it leaves your desk. So the systems look different and are built the same way.

Work came first because that is where ten years of evidence is. Wealth came second because I needed it myself. Life is a direction, not a product.