IAN
Sales Briefing · 2026
Infrastructure Autopilot Navigator
Prepared for Acme, Inc.

IAN

Your engineers run the product. We run the cloud.

Your cloud team, as a service: a dedicated platform engineer you chat with, backed by six AI agents that give them leverage. One channel. One person on the hook. Five engineers' worth of housekeeping — for the price of one.

Trusted by 40+ engineering teams
Lucia Clifford · Founder
iancloud.ai
IANAcme, Inc.
01 / 15 · The Problem
The problem you already know

Your platform engineers spend ~40% of their week on infra housekeeping.

40%
What that means in practice
Almost two days a week per engineer goes to triage, drift, cost reviews, on-call, and the kind of work no one wanted to do when they joined.
Sources · Stack Overflow Dev Survey 2024 · Puppet State of DevOps · IAN customer interviews (n=42)
Cost reviews
~6 hrs / wk
Security drift
~5 hrs / wk
Incidents / on-call
~7 hrs / wk
Release plumbing
~4 hrs / wk
Resource cleanup
~3 hrs / wk
Tickets & reports
~3 hrs / wk
IANAcme, Inc.
02 / 15 · What it costs
What that costs you, today

Three numbers that don't show up on any dashboard.

Cloud waste
27%

of a typical AWS bill is idle, oversized, or forgotten. Reserved-but-unused, dev clusters left on, EBS volumes from 2022.

Source · Flexera State of the Cloud 2024
Engineer hours
~1.6 FTE

of a 5-engineer platform team is fully absorbed by infra housekeeping that no one is hiring for, and no one wants to do.

Based on 40% time × 4 platform engineers
Incident lag
11 hrs

median MTTR for a cost spike or security drift event — most of it is humans noticing, not humans fixing.

IAN benchmark · 28 mid-market AWS accounts
The compounding problem
Every quarter your cloud footprint grows. Your platform team doesn't. The gap is filled by Datadog alerts no one reads and Jira tickets that age out.
IANAcme, Inc.
03 / 15 · Meet IAN
What IAN is

Your cloud team, as a service.

A dedicated platform engineer who knows your stack, embedded in your Slack — backed by six AI agents that handle the volume. You get a human you can talk to, with the throughput of a team three times the size.

A real engineer · named & reachable Read-only by default Every action approved
ian.cloud / console
IANAcme, Inc.
04 / 15 · The Agents
Your IAN team

One engineer you trust. Six agents at their command.

Your dedicated platform engineer
A human on the hook.
MR
Your IAN engineer Senior platform engineer · assigned in week 1

You meet them in week 1. They learn your stack, your risk tolerance, and your weird Terraform module. They’re accountable for the outcomes — the agents are how they scale.

  • Reviews every IAN proposal before it reaches you
  • Joins your Slack — one channel, one human
  • Owns your incident response & weekly digest
  • Tunes policy, scope, and approval rules with you
Live in your Slack within 7 days of kickoff
— The six AI agents your engineer wields —
Cost

Watches your spend in real time. Finds waste in hours, not months.

Right-sizes EC2 / RDS against actual load
Drafts savings-plan PRs with the math
Security

CSPM that doesn't just alert — it proposes the fix.

Public buckets, open SGs, IAM drift
Remediation PR + audit entry, every time
Reliability

Triages incidents before the page even fires.

Posts root cause + runbook to Slack
Rolls back if the deploy did it
Releases

Owns the boring parts of shipping. Humans approve, IAN drives.

Canary, promote, rollback
Change windows + freeze logic
Scalability

Keeps headroom ahead of growth. No surprises at the next traffic spike.

Autoscaling policies tuned to real load
Capacity forecasts before you hit limits
Housekeeping

Closes the loop on everything else.

