People & HR

How to plan headcount as Independent Clinic Owner-Operators

People & HRFor Independent Clinic Owner-Operators3 apps11 steps~22 min to set up

You're running a three-provider clinic and headcount planning happens in a Google Sheet someone made two years ago, or a whiteboard conversation before the Monday morning huddle. You don't have an HR director — you are the HR director. Adding a part-time medical assistant means reverse-engineering your Plaid transactions to figure out what you actually spent on labor last quarter, squinting at your QuickBooks payroll entries, and guessing whether the revenue from a fourth provider slot would cover the cost before their 90-day ramp. You're making a $70,000 decision with month-old numbers and a calculator.

Build this on Starch → See the apps used

People & HRFor Independent Clinic Owner-Operators3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live headcount budget that tracks your actual labor spend against plan, updated from your connected bank and payroll data, so you know in real time whether you can afford to post that MA job listing.

A scenario model that shows side-by-side what your runway and break-even look like if you hire now vs. wait 60 days vs. add a part-time contractor instead of a full employee.

A quarterly budget view by cost category — clinical staff, admin staff, benefits, contractor fees — so you can walk into any staffing conversation with actual numbers instead of estimates.

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

Runway Analysis Scenario Analysis Budgeting

Data sources & config

Runway Analysis and Scenario Analysis pull revenue from Stripe (Starch syncs your Stripe data on a schedule) and expense data from Plaid bank feeds (Starch syncs your Plaid transactions on a schedule). Budgeting pulls actuals from the same Plaid connection. If your payroll runs through ADP or Paylocity, Starch connects directly to those on a schedule and can break out labor costs by employee or pay type. QuickBooks entity-level data — invoices, bills, vendor payments, journal entries — also syncs on a schedule for clinics that run their books there.

Prompts to copy

Connect my Plaid bank account and Stripe revenue. Show me my real net burn for the last 6 months, broken out so I can see what's going to labor costs vs. occupancy vs. supplies. Project forward 18 months at my current pace.

Build me two hiring scenarios side by side: Scenario A is I hire a full-time medical assistant at $52,000 starting next month. Scenario B is I bring on a part-time contractor at $28/hr for 20 hours a week. Show me how each one changes my runway and when I'd hit break-even assuming patient volume stays flat.

Set up a quarterly budget with these categories: clinical salaries, front desk and admin, benefits and payroll taxes, contractor and locum costs, and other overhead. Pull my actual spend from Plaid for Q1 2026 and show me where I'm over or under against what I budgeted.

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

Walkthrough

Step-by-step

1 Connect Plaid to Starch so your clinic's operating account transactions sync automatically — this becomes the foundation for every spend number you'll look at.

2 Connect Stripe if you take card payments directly, or connect QuickBooks if your billing person reconciles everything there; Starch syncs those on a schedule and the Runway Analysis app picks them up automatically.

3 Open the Runway Analysis app and let it calculate your real net burn for the last 6 months — not a single-month average, but the trend line that accounts for the slow January and the strong March.

4 Tag or confirm which transaction categories map to labor costs — clinical salaries, admin wages, contractor payments, benefits — so the scenario models know what's headcount-related vs. occupancy or supplies.

5 Open the Scenario Analysis app and describe your hiring question in plain language: 'Show me what happens to my runway if I hire a full-time MA at $52,000 starting June 1 vs. if I wait until September.' Starch builds the model from your actual baseline.

6 Add a third scenario if you're considering a locum or part-time contractor instead of a W-2 hire — describe the hours and rate and let the model run the math on total cost including your employer tax load.

7 Open the Budgeting app and set your quarterly targets by labor category: clinical staff, admin, benefits, contractors. The app auto-suggests allocations from your historical Plaid spend so you're not guessing.

8 Review the pace indicators each week — the Budgeting app shows you whether each category is under, on track, or over, with the variance in dollars so you can see if you're trending toward blowing past your admin labor line before the quarter closes.

9 If your payroll runs through ADP or Paylocity, connect it to Starch so you can see pay-period-level detail — not just the lump ACH debit on the bank statement — and confirm your loaded cost per employee is what you thought it was.

10 When you're ready to make a hire, use the Scenario Analysis output as the actual document you review with your accountant or business partner — it's a real projection built from your real numbers, not a template someone filled in with guesses.

11 Set a recurring reminder (or describe an automation to Starch) to pull a fresh runway view the first week of each month, so your headcount assumptions stay anchored to what the business actually did last month, not a plan you made in January.

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

Q2 2026 MA Hiring Decision — Lakewood Family Physio

Sample numbers from a real run

Clinical salaries (3 providers)	38,500
Front desk and admin wages	7,200
Benefits and payroll taxes	9,100
Contractor / locum costs	3,400
Occupancy and overhead	11,800
Stripe revenue (net of refunds)	74,600

