Illustrative demo data · Bounteous confidential
bounteous  ·  AWS Partner · Bedrock

Roper AI & Technology Spend Portfolio

One holding-company view of AI/tech spend across ~40 operating companies — rolled up, sliced by reporting segment, and paired against value returned. Model & token spend is metered live on AWS Bedrock.
Live on AWS Bedrock · 9 opcos metered real Bedrock cost/usage Roper input value / budget / seats Illustrative figures
Roper Technologies
40 operating companies

AI/tech spend by month — 2026 real-ready

Monthly spend stacked by segment vs the 1-year budget line. Hover a month for the top 3 companies in each segment.

Spend by segment

Share of full-year spend.

Spend by cost type mixed

Model/token = Bedrock; seats / services / training = Roper.
Seats = of spend at utilization.

By operating company

Click a row for the company pop-up. Click a header to sort; scroll within the table. LIVE = metered on Bedrock now.

Cost vs value — the Cost True-Up value = TBD

Spend (x, Bedrock) vs an illustrative value proxy (y). How we quantify "value" is still open — to deep-dive with Roper (hours saved? revenue influenced?). Shown only as the frame, not a claim.
Application SW Network SW Tech-Enabled
★ Stars
High value, controlled spend.
Scaling
High spend, high value.
Efficient-small
Low spend, solid value.
⚠ Watch
High spend, low value.

Budget vs actual — variance flagged budget = Roper input

Actual (Bedrock) vs plan (Roper). Variance beyond ±10% flagged, sorted so outliers surface.

Live cost-attribution pipe — AWS Bedrock real

Each opco invokes models through its own tagged application inference profile (segment → opco). Metered per profile, priced by our rate engine — the same pipe that scales to all ~40.

Verified — real invocations

Account 861887594055 · us-east-1 · amazon.nova-lite. Real tokens captured just now — volumes are modeled to Roper scale in the portfolio above.
The storyline: the pipe & these tokens are real; portfolio dollars are modeled and get replaced by real Bedrock data as each opco onboards. Operational (runtime) and development (Claude Code via CLAUDE_CODE_USE_BEDROCK=1) both route through Bedrock → one per-opco attribution plane.

How we measure value & effectiveness

The honest version. "Value" (hours saved / $) can't be captured directly from tokens — anyone who promises a hard number is bluffing. Here's the ladder: what's real today, what needs Roper's data, and what's only a model.
The AI productivity paradox (2025–26): adoption hit ~93% but independently-measured delivery gains stalled near ~10% — individual output (PRs, commits) soars while org delivery stays flat, because speed just shifts the bottleneck to review, QA & rework. So adoption ≠ value, and even PR volume ≠ value unless the work merges and ships.
TierWhat it measuresKindSourceStatusThe catch
A · Usageactive users ÷ seats, frequency, active time, acceptance rateeffectivenessAnthropic analytics + TokenTrailhave nowSeats ≠ adoption; acceptance rate is a vanity metric
B · Output / velocityPRs merged, commits, time-to-first-commit, throughputvalueClaude Code analytics + Githave (partial)PRs raised but not merged = review inventory, not value
C · Delivery — DORAcycle time, lead time, deploy freq, change-failure, rework/revertreal value / impactRoper Git/Jira/CI + pre-AI baselineneeds Roper dataThe honest ceiling — segment AI-vs-human & baseline
D · Business $ / ROIhours saved × rate, cost-per-useful-outcome, ROI %$ modela factor Roper setsassumptionNever assert; always a labeled, adjustable model
E · DevEx / SPACEsatisfaction, flow, well-beinghuman signalshort surveysoptionalCatches what activity misses; survey-based
Our definition (defensible end-to-end):
Effectiveness = adoption — are they using it well (Tier A).
Value = output that ships — PRs merged, throughput (Tier B → C).
Dollar ROI = a transparent, Roper-set model (Tier D) — never a number we invent.
Today vs. built with Roper:
Today (real): cost per company/user/model + usage + AI-attributed PRs/commits.
Phase 2 (joint): DORA outcomes on Roper's Git/Jira with a pre-AI baseline — where effectiveness becomes proven impact.
Sources: DORA 2025/26 · SPACE (GitHub/Microsoft) · DevEx (DX) · independent AI-coding ROI studies. Cost = measured (Bedrock). Value = this ladder. $ = Roper-owned model.
Data sources: real = live from AWS Bedrock (Cost Explorer / CloudWatch / invocation logs). Roper input = supplied by Roper finance/ops (budgets, seats, value/hours, non-Bedrock vendors). modeled = illustrative for this demo. The 9 Bedrock inference profiles, tags, and token counts are real (tag roper-demo:*, torn down after).