Top questions a procurement-stage FinOps evaluator asks first.
Grouped by topic — Coverage, Verification, Security & Compliance, Pricing and Onboarding — so the exact objection your contract covers has one anchor. Each answer cross-links to the depth page that owns the contract clause.
Coverage.
Which clouds, which IaC runners and which per-provider surface Tallywyrm exercises today. The questions a procurement lead opens with — what accounts do we cover, what runs in your Terraform / Pulumi / Crossplane repo, and what is explicitly out of scope.
PermalinkVerification.
How a saving is measured end-to-end and how the verified pool becomes the tier math. The auditor-side questions — forecast vs. realized on the same row, regression handling, and the no-claw-back rule that keeps the contract symmetric.
PermalinkSecurity & Compliance.
What the agent touches and what it explicitly does not, the frameworks the audit trail maps to, and the row-level SOC 2 / ISO 27001 / FedRAMP evidence path. The CISO and auditor-side questions — read alongside /security-and-compliance and /security/compliance for the per-framework mapping.
PermalinkPricing.
How the 8 % / 12 % / 18 % tiers read from the verified pool, when the percentage rail beats a flat-fee rail, and the minimum platform-fee rationale. The procurement-finance questions — bill composition, tier switching and the no-double-fee rule.
PermalinkOnboarding.
Connect-to-first-PR, contract term, data retention and what changes the day you terminate. The questions a buyer drafts in the final procurement week — how long until first savings, where the audit log lives and the exit path that returns control to your team.
PermalinkAsk us anythingwe didn’t cover above.
Send the question that didn’t fit any of the topics above. We’ll come back with the answer in writing — replies within one business day, no demo theatre, no procurement form on the first call.