Finn

Finn is the FinOps expert on your team — cloud cost, done with the math shown. Paste a bill and he finds the waste; propose a Savings Plan and he models the break-even against what your workloads are actually doing; forward a cost-anomaly alert and he traces the spike to the resource, the owner, and the person who changed it. When he says "this saves 34%," the numbers are right there.

Who Finn is#

Finn specializes in AWS cost optimization — Savings Plans, Reserved Instances, Cost Explorer, CUR, billing anomalies, right-sizing — with deep knowledge across GCP Committed Use Discounts, Oracle Universal Credits, Azure Reservations, and multi-cloud strategy. He thinks in unit economics (cost per request, per user, per GB), not just total spend.

What makes his advice trustworthy:

• He shows the calculations, not just the conclusion. Amortization schedules, break-even utilization, blended rates — the numbers behind every recommendation.
• He's precise about pricing. On-demand vs. effective Savings-Plan vs. spot vs. blended rates, and the edge cases AWS pricing hides.
• He's skeptical of vendor claims. When AWS says "save up to 72%", he calculates the realistic number for your workload.
• He weighs commitment against flexibility. He won't blindly push a 3-year All-Upfront RI onto a workload that's about to be torn down.
• He's direct. "You're overspending on idle RDS instances" beats "you might want to consider evaluating your database utilization."

Connecting AWS & Wiz#

Add read-only credentials in Settings and Finn's live powers switch on:

• AWS (read-only keys) — Cost Explorer spend, EC2/RDS/Lambda/S3/IAM inventory, Cost Anomaly Detection, resource tags, and CloudTrail (who changed what). This is his authoritative billing source.
• Wiz (GraphQL, read-only) — cloud inventory, security posture, ownership and aggregated cost attribution across clouds.
• Stripe (read-only) — when your revenue side is relevant to a unit-economics question.

Cost analysis#

Share a bill, CUR data, a Cost Explorer screenshot, or a spending breakdown and Finn dissects it: the top cost drivers, anomalies, and quantified waste. He does the math — amortized costs, effective hourly rates, break-even points, utilization percentages — and shows his work. With AWS connected he grounds "$X on EC2" in a Cost Explorer call he actually ran, citing the period and metric (and uses amortized cost for true SP/RI effective rates).

Cost-anomaly investigation#

Paste a cost-anomaly alert (or just describe one) and Finn runs the full playbook instead of restating the email:

1. Extract the anomaly's dimensions — service, account, region, usage type, date window, dollar impact.
2. Confirm via AWS — the real actual-vs-expected spend and the full root-cause list (the email usually truncates it).
3. Attribute the driver — daily spend grouped by usage type or resource, to pinpoint exactly what spiked and on which day.
4. Find the owner — read Owner/Team/CostCenter tags off the actual resources, or attribute by cost-allocation tag across accounts.
5. Find who changed it — CloudTrail names the actor, when, and from where. If it was automation, he points to the real human behind the IaC change, not the deploy robot.

The report tells you what spiked, by how much, when, who owns it, and who changed it — with the specific instance IDs and CloudTrail actor. He separates owner (the team that runs it) from maker (who performed the change); they're often different people.

Architecture cost review#

Share an architecture or tech spec and Finn reviews it through a cost lens: he flags the expensive choices — NAT Gateways, cross-AZ traffic, over-provisioned instances, idle resources — suggests alternatives, and estimates the dollar delta so a design decision has a price tag before you commit to it.

Savings Plans & RIs#

When you're weighing a Savings Plan (Compute, EC2 Instance, SageMaker), a Reserved Instance, or an equivalent on another cloud, Finn models the scenarios: break-even utilization, All Upfront vs No Upfront vs Partial, and term-length trade-offs, structured as current spend → recommended commitment → expected savings → break-even → risk factors.

For a concrete decision he folds in local context the raw math can't see — the team's memory for dated retirements, migrations and uncertainty that land inside the term (plus anything you just told him). A three-year All-Upfront looks great until he notices the workload is being torn down in month eight; the risk-adjusted verdict cites the exact signals it used.

AWS inventory#

Finn browses the connected AWS account read-only — identity and regions, EC2 instances, RDS databases (with tags), Lambda functions, S3 buckets, and IAM users and roles. It's the fast answer to "what do we actually have running" and the starting point for right-sizing or ownership questions.

Tag hygiene & changes#

Tags are how cost gets attributed, so Finn treats them as governance. He enumerates every value in use for a tag key — the complete set, with how many resources carry each and which services they span — so inconsistency jumps out (prod vs production vs Prod). When you want to standardize, he plans the change: he resolves the affected resources, checks with Cody whether Terraform manages each (and drafts the HCL edits), corroborates with CloudTrail, and hands you an interactive card with copy-paste Terraform and CLI commands to apply yourself — he never changes AWS.

FinOps strategy#

For the bigger picture — tagging strategy, showback/chargeback models, budgets and alerts, cost allocation, or account structure — Finn gives practical, implementable guidance grounded in how AWS (and other clouds) actually bill, not abstract best-practice slides.

Wiz (security & cost)#

With Wiz connected, Finn reads your tenant directly through its GraphQL API (read-only) — the underlying data, not dashboard widgets. He introspects the schema to find the real fields before querying, so he never guesses. Wiz's strength is the security-to-cost link: which resources, owned by which teams, with what posture — so he leans into per-team attribution and surfacing orphaned or idle resources. Where a question needs CUR-level detail Wiz doesn't expose (amortized effective rates, blended-vs-unblended nuance), he says so and points you to Cost Explorer or CUR instead of forcing Wiz to be a billing console.

Change-management review#

Finn can also score a change-management doc, runbook, or migration plan for operational safety — a deterministic 0–100 score across rollback, monitoring, blast radius, window, approvals, clarity, validation and data integrity, with every named alarm verified against the live monitor catalog. (Cody carries the same review; ask whichever you're already talking to.)

Org sites#

When a cost or ownership question needs the whole org to weigh in — confirming tag owners, collecting cost-center sign-offs — Finn can build the table from real data he pulled and hand you an org site card to publish. Teammates confirm rows, fix values, or add rows in a browser, every action attributed to their identity, syncing back so your copy stays the source of truth. You click Publish; he can't publish for you.

Watches, studios & lessons#

Finn shares the team's toolkit: put a cost query on the Night Shift watchlist to be alerted when spend crosses a threshold; jump into the right studio with a one-click chip; and correct him — "always show the amortized rate", "assume a 1-year term unless I say otherwise" — and he files it as a durable lesson that changes how the team works from then on.