Back to Registry

FuelVM Usage + Markup Platform (Executive Brief)

1) Executive Summary

FuelVM should launch a unified billing intelligence layer that:

1. tracks real model/provider costs per request,
2. applies configurable markup rules,
3. attributes usage/cost/revenue to website, client, product, and feature,
4. generates margin-aware invoices and dashboards.

This creates recurring revenue on top of AI/tooling usage already flowing through our products, while giving clients clear value reporting and predictable pricing.

---

2) Problem

Today, usage costs are fragmented across providers and products. That causes:

• weak margin visibility,
• hard-to-explain client billing,
• manual reconciliation overhead,
• lost recurring revenue opportunities.

For WordPress plugin deployments and SaaS tools, we need one metering and pricing engine that works per-site and per-client.

---

3) Product Vision

Core idea

A "Pricing Control Plane" that sits between usage events and billing:

• Ingests provider usage + cost data (LLMs, hosting, infra)
• Normalizes to a common cost model
• Applies markup logic by client/site/product
• Publishes invoice-grade outputs and profitability analytics

Surfaces

1. Internal Operations Dashboard
   • cost, revenue, gross margin by provider/product/client/site
2. Client-facing Usage Reports
   • transparent usage + value delivery summaries
3. WordPress Plugin Billing Layer
   • per-install telemetry and monetization hooks

---

4) Revenue Model Options

A) Pass-through + markup (recommended default)

• Client pays actual usage plus configurable markup (e.g., 10-30%)
• Best for variable usage products

B) Tiered bundles + overage

• Monthly included credits + overage markup
• Best for agency retainers and predictable planning

C) Hybrid floor + variable

• Base platform fee + pass-through markup over threshold
• Best for mixed low/high usage clients

---

5) Markup Strategy (invisible but defensible)

Markup should be configurable and policy-based, not hardcoded.

Markup dimensions:

• Provider (OpenAI, Anthropic, OpenRouter, etc.)
• Model class (premium/reasoning/fast)
• Product/feature (report generation, audits, automation)
• Client tier (standard/pro/enterprise)
• Channel (SaaS app, WP plugin, API)

Pricing controls:

• min margin floor
• max client protection cap
• rounding rules
• monthly budget guardrails
• hard stop / degrade mode when limits hit

---

6) WordPress-Specific Deployment Model

For WordPress plugins, meter per installation and map to account:

Per event captured:

• site ID / install ID
• feature invoked
• model/provider used
• tokens/compute units
• raw cost
• markup-adjusted billable cost
• timestamp

Business outcomes:

• bill per site or aggregate per client portfolio
• compare plugin ROI per installation
• monetize premium AI features natively inside plugin ecosystem

---

7) Architecture (high-level)

1. Usage Collectors
   • provider APIs + app events + plugin telemetry
2. Normalization Layer
   • unified schema for usage/cost events
3. Pricing Engine
   • applies markup and policy rules in real time or batch
4. Ledger / Cost Events Store
   • immutable financial event history
5. Invoice & Reporting Layer
   • billing outputs, client dashboards, margin analytics

Non-negotiables:

• immutable event ledger
• versioned pricing rules
• tenant/client isolation
• audit logs for every pricing decision

---

8) Governance and Risk Controls

• Deny-by-default access model for billing data
• Role-based separation (ops vs finance vs client view)
• Price change approvals and effective-date controls
• Revenue leakage alerts (usage with no mapped price rule)
• Data quality checks (missing provider costs, duplicate events, clock drift)

Compliance posture (phase-appropriate):

• invoice traceability from billed amount back to raw event
• explainable pricing for client disputes

---

9) Rollout Plan

Phase 1 (2-3 weeks): Foundation

• Unified usage/cost schema
• OpenAI + Anthropic + OpenRouter ingestion
• Basic markup policy engine
• Internal margin dashboard (MTD)

Phase 2 (2-3 weeks): Hosting + site attribution

• Add Vercel + Cloudflare + WP Engine feeds
• Per-app/per-site cost attribution
• Client/account mapping and margin by website

Phase 3 (2-4 weeks): Productization

• Client-facing billing summaries
• WP plugin metering adapter
• Tiered plans + markup controls
• Alerting, budgets, and invoice export automation

---

10) KPI Targets

• 95%+ usage events attributed to client + site
• <1% unpriced usage events
• Margin visibility at provider/product/client/site levels
• Invoice reconciliation time reduced by 70%+
• Positive gross margin on AI-enabled features across active clients

---

11) Strategic Fit

This platform turns cost tracking into a revenue engine:

• better pricing discipline,
• recurring monetization from AI/plugin usage,
• stronger client value narrative,
• scalable economics as usage grows.

In plain terms: we stop treating model/infra spend as chaotic overhead and start treating it as a managed margin business.