Heather

Problems may come in different shapes

not reading?

Matt - Engineering

Matt reviews PRs from Montreal. His team is in Paris.

Every review needs context that isn’t in the Jira ticket. Why the dev made this decision. Why the acceptance criteria reads the way it does. What the PO had in mind. What was tried and ruled out. What the tradeoffs were.

Daily standups give him 60 seconds of vague summary, not the real reasoning. Most devs already push back on standups: 15 minutes that interrupt focus, shared context that stays surface-level. The intent is right. The format isn’t. Documentation is partial. Recorded meetings let him watch but not ask. A question at 2 PM Montreal waits 18 hours for an answer from Paris. By the time the answer comes back, the question has shifted.

Agile was supposed to fix this. A rushed 15-minute standup where everyone speaks vaguely isn’t depth. The actual reasoning, the decisions, the tradeoffs, the things that make a review meaningful, live in people’s heads and in scattered threads across Slack, Jira, GitHub, and email.

Reaching it requires reaching the person. Who is in another meeting. Or in another timezone. Or asleep. Or out sick. Or on vacation. Or just heads-down on something else that needed them more.

Anne ordered samples from a supplier.

She used the specs she had. The specs she needed existed: in Claire’s previous emails with the same supplier, in a doc from a past project that had the full requirement list, in Claire’s notes from the last quarterly review. Claire knew exactly where they were. Anne didn’t have access to most of it, and didn’t know the rest existed.

Claire was in back-to-back meetings that day. The samples came back unusable.

Claire would have answered in two seconds. Anne would have asked, if she’d known what to ask, and where to look. Neither of them did anything wrong. They just couldn’t reach each other in time, and the context that would have saved the order sat in places Anne couldn’t see.

This isn’t anecdotal

$1.2 trillion
Annual cost of workplace miscommunication in the US.
Grammarly and The Harris Poll, State of Business Communication, 2022.
$62.4 million
Average annual loss per large company because information wasn’t understood or acted on in time.
Holmes Report, analysis of 400 corporations.
7.47 hours
Per worker per week lost to clarifying unclear communication and following up on asks. Nearly a full workday.
Grammarly and The Harris Poll, 2022.

Heather, here

Before Heather is anywhere else, Heather is here.

With you, holding your work, your routines, your context. Not as an assistant talking to you. As the thoughts you'd have if you remembered everything

Heather

9 connected

Monday, May 11

Cohort 13 acceptance memo due Friday. Draft pulled together from last week's partner thread.
Founder check-in with Sofia M. in 30 minutes. She asked about the Series A signaling memo last call.
Partnership intro to Andreas K. Four days waiting.
Demo day prep. Three founders haven't shared their final pitch decks yet.

Nostalgia vibes?

Time to remember

Heather, there

When you can't be there, Heather can.

People you've shared your Heather with reach you on their schedule, not yours. They get answers grounded in your actual context. In your voice. With sources. Scoped to what you've decided they can see. You see what was asked, what was answered, and what's queued for you.

Heather

9 connected

Heathers connected

Heathers you may know

Marcus C.

Founder, currently in Cohort 13 at M Ventures

Suggested by: Cohort 13 cohort, Slack workspace

Priya A.

Partner, Initialized Capital

Suggested by: Email contacts, frequent threads

Emma B.

Senior PM, Lumina

Suggested by: Slack workspace

Heather, everywhere

Heather lives everywhere you work, every tool you use to communicate, share, create.

Messages that weren't sent. Emails not read. Documents not shared. Meetings you weren't there for. Calls not answered. Covered, the way you would have covered them, traced back to who you are and what you've shared.

Heather

Today

Yesterday

Earlier activity collapsed

Literally, everywhere

This shape looks right. Walk me through the 3 OKRs one more time?

Here's the final cut for Q3:

Launch v2 self-serve onboarding. Activation 35% to 50%.
Ship team-roles permission model. 8 design-partner accounts using it.
Bring CAC down to $480 on the Marketing-Sourced channel.

Tight, measurable, and the design-partner anchor on #2 means we won't ship something no real customer asked for.

Great. Save this to Heather.

Saving conversation

Write a message…

Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

Tighten this into a one-liner I can read in standups?

“We're the only tool in this category where the workspace itself remembers what each person knows. Notion stops at the page; we keep the person attached to it.”

That sentence covers three things in one line: the differentiator, the closest competitor, and what we're not.

Perfect. @heather save this

Heather

Saving the thread to your Heather context now

Ask anything

Heather

Thinking

ChatGPT can make mistakes. Check important info. See Cookie Preferences.

Claude | orbital

+  return await fetchWithRetry(url, {
+    maxAttempts: 3,
+    baseDelay: 200,
+  });
 }

Wrote src/lib/api/fetch-with-retry.ts (47 lines)

Updated src/lib/api/index.ts

Summary of this session:

• Extracted retry logic into one reusable helper
• Added exponential backoff with jitter
• Wrote 8 unit tests, all passing
• Removed 3 duplicate implementations from billing, auth, and notifications

> Nice. Let's save the progress so far and tell Heather what we've done. /heather:save

Saving session to Heather...

Tagged: refactor, api, retry

✓ Saved as “Retry helper consolidation”

Seasoning…(10s · thinking with max effort)

# cohort-13-selection

Jonathan G.9:42 AM

Heading into back-to-back office hours this morning. Pull in Jonathan-via-Heather if anything needs me before 1 PM.

Sarah K.10:15 AM

@Jonathan-via-Heather what's the timeline we're committing to for demo day? The events team needs to lock the venue today.

Jonathan-via-HeatherAPP10:15 AM

Demo day is June 6, not May 30. Decision was finalized this morning after the partner sync. Three founders need extra time to land their final decks. Lock the venue for June 6.

Source: Partner sync notes May 6 · Slack thread with Daniel, Yuki, and Olivia earlier this morning

Logged to Jonathan's digest

Message #cohort-13-selection

Re: Term sheet exclusivity language for Cohort 13 closeout

Sent · 10:47 AM

FromJonathan G.<jonathan@m-ventures.co>via hi-heather.ai

ToAndreas K.<andreas@northbeam.capital>

Hi Andreas,

Sharing the redacted Cohort 12 closeout exclusivity language below. Names and specific terms removed; structure and clauses intact.

[Redacted Exclusivity Clause]
[ ] No-shop period: 60 days from term sheet execution.
[ ] Carve-outs: limited to LP-of-record introductions made prior to ...
[ ] Fiduciary out: standard board fiduciary exception applies.

A few notes: we landed on this version after pushback from two LP counsel reviews. The 60-day no-shop provision was the main point of friction. If Initialized is proposing something with a longer window, that's worth flagging.

Sent by Heather on Jonathan G.'s behalf

Sources: Cohort 12 closeout doc · LP counsel email thread Mar 14

Jonathan-via-Heather (You)

S

Sofia M.

H

Hugo S.

C

Claire D.

12:34 PM|VSB (S26) - prep talk

To reach us, just say@hi-heather.ai

A figure looking up, surrounded by floating red dots

Here, There and Everywhere

Heathers connected

Heathers you may know

Re: Term sheet exclusivity language for Cohort 13 closeout