People & HR

How to set compensation bands as DTC Brand Founders

People & HRFor DTC Brand Founders3 apps12 steps~24 min to set up

You're scaling from 3 to 15 people and suddenly realize you've been paying everyone based on vibes, a Google Sheet from two years ago, and whatever number you said in the offer call. Your warehouse lead makes more than your paid social manager because she negotiated harder. Your new customer success hire found out what the ops coordinator earns and now you have a retention problem. You have no idea what a senior Klaviyo strategist should earn in 2026, no HR person to ask, and the last time you looked at comp benchmarks was a LinkedIn post. Meanwhile payroll is your second-largest expense after ad spend and you've never modeled what a 20% salary increase across the team does to your runway.

Build this on Starch → See the apps used

People & HRFor DTC Brand Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A set of defined compensation bands by role and level — warehouse, creative, growth, ops, customer support — grounded in your actual payroll data and market benchmarks, not gut feel

A live budget model that shows what your current team costs versus what it would cost if everyone moved to band midpoints, stress-tested against your Plaid and Stripe actuals

A simple internal reference doc your team leads can use when making offers, so you stop re-inventing comp from scratch every time you post a job

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

Budgeting Scenario Analysis Knowledge Management

Data sources & config

Starch syncs your Plaid transaction data on a schedule to pull 12 months of payroll and contractor spend. Starch syncs your Stripe data on a schedule to establish your current revenue baseline for runway modeling. Starch connects to Gusto or Rippling from its integration catalog — the agent queries live headcount, salary, and pay rate data when your budgeting and scenario apps run. Your Notion pages connect through Starch's scheduled sync so the Knowledge Management app can surface your existing role docs and comp history.

Prompts to copy

Pull my Plaid transactions for payroll and contractor payments over the last 12 months, break them down by role category (warehouse, growth, creative, ops, customer support), and show me total annual cost per category with headcount

Build me three scenarios: current comp structure, everyone moved to band midpoints, and a 15% merit increase for top performers only. Show runway impact for each using my current Stripe revenue run rate and Plaid burn

Create a compensation bands reference page in my Knowledge Management wiki. Include role levels (L1-L4) for warehouse associates, paid social managers, email/CRM specialists, ops coordinators, and customer support leads. Include band floors, midpoints, and ceilings. Add a section on how to use the bands when making an offer.

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

Walkthrough

Step-by-step

1 Connect Plaid so Starch syncs your business bank account on a schedule — this gives you 12 months of categorized payroll and contractor payment history without touching your accounting software first.

2 Connect Gusto or Rippling from Starch's integration catalog so the agent can query live employee records, current salaries, and job titles when it runs your compensation analysis.

3 Open the Budgeting app and prompt Starch to pull all payroll transactions from Plaid, group them by role category (warehouse, growth/paid media, email/CRM, ops, customer support), and show you total annual spend per category with headcount count.

4 Identify your outliers — who's above market, who's below, and where your bands are invisible because you've never defined them. Starch surfaces this from your actual payroll data, not a spreadsheet you have to maintain.

5 Pull comp benchmark data for each role using browser automation — Starch can scrape Glassdoor, Levels.fyi for marketing/growth roles, and any industry-specific salary survey pages you normally Google manually, no API needed.

6 Define band floors, midpoints, and ceilings for each role level. Tell Starch: 'Based on the benchmark data you pulled and my current payroll actuals, suggest comp bands for L1-L4 across my five role categories. Flag anyone currently outside the suggested band.'

7 Open Scenario Analysis — with Plaid and Stripe synced, your actual revenue and burn are already the baseline. Model three scenarios: freeze at current comp, move everyone to band midpoints over 12 months, or apply targeted increases only to the roles where you're most likely to see attrition.

8 For each scenario, Starch shows you runway impact. If moving the warehouse team to band midpoints adds $8,400/month in payroll, you can see exactly how many months that shaves off your runway at current revenue — and what revenue growth rate makes it break even.

9 Identify the two or three roles where band gaps are widest and retention risk is highest. These are where you act first, not across the board.

10 Open Knowledge Management and prompt Starch to build a compensation bands reference page — include the role levels, band ranges, and a plain-English guide for how team leads should use the bands when extending offers or handling counter-offers.

11 Set a quarterly calendar reminder (Starch automates this through your Google Calendar connection) to revisit bands against updated Plaid payroll actuals and refresh the benchmark pull so the doc doesn't go stale.

12 Export the scenario outputs as a slide summary using Presentation Agent — coming soon in beta — so you have something concrete to walk your board through when comp strategy comes up in the quarterly update.

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 Comp Band Audit — 14-person DTC team, $4.2M ARR

Sample numbers from a real run

Warehouse associates (3 FTE)	138,000
Paid social manager (1 FTE)	72,000
Email/CRM specialist (1 FTE)	58,000
Operations coordinator (1 FTE)	61,000
Customer support (2 FTE + 1 contractor)	94,000
Creative/UGC manager (1 FTE)	68,000
Founders + leadership (3)	310,000
Total annual payroll	801,000

