## Turn usage limits into revenue triggers.

Stop waiting for the weekly export to spot an upgrade opportunity. Trigger expansion the exact millisecond a user needs more capacity.

### The pillars

### Four shifts. One runtime.

#### 01Pillar

##### Live threshold signals

**Old reality**  
You run a weekly query, export CSV, manually identify users near limits. By the time you reach out, they've churned or found a workaround.

**Metrifox reality**  
Define thresholds (80% of usage, 90% of credit balance). The second a user crosses, the runtime fires a webhook. CRM pinged. In-app prompt appears. Real time.

**The oh-shit moment**  
You discover your highest-value upgrade opportunities are users actively in the product. You've been waiting until after the limit. Expansion revenue, on the table.

#### 02Pillar

##### Frictionless, contextual upsells

**Old reality**  
Upgrade means a sales call, a Contact Sales button, a pricing page they have to navigate to. Each step kills conversion.

**Metrifox reality**  
The upgrade prompt appears in the product, exactly when they need it. 'You've used 100 credits this hour. Upgrade for 500 more?' One click. No redirects.

**The oh-shit moment**  
You realize your current upgrade flow has a 95% drop-off because it forces users out of the product. Metrifox keeps them in the flow.

#### 03Pillar

##### Automated top-ups (churn prevention)

**Old reality**  
Users hit a hard limit. 429 error. Frustration. Churn. You lose a customer over a $10 usage limit.

**Metrifox reality**  
Define top-up policies. At 100% of limit, auto-provision 50 more credits and bill later. Or prompt. Or both. Users never hit a hard stop.

**The oh-shit moment**  
You realize you've been churning users over limits that cost pennies to serve. Those users represent millions in LTV. Thrown away.

#### 04Pillar

##### Behavioral promotions

**Old reality**  
Everyone gets the same upsell at the same time, regardless of activity. No way to dynamically promote based on behavior.

**Metrifox reality**  
Define triggers. 'If a user generates 50 responses in 10 minutes, auto-provision 100 free credits.' Behavior → trigger → action.

**The oh-shit moment**  
You realize you've treated power users the same as casual users. Engagement-based revenue, left on the table.

### New vs Old

#### The leaky bucket vs the revenue engine.

| The old way · leaky bucket | The Metrifox way · revenue engine |
|-----------------------------|-----------------------------------|
| Signals: buried in weekly data warehouse exports. | Signals: live thresholds surfaced in milliseconds. |
| Upgrades: manual outreach from sales. | Upgrades: frictionless, contextual in-app prompts. |
| Churn: users hit hard limits and bounce. | Churn: automated top-ups keep them moving. |
| Promotions: static, time-based campaigns. | Promotions: behavior-triggered, real-time actions. |
| Expansion friction: high (sales calls, pricing pages). | Expansion friction: zero (one-click, in-product). |

"Your best customers are signaling they want to spend more. Are you listening?"

### The realization

Usage limits are not just technical boundaries. They are revenue signals. Every limit a user hits is them telling you they need more.

### The cost of doing nothing

Every week you delay real-time expansion triggers, you lose upgrade revenue, churn power users, and force sales to play catch-up.

### The Metrifox promise

Turn every usage limit into a revenue opportunity. Capture expansion the exact millisecond it's ready.

## Your stack, unchanged. Your billing, transformed.

Metrifox fits seamlessly into your existing workflow. No migration. No disruption. Just better billing.

**Payment**  
- Stripe  
- Adyen  
- Braintree

**Cloud**  
- AWS  
- GCP  
- Azure

**Data**  
- Snowflake  
- BigQuery  
- Redshift

**Observability**  
- Datadog  
- New Relic  
- Prometheus

**CRM**  
- Salesforce  
- HubSpot  
- Pipedrive

**Analytics**  
- Segment  
- Amplitude  
- Mixpanel

**Collaboration**  
- Slack  
- Teams  
- Discord

**Dev Tools**  
- GitHub  
- GitLab  
- Linear

**AI**  
- OpenAI  
- Anthropic  
- Cohere  
- LangChain

**Workflow**  
- Zapier  
- Make  
- Pipedream

### Three steps. Live in minutes.

Drop in the SDK, send events, gate features. Your existing infra keeps working. Metrifox becomes the runtime that governs every priced surface.

#### 01Install SDK

```bash
npm install @metrifox/sdk
```

#### 02Send usage events

```typescript
await metrifox.ingest({
  customer: "cust_123",
  metric: "api_calls",
  value: 1
})
```

#### 03Check entitlements

```typescript
const access = await metrifox.check({
  customer: "cust_123",
  feature: "generate_response"
})
```

## Start protecting your margins today.

No engineering overhead. No migration headaches. Just a runtime that makes billing disappear.

### Questions, answered.

The fast facts on how Metrifox fits into your stack. Need more?

**How fast can we go live with Metrifox?**  
Most teams ship their first metered, gated, and billed feature in under a day. Drop in the SDK, send events, and gate access with one call. No data migration required.

**Does Metrifox replace Stripe?**  
*Response to be provided*

**Can we change pricing without a deployment?**  
*Response to be provided*

**How accurate is usage tracking?**  
*Response to be provided*

**What stacks do you support?**  
*Response to be provided*

**Is Metrifox secure and compliant?**  
*Response to be provided*