Skip to content

Every meeting, recapped before you close the tab.

Patricia reads the transcript, writes up the decisions and next steps, posts the recap in your internal client channel, and files the notes as tasks in Asana. When a competitor comes up, she runs the research and pushes that to Asana too, before you have to ask.

What lands in #northwind-internal minutes after the call, without anyone taking notes:

#northwind-internalThreadProduct preview
PatriciaAppJust now

๐Ÿ“ Recap ยท Northwind weekly (30 min)

Decisions: September paid-social budget approved, launch moved to the 22nd.

Next steps, filed as tasks in the Northwind project in Asana:

  • Owen โ†’ refresh the paid-social ad set for the new date
  • Iris โ†’ send the revised timeline to the client
Pulled fromFirefliesAsana
PatriciaAppJust now

One more thing: Northwind flagged two competitors on the call. Want me to run a competitor ad research pass and push it to their Asana project?

Ricardo GhekiereJust now

@Pati yes, run the competitor research.

PatriciaAppJust now

On it. I'll pull those competitors' latest ads, summarise what changed, and add it to the Northwind project in Asana by Thursday.

Pulled fromAsana

How teams do this today.

Every client call ends with good intentions. Turning them into a written recap that people actually act on is where it falls apart.

The note-taker who missed half of it

Someone half-listens so they can type, still misses a decision, and spends the evening turning shorthand into something the client can read.

The transcription bot's wall of text

A meeting bot drops a full transcript and a generic summary in a folder nobody opens. No decisions pulled out, no next steps, and it charges per seat to do only that.

The next steps that evaporate

Three things were agreed on the call. None became a task, nobody owned them, and next week everyone reconstructs what was supposed to happen.

What it looks like when she owns it.

Client meeting recaps task in Patricia: an automated task that runs after each meeting, turns the transcript into a recap of decisions and next steps, posts it to the internal client channel and files the notes as tasks in Asana, with its recent runs listed
Set it up once: after each call she writes the recap of decisions and next steps, posts it to your internal channel, and files the notes as tasks in Asana. Every run is logged.
Integrations in Patricia with Fireflies, Asana and Slack connected and Google Drive available to connect, so she can read the transcript, file the notes as tasks, and post the recap
Connect where the meeting lives and where the work goes. She reads the transcript from Fireflies, files the recap and next steps in Asana, and posts to your Slack channel.
The Northwind project in Asana with the next steps from the call, each a task assigned to an owner with a due date, including the competitor ad research Patricia offered to start
Every next step from the call becomes a task in Asana, assigned to an owner with a due date, including the competitor research she offered to start.

Setup

Running in minutes, then it's hers.

Step 1

Add Patricia to Slack

She joins your workspace like any teammate. Two minutes, no engineering.

Step 2

Connect your meetings and Asana

Link Fireflies so she can read the transcript and Asana so she can file the tasks. One click each, no new tool to roll out.

Step 3

Tell her where recaps go

Pick the internal channel for each client and the format you want: decisions, next steps. She learns your voice from the first few.

Step 4

She takes it from there

After every call the recap lands in the channel, the next steps are filed as tasks in Asana, and she offers to start whatever came up next.

What she takes off your plate.

Real behavior of the skill, not a feature list.

Reads the meeting, not just the words

She pulls the transcript from Fireflies and writes what actually happened: decisions made, questions still open, and what was promised to the client.

Decisions and next steps, in your voice

The recap is the useful part, not a transcript: what was decided and what happens next, written in your team's voice rather than generic bot summary language.

Files the next steps as tasks in Asana

Every follow-up becomes an Asana task assigned to a real owner, with the context from the call attached, so people pick up work that already makes sense.

Runs the research when it comes up

When a competitor is mentioned on the call, she offers to run a competitor ad research pass and pushes the results straight to the client's Asana project.

Posts where the team already is

The recap lands in the internal client channel in Slack minutes after the call, tagged to the people who need it. No document to go hunting for.

One teammate, not another bot

Recaps are one thing she does, with no per-seat fee. The same teammate handles reporting, creative production, and client updates in the same Slack.

Things to ask her on day one.

@Pati

Recap the Northwind call and post it in the internal channel

@Pati

File the next steps from the call as tasks in the Northwind project

@Pati

Run competitor ad research on Northwind's rivals and push it to Asana

@Pati

Send me a recap of every call I had this week

@Pati

What did we decide on the Northwind call?

One skill down. She has more.

Patricia's value compounds when the whole workflow lives with her, not just one job.

Patricia + Fireflies

Where she reads the meeting from. She pulls the transcript and turns it into a recap of decisions and next steps.

Patricia + Slack

Where the recap lands, minutes after the call, in the internal channel the team already watches.

FAQ

Meeting recaps, answered.

Where does Patricia get the meeting content from?

She reads the transcript from your meeting tool. Connect Fireflies once and she picks up each call automatically, so nobody has to take notes or paste anything in. The recap is written from what was actually said.

What is in a recap?

The decisions made, the next steps, and any open questions, in that order. You decide the format once and she writes every recap that way, in your team's voice rather than a generic summary.

Do the next steps actually become tasks?

Yes, and that is the point. Each follow-up becomes an Asana task assigned to a real owner, with the context from the call attached. The call turns into tracked work in the right project, not a paragraph nobody reads.

What is the competitor research she offers?

When a competitor comes up on the call, she offers to run a competitor ad research pass: pulling their latest ads, summarising what changed, and pushing it to the client's Asana project. She offers first, you say go, and she gets on with it.

Can she do this per client or project?

Yes. Point each client at its own internal Slack channel and Asana project, and she routes every recap and every task to the right place. One meeting, and it reaches exactly the people and the project it should.

What does it cost per user?

Nothing per user. Meeting recaps is one thing Patricia does, so there is no per-seat fee the way standalone meeting bots charge. It runs on your workspace plan like everything else she does.

Is this all Patricia does?

No. Recapping meetings is one job. The same teammate handles client updates, reporting, creative production, and the rest of the work agencies hand her, all in the same Slack.

One of the jobs agencies hand her. See more admin use cases or browse them all.

Everybody deserves a Patricia.

She handles the mess. You keep the clients. See what changes in your first week.

Pick a time that works for you. You get a live walkthrough of Patricia on real agency work, and every question answered.

No credit card.