Sarah owns a three-provider physical therapy clinic in suburban Ohio. Her Plaid transactions show $70,000/month in operating expenses against $74,600 in net revenue from Stripe — a $4,600 monthly margin that feels thin when she's looking at adding a medical assistant. She connects both to Runway Analysis and sees that her real 6-month average burn is closer to $71,200/month once she accounts for the two slow months at the start of the year. Her projection at current pace shows 14 months of runway. In Scenario Analysis, she describes: 'Hire a full-time MA at $52,000 base, $8,400 in estimated benefits and payroll taxes, starting May 15.' The model shows her monthly expense rising to $76,700, flipping her from a $4,600 monthly surplus to a $2,100 monthly deficit — and compresses her runway to 9 months if revenue stays flat. Scenario B: she posts the role as 24 hours/week at $26/hr, total annual cost roughly $38,000 including taxes. That puts her monthly labor add at $3,200, still leaving a $1,400 monthly buffer. She exports the comparison and sends it to her accountant before posting the job listing. She posts the part-time role the next week.

Measurement

How you'll know it's working

Loaded cost per clinical FTE (salary + benefits + payroll taxes) vs. revenue per provider slot

Labor as a percentage of net collections — clinical staff separate from admin

Monthly runway in weeks, not months (a 3-provider clinic has thin buffers and needs granularity)

No-show and cancellation rate by provider, because open slots are the real driver of whether a new hire pays for itself

Time to fill an open clinical slot — because the cost of an empty chair often exceeds the cost of a faster, pricier hire

Comparison

What this replaces

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

Google Sheets / Excel headcount model

You built it once and it's already stale — the actuals are manually entered, the formulas break when someone edits the wrong cell, and it lives in a Drive folder nobody opens until there's a problem.

QuickBooks workforce or payroll reports

Good for what you paid, not for what a future hire will cost you; no scenario modeling, no runway projection, no way to compare hire-now vs. wait-60-days without building a separate spreadsheet.

Practice management add-ons (e.g., Kareo's business analytics)

Built for clinical and billing metrics; headcount and cash planning aren't native, and the add-ons assume a practice administrator role that most owner-operators don't have.

Hiring a fractional CFO or HR consultant

Absolutely worth it at some scale, but a $2,000/month retainer is hard to justify when the question is whether you can afford a $52,000 MA — Starch gives you the model first so the consultant conversation is faster and cheaper.

On Starch RECOMMENDED

One platform — runway analysis, scenario planning, quarterly budgeting 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 payroll is through Gusto — can Starch pull my actual labor costs?

Gusto is reachable from Starch's integration catalog of 3,000+ apps; the agent queries it live when your app runs. If you want deeper payroll detail with scheduled syncs, ADP and Paylocity connect on a schedule with Starch syncing pay runs, benefits, and employee records automatically. For Gusto specifically, the live query gets you current payroll data when your scenario model needs it.

My clinic doesn't use Stripe — we bill through our EHR and get ACH deposits. Can Runway Analysis still work?

Yes. Plaid picks up your bank account deposits regardless of where they originated — your EHR billing system, clearinghouse payouts, or direct insurance remittances all show up as transactions. The Runway Analysis app uses those real inflows as your revenue line, so you don't need a Stripe account for it to give you an accurate picture.

Can Starch tell me which of my three providers has open capacity next week, so I know if I even need to hire?

If your scheduling runs through Google Calendar or Calendly, Starch connects directly to those on a schedule and can show you open slots by provider. You'd describe what you want — 'show me each provider's booked vs. available hours next week' — and Starch builds that view. For EHR-native scheduling systems like Jane or SimplePractice, Starch can automate through your browser — no API needed — to pull availability data that isn't exposed anywhere else.

Is Starch SOC 2 certified? I'm careful about what I connect to anything clinical.

Starch is not currently SOC 2 Type II certified — that's worth knowing upfront. The workflows here involve financial data (Plaid, Stripe, QuickBooks) and calendar/email data, not PHI or clinical records. You should not connect Starch directly to your EHR's patient data. The headcount planning use case lives entirely in your financial and scheduling layer, which keeps you clear of HIPAA-relevant data in Starch.

The Scenario Analysis app shows my baseline — but my revenue is seasonal. Can I model that?

Yes. When you describe the scenario to Starch, you can specify the seasonality assumption — 'assume revenue drops 15% in January and February based on my historical pattern' — and the model incorporates it. Because the baseline is built from your real Plaid and Stripe history, the seasonal dip is already reflected in the trend data Starch uses as the starting point.

What if I want to see headcount costs broken out by clinical vs. admin staff separately, not as one labor line?

In the Budgeting app, you set up the categories yourself when you describe what you want: 'Create a quarterly budget with separate lines for clinical salaries, front desk wages, contractor costs, and benefits.' Starch maps your Plaid transactions and payroll data to those categories and tracks each one independently. You can be as granular as you need — some clinic owners track provider 1, provider 2, and provider 3 as separate lines during a growth period.