The blank page is an advantage
Most guides in this cluster are about untangling an old system. You get to skip all of it. No duplicate contacts from three eras of ownership. No forty custom fields nobody fills. No pipeline shaped by a tool bought in 2016. Teams that start clean reach trustworthy reporting faster than teams that migrate, because every record in the account was created on purpose.
The risk is different. Without an old system forcing decisions, blank-page teams either over-design for months or start typing with no design at all. The cure is a deliberately small first setup, built in days, refined from real use.
Decide these four things first
First, the stages. Name the five to seven steps a deal actually passes through, from first conversation to signed. Use the customer's actions, like demo done or proposal accepted, not your hopes.
Second, the deal definition. What is a deal, and when does one get created? A common rule: a deal exists once a real conversation about a possible purchase has happened. Everything earlier stays a lead.
Third, ownership. Who owns a deal, and can two people share one? Pipedrive says no, one owner per deal, and that clarity is worth adopting on day one.
Fourth, the few fields that matter. Deal value, expected close date and source cover most first setups. Add a field only when someone names the report that needs it.
Where your data already lives
| Source today | Becomes in Pipedrive | Notes |
|---|---|---|
| Accounting system customers | Organizations | The cleanest list you own. Start here. |
| Inbox and sent mail | People, via email sync | Sync fills contact history automatically. |
| Quote and proposal folder | Won and lost deals | Backfill a year for a reporting baseline. |
| Calendar history | Activity context | Shows who you actually met this year. |
| The founder's spreadsheet | Open deals | There is always one. Import it last, curated. |
| LinkedIn connections | Selective people records | Only real prospects, not the whole network. |
Pitfalls on the blank page
Over-configuration is the classic. A week of enthusiasm produces four pipelines, thirty fields and twelve automations before the first real deal is logged. Every unused field teaches the team that fields are optional. Build the minimum, then let usage pull the configuration forward.
The second pitfall is importing your whole address book. Two thousand LinkedIn contacts and every email correspondent make the account feel full and mean nothing. Import people you could plausibly sell to this year. The rest can arrive when they become relevant.
The third is skipping the team moment. A CRM adopted by the founder alone is a diary. Set one shared session where everyone creates their own deals, and agree the one rule that matters: if it is not in Pipedrive, it does not exist.
The step plan
1. Run the process workshop
Ninety minutes. Stages, deal definition, ownership and the first fields, written on one page.
2. Configure the basics
One pipeline, the agreed fields, users, email and calendar sync. Half a day of work.
3. Gather and import the data
Organizations from accounting, people from mailboxes, open deals from the sheet and the quote folder. Small, curated imports.
4. Work real deals for two weeks
No new configuration during this period. Collect friction notes instead.
5. Refine and add the first automations
Fix stage names that confused people, add the field someone missed, and automate the two actions everyone repeated.
Timeline and cost band
One to three weeks to a working setup. With a partner this lands around €3,000 to €6,000, the bottom of the market band, and it is also the route where doing it yourself is most realistic. The DIY versus partner test gives you an honest answer in ten minutes. If you do have a sheet that has quietly become your system, the spreadsheets guide covers that heavier start. The full rollout structure, including adoption, is in implementation in six steps, and the common mistakes guide is worth reading precisely because you can still avoid all twelve.