Internal Comms & Meetings

How to prepare an all-hands deck as Independent Clinic Owner-Operators

Internal Comms & MeetingsFor Independent Clinic Owner-Operators3 apps11 steps~22 min to set up

Once a quarter — or before a big team meeting — you sit down to pull together an all-hands update and realize you have to stitch it from four different places: your scheduling software to count visits and no-shows, your billing system for collections and denial rates, your inbox for the referral numbers you emailed yourself last month, and your own memory for everything else. You don't have a practice administrator to compile this. You don't have slides from last time that are even close to current. You spend two to three hours on a Sunday assembling a deck that's half-finished by Monday morning, then you talk over it apologetically because the numbers are a week stale.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Independent Clinic Owner-Operators3 apps11 steps~22 min to set up

Outcome

What you'll set up

A repeatable all-hands deck that pulls your real clinic numbers — visits, collections, no-show rate, open capacity — before every meeting, so you're not building from scratch each time.

A slide-ready narrative that covers the last period's wins, open issues, and what the team needs to know, drafted from your own notes and data without a designer or admin.

A searchable archive of every all-hands — decisions made, action items assigned, follow-ups owed — so 'didn't we talk about this?' gets answered in ten seconds.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Presentation Agent Meeting Notes Knowledge Management

Data sources & config

Starch connects to Google Calendar (scheduled sync) to pull provider schedules and open capacity; connects to Gmail (scheduled sync) to surface referral threads and outstanding billing follow-up emails; queries your practice management or billing tool through Starch's integration catalog if available, or automates the web-facing reporting page through browser automation — no API required. Notion connects via scheduled sync to store and retrieve past all-hands archives.

Prompts to copy

Build me a 12-slide all-hands deck for my three-provider clinic covering April 2026. Include: total visits (342), collections rate (87%), no-show rate (9%), denied claims pending follow-up (14 claims, $18,400 outstanding), one open provider capacity slot on Tuesdays, two referral sources we want to thank publicly, and a team recognition slide for our front desk coordinator. Tone should be direct and honest — we had a tough billing month and I want the team to understand why without sugarcoating it.

Transcribe today's all-hands meeting, summarize the key decisions, and extract action items with the person responsible and a due date. Archive it under 'All-Hands / April 2026' in our clinic knowledge base.

Create a knowledge base entry summarizing our April 2026 all-hands: attendance, decisions made, open action items, and any protocol changes the clinical team needs to follow going forward.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 One week before your all-hands, open Starch and tell it: 'Pull together a summary of last month's clinic operations — total visits, no-show count, collections rate, and any denied claims sitting more than 30 days — so I can prep an all-hands deck.' Starch queries your connected sources and drafts the summary.

2 Review the summary and add anything it couldn't pull automatically — context from a hard week, a staff situation, a referral relationship you want to highlight. You type this in plain language; Starch incorporates it.

3 Open the Presentation Agent app and describe the deck: number of slides, sections you want (operations, finance, team, priorities), and the tone. Starch builds the full slide deck from your summary and context.

4 Review each slide and iterate on anything that needs adjusting — swap a chart type, reword a talking point, add a recognition slide for a staff member. You describe the change; Starch makes it.

5 Export to PDF or a shareable link and send to your team 24 hours ahead so they can read the operations numbers before the meeting.

6 Run the all-hands. Starch's Meeting Notes app transcribes the session in real time — you talk, it captures. No one has to take notes.

7 After the meeting ends, Meeting Notes generates a summary with key decisions and action items. Review it for accuracy and confirm who owns each item.

8 Tell Starch: 'Add this all-hands summary to our clinic knowledge base under All-Hands / [Month Year], including decisions made and open action items.' It archives automatically into Notion via scheduled sync.

9 Any follow-up items that surfaced — a billing question you said you'd investigate, a protocol change you want to formalize — get captured as tasks. Starch can draft a brief protocol doc and file it in the knowledge base.

10 Before the next all-hands, tell Starch: 'Pull the action items from last month's all-hands and tell me which ones are still open.' It searches the archive and surfaces what's unresolved so nothing falls through.

11 Repeat the prep cycle with the prior deck as a template — same structure, updated numbers, new context. Over time your all-hands becomes consistent and takes forty-five minutes instead of a Sunday afternoon.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 All-Hands — Three-Provider Family Practice

Sample numbers from a real run

Total visits (April)	342
No-show rate	9
Collections rate (%)	87
Denied claims pending follow-up (count)	14
Outstanding denied-claim value ($)	18,400
Open provider capacity slots (Tuesdays)	1
New referral sources (month)	3

