Your first week
One habit, not a deployment project. Do this one thing and the rest follows.
The only habit that matters
After every call or meeting, leave a short note — or record a one-minute voice note. That is it. No form, no required fields, no report.
It is the only input that actually gets done in practice, and the rest of the system is built out of it: tasks come out of notes, history lands on the account, and Pulse hands it back to you later.
The first week, in order
- Day one: import your contacts
- Day one: invite your colleagues — history is worth something once several people are writing it
- Every day: a note or a voice note after each call
- Day three: check that the tasks which came out of your notes are the right ones
- End of the week: look at the pipeline once and rename the stages in your own words
What not to do in week one
Do not write the full service catalogue, do not create every field, and do not import three years of history.
These are the tasks that kill deployment projects, and they are almost never needed in the shape they were imagined on day one.
What week two should look like
If the habit has taken, there are specific signs: the Work page is no longer empty, a few tasks that came out of notes are sitting on the board, and Pulse has started surfacing engagements nobody has touched for days.
If none of that happened, the problem is not the tool — the notes were not written. Do not go to settings; go back to the one habit.
Read this next
- Work, tasks & PulseThe Work streamEvery feed and every task in one stream. The page you open in the morning.
- Work, tasks & PulsePulseEngagement cards, ordered by which one needs attention now.
- Contacts & engagementsNotes, replies and decisionsThe three things you write into a feed, and how they differ in practice.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.