Kimono Contact Page (KFS) — v13.1
Read this before reviewing the other tabs. It places the comp in context.
The Kimono Contact Surface (KFS) is the canonical relationship page inside the full Kimono app. It is where everything Kimono knows about a person lives — surfaced in three swimlanes: Signal · Contact · Timeline. This prototype is a static HTML comp for design review. It is not a wireframe; it is close to final fidelity.
| Service | Interface | Connector |
|---|---|---|
| SMS | ✓ | — |
| iMessage | ✓ Apple | ✓ Desktop only |
| ✓ since Jun 14 | ✓ since Jun 14 | |
| Telegram | — | ✓ |
| Signal NEW Jun 15 | — (source only) | — |
Interface = where the user and Kimono talk. Connector = a source that supplies knowledge and inference. Independent per service.
Your merged, de-duped, beautiful contact database.
When a user connects their sources — iMessage, Gmail, WhatsApp, LinkedIn, CardDAV, Telegram, Signal — they don't get a clean contact list. They get a mess: duplicates, stale fields, fragments across silos, people entered three different ways across four apps. Kimono Contacts is the clean layer that sits beneath everything else.
At first launch, Kimono surfaces your top 25 contacts — the people you interact with most, de-duped and enriched into a single canonical record. Over time the database grows through a set of mechanisms:
- Birthday signals — upcoming birthdays surface contacts before you'd otherwise think of them
- Interaction depth — frequent email threads, call history, and message chains promote contacts to the canonical list
- Calendar — people on upcoming meetings are automatically surfaced and kept current
- Daily brief — the morning brief keeps your most active relationships fresh
- Interaction tool — when live, adds real-time relationship signals to the graph
- Paid tier — full contact database import; every person you've ever exchanged a message with
Relationship strength as concentric rings.
Not all contacts are equal. Kimono scores every relationship by recency, frequency, and depth of interaction — then places each person in one of four halos. The closer to the centre, the stronger the relationship. Halos are dynamic: they drift outward as contact fades, and inward as you re-engage.
1
These are the open questions that block V2 shipping. Each person is tagged by domain. Reply in Figma comments or in a doc — Titus will consolidate.
| Chay | Is the in-thread expand → collapse pattern the right interaction for Mini → Mid? The live app's top-right stacks three controls: Kimono ID QR (→ kimono.id), “3 contacts” pill (does nothing today), and user photo (→ settings). Does this stacked-three stay, consolidate, reorder, or get redesigned? |
| Chay + Alek | Mid → Full transition — should opening the full Kimono Contacts page replace the chat surface, open in a side panel, or open in a new tab? Three options on the table, no winner yet. |
| Alek | Is in-place inline expansion feasible at the scale we're imagining — multiple Mini cards in the same thread, all expandable independently? |
| Sutha | Where does the data for a Mini's truncated field list come from — last-touched record, canonical Kimono Contacts, an enrichment cache? What's the right freshness contract per source? |
Cold-to-warm Signals and Outstanding (“You owe / They owe”) Signals already ship in the Kimono app today — these are not new in vDream.
vDream proposes expanding them: more lead time on cooling signals, channel-specific phrasing (SMS reads differently than email), batch surfacing in a single weekly digest, and proximity-triggered surfacing (auto-armed from message parsing, e.g., when you said “ping me when you're in Venice”).
When a new user connects their sources, they have a mess. Kimono cleans it up.
The moment a user links their accounts — Gmail, iMessage, WhatsApp, LinkedIn, CardDAV, Telegram, Signal — Kimono has access to thousands of contact fragments across siloed systems. People appear three ways: "Jon Friedman", "Jonathan Friedman", "J. Friedman jf@liminal-ad.com". Fields are wrong. Companies are outdated. Birthdays are missing. Duplicate records everywhere. This is the raw material.
The Kimono app today renders contacts in chat as three disconnected things: a one-line pill that doesn't expand, a richer card that appears as a separate response with no link to the pill, and a Full Kimono Contacts page reachable only through completely separate navigation. The top-right of the chat surface stacks three controls — a Kimono ID QR icon (→ kimono.id), a “3 contacts” pill (tappable-looking but does nothing today), and a user avatar (→ settings) — none of which connect to the contact flow below.
This tab demonstrates the proposed fix end-to-end: a single Mini pill that expands in place to a Mid card on tap, with a clear link from Mid to the full Kimono Contacts page.
Section 1 shows what exists in the live app today — the broken three-render reality, with faithful production chrome so you can see exactly what users see. Section 2 shows the V2 proposed behavior. Section 3 shows vDream (north-star) — the same transitions with a richer Mid card.
Mini in chat → Mid expansion → Full KFS page.
Today's product shows contact cards in chat — but they're broken: three separate renders with no connected flow. Below is what actually exists in the app today, followed by the V2 proposal and vDream. Persona throughout: Jonathan J. Friedman, Titus's recurring coaching client (architect, LIMINAL A+D, Toronto).
These are faithful reproductions of what the Kimono app currently renders. Three separate states with no connected interaction between them.
Two versions of the connected flow. Both use Jonathan J. Friedman. Tap the Mini pill in either column to expand it.
One connected affordance. Mini → Mid expands in place. Mid → Full is the open question.
Same flow. More in the Mid: Signal, recent interactions, inline contact methods. No AI Summary in Mid (Full KFS only).
Signal. Contact. Timeline. — three surfaces, one person.
The live app already runs on three surfaces. Contact is always there. Signals appears as a tab per-contact when there's something to act on (Boris has it; Dinara doesn't — zero signals). Timeline lives on the right rail today. v13 adds Mini→Mid→Full state stepper, fixes dossier links, and cleans up onboarding and gives Contact its hero treatment.
v1 = today, as audited. v2 = quick wins on the same data model (Summary first, footer CTAs, multicolor clickable tags, platform-filtered Timeline, all-platform Social, user notes). vDream = the three swimlanes stop competing for one column — lateral panels on desktop, swipeable surfaces on mobile, dossier renders into Contact (not chat).
Kimono surfaces who's slipping — before you notice
One glance at the top of your day. Tap the debt tile to open the at-risk list; the Monday digest lands in your inbox.
Ask in plain language across every note you've taken
Semantic search over the private notes layer — not just keyword match.
Type it like you'd say it — or paste a profile
Natural-language capture parses names, places, and context into a structured stub you can confirm.
Drop an event photo, Kimono recognizes the room
Face matching against your relationship graph — known contacts get linked, new faces become stubs.
Timely pushes when a relationship needs you
The same signal engine that powers the dossier pushes a single, actionable nudge — never noise.
Every field knows where it came from
Three display treatments under evaluation — dot-per-field, an inline sources line, and tap-to-reveal.
New contacts from your inbox, already sorted
Kimono scans incoming signatures silently. When it finds someone new it adds them and tells you — no prompts, always undoable.
Export the whole graph, any format
Kimono is the identity layer you own — take it with you at any time.
Martin Tobias
Martin Tobias is Managing Partner at Incisive Ventures, a pre-seed B2B software fund based in Seattle. He's a 3x CEO and prolific angel — 200+ investments, six unicorns in four years. Titus and Martin go back to the early 2000s (Razorfish / Microsoft) with a meeting scheduled Jan 26 to introduce Rotimi.
- Met early 2000s — Titus at Razorfish, Martin at Microsoft
- 200+ investments, six unicorns — prolific angel investor since the early 2000s
- Had meeting August 13, 2025
- Meeting scheduled January 26, 2026
- Introduced to Rotimi (Kimono team)
- Backed 6 unicorns in 4 years
Signal · Martin
Timeline · Martin
Alek Krstic
Alek Krstic is Co-Founder and Head of Product Engineering at Kimono. He owns the React Native app, the KFS sync layer, and the contact-enrichment pipeline that ingests Google, Apple, Microsoft, iMessage, Telegram, and WhatsApp data. Day-to-day, Alek, Sutha, and Titus ship product together — daily Slack threads, multi-thread chat, and the keeper of engineering velocity. Currently driving the Dossier-into-Contact merge (Jira KP-412) and the EnrichLayer rename.
- Co-founded Kimono with Titus (2024)
- Founded Outpost CRM, acquired 2023
- React Native + offline-first specialist
- Owns Agent SDK surface and vDream prototype
- Flagged complexity concerns on v7 (Apr 15)
Signal · Alek
Timeline · Alek
Chay Dib
Chay Dib is a contract designer in Los Angeles, formerly Razorfish. She owns brand + visual identity for Kimono — onboarding illustrations, Kimono ID share flow, and the in-progress brand guidelines V4.5. Sharp, fast async feedback — short turnaround works better than long briefs.
- Just joined Razorfish full-time (Apr 8, 2026)
- Did Kimono onboarding illustrations (Sep 2025)
- Los Angeles, CA
- Brand refresh concepts delivered Feb 2026
- Previously 3 years freelance via Dribbble
Signal · Chay
Timeline · Chay
Martin Tobias
Martin Tobias is Managing Partner at Incisive Ventures, a pre-seed B2B software fund based in Seattle. He's a 3x CEO and prolific angel — 200+ investments, six unicorns in four years. Titus and Martin go back to the early 2000s (Razorfish / Microsoft) with a meeting scheduled Jan 26 to introduce Rotimi.
- Met early 2000s — Titus at Razorfish, Martin at Microsoft
- Backed 6 unicorns in 4 years
- Fund IV thesis overlaps with Kimono
- Asked about ARR trajectory (Apr 14, 2026)
- Last shared doc: Q1 metrics draft (3w old)
Signal · Martin
Timeline · Martin
Alek Krstic
Alek Krstic is Co-Founder and Head of Product Engineering at Kimono. He owns the React Native app, the KFS sync layer, and the contact-enrichment pipeline that ingests Google, Apple, Microsoft, iMessage, Telegram, and WhatsApp data. Day-to-day, Alek, Sutha, and Titus ship product together — daily Slack threads, multi-thread chat, and the keeper of engineering velocity. Currently driving the Dossier-into-Contact merge (Jira KP-412) and the EnrichLayer rename.
- Co-founded Kimono with Titus (2024)
- Founded Outpost CRM · acq. 2023
- Owns Agent SDK + vDream prototype
- Flagged v7 complexity concerns (Apr 15)
Signal · Alek
Timeline · Alek
Chay Dib
Chay Dib is a contract designer in Los Angeles, formerly Razorfish. She owns brand + visual identity for Kimono — onboarding illustrations, Kimono ID share flow, and the in-progress brand guidelines V4.5. Sharp, fast async feedback — short turnaround works better than long briefs.
- Just joined Razorfish full-time (Apr 8, 2026)
- Did Kimono onboarding illustrations (Sep 2025)
- Brand refresh delivered Feb 2026
- Active on Dribbble — 48 shots
Signal · Chay
Timeline · Chay
Same city. Surface who to follow up with.
Kimono detects when you land near a contact. One notification surfaces 3 people worth seeing — with last-touch context and an open ask pre-loaded. No manual check required.
Catch drift before the relationship cools
Kimono tracks interaction frequency per contact. When the gap widens past your baseline it surfaces a signal — no spreadsheet, no manual tracking.
Touch gap: 11d → 37d · baseline is 10d. Last you heard from him was about the board deck.
No touch in 4 months. Halo 2 → Halo 3 demotion queued in 7 days unless you act.
Meeting prep arrives before you open the invite
15 minutes before any calendar event, Kimono assembles context — open asks, last message, shared contacts, what changed since you last met — and hands it to the agent before it starts. No prompting.
Track two-way IOUs across your whole network
Kimono extracts commitments from emails and chat — "I'll intro you to X", "send me the deck" — and tracks them per contact, unprompted. Outstanding asks appear on the contact page and in pre-meeting briefs.
Committed Jan 26 · 60d overdue
Committed Jan 10 · 83d open
Kimono keeps your inner circle tight automatically
As contacts warm or cool, Kimono quietly promotes and demotes them between halos. Halo 1 stays reserved for people who actually reciprocate. Pre-warns you 7 days before any Halo 1/2 demotion.
Martin Tobias
Martin Tobias is Managing Partner at Incisive Ventures, a pre-seed B2B software fund based in Seattle. He's a 3x CEO and prolific angel — 200+ investments, six unicorns in four years. Titus and Martin go back to the early 2000s (Razorfish / Microsoft).
Most recent contact was a follow-up August 13, 2025; meeting scheduled Jan 26, 2026 to introduce Rotimi. His public thesis emphasizes personal AI, data ownership, and writing checks in person — aligned with Kimono's wedge.
- Met early 2000s — Razorfish / Microsoft era
- Backed 6 unicorns in 4 years
- Fund IV thesis overlaps with Kimono
- Last shared doc: Q1 metrics draft (3w old)
Signal · Martin
Timeline · Martin
Alek Krstic
Alek Krstic is Co-Founder and Head of Product Engineering at Kimono. He owns the React Native app, the KFS sync layer, and the enrichment pipeline.
Day-to-day Alek is the partner Titus ships product with. Currently driving the Dossier-into-Contact merge (Jira KP-412) and the EnrichLayer rename. Direct, receipts-required, allergic to slop.
- Co-founded Kimono with Titus (2024)
- Founded Outpost CRM · acq. 2023
- Owns Agent SDK + vDream prototype
Signal · Alek
Timeline · Alek
Chay Dib
Chay Dib is a contract designer in Los Angeles, formerly Razorfish. She owns brand + visual identity for Kimono — onboarding illustrations, the Kimono ID share flow, and the in-progress brand guidelines V4.5.
Pushed back on the orange/gold balance in V4.4. Prefers async review with sharp, fast feedback — short turnaround works better than long briefs.
- Just joined Razorfish full-time (Apr 8, 2026)
- Did Kimono onboarding illustrations (Sep 2025)
- Brand refresh delivered Feb 2026
Signal · Chay
Timeline · Chay
Your inner circle manages itself
Kimono promotes and demotes without asking. You get a notification and a one-tap undo — never a confirm dialog. Cold contacts drop out of the Google 20k count automatically.
Steve won't count against Google's 20k limit
Address changes update themselves
Kimono infers address changes from package delivery emails, LinkedIn updates, and calendar locations — cross-references them, and updates when confidence is high. You see what changed and why.
See the path to anyone through people you know
Kimono maps who-knows-who across your full graph without ever exposing the map to anyone else. Ask about a company and it surfaces the shortest warm path — and who's the right connector.
Every fact traces to its source
Every piece of information Kimono holds about a contact shows where it came from, when it was last verified, and what confidence level it carries. Nothing is asserted without evidence.