"We have 80 open recommendations and nobody with time to assess them."
Professional services · Pre-sales, savings capture and operation
The platform finds the savings. Someone has to make them happen.
LevelFour delivers recommendations and ready-made pull requests. What separates a recommendation from a smaller invoice is technical decisions, approvals and daily discipline. Norvum puts senior people at exactly those two points: a Forward Deployed Engineer to unblock the decisions and a Platform Operator to run the platform every day.
The problem
A recommendation is not a saving. A saving is what shows up on the invoice.
What we hear from teams that already have a cloud cost tool:
"The rightsizing PR has been sitting for three weeks waiting for the service owner."
"Nobody looks at the anomaly alert until the bill arrives."
"We bought reservations once. We never reviewed coverage again."
"Half the resources have no tag. Showback per area doesn't add up."
"Our FinOps person left. The tool has no owner."
Before you buy
Risk-free pre-sales: you see the savings before you sign.
No license comes in without a number. Three steps, run by Norvum, with read-only access and nothing to install.
Savings diagnosis
We connect LevelFour read-only to your AWS, GCP, Azure accounts and Kubernetes clusters. Within days you have the savings potential per service, per team and per module, inside the platform's 14-day trial.
Business case
Which modules make sense for you (Cloud Savings on success fee, Cost Governance, Kubernetes Savings), what lands each quarter, the risk of each action and the number that goes to the board. We also say what isn't worth it.
Frictionless contracting
Billing through the AWS, GCP or Azure marketplace, on the cloud account you already have, no new procurement process. Success-fee and monthly-module terms explained up front, in writing, with a defined baseline.
After you buy
Two roles. One to unblock, one to sustain.
Hire one, the other, or both in sequence. Both work inside LevelFour and report the same auditable savings the platform shows.
Per sprint · 2 to 4 weeks · fixed price
Forward Deployed Engineer
A senior engineer embedded in your team with one mission: turn the backlog of recommendations into applied savings and fix the governance that blocks the next round.
- Ranks recommendations by impact and risk, and gets the "yes" from each service owner
- Rightsizing, scheduling, cleanup of idle and orphaned resources
- Reservations, Savings Plans and Committed Use: coverage and purchases decided with finance
- Reviews and merges the IaC pull requests LevelFour generates, in your review flow, with rollback
- Governance: tagging policy, allocation per team, budgets, alerts and showback that adds up
- Kubernetes: requests and limits, idle cost per namespace, attribution per team
Deliverable per sprint: savings applied and verified in LevelFour's audit trail, plus the list of what was left out and why.
Monthly · instead of or alongside your team
Platform Operator
Someone who owns LevelFour every day, so the number doesn't creep back up. Triage, review, reporting and platform administration, on a fixed cadence with a named owner.
- Daily: anomaly and alert triage, routed to the right team
- Weekly: review of new recommendations and follow-up on pending ones
- Monthly: showback and chargeback per area, executive report with verified savings, coverage and open items
- Administration: accounts, users, integrations, tags and budgets inside LevelFour
- Two modes: Operated (Norvum runs it) or Co-managed (we run it with your team and hand over when they're ready)
Deliverable per month: an auditable executive report and a platform kept current: zero unanswered anomalies, zero recommendations without an owner.
Which combination is yours
Three situations we see every month.
"I have a team. I don't have time."
FDE per sprint
One or two sprints to clear the recommendation backlog and get governance in place. Your team carries on from there.
"I have nobody to look at this every day."
Platform Operator, Operated mode
Norvum runs LevelFour for you. You get the monthly report and approve what needs a decision.
"I want to start from zero and never go back."
FDE + co-managed Operator
Capture sprints first, then operation alongside your FinOps person until handover. A good engagement ends with your team in charge.
How it works
From diagnosis to operation, without letting go of your hand.
Every stage ends with a number. You decide whether to move to the next.
01
Diagnosis · days
Read-only connection, savings potential per service and team. No cost, no commitment.
02
Business case and contracting
Modules, quarterly targets, written baseline. License via marketplace or direct contract.
03
Capture sprints · FDE
Embedded engineer applies the highest-impact recommendations and fixes governance. Savings verified at the end of each sprint.
04
Continuous operation · Platform Operator
Daily, weekly and monthly cadence. An executive report you take to the board without rework.
Rules we don't negotiate
Built to pass your security team and your CFO.
Written baseline
Before any sprint or month of operation, the starting point is documented. No baseline, no savings to claim.
Savings validated on the invoice
We only count what LevelFour verifies and your invoice confirms. Same audit trail as the platform, same numbers for the board.
Read-only by default
Changes go through your review flow (PRs) or with recorded approval. Norvum stores no credentials.
Senior, no rotation
The person who does the diagnosis is the one who joins the sprint and runs the platform. You know the name, and it doesn't change every month.
Frequently asked questions
What people ask before hiring.
Does the Forward Deployed Engineer need write access to our accounts?
Not by default. Changes go in as infrastructure-as-code pull requests, reviewed and approved by your team. When an action requires the console, it's done with recorded approval and temporary access, inside your change process.
How are savings measured?
A documented baseline before we start; savings verified by LevelFour and confirmed on the invoice, with an audit trail per resource and per action. The per-sprint or per-month report uses those numbers, not estimates.
Does the Platform Operator replace my FinOps person?
You choose. In Operated mode, Norvum owns the platform and you approve decisions. In Co-managed mode, we run it with your person and hand over when they're ready, with documented runbooks and cadence.
Does it work across multi-cloud and Kubernetes?
Yes. AWS, GCP, Azure and Kubernetes are natively supported by LevelFour, and both roles cover all four.
How much does it cost?
The FDE has a fixed price per sprint, set after the diagnosis. The Platform Operator is monthly, sized by number of accounts, clusters and mode (Operated or Co-managed). No open-ended hours. The LevelFour license is separate and follows the platform's model: success fee on Cloud Savings and monthly on the other modules.
Remote or on-site? Which countries?
Brazil and Portugal, in Portuguese or English. Operation is remote; diagnosis and sprint kick-off can be on-site when it makes a difference.
Start with the diagnosis. 15 minutes to connect and it costs nothing.
Read-only access, no code changes, no agent to install. You leave with a number.