Someone on your team became the cloud bill person. They have no idea how it happened.
There's always one person on the team who has quietly become the cloud bill person. Nobody assigned them. They just stopped saying no when the AWS invoice landed every month. Now they open 3–4 dashboards a week and hope nothing important slipped through.
I'm building in this space, and after auditing a bunch of teams' setups, the same patterns keep showing up:
- Dev and staging environments are running 168 hours a week. The team
actually uses them about 50. - Hot-tier storage where 80% of the data hasn't been touched in 2+ years.
- Hackathon clusters and debug RDS instances nobody remembered to delete.
- Production over-provisioned for traffic that hits twice a quarter.
The built-in tools (Trusted Advisor, GCP Recommender, Azure Advisor) catch about 14% of it. They check a fixed rule set, one cloud at a time. Everything else sits there until someone with a free afternoon goes looking. Most teams never get that free afternoon.
I'm working at ZopDev on a FinOps tool called Zopnight to handle this across the three clouds happy to talk about it if anyone's curious, but that's not really why I'm posting.
What I'm actually curious about: does your team have a cloud bill person? How did they end up with the role? Did they volunteer, get voluntold, or just inherit it when someone left? And does anyone have a setup that actually works long-term, or is it always one person quietly suffering?
(For anyone who wants to look: https://zop.dev/zopnight)
This is a strong wedge because the pain is not just “cloud bills are high.” It is that cloud cost ownership quietly falls onto one person without a real operating system around it. That makes the problem feel more human and urgent than another generic FinOps dashboard.
The sharper positioning might be “cloud cost hygiene without a dedicated FinOps team.” Small teams do not need another advisor panel that flags obvious issues. They need something that finds forgotten infra, explains what matters, and turns cleanup into actions before the monthly invoice becomes someone’s unpaid side job.
One thing I’d watch is the Zopnight name. It has personality, but if this becomes serious multi-cloud FinOps infrastructure, Davoq.com would carry the technical trust and backend-systems feel more cleanly.
Yeah, the accountability vacuum thing is real; nobody owns it, so nobody fixes it.
That's kind of exactly what Zopnight does , it finds the non-prod infra that's been running all weekend while nobody's using it and turns it off on a schedule. No dashboard hunting, no free afternoon required.
That actually makes the positioning much sharper.
The strongest version is probably not “cloud cost optimization” at all. It is more like “auto-cleanup for forgotten non-prod infrastructure.”
That feels more concrete because the buyer instantly understands the waste pattern: dev/staging resources running nights and weekends because nobody owns cleanup.
I’d probably make that the core wedge instead of competing with broad FinOps dashboards.
The only thing I’d still be careful with is the name. Zopnight has personality, but if this grows from scheduled cleanup into a serious infra hygiene layer across cloud teams, the brand may start feeling lighter than the problem.
That is why Davoq came to mind. It sounds more like backend infrastructure and less like a small utility. Not saying you need to rename immediately, but I’d pressure-test that before the product gets too tied to the current name.