DB-Leads finds the sales mandates already hiding in your database. The database scan works through your imported contacts and their activity history for seller signals (mentioned follow-up mandates, sell intent, life events) and files evidence-backed findings into a review inbox. A single won mandate is worth 15 to 20k EUR in commission on average: one hit, and the tool has paid for itself.
What this tool is for, and what it isn't
"Leads" can mean two very different things. DB-Leads is deliberately built for only one of them:
What it does
Database scan
One click works through every imported contact in two stages: a free prefilter (time window, exclusions, signal keywords like "Folgeauftrag"), then AI deep analysis per candidate. Runs in the background and is resumable.
Findings inbox
Every finding comes with a seller score (0 to 100), signals with evidence quotes, and a one-liner. Accept, dismiss, or snooze: the decision is always yours.
AI briefing per lead
A detail page per lead: situation summary, next step, ready-to-send opener, signals, sales-readiness. Every statement is backed by evidence from a concrete activity.
Pipeline board & list
Accepted findings move through freely configurable stages. Drag & drop, or work the sortable, searchable list, including the "Last contact" filter.
onOffice connection
Your existing database is imported and made scannable: addresses and activities, in the background, scaling to 15,000+ entries. Re-syncing updates instead of duplicating.
Customer view & REOS AI
One click expands any lead into its own enterprise page with all facts, the briefing and the history. Alongside it the platform assistant works directly with this lead, dossier attached automatically.
Refresh contact details
Send a contact an email with a personal link so they can check their own details. Whatever comes back lands on the record. The drawer shows per contact what is still open and what has been answered.
Run-through
The mode for an afternoon on the phone: the visible list becomes a queue. Read, call, press one of five outcomes, next contact. Every outcome writes to the history and to the onOffice log.
Ownership
Which properties a contact owns, read from correspondence: address, type, size, year built, each with its evidence. Exactly what sits in no record before the mandate. You can add and confirm entries yourself.
Getting started
Install the tool
Install DB-Leads from the marketplace. On install, a sensible default pipeline is created, including signals and disqualification reasons.
Import your database
Connect onOffice (see below) and import your database: addresses and activities. If you want to look around first, you can deliberately load sample data in the setup assistant. It is labelled as such everywhere and disappears automatically once you connect your real onOffice.
Start the database scan
Start the database scan from the tool page. The free prefilter checks every contact; the AI analyzes the candidates inside the time window.
Review the findings
Open the Findings view and work through the suggestions: accept, dismiss, or snooze.
Settings
Settings (gear icon, top right, /settings/tools/db-leads) are organized into five groups, in the order of the work. Every area has its own address (/settings/tools/db-leads/<area>):
Further guides
Database scan
The core feature: prefilter, AI deep analysis, seller score, and the findings inbox.
Acquisition agent
The status engine: the AI reads the onOffice activities, derives the pipeline status, and keeps your stages sorted.
onOffice import
Connect, field mapping, background sync, and scaling to 15,000+ addresses including activities.
List, filters & export
Filter (including "Last contact"), sort, edit many leads at once, and export the filtered set as CSV.
Customer view & AI
The enterprise detail page in a new tab and the lead-scoped REOS AI agent.
Working in the assistant
Filter the database, read findings and dossiers, set notes, follow-ups, phases and ownership, every change after confirmation.
Rules
The if-then rules: when something happens on a contact, the tool runs actions on its own. Starts paused, with a log.
Settings in detail
Every area in five groups: Connection, Finding, Working, Access and Other.
Setup
Setup in five steps: data source, import your book, write-back, opt-outs, first scan.
Board and phases
The four views and the pipeline: your own phases, their status, drag and drop.
Durcharbeiten
Work a stack of contacts in one sitting: frozen queue, five outcomes, briefings prepared ahead.
Ownership
Which properties a contact owns, with evidence. Why your own listings are not shown here.
Follow-ups
Defer contacts as real tasks in onOffice, with a reminder on the due date.
Refresh contact details
The data request: personal link, documented consent, answer straight onto the record.
Permissions
The ten permissions, and the two deliberately preset for nobody.
Reset
Discard assessments and findings. Contacts and activities are never touched.
Troubleshooting
Common questions and what to do about scan, sync, AI, or permission issues.
Refreshing contact details
In a database that has grown for ten years, the most common reason a call fails is not a bad assessment but a dead phone number. Instead of guessing, you ask the person.
Ask
Open the contact and click "Request details" under Data requests. They receive an email with a personal link in the name of your office. The form asks for email, phone, address and, right at the end, whether a sale is on their mind.
Wait without chasing
After seven days without an answer, exactly one reminder goes out automatically, provided you allow that for this tool. If the action policy is set to "approval", it lands under Approvals and waits for your click instead.
Take the answer over
Whatever the person confirms is stored on the contact, and an activity is recorded as real contact. The consent at the end of the form becomes a permission in your communication settings.
The link is valid for 21 days. As long as nothing has come back you can withdraw it at any time; it stops working immediately. Below the list you see how many of the people contacted across the whole workspace have answered, once there are enough cases for a meaningful rate.
Two things that would otherwise surprise you:
- The reminder carries a new link. We cannot resend the original one because it is not stored in plain text anywhere. The old link stays valid, so anyone who finds the first email still gets through.
- Anyone who has objected to being contacted receives nothing. The button tells you so instead of quietly doing nothing.
Connecting onOffice
You set up the onOffice connection centrally under Settings → Integrations → onOffice, not inside the tool. That is intentional: one connection every tool uses, kept safe in one place.
Full onOffice guideInside the DB-Leads tool, only the tool-specific part remains:
- "onOffice" tab: if onOffice isn't connected yet, a button takes you straight to Integrations. Once connected, Sync now imports your existing database (addresses and activities) and makes it scannable (re-run = update, not duplicate).
- Field mapping: which onOffice field maps to which field is managed by the central integration under Settings, Integrations, onOffice. Sensible default mappings (first name, last name, email, phone, customer no.) are set out of the box.
What is included in the DB-Leads add-on?
DB-Leads is an add-on tool with a monthly price. Included are the AI analyses of the database scan with a fixed quota of full scans per month; incremental scans over new activity only are possible at any time and the prefilter is always free. Single briefings are billed against your credit balance, and from the Max plan you can run everything on your own provider key instead. All figures and rules: Cost and add-on.
Data protection
Lead data is personal data, and owner mining needs clear boundaries:
Frequently asked questions
Boundary to your CRM, the evidence behind each finding, anti-discrimination limits, data protection and what remains after uninstalling: Questions and answers.