How Kept works

Kept reads the communication you already send and receive: email threads, calendar invites, meeting transcripts, WhatsApp notes and decks. It builds a structured record from them, so you are not maintaining one separately.

Step 1: Connect your email and calendar

Setup takes about two minutes. Connect Gmail and Google Calendar, and Kept starts reading. From the same place you can add Google Meet, WhatsApp and Slack when you’re ready. If there are labels, domains or chats you want left out, exclude them, and Kept leaves them alone.

Step 2: Kept builds the record

Kept works through your threads, invites, transcripts and decks, and creates records for deals, people, companies, co-investors and portfolio companies. Every field carries its source. An ARR figure pulled from a deck appears as “Q3 deck · p.7”, not as a bare number with no trail. A round size mentioned in an email links back to the thread it came from. The record is current within an hour of connecting.

Step 3: Review what matters

Kept does not overwrite what you entered without telling you first. When something new contradicts a field you set, Kept shows the exact change: the old value, the new value and where the new value came from. Then it waits. Nothing you entered changes until you decide.

This matters because not every update is a correction. A founder mentioning a rough runway figure in a casual email may not supersede the number in their board deck. Kept gives you the context to judge, then acts on your call.

Step 4: Correct once, and it stays corrected

A fictional example. Kept reads Halcyon Grid’s March update and proposes a runway of 22 months. You know their number leaves out the bridge note, so you correct it to 18 months and say why. Kept stores 18 months and your note, and from then on reads bridge notes that way for every company.

The record stays clean over time without periodic audits. You correct something once and move on.

Step 5: The record stays current

A static record is only useful at the moment someone last updated it. Kept keeps working after setup and sends signals when something matters:

• Meeting briefs before a call, with the intro, co-investor history and open questions.
• Portfolio warnings when a number moves between two updates, such as runway falling from 21 to 14 months.
• Deals gone quiet when a live conversation has had no reply or meeting for a while.

Each signal says exactly where it came from.

What you can do with it

• Pull up everything Kept knows about a company before a call, including the specific deck pages it read
• See which active deals have gone quiet and decide where to follow up
• Trace any portfolio number back to the update or deck it came from
• Search across deals and portfolio companies by stage, co-investor or owner
• See every deal you share with a co-investor in one place
• Hand a new team member the full history of a deal without a briefing

How this differs from a CRM

A legacy VC CRM expects you to log calls, update stages and fill in fields after every interaction. The record reflects whoever remembered to enter something last. Keeping it current is real work, and most teams eventually let it slip.

Kept works the other way round. The record builds from what already happened, and your job is to review and correct rather than create. You are not maintaining a database. You are checking a record Kept has already written.

Getting started

Request early access. Setup takes a few minutes and the record is current within an hour. Founders raising can request founder access.

Frequently asked questions

Do I need to migrate data from my current tools?

No. Kept builds the record from your email, calendar and meetings. Many firms run it alongside their current CRM or spreadsheet at first, and you can export everything as CSV or JSON at any time.

How long does setup take?

About two minutes to connect Gmail and Google Calendar. The record is current within an hour.

Does anyone at Kept read my email?

Kept is designed so the record builds automatically. You choose what it reads and can exclude labels, domains and chats. For details on data access and protection, see the Security page or ask us during onboarding.

What happens when Kept gets something wrong?

You correct it. Kept shows where the value came from, so you can see why it read it that way. Once you correct a field and give a reason, Kept keeps your value and applies the same reading next time.