Work
Currently building
rattl — a revenue floor a credit committee can act on
An EV charging site can run exactly as modelled and still be declined, because nobody will state in writing what the downside looks like. rattl contracts that downside as a number.
The hard part was never forecasting revenue — plenty of tools do that. It is being willing to put a figure in writing that you would have to pay against, and to withdraw it when the evidence turns. That single constraint decides the whole product.
Design-partner stage, and said plainly on the site: sites are scored free of charge to build a calibration record, and no insurance instrument exists yet — writing a real floor needs a licensed carrier and one is not signed.
Visit rattl.in ↗Working tools
Three interactive prototypes. Each takes a real decision from my domain and makes it usable — with the reasoning and the honest limits attached.
Agentic evaluation
The trust threshold
When should an autonomous agent be allowed to act? Set your system’s numbers, watch trust survive — or not.
Open the tool →EV infrastructure
Agstya.charge
Charge-siting intelligence: map, ROI model, price engine, portfolio view — with a candid “what’s fake here.”
Open the prototype →Insurance & risk
Hemma
A home-repairs log that reprices insurance risk from maintenance history — a 2024 concept, rebuilt and honestly labelled.
Open the prototype →Product case studies
Product strategy, worked end to end
Two product-strategy studies — market, users, a falsifiable thesis, and a roadmap. The thinking, worked end to end.
Developer tools · adoption
Growing adoption of a code-analysis tool
Top 3 bets to win Java developers — and why adoption is a context problem, not a coverage problem. Includes a clickable prototype.
Read the case + try it →Fintech · market strategy
A trust-first fraud platform for digital payments
Positioning a mainframe as the fraud-proof backbone for digital payments — market, competition, product. Includes a clickable prototype.
Read the case + try it →