Pieter van Dam
Person
Brakkevoort Logistics · champion
Pieter van Dam is the CRM champion and platform admin at Brakkevoort Logistics. He leads the weekly shipper review and acts as decision-maker, but is under pressure to justify Growth spend to his CFO as usage falls and freshness tickets mount.
Who they are
Insight
As at Fri 9 Oct 2026Pieter van Dam is the CRM champion and platform admin at Brakkevoort Logistics. He leads the weekly shipper review and acts as decision-maker, but is under pressure to justify Growth spend to his CFO as usage falls and freshness tickets mount.
Role: Head of Commercial Excellence in Rotterdam, CRM role champion, with a platform user account created 2025-04-01. He joined onboarding, QBR, check-in and renewal calls and raised the tickets.
Influence: He wants to renew Growth but says he cannot argue with Marloes Hendriks if usage stays low. He asked 22% of the organisation's questions over the last 12 months and the last 90 days, which is a key-person risk.
Watch: He escalated three high priority tickets on 24 Jul 2026 and said "I am not asking for money. I am asking for reliability." The 1 Apr 2027 renewal needs a value case he can take to the board.
CRM records
| Organisation | Title | Role | |
|---|---|---|---|
| Brakkevoort Logistics | Head of Commercial Excellence | champion | pieter.vandam@brakkevoort.example |
Activity
- 24 Sep 2026eventYour renewals, read by the brain
+40 - 16 Sep 2026callBrakkevoort Logistics / BG-Demo – Check In
- 2 Sep 2026email threadInvitation: Your renewals, read by the brain
- 27 Aug 2026email threadFollow-up from our QBR
+2 - 26 Aug 2026callBrakkevoort Logistics / BG-Demo – QBR+2
- 28 Jul 2026email threadCheck-in notes from our call
- 27 Jul 2026callBrakkevoort Logistics / BG-Demo – Check In
- 24 Jul 2026callBrakkevoort Logistics / BG-Demo – Escalation
+2 - 22 Jul 2026ticketRefresh still not running, need urgent update
- 21 Jul 2026ticketDashboards not refreshing
- 20 Jul 2026email threadFinding a time to talk through the escalation
- 13 Jul 2026ticketBrain queries running slowly
- 26 May 2026callBrakkevoort Logistics / BG-Demo – Check In
- 19 May 2026email threadCheck-in call: finding a time
- 23 Mar 2026callBrakkevoort Logistics / BG-Demo – Check In
- 25 Feb 2026callBrakkevoort Logistics / BG-Demo – QBR+1
- 23 Feb 2026callBrakkevoort Logistics / BG-Demo – Renewal
+2 - 6 Jan 2026callBrakkevoort Logistics / BG-Demo – Renewal+1
- 31 Dec 2025dealBrakkevoort Logistics – Renewal
- 2 Dec 2025email threadCheck-in notes and next steps
- 1 Dec 2025callBrakkevoort Logistics / BG-Demo – Check In
- 25 Nov 2025email threadQuick check-in before the year end
- 26 Sep 2025ticketHow to build a custom dashboard for exception accounts
- 3 Sep 2025ticketConnector stopped syncing data
- 26 Aug 2025callBrakkevoort Logistics / BG-Demo – QBR
- 21 Aug 2025email threadBooking the QBR
- 28 Jul 2025callBrakkevoort Logistics / BG-Demo – Check In
- 21 Jul 2025email threadScheduling our check-in
- 19 Jun 2025ticketGuidance on rolling out to the wider team
- 22 May 2025callBrakkevoort Logistics / BG-Demo – Onboarding
- 24 Apr 2025callBrakkevoort Logistics / BG-Demo – Onboarding
- 9 Apr 2025callBrakkevoort Logistics / BG-Demo – Onboarding
- 4 Apr 2025email threadKickoff follow-up and next steps+1
- 3 Apr 2025callBrakkevoort Logistics / BG-Demo – Kickoff+1
- 26 Mar 2025email threadKickoff scheduling for the implementation
- 17 Feb 2025email threadFollowing up on the proposal for Brakkevoort
- 17 Feb 2025callBrakkevoort Logistics / BG-Demo – Proposal
- 7 Feb 2025callBrakkevoort Logistics / BG-Demo – Demo
+2 - 31 Jan 2025email threadDemo follow-up and next steps
- 29 Jan 2025callBrakkevoort Logistics / BG-Demo – Demo
- 22 Jan 2025email threadBooking the demo
- 17 Jan 2025email threadFollowing up on our discovery call
- 16 Jan 2025callBrakkevoort Logistics / BG-Demo – Discovery
- 9 Jan 2025email threadSetting up a discovery call
- 27 Dec 2024dealBrakkevoort Logistics – New