The AI teammate teams open before every meeting

Make COG the place work starts, moves, and gets remembered.

Lead with one behavior people repeat every day: meeting prep, live capture, and follow-through. Then turn that wedge into a memory-rich execution agent that teams trust to act with approval.

Daily habit

Before, during, after

COG should stay open through the whole meeting loop.

Strongest wedge now

Meeting Note Taker

Start where teams already create too much manual work.

Long-term moat

Memory + approvals

Trusted actions across systems of record.

The right product story

Start with one repeatable workflow. Expand from there.

Investors and users should see one clear wedge in front, then a believable ladder into a stronger work agent.

TodayPrep, capture, summarize
SoonDraft follow-ups and tasks
ThenTrusted memory and approved actions

The winning loop is:

meeting -> decision -> follow-up -> completion -> remembered context

Model the weekly value

Daily Operating Loop

This is the behavior COG should own every workday.

COG daily cockpit

Open COG before the call, not after the damage is done.

Prep brief ready 11 minutes before start
Suggested command

/brief Seoul expansion review

Prior decisions

4

Pilot budget approved, timeline still open, finance asked for lower burn.

Open blockers

3

Vendor terms, hiring lead time, and launch scope are still unresolved.

People in room

6

CEO, finance lead, ops lead, recruiting, PM, and regional manager.

What COG surfaces

Agenda skeleton drafted

Ready

Opening decisions, blocker review, budget ask, next checkpoints.

Last meeting recap pinned

Pinned

Budget gate, hiring dependency, and office shortlist are surfaced inline.

Risk prompt suggested

Prompt

Ask whether vendor onboarding delays shift the May target.

Why users come back

Users get context before they walk into the room.

COG becomes the meeting prep habit instead of a passive notes archive.

The value starts before transcription even begins.

Why Teams Would Use COG Every Day

The product should earn repeat usage at multiple points in the day.

Open before every meeting

Prep is where COG becomes part of the calendar, not another tool people remember too late.

Stay open during the call

Live capture, detected decisions, and owner prompts give users a reason to keep COG visible while the meeting is happening.

Close the loop right after

Summaries, follow-up drafts, and action trackers should be ready while the context is still warm.

Come back for memory

Searchable people, decisions, and topics turn yesterday's meetings into tomorrow's operating context.

Current Wedge, Clear Expansion

Put the current meeting workflow in front and let the rest read as the ladder up.

See the ladder
Use every day

Meeting Note Taker

Lead with Korean-first meeting capture, transcript refinement, action items, and summaries that teams actually keep.

Best first buyer story

Meetings create avoidable prep work, lost decisions, and weak follow-through. COG solves that immediately.

Why it compounds

The same meeting data becomes prep context, searchable memory, and approved execution later.

Natural extension

Meeting Prep Briefs

Use prior transcripts, decisions, and tasks to prepare the room before the first person speaks.

Habit moat

Execution Orchestrator

Move approved actions into systems of record and keep commitments visible between meetings.

Enterprise trust

Decision Guardrails

Show citations, owners, dependencies, and timing risks before expensive plans become locked in.

What should feel real now

The Product Surface Users Should Want Today

Live Korean transcript preview

Immediate speech-to-text gives users value during the meeting, which is stronger than a post-call-only product story.

Refined transcript layer

A higher-quality second pass makes summaries, decisions, and action extraction worth trusting.

Decision and owner extraction

The product should foreground what was decided, who owns what, and what still lacks an owner.

Saved meeting memory

Recent recordings, transcripts, and outputs should stay accessible so value compounds over time.

Follow-up outputs

A strong default should be recap drafts, task drafts, and reminders, not just a polished wall of text.

Privacy-sensitive handling

Customer-controlled or local-first treatment matters if COG wants to win serious business workflows.

Product Promise

Before

Know what matters before the meeting starts.

During

Capture what was actually decided while the room is still live.

After

Leave with follow-up already shaped for execution.

Everyday Test

If a user can say, "I open COG before every important meeting and I trust it to move the work right after," the product is on the right path.

Fastest Valuable Ships

These additions make COG feel useful every day without changing the product story.

Prep brief command

1-2 weeks

Build a daily opener that assembles prior decisions, open tasks, and unresolved questions for the next meeting.

Follow-up draft center

1-2 weeks

Generate editable email and chat follow-ups from the summary view so users can move work immediately.

Approval queue

2-3 weeks

Let users confirm owners and due dates before pushing tasks into Notion, Jira, Linear, or Asana.

Meeting memory search

2-3 weeks

Search people, accounts, decisions, and risks across prior transcripts to create durable operating memory.

Weekly Value Model

A simple way to show why COG earns daily usage.

Team size10
Meetings per person / week7
Follow-ups per meeting3

Modeled weekly impact

What daily usage compounds into

70 meetings touched / week

Hours reclaimed

25

From prep, note cleanup, and follow-up drafting.

Follow-ups tracked

151

Review-ready actions instead of forgotten commitments.

Decisions searchable

112

New context available for the next week of meetings.

The pitch this model supports

COG is not another passive summary tool. It becomes the daily operating layer that prepares meetings, captures decisions, and keeps work moving after the room clears.

Roadmap to the best work agent

The roadmap gets stronger once COG owns a workflow people already repeat. From there, memory and approved execution become credible.

Phase 01

Compounding memory

Unify transcripts, summaries, owners, dates, and decisions so every meeting starts with real context instead of a blank page.

Phase 02

Approved cross-tool actions

Draft or write follow-ups into email, chat, tasks, docs, and CRM with approval before execution.

Phase 03

Trustworthy guardrails

Show citations, permission boundaries, ambiguity, and risk checks so teams can rely on COG for higher-stakes work.

Phase 04

Role-specific operating surfaces

Package the same memory and action layer for sales, recruiting, founder ops, customer success, and product leadership.

What the eventual agent must do

The strongest version of COG is not a better chatbot. It is a permission-aware teammate that remembers context, proposes the next move, and can act with approval.

Search across tools

Work before and after meetings

Take approved actions

Show citations and guardrails

See investor criteria

Investor lens

What a strong COG story should prove next

Weekly habit

COG should be opened before, during, and after recurring meetings. That is the retention engine.

Action completion

The product should prove it increases follow-through, not just note quality.

Memory advantage

Each new meeting should make COG more useful because the system remembers decisions, people, and unresolved issues.

Trust to act

Users should become comfortable approving actions across tools because the product shows enough context to trust it.