Auto-files tickets with full context
Drafts weekly platform digest
IANAcme, Inc.
05 / 15 · Cost Agent
Cost Agent
Find & fix cloud waste · Continuously
Avg. spend reclaimed
18–24%
ian.cloud / cost / proposals
Tells you what's costing you, why, and what the fix looks like — with the math attached.
Detect Tracks every account against learned baselinesSpikes flagged within ~1 hour, not at month-end
Diagnose Pinpoints the resource, owner, and likely cause"This dev cluster has been at 4% utilization for 11 days."
Propose Drafts the Terraform / IaC change as a PRWith projected monthly savings and rollback plan
Act Executes on approval — Slack thumbs-up or PR mergeEvery action logged with diff + actor + timestamp
Customer result
Mid-market SaaS, $180K/mo AWS spend → $38K/mo recovered in 6 weeks.
IANAcme, Inc.
06 / 15 · Security Agent
Security Agent
Posture watched 24/7 · Remediation drafted
Median time-to-fix
< 2 hours
ian.cloud / security / findings
A CSPM that closes its own findings — under your approval, mapped to your controls.
Watch Continuous posture across all in-scope accountsPublic S3, IAM drift, open SGs, KMS rotation, secrets in env
Frame Maps each finding to your compliance regimeSOC 2, ISO 27001, CIS, HIPAA — your control IDs included
Fix Drafts the policy / IaC change as a reviewable PRPlus a one-line rationale your auditor will accept
Prove Every change → audit log with diff + approverExportable for your next SOC 2 evidence pull
Customer result
100-employee fintech, SOC 2 prep → cut auditor follow-ups by 70%.
IANAcme, Inc.
07 / 15 · Reliability Agent
Reliability Agent
Triages before the page fires
MTTR reduction
~60%
ian.cloud / incidents / live
Cuts the time between "something's wrong" and "here's the root cause" from hours to minutes.
Correlate Reads alerts, logs, metrics across Datadog, CloudWatch, etc.Stitches the timeline humans would have to assemble by hand
Hypothesize Posts a root-cause candidate with evidence"DB CPU saturated since 14:02; correlates with deploy v412."
Suggest Points to the matching runbook — or drafts oneRollback, scale-out, or restart commands ready to approve
Close Writes the post-mortem stub when the incident resolvesTimeline, contributing factors, action items — you edit and ship
Customer result
B2B SaaS, 300-eng org → MTTR dropped from 47 min to 18 min.
IANAcme, Inc.
08 / 15 · And three more
Releases · Scalability · Housekeeping

The three agents that handle the work no one ever celebrates.

Releases Agent

The boring parts of shipping, done right. Humans approve, IAN drives.

  • Canary, promote, rollback orchestration
  • Feature-flag plumbing and clean-up
  • Change-window logic + freeze windows
  • Auto-generates release notes from PRs
  • Posts deploy status to Slack with diff links
Scalability Agent

Keeps your capacity ahead of your traffic. No surprises at the next launch.

  • Autoscaling policies tuned to real workload patterns
  • Capacity forecasts before you hit account or quota limits
  • Right-sizes for growth, not just for cost
  • Pre-warms infra ahead of known traffic events
  • Flags single points of failure as you grow
Housekeeping Agent

Closes the loop on everything the other agents touch. Keeps the org informed.

  • Auto-files tickets in Jira / Linear with context
  • Drafts the weekly platform digest
  • Keeps tags, owners, and runbooks current
  • Surfaces "things you should know" to leadership
  • Auditor-ready report generation on demand
IANAcme, Inc.
09 / 15 · Before & After
A Tuesday on your platform team

Same day. Same team. Very different shape.

Today

Reacting to five tools and a Slack thread.

08:42Slack ping from finance about last week's AWS billEngineer opens Cost Explorer, starts pulling reports
10:15PagerDuty: API latency spikeThree engineers jump in to triage; root cause buried in DD
11:50Wiz finding: public S3 bucket in stagingGoes in the backlog. Will get to it "this sprint."
14:00Cost review meetingHalf the meeting spent reconciling tags. No decisions made.
16:30Release rollback — manualSenior eng walks through runbook by hand on call
18:10"I'll write that postmortem tomorrow."It does not get written tomorrow.
Eng hours spent~17
With IAN

Reviewing IAN's proposals over coffee.

08:30Slack DM from Maya, your IAN engineerMorning digest: 3 cost proposals worth $4.2K/mo, 2 security fixes, 1 idle cluster
09:05Engineer approves 4 of 5 PRs with one clickOne gets a comment — IAN updates the proposal in 30s
10:12API latency anomaly — Maya posts hypothesis first"Likely DB CPU; correlates with v412. Rollback drafted."
10:18Engineer approves rollback. Incident closed.IAN drafts postmortem stub automatically
14:00Cost review meetingIAN's report is the agenda. Decisions made in 20 min.
17:00Engineer ships a feature.Yes, the actual product. Imagine that.
Eng hours spent~4
IANAcme, Inc.
10 / 15 · The Math
What this looks like for you

Concrete math, not a hand-wave.

