Welcome back!
Every lead here started with a search PARA ran for you. Let's find more today.
$0
Estimated cost, all-time
Ready when you are
Set your parameters below and click Start — this'll only take a few minutes.
0 of 60 found
0%
Start a run to see live activity here...
Takes postings found above and finds real contacts for each — only real, confirmed emails get saved to crm_leads, attributed to "PARA (AI)."
Click "Find contacts now" to see live activity here...
Guide
How to use PARA, where your data lives, and what to do when something looks off.
1. What PARA actually does right now
PARA searches job boards for fresh postings matching Pontoon's real targeting rules (company size, industry, freshness), finds real contacts, and saves qualifying leads straight into RAT.
- check Discovery finds real, qualifying job postings
- check Enrichment finds real contacts and writes them into crm_leads, attributed to "PARA (AI)"
- check Duplicates are blocked automatically, matching RAT's own rule
2. Where everything lives
| Piece | What it is | Where it lives |
|---|
| The Dashboard | The page you open and click Start on | pontoonpara.pages.dev |
| The Backend | The engine that does the searching | Railway - pontoon-para-backend-v2 |
| The Database | Where results and history are stored | Supabase - pontoon-ats (same project as RAT) |
3. How to run a discovery search
- Fill in Industries - comma-separated (e.g., Construction, Manufacturing, Legal, Accounting & Finance)
- Days back - how far to search (max 7). An older posting that's still open is a good sign, not a bad one.
- Max employees - the hard cap on company size (default 500)
- Target leads - how many qualifying postings you want this run to find
- Check the job boards you want this run to use
- Click Start discovery run and watch the live feed
4. Understanding the status colors
| Status | What it means |
|---|
| Idle | Nothing running, ready to start |
| Running | Actively searching right now |
| Healthy | Run finished, hit its target, zero errors |
| Minor issues | Finished with some errors, but found most of what you asked for |
| Needs attention | Something went wrong - check the red banner for the exact reason |
5. Email policy
PARA always tries to find a real email directly first. If it can confirm the company's real domain but not the specific person's email, it constructs a likely one using the same pattern logic your RAs use - marked "medium confidence." Only when the domain itself can't be confirmed at all does a contact get skipped.
6. Common situations and what they mean
"Needs attention" with a message about API usage limits - your Anthropic account hit a spending cap, not a bug. Check console.anthropic.com, raise the cap or wait for the reset date shown in the message.
Live feed looks stuck - give it a minute, each search round takes real time. Check Railway's Deploy Logs for live proof of activity.
"No job boards selected" - check at least one board before starting.