Starch pulled 12 months of payroll transactions from Plaid and cross-referenced them against live Gusto records to produce a role-level breakdown. The analysis flagged one immediate problem: the ops coordinator at $61,000 was $9,000 above the suggested midpoint for her level, while the email/CRM specialist at $58,000 was $7,000 below market midpoint for someone managing a 40,000-subscriber Klaviyo list that drives 28% of revenue. That's the retention risk — the person running your highest-ROI channel is the most underpaid on the team. Starch's browser automation pulled current Glassdoor ranges for email marketing managers at companies with $1-10M revenue and confirmed the gap. The Scenario Analysis showed that moving the email specialist to $67,000 and holding the ops coordinator flat until her next review adds $9,000 annually ($750/month) — at current $350K MRR and 18-month runway, this is a rounding error. Doing nothing and replacing the email specialist costs an estimated $25,000-$40,000 in recruiting and ramp time, plus 90 days of degraded Klaviyo performance during transition. The Knowledge Management page now gives the paid social manager — who is actively hiring a junior support role — a clear framework: L1 paid social support tops out at $52,000, L2 (owns at least one channel independently) floors at $58,000. No more offer calls where you're making up a number while the candidate is on the phone.

Measurement

How you'll know it's working

Payroll as % of revenue (target: under 20% for most DTC brands at Series A stage)

Comp band coverage: % of employees whose current salary falls within defined band range

Runway impact per $10K annual payroll increase (modeled monthly against Stripe MRR)

Attrition risk score by role: who's most underpaid relative to band midpoint

Offer acceptance rate by role — a leading indicator that your bands are competitive

Comparison

What this replaces

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

Spreadsheet (Google Sheets) + Glassdoor manual research

Free and flexible but the benchmark research takes 4-6 hours per round, the sheet goes stale within a quarter, and there's no connection to your actual payroll data so the model is always an approximation.

Rippling or Gusto built-in comp tools

Helpful if you're already in those systems, but they don't connect to your Plaid burn data or Stripe revenue, so you can't model runway impact of comp changes without exporting to yet another spreadsheet.

Radford / Mercer / Levels.fyi comp surveys

Good benchmark data for tech roles but expensive ($2K-$10K+/year), not calibrated for DTC warehouse or creative roles, and still requires manual integration with your actual headcount and budget.

Carta Total Comp

Strong for equity-heavy tech companies; less relevant when most of your team is hourly warehouse workers and performance-bonus-driven growth marketers with no equity conversation.

On Starch RECOMMENDED

One platform — quarterly budgeting, scenario planning, 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 payroll goes through Gusto but my bank account transactions are messy — will Starch actually be able to categorize who's an employee versus a contractor?

Yes. Starch pulls from two sources simultaneously: your Plaid bank data (which shows the raw payroll debits) and your live Gusto records (queried from Starch's integration catalog), which have the structured employee and contractor data. The agent reconciles them. If a contractor's payments are labeled inconsistently across months, you can tell Starch how to handle edge cases in plain English — 'treat any Venmo payment to [name] as contractor cost, category: creative.'

I don't have an HR person. Is this too complicated to set up without one?

That's exactly who this is built for. You describe what you want — 'show me what everyone on my team earns by role, flag who's above or below market, and model what it costs to fix the gaps' — and Starch builds it. You don't configure anything manually. The Knowledge Management page your team leads will actually reference also gets built from a prompt, not a template you have to fill out.

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

Starch is not currently SOC 2 Type II certified — worth knowing before you connect Gusto or Plaid. There's no on-prem or self-hosted option. If SOC 2 is a hard requirement for your team, that's an honest constraint today. Most DTC founders at the 5-20 person stage aren't blocked by this, but you should make that call with your own risk tolerance.

Can Starch pull compensation benchmarks automatically, or do I have to enter market data manually?

Starch can pull benchmark data from publicly available pages — Glassdoor, LinkedIn Salary, Indeed, and role-specific salary survey sites — through browser automation, no API needed. You'd prompt something like: 'Pull current market salary ranges for email marketing managers and paid social managers at DTC e-commerce companies with $1-15M revenue, using Glassdoor and LinkedIn Salary.' Starch navigates those pages and returns the ranges. You review them and decide which benchmarks you trust before they flow into your band model.

What if my roles don't map cleanly to standard job titles — like my 'growth person' does paid social, email, and influencer sourcing?

Tell Starch that. 'My growth manager covers paid social on Meta, owns our Klaviyo flows, and manages our influencer relationships. Pull benchmarks for each of those functions separately and suggest a blended band that reflects all three.' The agent works with how your team actually operates, not how an org chart says it should. You can define your own L1-L4 levels with whatever criteria matter for your business.

Will the compensation bands page in Knowledge Management stay up to date, or will it get stale like every other internal doc?

Starch's Knowledge Management app detects when documentation goes stale — you can set a review cadence (e.g., quarterly) and it will flag the comp bands page for review when the time comes. It won't automatically update the numbers without you, because comp decisions need a human sign-off. But it will remind you to revisit and make it easy to re-run the benchmark pull and payroll analysis when you do.