BuildsRelationship memory
Folio
Contact product
A contact product that keeps a shareable card and a private memory of the relationship as two different surfaces.
A. RiveraSample contact
Card ready- Last conversation
Walked the product scope and the points that need a person.
- Open thread
Send the revised outline before Thursday.
- Preference
Morning calls. Keep notes off the shared card.
- Boundary
Private memory stays put. The shared card carries only what was marked public.
What it solves
A contact record that only stores a name and a number forgets the thread. A record that shares everything forgets that some memory is private.
Capabilities
- A card that can be handed over, including by QR
- Private notes that stay off the shared card
- Open threads and follow-ups attached to the person
- Preferences that are there before the next conversation
Where it gets hard
- Public identity and private memory have different permissions
- Notes have to be useful months later
- The shared card must stay small enough to hand to someone
- The product has to feel like a person, not a CRM wall
In the loop
An agent can summarize the recent thread before a conversation.
The person decides what is stored, and what is allowed onto the shared card.
Studio product example. Not a client case study, and not a claim about results.