The first thirty days

What happens after your go-ahead — per day, with your time alongside

Every client goes through the same playbook; it lives in the platform, not in our heads. Your commitment in thirty days: about four hours, spread over five moments. Anything missing becomes an action item with an owner, never a reason to wait.

Day by day

What we do, what we ask of you, what you get

WhenWhat happensYour timeWhat you get
Day 1Go-ahead
Service agreement and data processing agreement signed; we create your workspace and put it in your name.
Two signatures—
Day 1Welcome
You receive the welcome e-mail: what happens in thirty days, your mailbox address, and whom you invite as contract owner or reader.
5 minutes of readingWorkspace, mailbox address
Day 2Access
Your contacts sign in without a password (code by e-mail or Entra ID). Roles are set; the stand-in is named in the data processing agreement.
10 minutesSign-in for your people
Day 3Document request
We send one list: contracts and annexes, twelve months of creditor records, contract owners, open issues. Forwarding to the mailbox is enough; we do the sorting.
30 minutes of gathering, or your assistant—
Day 3–7Sources
Accounting export (Exact, AFAS, Business Central) and the Entra or Workspace export, with the instruction for your package. Anything missing becomes an action item, not a reason to stall.
15 minutes per exportMailbox fills up; first interpretations visible
Day 8–12Register
We enter vendors and contracts with end date and notice period, generate the obligations and run the clause check. You watch the register grow.
—Vendor register, renewal radar
Day 12First check
Ten minutes through the register together: are owners, amounts and dates correct? You correct, we process.
15 minutes (video call)Checked register
Day 14Nulmeting delivered
Register, AI inventory and priority list as PDF and in the platform. If you started with the Nulmeting (baseline scan), this is the delivery point — and the moment to decide on continuous monitoring.
30 minutes (delivery meeting)Nulmeting: AI & Vendor Scan
Day 15–21Assessing
Risk profile per vendor, tiers and reassessment rhythm, playbook aligned with your hard requirements. Savings opportunities and approaching deadlines at the top of the work queue.
20 minutes: which clauses are a hard requirement for youRisk profile, priority list
Day 22–28First file
The next notice deadline gets a renewal file: usage, invoices, list price, clause gaps and our proposal. The contract owner scores the vendor (five questions).
15 minutes (scorecard)Renewal file with proposal
Day 30Delivery and rhythm
Tour of the portal, rhythm agreed (weekly overview, monthly refresh, quarterly meeting), notifications tested. From here on it runs.
45 minutes (delivery meeting)Working rhythm; first weekly overview

Added up: two signatures, three meetings of fifteen to forty-five minutes, one document request and two exports. If you start with the Nulmeting, you are at the delivery on day 14; if you start directly with Zicht, Grip or Verantwoording, you go through the whole schedule.

Who decides

We prepare, test and negotiate; you take every decision on renewing, terminating or signing.

In thirty days that comes up three times: at the check of the register (day 12), at the priorities (day 15–21) and at the first renewal file (day 22–28). Every decision is recorded in the platform with who took it and when; that too is part of the audit trail.

After that

A weekly overview by e-mail, the monthly accounting export, the quarterly report and meeting, and every year the reassessment and the exercise with the stand-in. The playbook keeps running; you notice it in the renewals that land on the table on time and prepared.

Start with a NulmetingBook twenty minutes