The order below matters. Agents can only score accounts that exist, and reviewers only see accounts in their territory, so the first steps decide whether the later ones produce anything.
Owners and Admins do this. Your account team does it with you for a new organization, which Rembrandt provisions and whose first owner is invited in. See Getting Started.
1. Invite your team
Settings → Organization → Members. Each person gets an organization role that controls what they may do in the platform, and optionally a sales role (BDR, AE, Sales Director) that decides which reviews they can hold.
Invite in bulk with a CSV if you are onboarding a whole team.
See Organization.
2. Bring in your accounts
Intelligence → Accounts. Add them by hand or import a CSV. Only the company name and headquarters country are required.
Rembrandt does not invent your account list, and connecting a CRM does not create accounts either. This is the step everything else runs on.
See Accounts.
3. Assign territory
Set which rep owns which account, on the account itself.
Reviewers only ever see accounts in their territory. Skipping this is the most common reason a team reports an empty queue while work clearly exists.
4. Define what you sell against
Configuration → Pain clusters. A pain cluster is a problem you solve, with a detection prompt describing what an account experiencing it looks like, scoped to one or more domains.
Give each one a Playbook: the buying committee to look for, the copy direction for that pain, and proof points of customers you helped with it.
See Signals and Scoring.
5. Define what to look for
Configuration → Domains groups your business areas. Configuration → Frameworks holds the buying signals inside them, per source: jobs, news and reports.
Configuration → Agents puts the two together: an agent runs one framework against a set of accounts on a schedule, and produces the evidence your pains are scored on.
See Signals and Scoring.
6. Decide who reviews what
Settings → Organization → Sales → Pipeline. Set the conviction score an account needs before it reaches anyone, your review stages and who holds them, the SLAs, and who runs the outreach after final approval.
Start with one stage. Add more when you know you need them.
See Review pipeline.
7. Connect your systems
Settings → Organization → Integrations.
-
Your CRM matches accounts to the companies your team already maintains, and keeps their contacts current. See CRM.
-
ZoomInfo sources the people at accounts where nobody in your CRM works yet. See ZoomInfo.
Then say who you want to reach, under Settings → Organization → Contacts. See Contacts.
8. Prepare the outreach
Settings → Organization → Sales. Build the sequences a reviewer can commit an account to, and set the copy guidance the AI writes them by: tone, language, the words to avoid, and the message structures.
See Sequences and Copy.
You are ready when
-
Every account has a territory owner
-
At least one agent has run and produced evidence
-
Your conviction threshold lets a sensible volume through, rather than everything or nothing
-
One sequence exists, with a structure on every step
From there the day-to-day is Funnel and Campaigns.