Pursuvo runs a pipeline: sources bring opportunities in, the scoring engine sorts them, and sequences carry your outreach out. Set your workspace up in this order and the pipeline can fire end to end on the first day.
Add a source
Open the sources page in your workspace and add at least one. SAM.gov is the safest start for federal opportunities; the one-click state bid boards and the generic RSS, REST, and webhook adapters cover the rest. Sources can be disabled at any time without being deleted, so it costs nothing to experiment.
The full adapter catalog, and what each one needs from you, is in Connecting sources.
Configure outbound email
On the outbound email settings page, pick a provider. Resend is the production path; Console mode runs the whole pipeline as a dry run without sending a single real email, which is the right way to spend your first day. To send for real you will need:
- A Resend API key
- A verified sender address and display name
- A physical mailing address (CAN-SPAM requires one in the footer)
- An unsubscribe URL
- A daily send cap; 5 to 10 is a sane first-day value
The webhook signing secret is optional but strongly recommended: it is what lets bounces and spam complaints flow back into Pursuvo automatically. See Bounces, replies, and unsubscribes for the setup.
Create a sequence
A template is an email body, written with Liquid tokens such as {{contact.first_name}}. A sequence chains up to five templated steps with per-step delays. Create at least one template, then build a sequence whose agency type matches the agencies your sources ingest. Without a sequence, scored opportunities have nowhere to go.
Tokens, selection rules, and send windows are covered in Sequences and templates.
Connect a CRM
This step is optional. Pipedrive, HubSpot, and Salesforce are supported. Once connected, every new opportunity that scores Pursue or Partner gets a deal created in your CRM automatically, so pursuit state lives where your team already works.
Let the worker run
Once everything is configured, the background worker takes over on a fixed cadence:
- Ingestion pulls new opportunities daily at 06:00 UTC
- Processing scores, enriches, and enrolls every 30 minutes
- Sending runs every 2 hours, inside each step's send window
First sends typically appear within 2 to 3 hours of the first ingestion run. If the pipeline stays quiet longer than that, walk the checklist in Troubleshooting.