Writing/Granola's Three-Month Offer: How I'd Evaluate It
§ 03 · ai

Granola's Three-Month Offer: How I'd Evaluate It

A practical three-month Granola evaluation plan for new users who start through my affiliate link.

Affiliate disclosure: I may earn a commission if you buy through a link here, at no added cost to you. The recommendation and caveats are mine.

Granola's Three-Month Offer: How I'd Evaluate It
Plate · Essay · Aug 2, 2026

title: "Granola's Three-Month Offer: How I'd Evaluate It" author: Zachary Proser date: 2026-08-02 description: A practical three-month Granola evaluation plan for new users who start through my affiliate link. image: https://zackproser.b-cdn.net/images/granola-hero.webp tags: [ai, productivity, meeting-notes, granola] hiddenFromIndex: true

New users who start Granola through my affiliate link get their first three months free. This is the practical reason to use my link: the same product, with enough time to judge it across your real calendar instead of one unusually good meeting.

What I would test during the three months

Granola became useful to me when I stopped treating every meeting the same. A recurring 1:1 needs a different note from a customer call, and both differ from an interview or planning session.

Use the offer to answer four questions:

  • Do the notes catch the decisions and details you normally miss while listening?
  • Can you build a template that matches a meeting you attend every week?
  • Do you use the transcript later, or does it become another archive you ignore?
  • Does the output make the follow-up easier: a Slack update, email, CRM entry, or task list?

Month one: learn whether you trust the note

Start with ordinary, low-risk meetings. Read every transcript and edit every note. You are testing accuracy, speaker context, and whether the output reflects what mattered to you—not whether the first automatic summary looks impressive.

By the end of the first month, you should know which meeting types work well and where overlapping speakers, room acoustics, or specialized vocabulary cause trouble.

Month two: make the output fit your work

Create one template for the meeting you attend most often. Keep it short. Ask for the decisions, open questions, owners, and follow-ups you already need after that meeting.

Then test one downstream task. Turn a customer call into a CRM update, or a team sync into a concise status note. The value comes from the work you can finish after the meeting, not the existence of a transcript.

Month three: decide whether you would miss it

Look back over the previous two months. Count how often you searched an old meeting, used a generated note, or completed a follow-up faster. If Granola disappeared tomorrow, would your work become slower or less reliable?

That answer is more useful than a generic time-saved estimate.

What happens after the offer

Granola currently has a permanent Basic plan at $0 with limited accessible meeting history. The Business plan is $14 per user per month and adds full history, more advanced AI features, integrations, and MCP access. Those public prices were checked in August 2026; confirm the checkout details before choosing a plan.

The paid plan makes sense when the history and integrations have become part of your workflow. The free Basic plan may be enough when you mainly need current meeting notes and do not rely on a long archive.

Who should skip it

Granola keeps a bot out of the participant list, but it sends captured audio to cloud transcription providers. Choose a different workflow if your organization forbids that processing, if you need saved audio or video playback, or if everyone on the call needs a shared live transcript.

You also remain responsible for disclosure, consent, company policy, and applicable law. A quiet participant list does not remove those obligations.

§ More in the series

More for this.

The Modern Coding letter
Applied AI dispatches read by 5,000+ engineers
No spam. Unsubscribe in one click.
Zachary Proser
About the author

Zachary Proser

Applied AI at WorkOS. Formerly Pinecone, Cloudflare, Gruntwork. Full-stack — databases, backends, middleware, frontends — with a long streak of infrastructure-as-code and cloud systems.

Discussion

Giscus