People & HR

How to set compensation bands as Independent Clinic Owner-Operators

People & HRFor Independent Clinic Owner-Operators2 apps12 steps~24 min to set up

You set compensation for your front desk coordinator, your medical assistant, and your billing specialist based on what felt right when you hired them, a Glassdoor search from two years ago, and what you could afford that month. Now one of them mentions a friend at another clinic making $4 more an hour, and you realize you have no documented framework to point to. You're not running a 30-provider group with an HR department — there's no compensation philosophy, no band structure, no annual review cadence. It lives in your head and your QuickBooks, and every raise conversation is a fresh negotiation you're not prepared for.

Build this on Starch → See the apps used

People & HRFor Independent Clinic Owner-Operators2 apps12 steps~24 min to set up

Outcome

What you'll set up

A documented compensation band structure for each clinical and admin role in your practice, anchored to your actual payroll data from Paylocity or ADP

A living Knowledge Management wiki that records your compensation philosophy, band ranges, and review schedule so it's findable and not just in your head

A repeatable annual review process you can hand off partially to a lead staff member — so raise conversations have a framework, not just vibes

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

Knowledge Management Budgeting

Data sources & config

Starch syncs your payroll data on a schedule from Paylocity or ADP (scheduled-sync providers), giving the agent access to current salaries, pay grades, and headcount by role. For market benchmarking, Starch automates your browser to pull publicly available salary survey data from sites like the MGMA or BLS Occupational Employment tables — no API needed. The Budgeting app connects to your accounting data via QuickBooks (scheduled-sync), so the payroll cost scenarios run against your real numbers.

Prompts to copy

Build me a compensation bands wiki for a three-provider outpatient clinic. Roles include: front desk coordinator, medical assistant, billing specialist, practice manager, and per-diem licensed clinician. For each role, include a band range with floor, midpoint, and ceiling, a short description of what moves someone through the band, and a note on our review cadence (annual, with a mid-year check-in). Pull in our Paylocity data to show where each current employee sits relative to their band.

Create a quarterly budget view that breaks out our total payroll by role category — clinical, admin, billing — and shows what a 4% across-the-board raise in Q3 would cost versus a merit-only approach where only employees below midpoint get an increase. Use our actual payroll data from ADP and compare to last quarter's spend.

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

Walkthrough

Step-by-step

1 Connect Paylocity or ADP to Starch. Starch syncs your employee list, current pay rates, job titles, and pay history on a schedule — this becomes the ground truth for your band-setting exercise, so you're not pulling numbers manually.

2 Connect QuickBooks to Starch. Starch syncs your actual payroll expense by category, so the Budgeting app can show you what each band decision costs in real dollars against your quarterly labor budget.

3 Open the Knowledge Management app and describe your practice's role structure: front desk, medical assistant, billing specialist, practice manager, and any licensed clinician roles. Tell Starch to build a compensation wiki with a page per role.

4 For each role page, prompt Starch to define a floor, midpoint, and ceiling band range. Pull in the current salary from your Paylocity sync and show where each employee sits — at band floor, midpoint, or ceiling.

