Stand Up a CRM and Outreach Pipeline in One Run
Company discovery, enrichment, dedup checks, tasks, and linked records, verified after every write, with a completion packet showing what changed and what needs human judgment.
Define the CRM shape you want built
Connect Apollo for discovery and enrichment and your CRM of record, HubSpot, Attio, or Close. Opulent builds the whole operating structure in one pass, not just a list of names.
Tell Opulent the shape once, in a playbook (a reusable, named set of steps): the fields you track, the target states, the dedup rule, and what a complete record looks like. The run holds to that shape end to end.
Playbook: !stand-up-pipeline Build the deal-sourcing CRM: 1. Discover companies matching [thesis]; enrich each with Apollo. 2. Dedup against existing records by domain before creating any. 3. Create company records with our fields: source, target state, model status, last touch, next touch, post-target reason. 4. Create and link people, brokers, and intake documents. 5. Create the next task per company (specific, dated). 6. Draft process-update emails from verified facts only. 7. Verify the structure after write; list what needs judgment.
Hand Opulent your existing field list or a sample record so the new structure matches what your team already reports on, instead of a shape you have to remap later.
Kick off the one-pass build
This is an on-demand run: send the kickoff message when you want the pipeline stood up, a new fund, a new thesis, a new territory. Paste the message from the top of this page with your thesis filled in.
For an ongoing operation, wrap the same playbook in a schedule so newly discovered companies are added and structured on a cadence rather than in one big push.
The sharp edge: a build with no dedup rule creates duplicates against records that already exist. Confirm the dedup key (usually company domain) before the first run so it merges rather than doubles.
Watch the run build and verify the structure
Take a run that stands up a fresh sourcing pipeline for a vertical:
The run does not stop at data entry, it verifies the structure it wrote and only then reports done.
Run: stand up "vertical SaaS roll-up" pipeline Run actions: - Discovered 90 companies in the thesis; enriched with Apollo. - Deduped against 240 existing records, merged 12, created 78. - Populated fields on all 78: source, target state, next touch, model status. - Created 78 next tasks and linked 41 known people and 4 brokers. - Drafted 9 process-update emails from verified facts. - Re-read the CRM: confirmed 78 records complete; flagged 6 companies with conflicting founding data for human review.
What exists after one run
When the run finishes, you have a working pipeline, not a spreadsheet to import, and every piece is verifiable:
Company records created with your fields populated and target states set. People, brokers, and intake files linked to the right companies. A next task on each record. Draft process-update emails ready to send. A completion packet listing what changed and what needs your judgment.
The completion packet is the proof-of-work: because Opulent re-reads the CRM after writing, it reports the structure that actually exists and names the records it could not resolve alone.
Sharpen the build for next time
When the run keeps mis-populating a field or missing a link, add the rule to !stand-up-pipeline, or write it into memory (the notes a run recalls next time), like "always set target state to 'watch' when funding is older than 24 months".
Review the flagged records each run; teaching Opulent how you resolved a conflict shrinks the judgment queue over time.
The natural chain: once the pipeline exists, hand it to Self-Evolving Pipeline Operations for weekly hygiene, or feed new names from Event Prospecting straight into this build.