Going into the April all-hands, the clinic owner pulled last month's numbers and found a rougher-than-expected billing picture: 14 denied claims totaling $18,400 still sitting in queue, and a collections rate that had dipped to 87% from the usual 91%. She typed into Starch: 'Draft a 12-slide all-hands deck. April visits were 342, no-show rate was 9% which is better than March's 13%, collections rate dropped to 87% because of three payer-specific coding issues we're fixing, and we have $18,400 in denied claims being worked by billing. I want a slide that explains the collections drop honestly without alarming the team, a slide on the no-show improvement and what we did differently with reminder cadence, a recognition slide for our front desk coordinator who handled the insurance calls, and a priorities slide for May covering the denial follow-up and filling Tuesday open capacity.' The Presentation Agent built the deck in about four minutes. She adjusted two slides — changed the collections chart to show the three-month trend rather than just April, and softened one line that read as more alarming than she intended. The deck went out Friday. Monday's meeting ran 35 minutes. Meeting Notes captured the session; when the billing coordinator asked a follow-up question about the coding fix the owner had mentioned, the transcript surfaced the exact moment. Action items — owner to call the payer by April 18, billing to resubmit the 14 claims by April 21 — went into the knowledge base. Two weeks later, Starch surfaced both items as still open, which they were.

Measurement

How you'll know it's working

No-show rate (target: under 10% per month)

Collections rate (target: 90%+ after write-offs)

Denied claims outstanding — count and dollar value older than 30 days

Provider capacity utilization — open slots vs. filled by day of week

Referral volume by source (tracking which relationships are sending patients)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Slides built manually each quarter

Full control over every pixel, but you're rebuilding from scratch every time and the numbers are only as current as what you remember to copy in.

Canva or Beautiful.ai for presentation design

Better templates than blank Slides, but still requires you to populate every number manually — no connection to your calendar, inbox, or billing data.

Practice management software built-in reports (Jane, SimplePractice, Kareo)

Good at generating the raw data — visits, no-shows, revenue — but outputs a report, not a deck, and has no narrative layer or action-item tracking.

Hiring a part-time practice administrator to prep the deck

A real person who knows your clinic is genuinely valuable, but $25–40/hr for deck prep that takes 3–4 hours each quarter is expensive for a task that's mostly data assembly and formatting.

Notion or Confluence as a meeting archive

Starch connects directly to Notion via scheduled sync, so this isn't an either/or — Notion can be your archive and Starch populates it automatically after each all-hands.

On Starch RECOMMENDED

One platform — presentation agent, meeting notes, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

My clinic runs on Jane (or SimplePractice or Kareo) — can Starch pull data from it directly?

Depends on the EHR. Starch connects to 3,000+ apps through its integration catalog, so if your EHR has an API, there's a good chance Starch can query it live when building your deck. If it doesn't have a formal API connector, Starch can automate the web-facing reporting pages through your browser — no API needed. Either way, you describe what data you need and Starch figures out how to get it.

I don't have a designer. Will the slides actually look presentable?

Presentation Agent is currently in development — request beta access to get notified when it launches. In the meantime, Starch can still draft the narrative content, pull the data, and structure your talking points so that when you drop it into a Google Slides template, you're filling in, not building.

What if the numbers I need are split across my EHR and my billing software?

That's exactly the situation Starch is built for. You can connect multiple sources — calendar, inbox, your billing tool from the integration catalog, or the web-facing side of your EHR via browser automation — and tell Starch in plain language what to pull from each. You describe the deck you want; Starch pulls from wherever the data lives.

Is this HIPAA-compliant? I'm nervous about putting patient data into an AI tool.

Starch is not SOC 2 Type II certified today, and we're not going to pretend otherwise. For an all-hands deck, you're typically working with aggregate numbers — visit counts, rates, revenue totals — not individual patient records. Most operators keep it at that level for an all-hands anyway, which avoids the PHI question entirely. If your workflow needs to touch individual patient data, that's a conversation worth having before you connect anything.

Can I use this to track whether the action items from the meeting actually got done?

Yes. Meeting Notes extracts action items and assigns them to the right people. Those get archived in your clinic knowledge base via Notion. Before the next all-hands, you tell Starch: 'Pull the open action items from last month's all-hands' and it surfaces what's unresolved. It's not a full project management system, but for a three-provider clinic running a monthly all-hands, it's enough to stop things falling through the cracks.

How long does this actually take once it's set up?

Once your data sources are connected and you've done one cycle, the prep for a monthly all-hands should run 45–60 minutes: 10 minutes reviewing the auto-pulled numbers and adding context, 15–20 minutes iterating on the deck, a few minutes exporting and sending. The first time takes longer because you're setting up connections and figuring out what you want the deck to cover — plan 2–3 hours for the initial setup.