5 Use browser automation to pull market benchmarks from publicly available sources (MGMA salary data, BLS Occupational Employment Statistics, or your state's labor department wage reports). Starch automates your browser to retrieve these figures — no API needed.

6 Add a compensation philosophy section to your wiki: one paragraph on how your practice thinks about pay relative to market (e.g., targeting 50th percentile for admin roles, 60th for clinical), and what triggers a band adjustment versus a one-time bonus.

7 Document your review cadence in the wiki: annual review in January, mid-year check-in in July, and the criteria that move someone from floor to midpoint (tenure, patient satisfaction scores, billing accuracy rate).

8 Open the Budgeting app and run a scenario: what does your total payroll look like if everyone below midpoint gets a raise to midpoint by Q3? Starch pulls from your QuickBooks payroll data and your ADP headcount to calculate the delta.

9 Create a second scenario in the Budgeting app: merit-only raises capped at 5% for employees currently rated above midpoint. Compare both scenarios side-by-side to see which fits your Q3 budget without cutting into your collections cushion.

10 Set up a Starch automation: every November, Starch pulls the latest payroll data from Paylocity, compares each employee's current salary to their band midpoint, and drops a summary into your Knowledge Management wiki flagging anyone who has drifted outside their band — so your January review conversations start with data, not guesswork.

11 Publish the compensation bands wiki to your team leads (practice manager, if you have one). The AI search in Knowledge Management means they can answer 'what's the pay range for a new MA hire?' without calling you.

12 Set a calendar reminder in Google Calendar — Starch connects directly to Google Calendar — to revisit band ranges each January and update the wiki, so the document doesn't go stale the way a spreadsheet would.

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

January 2026 Compensation Review — Lakeview Family Practice

Sample numbers from a real run

Front Desk Coordinator (2 FTE)	82,000
Medical Assistant (1 FTE)	44,000
Billing Specialist (1 FTE)	52,000
Practice Manager (0.5 FTE, part-time)	38,000
Total current annual payroll (non-clinician)	216,000
Cost to bring all staff to band midpoint	9,400
Cost of 4% across-the-board raise	8,640

Lakeview Family Practice is a three-provider clinic in a mid-size Midwestern city. Going into January 2026, the owner-operator pulled Paylocity data into Starch and found that both front desk coordinators were sitting at their band floor — hired two years ago at $19/hour against a band of $19–$24. The billing specialist was above midpoint at $25/hour against a $22–$27 band, which tracked with her tenure and low denial rate. The practice manager was part-time and below midpoint. Starch's browser automation pulled the latest MGMA Allied Health Salary Survey figures and confirmed the front desk band floor was now under market for the metro area by roughly $1.50/hour. The Budgeting app showed that bringing both coordinators to midpoint ($21.50) would cost $5,200 annually — less than the across-the-board 4% raise that had been the default plan, and more defensible because it targeted actual compression rather than spreading money evenly. The Knowledge Management wiki now holds the band structure, the rationale, and the January 2026 review notes — so next January, whoever runs the review (the owner or the practice manager) starts with context, not a blank page.

Measurement

How you'll know it's working

Total non-clinician payroll as a percentage of monthly collections (target: under 28% for most outpatient primary care)

Number of staff paid below band floor or above band ceiling (target: zero)

Voluntary turnover rate by role — front desk and billing specialist churn is expensive and disruptive

Time to fill open clinical and admin roles, as a proxy for whether your compensation is competitive enough to attract applicants

Payroll cost variance versus quarterly budget — tracked in the Budgeting app against your QuickBooks actuals

Comparison

What this replaces

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

Spreadsheet (Google Sheets or Excel)

Works fine for the initial build, but the file goes stale immediately, nobody can find it except you, and there's no connection to your actual payroll data — so every review starts with manual data entry.

Gusto or Rippling compensation tools

If you're already on Gusto or Rippling for payroll, their built-in comp tools cover basic band tracking — but they don't connect to your accounting data or give you a wiki your team can search, and they assume you want to stay inside their ecosystem.

Bamboo HR compensation module

Designed for companies with dedicated HR staff; the setup overhead and per-seat cost don't make sense for a three-to-five person admin team at an independent clinic.

A fractional HR consultant

A good fractional HR person will build you a real comp framework, but at $150–$250/hour for a project engagement, you're paying for output you then own statically — it doesn't update when your payroll does.

On Starch RECOMMENDED

One platform — knowledge management, 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

Does Starch connect to my EHR for this workflow?

Not directly for compensation data — your EHR handles clinical documentation and billing, not payroll. The compensation workflow pulls from Paylocity or ADP (both scheduled-sync providers), and from QuickBooks for your actual labor expense. If your clinic runs payroll through a system that isn't on that list, Starch can automate your browser to pull reports from that system's web portal — no API required.

I don't have Paylocity or ADP — we use Gusto. Can Starch still do this?

Yes. Gusto is reachable from Starch's integration catalog of 3,000+ apps; the agent queries it live when your app runs. You won't get the scheduled-sync depth that Paylocity and ADP have, but the agent can pull current employee pay data on demand for your review workflow.

Is Starch SOC 2 certified? I'm cautious about connecting payroll data.

Starch is not yet SOC 2 Type II certified — that's worth knowing before you connect payroll data. It's on the roadmap. In the meantime, the scheduled-sync connection to Paylocity and ADP uses standard OAuth and pulls read-only payroll data; you're not writing back to those systems.

How do I benchmark pay rates against the local market? I can't afford an MGMA membership.

Starch can automate your browser to pull publicly available salary data from the Bureau of Labor Statistics Occupational Employment and Wage Statistics tables, which are free and updated annually by metro area. It can also pull from any public job board or salary aggregator you can access in a browser. You describe what you want scraped and Starch handles the navigation — no API, no subscription needed.

Will this replace having an HR person?

It replaces the parts that are really just data organization and document maintenance — keeping the bands current, connecting them to actual payroll, and making them findable. It doesn't replace judgment on tricky situations: a staff member going through a hard personal stretch, a compensation dispute with a clinician, or the conversation itself. Those still require a person.

What if my compensation bands need to stay confidential from staff?

The Knowledge Management wiki can hold whatever you choose to share. You control what's published to team leads versus what stays in a private section only you access. The payroll data from Paylocity or ADP stays in Starch's connected data layer — individual salaries aren't surfaced to anyone without explicit prompting.