LimeLeads
Sample data — front-end shell built on the CallSuite design system. Numbers illustrate layout only, pending live wiring to Meta, Stripe and the Lead Router.
Welcome
Here's where LimeLeads stands.
Action points
Money
Last 30 daysMRR
trailing 30 days of revenue, plotted dailyRevenue run rateProfit run rate
Weekly P&L
show all| Week | Spend | Revenue | Profit | Margin | Bounced | Leads in | Sold |
|---|
What a qualified lead costs
current quiz onlyPipeline
Trends
last 30 daysRevenueAd spendRaw CPL
—
RevenueAd spendRaw CPL
Lead economics
BusinessLoans.com ladder · current quiz only, from 22 July—
Cost per qualified lead
by what the lead is worth · current quiz only| Window | Leads | Duds | Premium 95+ | Standard 70 to 94 | Cost per premium | Cost per standard | Blended |
|---|
Revenue by client
| Client | Leads | Revenue |
|---|
Recurring watch
30-day run-rate
—
Repeat-buyer rev
—
Standing orders (MRR)
$0
Active clients
—
What the loan leads return
current quiz only, since 22 July—
Reconcile against their sheet
drop the BusinessLoans marketplace CSV · checked in this browser only, nothing is uploadedDrop the marketplace CSV here, or click to choose the file
Master delivery log
| Received | Lead | Business | Type | Routed to | Status | Score | Worth | Sold for |
|---|
Buyers
Lead intelligence
Cost by ad
last 30 daysQualified per day
last 30 daysDeal calculator
model a buyer's terms → projected profit / lossHigh$at%
Med$at%
Low$at%
Blended calculator
add buyers with the buttons, drag the sliders → whole-book blend, revenue, marginText conversations
Loan Applicants - Keep Alive
How this works: the timeline below is the sequence a person walks through. They enter at Start; each message sends after the delay shown on its pill, and any reply from the lead stops their sequence and hands them to you. Press + anywhere to insert a message at that exact point. Placeholders that fill per person: {{first_name}}, {{business_name}}, {{company}}, {{agent_name}}. Cards showing two variants send each person one at random. Nothing here sends anything: sending stays on the Send next batch button.
Sales pipeline
| When | Company | Contact | Source | Stage |
|---|
Playbook
the living sales bank, mined from every call and growingInbox
conversations from the Loans campaigns, unified across every inboxAds
every ad's angle, format and script, next to the leads it actually producedLeads, qualified and premium come straight from the lead table via utm_content, so they are live. Impressions, CTR and spend fill in when the Ad Feedback Loop workflow gets its Meta token; the kill flag needs those. A struck ad is marked killed.
Simulator
a live sandbox for Ava, the SMS reply agent. Type as the lead and she answers for real.
What this is, and what it is not.
It writes nothing. There is no Twilio node and no Supabase node in the sandbox workflow, and its short term memory sits in a separate Redis namespace, so a test here cannot touch a real conversation.
It holds a snapshot of Ava's system prompt. If the live reply agent's prompt is edited, this copy drifts until the sandbox one is updated to match, so treat a surprising answer as a possible prompt gap rather than a bug.
The sandbox key sits in this page's source on purpose. It is a different key from the dashboard's, the worst case if it leaks is somebody burning sandbox tokens, and it rotates in a single field, sim_key in the workflow's Config node.
The workflow has to be switched to Active in n8n before anything answers. If it is off you will get a clear message below rather than a silent failure.
It writes nothing. There is no Twilio node and no Supabase node in the sandbox workflow, and its short term memory sits in a separate Redis namespace, so a test here cannot touch a real conversation.
It holds a snapshot of Ava's system prompt. If the live reply agent's prompt is edited, this copy drifts until the sandbox one is updated to match, so treat a surprising answer as a possible prompt gap rather than a bug.
The sandbox key sits in this page's source on purpose. It is a different key from the dashboard's, the worst case if it leaks is somebody burning sandbox tokens, and it rotates in a single field, sim_key in the workflow's Config node.
The workflow has to be switched to Active in n8n before anything answers. If it is off you will get a clear message below rather than a silent failure.
Scenariowho she thinks she is texting
Scenario changes apply to the next message you send. Starting a fresh conversation gives her a new session id, so she forgets everything said before it.
Webhook settings
Editing these changes this browser tab only, so a rotated key can be tested without a new build. Refreshing puts the built in values back.
Session id
Text thread
ready