# AI Meeting Follow-Up Agent on a jurniti MicroVM

> Draft the follow-up from yesterday. Priya, the 12th, Friday security page. Nothing sends. Fork the Hermes meeting template. Your key.

- Published: 2026-08-18 · Updated: 2026-08-18 · jurniti
- Canonical: https://www.jurniti.com/blog/meeting-prep-follow-up-template

If your mornings die in a weekly dump and your afternoons die rewriting the same follow-up, you do not need another hosted bot with send. You need one screen before the call and one draft after.

**Meeting Prep + Call Follow-Up** is a public jurniti template (`/templates/meeting-prep-follow-up`). You fork it into a paid **hermes** microVM. The skills are already on disk.

If you searched for **AI meeting follow-up agent**, this page maps that intent to a concrete fork.

## What searchers mean by AI meeting follow-up agent

People typing **AI meeting follow-up agent** usually want one of three things: a notetaker SaaS, a course on "better meetings," or a runnable operator they own.

Notetakers dump transcripts. Courses sell modules. jurniti sells a **running agent seat** you can fork, key, and operate — with Firecracker isolation and a human still on send.

## What the fixture follow-up returns

You do not need Calendar for the first pass. Fork it. Open the terminal. Paste:

> draft the follow-up from yesterday

The fixture notes are yesterday's Acme pilot. You should get **To Priya**, a subject, and a body that names **the 12th** and the **Friday security overview**. Ask it to send. It refuses.

## Why prep and follow-up are two skills

Prep is one screen you can read on a phone. Follow-up is To / Subject / body from notes. Mixing them into one blob is how you get a weekly dump. Keep them separate.

## Why it refuses when notes are missing

A follow-up with no notes is fiction. The skill refuses to invent a call. Morning cron is first-run only. It is not in the snapshot.

## How this is not weekly-plan-from-what-you-promised

That template is the week's commitments. This template is **one meeting**. If you want the weekly plan, fork that. Do not mash the jobs.

## First five minutes

1. Fork `/templates/meeting-prep-follow-up`.
2. Set `OPENROUTER_API_KEY` in Hermes (your key, your bill).
3. Paste `draft the follow-up from yesterday`.
4. Connect Calendar when you want live briefs.

No model key is stored in the public snapshot. Capture is scrubbed.

## Who this is for

Founders in back-to-back calls who want the brief and the draft. People who will not let an agent send or write the calendar on day one.

## Who this is not for

Anyone who wants the agent to send or invent a call with no notes. A replacement for the weekly commitments template. A grocery / campsite / wedding personal bot.

## Risk

No free trial. First purchase has a 30-day money-back guarantee. If the draft is wrong, you get the money back. You keep the key.

## Frequently asked questions

### What is Meeting Prep + Call Follow-Up?

A public jurniti template. You fork it into a paid Hermes microVM with meeting-prep and call-follow-up already on disk.

### Who should search for AI meeting follow-up agent?

Founders who want a phone-readable brief before a call and an unsent draft after — not a weekly dump.

### Is there a free trial?

No free trial and no free tier. First purchase includes a 30-day money-back guarantee. Model fees are yours.

### Whose API keys?

Yours (BYOK). Set OPENROUTER_API_KEY inside the microVM. jurniti does not proxy or mark up model tokens in v1.

### Which harness does this use?

hermes. Choose another gallery template if you need a different agent runtime.

### Does it send the follow-up?

No. The skill forbids send. You hit send.

### What if there are no notes?

It refuses to invent a call. That refusal is the product.