To: Anyone asking why we started this
From: The Technivex founders
Re: Why cloud cost, why now
We'd each sat in the same meeting before: finance asking why the cloud bill jumped 40% this quarter, engineering shrugging because nobody could say which service did it, and both sides working off numbers that didn't agree.
The tools that existed stopped at the resource level — useful for a cloud architect, useless for a CFO trying to explain spend to a board. So we started building the layer in between: a cost model both sides could actually read.
We're a few months in, pre-seed, and still tuning the allocation logic against real bills from our first design partners. We don't have this fully figured out yet — that's what building it with real finance and engineering teams looks like.
— The Technivex team
Pre-seed
Current stage
5
People on the team
Lalitpur
Where we're based
What we optimize for right now
Numbers finance can defend
An allocation rule nobody can explain is worse than no allocation at all — every number traces back to a visible rule.
Engineers see it too
Cost tooling built only for finance gets ignored by the people who actually control spend. We design for both.
Boring is a feature
A cost platform that's exciting to use is usually one that's unreliable. We'd rather be dependable than flashy.
Want to be a design partner?
We're onboarding a small number of teams directly with the founders.