Modeled on $100K/mo AWS · 4-eng platform team
Cloud reclaimed
$18K/mo
~18% of your AWS spend, recovered via right-sizing, idle cleanup, savings plans.
18% × $100K/mo
+
Engineer time freed
$25K/mo
~1.5 FTE of platform engineer time given back to product work.
1.5 FTE × $200K loaded ÷ 12
−
IAN subscription
$7K/mo
Growth tier — fits the modeled spend bracket.
Single line item, all-in
=
Net benefit
$36K/mo
Cash + capacity, every month. Compounds as your footprint grows.
~$432K / yr · 5.1× ROI
Payback period
< 30 days
Most customers see net savings inside the first billing cycle.
First-year value
$432K
Recovered AWS spend + reclaimed engineering capacity.
What changes
No new hires.
Your platform team grows in capability, not headcount.
IANAcme, Inc.
11 / 15 · What customers say
Social proof

40+ engineering teams trust IAN with their cloud.

IAN's Cost Agent found $22K in monthly waste in the first week — money we'd been bleeding for over a year. The security posture work that used to take our team two weeks every quarter now happens continuously in the background. Having a named engineer in our Slack who actually knows our stack made the difference.

YP
Yulia Petrova CEO · BeeMotion
18–24%
AWS spend recovered
Average over first 90 days
< 2 hrs
Median time-to-fix
Security findings closed under approval
~60%
MTTR reduction
Across customers using the Reliability Agent
IANAcme, Inc.
12 / 15 · How it works
How work flows

Two-way work. One human in the middle.

You
Head of IT & team
Reaches us in
  • IAN web console
  • Slack
  • Microsoft Teams
  • Mattermost
requests
summaries
IAN team
Your engineer + 6 agents
Picks up & works it
  • Triages the request
  • Agents draft the fix
  • Engineer reviews & sends to you
  • Ships under your sign-off
acts on
watches
Your cloud
What we operate on
Read-only by default
  • AWS
  • GitHub
  • GitLab
  • Terraform
  • MCP-compatible
When you raise it

Ticket in the console. Message in Slack or Teams. Your engineer picks it up, works with the agents, and ships the change after you approve. You get the summary back in the same channel.

When the cloud drifts

Cost spike, posture drift, incident — agents detect it first. Your engineer reviews, tunes, drafts the fix. You only see what needs your call — and the summary of what got done.

IANAcme, Inc.
13 / 15 · Pricing
Pricing

Flat monthly. Sized to your footprint.

No per-seat. No per-action. Unlimited agent operations on every tier. Pick the tier that matches your AWS spend.
Starter For teams getting their AWS bill under control.
$5K/ month
Footprint up to ~$50K/mo AWS in scope
  • Unlimited agent operations
  • 1 platform engineer backing you
  • All 6 agents · read-only by default
  • Slack + web console + audit trail
  • Business-hours response
Most chosen Growth For teams scaling cloud faster than they're hiring.
$7K/ month
Footprint $50K–250K/mo AWS in scope
  • Unlimited agent operations
  • Dedicated engineer + backup
  • All 6 agents · operate scope available
  • Mattermost + Cursor + Claude integrations
  • 24/5 response · custom policy
Scale For multi-account orgs with compliance needs.
$15K/ month
Footprint $250K+/mo or many accounts
  • Unlimited agent operations
  • Dedicated engineer + on-call rotation
  • VPC deployment available · SSO · custom RBAC
  • SOC 2 / ISO evidence packs included
  • 24/7 response · quarterly business review
Annual Save 15% on annual prepay. Pilot terms available — 30-day proof, exit anytime in the first quarter, no questions asked. BYOK on inference
IANAcme, Inc.
15 / 15 · Next Steps
From here

What the first 30 days look like.

A pilot is three conversations and one read-only connection. You'll have concrete savings proposals before the first invoice.

Week 1 · This week
30-min scoping call
We confirm in-scope AWS accounts, your primary technical contact, and which agents to start with. Sign mutual NDA + pilot terms.
Week 2
Read-only connect
IAN ingests your AWS, IaC, and Slack workspace. Within 72 hours: your first findings report — cost, security, reliability.
Weeks 3–4
First fixes shipped
You approve the first wave of proposals. Net savings tracked weekly. Conversion to subscription on day 30 — or walk away.
Reply to this deck [email protected]
iancloud.ai/pilot Book your scoping call →
Tweaks
/ mo
Show pricing slide