Documentation Index
Fetch the complete documentation index at: https://docs.monk.com/llms.txt
Use this file to discover all available pages before exploring further.
Self-Serve vs Enterprise Workflows
Monk is enterprise-first — our UI and workflows are designed for sales-led, negotiated contracts. That said, self-serve billing is fully supported via API for companies that need it.Enterprise Billing (Primary Focus)
Enterprise billing is ops-driven via UI. Engineering focuses on metering and event ingestion; Revenue/Finance Ops handles contracts, credits, and invoices.What Engineering Owns
| Component | Responsibility |
|---|---|
| Meters | Define all billable metrics comprehensively |
| Rate Cards | Set up global rates for dimensional pricing |
| Events | Send usage data once contracts exist |
What Ops Owns (via UI)
| Component | Responsibility |
|---|---|
| Customers | Created via Contract Extraction or SFDC sync |
| Contracts | Created via Contract Extraction flow |
| Credits | Granted during contract setup |
| Invoices | Generated and managed via UI |
| Rate overrides | Custom pricing per contract |
Typical Setup
- Eng (one-time): Create meters and rate cards comprehensively
- Integration: Connect Salesforce to Monk
- Deal closes: SFDC sends data to Monk
- Ops: Use Contract Extraction flow to review and create:
- Customer record
- Contract with plan assignment
- Prepaid credits (if applicable)
- Initial invoice
- Eng: Start sending events for the customer
- Usage tracked, invoices generated per contract terms
For enterprise, keep Plans and Pricing simple. Complexity lives in Rate
Cards (on meters) and Contract-level overrides set during Contract
Extraction.
Salesforce Integration
Monk integrates with Salesforce to streamline the deal-to-billing flow:- Deal closes in SFDC → Opportunity data synced to Monk
- Contract Extraction → Ops reviews deal terms in Monk UI
- Customer/Contract created → Based on SFDC data + manual review
- Credits granted → Per negotiated terms
- Events flow → Eng sends usage once contract is active
The Contract Extraction flow is an ops process, not an API. It’s designed
for human review of enterprise deals before billing begins.
Self-Serve Billing (API-Driven)
For self-serve products, billing can be API-driven and automated. Engineering owns the full flow.What Engineering Owns
| Component | Responsibility |
|---|---|
| Meters | Define all billable metrics |
| Pricing | Configure rate structures |
| Plans | Bundle pricing into products |
| Contracts | Auto-create via API on signup |
| Events | Send usage data in real-time |
| Credits | Grant via API (if offering trials/promos) |
Typical Setup
- Create meters for each billable metric
- Create pricing attached to meters
- Create plans bundling pricing
- On user signup: API call to create customer + contract
- As user consumes: API calls to send events
- Invoices generated automatically
Quick Comparison
| Aspect | Enterprise | Self-Serve |
|---|---|---|
| Contract creation | UI-driven via Contract Extraction flow | API-driven, automated |
| Eng responsibility | Meters, rate cards, events | Everything (meters, pricing, plans, contracts, events) |
| Ops responsibility | Contracts, credits, invoices, customer setup | Minimal |
| Integrations | Salesforce → Monk → Contract Extraction | Your app → Monk API |
| Complexity lives in | Rate Cards and Contract overrides | Plans and Pricing |
Key Differences
Meters & Rate Cards
| Workflow | Approach |
|---|---|
| Enterprise | Meters need comprehensive rate cards upfront; Contract Extraction applies overrides |
| Self-Serve | Meters can be simpler; pricing complexity lives in Plans |
Plans & Pricing
| Workflow | Approach |
|---|---|
| Enterprise | One or few simple plans; customization happens at contract level |
| Self-Serve | Multiple plans for different tiers (Starter, Pro, Enterprise) |
Contract Creation
| Workflow | Approach |
|---|---|
| Enterprise | Contract Extraction UI flow (not API-driven) |
| Self-Serve | POST /v1/contracts API call on signup |
Credits
| Workflow | Approach |
|---|---|
| Enterprise | UI: Configured during Contract Extraction |
| Self-Serve | API: POST /v1/contracts/{id}/credits/promotional/grant for trials/promos |
Hybrid Approach
Many companies use both:- Enterprise customers: Contract Extraction flow via UI
- Self-serve customers: API-driven flow
Next Steps
How Usage-Based Billing Works
Core concepts for both workflows
Create Your First Meter
Start with metering
Dimensional Pricing
Set up rate cards (especially for enterprise)
Enterprise Billing
Contract-level customizations