Customer intelligence
People, timelines, signals.
One record per person
Fields
Click a value to change it.
- Name
- Ada Marsh
- ada@northwindprint.example
- Phone
- +1 208 555 0143
- Title
- Owner
- OS
- mac
Identities
- ada@northwindprint.example
- anon
- mtol9kx4jjq5co1a
- account
- acct_5f2a91
First touch never changes, even after a merge: google · cpc → /pricing.
Timeline
Everything that happened, and who did it. Current stage: Paying.
Today
- Purchase
Purchased credits
from google · cpc · /pricing
3:51 PM
- Stage
Moved to Paying
Lifecycle events (purchase)
3:50 PM · automation
Yesterday
- Email out
Sent: Your first project, step by step
to ada@northwindprint.example · Product updates
3:51 PM · Sent
Mon, Sep 14
- Note
Called back about the seat count; wants three
5:51 PM · Ben Okafor
Fri, Sep 11
- Account
Created an account
from google · cpc · /pricing
5:51 PM
- Form
Subscribed to Product updates
“Send me product updates.” · 203.0.113.9
4:51 PM
- Visit
Pageview /pricing
from google · cpc
3:51 PM
Connections
Other records linked to this one.
- Member of
- Northwind Print Organization
- Subscription
- Studio, $49 a month Paying
Tasks
What to do next, who it is for, and when it is due.
- Send the three-seat quotedue Fri · Ben Okafor
- Call back about seatsdone 3 days ago by Ben Okafor
Sample data, not a customer's.
One record across devices
Four rows in four systems, usually. Here, one record.
- No cookies, no fingerprint
- One random id in the browser. Clear it, and it's a new one.
- The earliest first touch is kept
- A merge always keeps the earliest source, never the latest.
- Merging two people is a judgement
- Never automatic. Kicklace shows the pair; a person decides.
The lifecycle is derived
- 1Visitor
Seen, and nothing more yet
- 2Signed up
Created an account
- 3Activated
Did the first real thing in the product
- 4First value
Got what they came for
- 5Paying
Paid
- 6Expanding
Bought more of it
- 7Retained
Paid past a full period
- Seven rungs, worked out from events
- Visitor through Retained. A stage moves because something happened.
- Trial and churn read from the money
- Trial, paying, churned, free — read off subscriptions and purchases.
- A rung is a population, not a destination
- Automations listen to a rung the same way they listen to any population.
What Kicklace stores
- Records, identities and interactions
- A record, an identity that recognises it, an interaction that happened.
- Export and delete, both whole
- Export: everything, one file. Delete: the record and everything that refers to it.
Find any record fast
Search everything. Save any filter as a view.
| Person | Stage | Lists | First seen | Last activity | |
|---|---|---|---|---|---|
| AMAda Marshada@northwindprint.example | Paying | Product updates | google · cpc → /pricing | 2 h ago | |
| BOBen Okaforben@harborlights.example | Activated | Product updates, Tips | reddit · social → /signup | yesterday | |
| CVCleo Vargacleo@tessellate.example | Signed up | none | direct → / | 3 days ago | |
| DADev Ananddev@copperline.example | First value | Product updates | newsletter → /product | 5 days ago | |
| ·Anonymous 7f3a2cno email yet | Visitor | none | chatgpt.com → /how | just now |
Questions
How does Kicklace know two visits are the same person?
The browser keeps one anonymous id, and the moment an email address turns up — a sign-up, a subscribe — that browser joins the record it belongs to, wherever it was seen before.
What does the reading on a record actually say?
One sentence that carries a change, a comparison or a duration, with the facts it is built from beside it — never a column of the table read out loud.
More on readings: Product.
Join the waitlist
One company at a time.