Overview
Apollo.io uses a credit-based pricing model where users spend credits to access contact data (like emails, phone numbers, and exports), with higher plans offering more monthly credits. This guide shows how to build the same model in Tirdad.Pricing Breakdown
1. Key Chargeable Features in Apollo
In this model, credits are deducted when the user does an action (e.g. unlock email, export). In Tirdad you will map each action to a credit cost and debit the wallet.A. Contact Data Unlock & Enrichment
How Credits Are Applied
Prepaid allocation: When a user subscribes, they receive credits up to the plan limit. You configure this as recurring grants on the plan. Plans can be billed annually with recurring grants (e.g. credits per month).- Professional plan → 48,000 credits/year (or e.g. 4,000/month as recurring grants)
- Basic → 30,000 credits/year (or e.g. 2,500/month as recurring grants)
| Action | Credit Cost |
|---|---|
| Unlock verified email | 1 credit |
| Unlock mobile number | 5–10 credits |
| Export contact | 1 credit |
| API enrichment | 1 credit per record |
B. Email Sending & AI Outreach Credits
How Credits Are Applied
Email Sending Model: Depending on plan, choose one: daily send limits per mailbox or credits per email sent. When you set up features, create a metered feature (e.g. Emails Sent) and set the credit cost per use.| Action | Credit Cost |
|---|---|
| Send 1 email | 1 credit |
| AI-generated personalization | 1 additional credit |
| Email verification | 1 credit per email |
2. Apollo-Style Credit Model
Key Behaviors
Set cost per action
Define a credit cost for each action (e.g. 1 for search, 5 for export) in your app or feature config.
Example: Credit Cost per Action
| Action | Credit Cost |
|---|---|
| Contact Search | 1 credit |
| Contact Export | 5 credits |
| Email Enrichment | 2 credits |
| Phone Reveal | 10 credits |
Example: Credit Packages (Prepaid)
| Plan | Credits | Price |
|---|---|---|
| Starter | 1,000 | $29 |
| Growth | 5,000 | $99 |
| Pro | 20,000 | $299 |
3. When to Use Credit-Based Pricing
Different cost per action
Use credit-based pricing when each action has a different cost (e.g. 1 credit to unlock an email vs 10 credits to reveal a phone number).
4. Complete Flow Summary
High level, you will:Create Features
Create metered features for each action that costs credits. Link each feature to plans via entitlements; there you set which features each plan gets and optional free usage (e.g. 50 free, then deduct from credits). See Linking features to plans.
Create Plan
Create a Plan with credit packages or usage charges (e.g. annually billed with recurring credit grants per month).
Tirdad Set-up
To implement Apollo-style credit-based pricing in Tirdad, follow these steps in order.Step 1: Create Features (Metered)
Navigate to Tirdad Dashboard → Product Catalog → Features
Step 2: Create Plan (with Credits or Recurring Grants)
Navigate to Tirdad Dashboard → Product Catalog → Plans
Step 3: Credit Grant and Entitlement (Plan-Based Path)
Do this: Open the customer → Add Subscription → select your plan. Result: The customer gets the plan’s credit grants (e.g. monthly) and access to the features you linked to that plan (including any free usage you set).
Step 4: Create Customer
Navigate to Tirdad Dashboard → Customer Management → Customers
Flex Corporation). Add External ID if you use it for API lookups.For details, see Customer Management.Step 5: Get wallet balance and validate before action
Before allowing the user to perform a credit-consuming action, call the Get Wallet Balance API (e.g. with customer identifier or wallet ID). If balance is available and sufficient for the action cost, proceed. If not, do not proceed—block the action or prompt the user to top up, then leave.
Step 6: Top Up the Wallet (Initial or Add-On Credits)
On the customer’s Wallet tab, click Top-up Wallet.
- Choose the credit type that matches your Price Unit (Custom → Credits).
- Enter the amount in credits (e.g. 1,000).
- Complete the top-up (e.g. Add Credits or link to payment).
Step 7: Debit Wallet When User Performs an Action
Each time a user does an action (search, export, enrichment), do the following in your app or backend:Debit via API: Call the wallet debit endpoint with the customer identifier (e.g. External ID) and the amount in credits.Debit via Dashboard: Customer → Wallet → Manual Debit; enter the amount in credits and reason (e.g. “Contact export – 5 credits”).For more, see Manual Debit.
Check entitlement
Check entitlement: Does this customer’s plan allow this feature? (You set this when linking features to plans.) If not, block the action.
Look up credit cost
Look up credit cost: Use your mapping (e.g. the tables in Key Chargeable Features in Apollo above) and get the cost for this action.
Check balance
Check balance: Call the Tirdad API or open the dashboard and read the customer’s wallet balance.
Debit if sufficient
If balance ≥ cost, call the Tirdad API to debit the wallet by that amount, then perform the action.
Next Steps
After setup, do this:Map actions to credit costs
Map actions to credit costs in your application (e.g. 1 credit per search, 5 per export) and call the debit API (or Manual Debit) after each action.
Monitor wallet balances
Optional: Set low-balance alerts; see Low balance alert.
Optional: Plans with credit packages
Add more plans with credit packages (recurring or one-time) using the same Price Unit; see Custom pricing use cases.