PlaybookFounder45 min · 6 stepsUpdated 1 November 2026
Connect first the source where your team makes promises, because that is where work goes missing. That is usually email, sometimes chat, and the CRM only when the team updates it every day. You can decide in 45 minutes, using last week's commitments as evidence.
Who it is for, and how long it takes
Who it is for
How long
What you need
What you end with
Founders and operations leads choosing where a new system, or a new chief of staff, should start reading.
About 45 minutes in one sitting with the team lead.
Last week's open commitments, the list of tools your team uses, and the team lead in the room.
One source chosen for a reason you can write in a sentence, a second source queued, and a date to add it.
Key takeaways
Start where promises are made. The record of a promise usually comes later, if it comes at all.
Count real commitments from last week before you decide. Opinions about which tool the team uses are often wrong.
One source done well is worth more than three done halfway. Add the second only when the first is trusted.
Every company has more places where work lives than anyone can list from memory. Connecting all of them at once makes noise, and connecting the wrong one first makes a quiet week that tells you nothing. This playbook is a short exercise in evidence: find where last week's promises were made, then start there. It works as well for onboarding a new chief of staff as for setting up software.
Worked example. The examples use Vaultex, a safety-footwear manufacturer in Greater Noida and GeniOS's first design partner. The buyers, orders and dates are for illustration only.
PrepBefore you start
Bring these to the 45-minute session, so the decision rests on evidence.
The team lead in the room, plus anyone who talks to buyers or suppliers most days.
Last week's sent email, chat threads and calendar open, so you can check what was actually said.
A blank sheet with the columns from the commitment log below.
The list of tools the team uses, including chat on personal phones.
A working rule for what counts as a promise: any date, price, quantity or meeting offered to someone outside the team.
Agreement that the first source is connected read-only, so nothing in it changes.
StepsThe steps
45 min · 6 steps
List last week's commitments
Sit with the team lead and write down every promise the team made last week: quotes, delivery dates, samples, payments and meetings. Aim for twenty or more, and keep the small ones. At Vaultex, Harsh lists the Bata quote, a sample date for Reebok and a call with the steel toe-cap supplier.
Mark where each one was made
Next to each promise, write the place it was first said: an email, a chat message, a call, a meeting or a CRM entry. Use the first place only. A later copy into a sheet does not count.
Mark where each one was recorded
Now write where the team tracks it, if anywhere. The gap between the two columns is the work that goes missing. At Vaultex, the Bata quote was promised in a chat message and never reached email or the CRM.
Apply three tests
Pick the source that holds the most first promises, is used every day, and is read by the person who owns the outcome. Email usually wins for buyer and supplier work. Chat wins when deals are agreed in groups. The CRM wins only when the team updates it daily.
Connect it read-only and watch one week
Connect the chosen source read-only, so nothing in it changes. With GeniOS, the owner reads the intelligence from that source each morning. Without it, have the team lead check that source each evening against a running list. Either way, check how many of last week's promises would have been caught.
Queue the second source with a date
Write down the next source and the day you will add it, usually one to two weeks later. Add it only when the owner trusts what the first source produces. At Vaultex the second source is email, so the quote promised in chat can be checked against the quote actually sent.
TemplateCopy this commitment log
Use these columns for steps one to three, and the decision note for step six.
Promise
First made in
Recorded in
Owner
Due
Quote for 12,000 pairs of S3 shoes to Bata
Chat
Nowhere
Harsh
Friday
Sample date for Reebok
Email
Production sheet
Anushka
15 November
Call with the steel toe-cap supplier
Phone
Calendar
Harsh
Tuesday
Decision note. "We are connecting [source] first because [number] of last week's [total] promises were first made there, and [owner] reads it every day. We will add [second source] on [date] if [owner] trusts the first two weeks."
ExampleWorked example: Harsh's 45 minutes at Vaultex
How the decision might go for the sales team at Vaultex.
The list. Harsh opens last week's threads and lists a little over twenty promises. Most buyer promises were first made in chat: the Bata quote, a revised sample date for Reebok, a call time with the steel toe-cap supplier. Supplier price talks happened in email, including the 8% rise. Only a few promises reached the CRM, all after the fact.
The tests. Chat holds the most first promises, the team uses it all day, and Harsh, who owns the outcome, reads it constantly. It passes all three tests. The CRM fails the daily test, because deals are entered after they are agreed.
The first week. Chat is connected read-only. The intelligence turns up a promise Harsh had forgotten: a sample pair offered to a Bata sourcing lead in a group chat on Thursday. It also shows the Bata quote as promised and not yet sent, which is the kind of item the 24-hour quote playbook is built to catch.
The second source. Email is queued for the following Monday, so the quote promised in chat can be checked against the quote actually sent. Delivery dates found in chat go to Anushka, which is where getting promises onto the production plan starts.
MistakesCommon mistakes
These five mistakes make the first week quiet or noisy, and both tell you little.
Choosing by opinion. Teams often say everything is in email, then find half their promises in chat. Count first.
Counting copies as sources. A promise copied into a sheet was made somewhere else. Use the first place it was said.
Forgetting personal chat. One salesperson's phone can hold many of the buyer promises. Ask directly.
Connecting three sources in week one. The first week turns into noise. One source, one week, then the next.
Starting with the CRM because it looks tidy. Tidy records often arrive after the promise. Check whether deals are actually agreed there.
What good looks like after
You can name the source where your team makes most of its promises, with last week's list as evidence.
The team lead agrees with the choice, because it came from their own commitments.
The first week turns up promises that were made and never recorded anywhere.
A second source is on the calendar, with a date and a reason.
Nobody is arguing for connecting everything at once.
If the list of commitments is short, the team is probably promising things in calls and meetings. Start with the calendar and meeting notes instead.
Ask the owner whether they read every item without a reminder
Yes, by the end of week one
Second source on the calendar
Check the decision note
A date and a reason
Questions
What if our team uses all three equally?
Pick the one the owner already reads every day without being asked. A source the owner trusts gets real attention in the first week, and that attention is what builds trust in the new routine.
Why start read-only?
Read-only means nothing in your tools changes while you learn what the new system sees. It keeps the first weeks low risk and lets you check its picture of the work against your own.
When should the CRM come first?
When the team updates it every day and deals are agreed inside it. In many smaller companies the CRM is filled in after the fact. It then shows outcomes and misses the promises that led to them.