ContextApp — Walk Into Every Meeting Already Briefed

The calendar

It's a calendar. That's the point.

Not a layer bolted onto one, and not another tab to keep open. The calendar hasn't been rethought in decades — so this starts there, and everything else attaches to it.

Every calendar, one view

Work, personal, the second work account. Merged, color-kept, no switching.

Your team's week beside yours

See who's in what, where the load sits, and who else is already in the room.

Day, week, month

The views you already use, faster, with keyboard-first navigation.

See which meetings have a record

Transcribed, email-only, or nothing yet — visible at a glance across the whole week.

Record and revisit

Capture a call from the calendar and find it later by the meeting it belongs to.

Search everything it touches

One search across meetings, people, companies, documents, and what was said.

How it works

Before. During. After. Every meeting.

Because it owns the calendar, it can be there at the three moments context normally goes missing.

Before

The brief is already there.

Open the event and read it. Where the last conversation left off, the questions still unanswered, the documents people actually referenced. Or ask for it out loud on the drive over.

Briefing

Third session with this group on the rollout. The open question is still the timeline for the two regional sites — raised on the 14th, raised again in last week's thread, and not yet answered. Worth arriving with a position.

Rollout plan — Q3.pdf · cited in the last two sessions Re: regional timing · 12 replies, three name the same gap Transcript · call on Aug 20

Every brief shows what it read. You can check it before you trust it.

During

Ask, without interrupting.

A typed question in the panel beside the event, mid-meeting, while someone else is talking. The answer comes back in that meeting's context — this account, this history, these people — not the whole internet's.

Ask

what did we commit to last quarter?

Two things, both in the June recap: a mid-August pilot in the two northern sites, and a written security summary before procurement review. The pilot moved to September on the 12th. The summary hasn't been sent.

Nobody in the room hears a thing.

After

It becomes the follow-up.

The recap writes itself from what was actually said, and then gets shaped for whoever picks it up next — carrying the slice that person needs and nothing they shouldn't have.

Handoff

To Priya Owns the next call. Gets the two open decisions, what changed on timing, and the one thing to avoid re-litigating.

Held back Internal pricing discussion. Not hers to carry into the room.

You decide what passes. The rest stays where it was.

Where the context comes from

You don't feed it.

Nobody keeps a second system up to date. Connect the places the work already happens, once, and it reads from there.

Google & Outlook calendars

Your existing calendars sync in — all of them — and stay in sync both ways.

Gmail & Outlook

The threads where decisions actually get made and then forgotten.

Google Drive

The documents people cite in the room, linked to the meetings that cited them.

Meeting transcripts

What was said, attached to the event it was said in.

Forwarded email

Send anything to a private address and it lands in context.

File uploads

Drop in the things that live outside every system.

Your own notes

Written as instructions, not reminders — the agent acts on them.

People and companies

Built as it reads, so history follows the relationship, not the folder.

Read access only, scoped to what you connect. It never sends, deletes, or edits anything on your behalf — the specifics are spelled out in Data Practices below.

The part that compounds

You had the call. Someone else has the next one.

This is where the hours actually go — not in the meeting, in the retelling of it. Context that lives with one person has to be re-explained every time the work moves. Context that lives with the meeting doesn't.

1You finish a call. The recap is already written from what was said.
2You pick who's next, and what they should walk in knowing.
3It arrives on their invite — their starting point, not your notes.

Where it left off

Timeline for the two regional sites is the open decision. Raised twice, still unanswered. They expect a position, not a question.

What changed since

Pilot moved from August to September. The security summary they asked for has not gone out.

Don't reopen

Scope was settled in June. Everyone has moved on from it.

Held back from this handoff: internal pricing discussion, two unrelated threads.

Over time

It gets sharper the more it's used.

Each brief teaches the next

What you kept, what you cut, what you asked for anyway — the next brief on the same relationship starts closer.

History follows the relationship

People and companies accumulate their own thread, so a first meeting in a year isn't a cold start.

Context outlives the person holding it

When someone leaves, or takes a week off, the thread is still there. It was never in their head.

Who's building it

Twenty-two years building together.

From TrueCar, through OneCloud Systems, to Diversis Capital — with an advisory board spanning GTM, sales and M&A, legal, and marketing.

Meet the full team →

Oded Noy

Founder & CEO

Co-Founder, TrueCar (IPO) · Sr. Operating Partner, Bloom Equity Partners & Diversis Capital · Managing Partner, Amplify.la.

Yoshi Okayama

Co-Founder & CTO

Operating Partner, Diversis Capital · CTO, Tempo Software · VP Engineering, TrueCar.

Data practices

How We Use Your Data

Transparency is central to how ContextApp operates. Here is exactly what data we access and why.

Calendar Data We read your Google Calendar events (titles, attendees, times) to identify meeting participants and build your professional network graph. We never modify or create events.
Email Data We read email headers and content from Gmail or Microsoft Outlook to extract contacts, companies, and conversation context. We never send, delete, or modify your emails.
Drive Files We read files from Google Drive that you choose to sync so we can extract entities and context. We never modify, delete, or create files in your Drive.
AI Processing Your data is processed by AI models (Anthropic Claude) to extract entities, summarize content, and answer your questions. Data is sent only when needed and is not used to train AI models.
Your Data Stays Yours All data is scoped to your account. We do not sell, share, or use your data for advertising. You can delete your data at any time.

Security

Security & Privacy

Your data is protected by enterprise-grade security at every layer.

Encrypted at Rest & in Transit

All data is encrypted at rest using AES-256 and in transit using TLS 1.2+. Database storage, file uploads, and backups are all encrypted by default.

No AI Training on Your Data

Your data is never used to train AI models. We use Anthropic Claude under their commercial API terms, which explicitly prohibit using customer data for model training.

Tenant Isolation

Every account is fully isolated. Your data is scoped to your organization and is never accessible to other users or accounts.

Walk into every meeting already briefed.