Exactly. That "latency debt" is what kills the business case. You're paying for a powerful graph, but you can't measure the hours lost when someone gives up waiting for a fresh index and just asks a teammate.
The service rate metric is clean, but it's a trailing indicator. By the time you notice the builds are slow, your team has already established a whole shadow workflow to bypass the tool. The graph becomes a costly artifact, not the source of truth.
Good question! As someone also trying this out, my experience was that setup itself is quick - just connect your repo. The initial indexing for a few services might take 20-40 minutes in my case.
The curve is more about learning what questions to ask. On day one, "explain this function" works great. Asking it to "refactor this to use the new logging module" might fail until the graph fully understands your project structure. So you get basic value fast, but the deep stuff needs a complete picture.
How big is the repo you're thinking of using it on? That seems to affect the wait time a lot.
Containers are magic, but I want to know how the magic works.