Strategy & Planning

How to run a pricing analysis as Small Finance Teams

Strategy & PlanningFor Small Finance Teams2 apps12 steps~24 min to set up

You're a three-person finance team supporting 200 people, and pricing analysis doesn't get a dedicated meeting — it gets a Tuesday afternoon when the CEO asks 'should we raise prices on the enterprise tier?' and expects a real answer by Thursday. That means you're manually pulling gross margin by product line out of NetSuite or QuickBooks, cross-referencing Stripe invoices to see what customers actually paid versus list price, and building a discount-rate table in Google Sheets from exported CSVs. By the time you've cleaned the data, close week has collided with the request and you're sending a half-finished deck with a caveat that the numbers are 'as of last month.'

Build this on Starch → See the apps used

Strategy & PlanningFor Small Finance Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live pricing analysis surface that pulls your actual Stripe revenue, QuickBooks cost data, and Plaid cash transactions into one place — so gross margin by product line or customer segment is never a manual export again.

A scenario comparison showing what happens to runway and break-even if you raise prices 10%, 15%, or 20% — built on your real burn and revenue baseline, not spreadsheet assumptions.

A repeatable workflow that turns a CEO pricing question into a defensible, numbers-backed answer in hours, not two days.

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

Scenario Analysis Transaction Insights

Data sources & config

Starch syncs your Stripe data on a schedule (charges, customers, invoices, subscriptions) and your Plaid transactions on a schedule (categorized spend, balances). QuickBooks entity-level data — invoices, bills, vendors, payments, journal entries — also syncs on a schedule. The Scenario Analysis starter app wires Stripe and Plaid as the baseline; you extend it with QuickBooks cost data to get to fully-loaded margins. No CSV exports, no manual refresh.

Prompts to copy

Connect my Stripe and Plaid data and build me a pricing analysis app that shows gross margin by product line, average discount rate by customer segment, and what our net revenue retention looks like at current prices versus a 12% price increase.

Build a scenario comparison: baseline is current Stripe ARR and Plaid burn. Scenario A raises enterprise plan prices by 10%, Scenario B by 15%, Scenario C by 20%. Show runway, monthly burn, and break-even date for each — and flag if churn assumptions change the outcome materially.

Show me every Stripe transaction in the last 90 days grouped by plan type, and flag any invoice where the amount charged was more than 5% below list price.

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

Walkthrough

Step-by-step

1 Connect Stripe, Plaid, and QuickBooks in Starch — all three sync on a schedule, so your pricing analysis always starts from current data, not last month's export.

2 Open the Scenario Analysis starter app. It comes pre-wired to Stripe and Plaid for revenue and burn; tell Starch to extend it with QuickBooks invoice and bill data to get cost of goods sold into the margin calc.

3 Tell Starch: 'Show me gross margin by product line for the last 12 months, using Stripe revenue and QuickBooks COGS.' Starch builds the view — no pivot table required.

4 Add a discount-rate layer: 'For each Stripe plan type, show me the average invoiced amount versus the current list price. Flag any customer segment where the average discount exceeds 10%.' This surfaces where you're already giving price away.

5 Pull the Scenario Analysis app up and set your baseline: current Stripe ARR, current Plaid monthly burn, QuickBooks headcount cost from payroll-related bills. This is your 'price unchanged' scenario.

6 Fork Scenario A: raise enterprise plan revenue by 10% (adjust the revenue assumption), hold churn flat. Starch recalculates runway and break-even automatically.

7 Fork Scenario B and C at 15% and 20% price increases. Add a sensitivity note: 'If churn increases by 5 percentage points in response to the price increase, what does that do to runway in each scenario?' Starch shows you the delta.

8 Use the Transaction Insights app to spot any cost trends that affect your margin math: 'Show me month-over-month change in vendor spend for infrastructure and third-party SaaS in the last six months.' A cost spike you missed changes the pricing floor.

9 Pull net revenue retention from Stripe data: 'Calculate NRR for the last four quarters — expansion minus churn minus contraction, divided by starting ARR. Break it out by plan type.' This tells you whether your current pricing is already leaving expansion on the table.

10 Describe a summary view to Starch: 'Build me a one-page pricing analysis dashboard that shows current gross margin by product line, discount rate by segment, NRR by plan, and the three pricing scenarios side by side with runway impact.' This is what you send to the CEO — not a deck rebuild.

11 Set the analysis to refresh automatically when Stripe and Plaid sync. Next time the CEO asks, you open the dashboard instead of pulling CSVs.

12 If you want to model competitor pricing, tell Starch: 'Pull the pricing pages from [competitor A] and [competitor B] and summarize their plan structures and list prices.' Starch automates that through your browser — no API needed.

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

Q1 2026 Enterprise Pricing Review — March close week

Sample numbers from a real run

Stripe ARR (Enterprise tier)	1,840,000
Stripe ARR (Growth tier)	620,000
QuickBooks COGS (infrastructure + CS)	487,000
Implied gross margin (blended)	75
Average enterprise discount rate	14
NRR (trailing 4 quarters)	108

In March 2026, the CEO asked whether Starch should raise enterprise plan prices before the next board meeting. The finance team had 48 hours. Instead of exporting Stripe invoices and rebuilding a margin model from scratch, they pulled up the pricing analysis surface they'd built in Starch two weeks earlier. Stripe showed $1.84M in enterprise ARR and $620K in growth-tier ARR — but the discount-rate view flagged that the average enterprise invoice was coming in 14% below list price, meaning effective ARR was closer to $1.58M. QuickBooks COGS (infrastructure vendors, customer success contractor bills) came to $487K against $2.46M in total revenue, giving a 75% blended gross margin. The Scenario Analysis app showed that a 12% list price increase — even assuming 6% incremental churn — extended runway by 31 days and lifted gross margin to 77.4% at the blended level. The 'no increase' scenario showed break-even at month 19; the 12% increase moved it to month 17. The team sent the CEO a link to the dashboard by end of day Wednesday. The board deck slide took 20 minutes, not two days.

Measurement

How you'll know it's working

Gross margin by product line (actual, not blended)

Effective ARR after discounts (list price vs. invoiced amount by segment)

Net revenue retention by plan type (trailing four quarters)

Runway impact of price change under 3 churn sensitivity scenarios

Month-over-month COGS trend as a percentage of revenue

Comparison

What this replaces

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

Google Sheets + Stripe CSV exports

You can build any model you want, but every pricing question starts with a 45-minute CSV pull and clean, and the model is stale the moment you close it.

NetSuite or QuickBooks built-in reports

Good at ledger-level margin reporting, but can't join to Stripe invoice-level discount data or run multi-scenario runway projections in the same surface.

Mosaic or Runway (financial planning SaaS)

More structured financial modeling with board-ready templates, but significantly more expensive for a three-person team and still requires manual scenario setup rather than describing what you want in plain English.

Excel + manual competitor research

Full flexibility, but competitor pricing benchmarking means someone spending two hours clicking through pricing pages — Starch automates that through the browser with no API required.

On Starch RECOMMENDED

One platform — scenario planning, transaction insights 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 sync our QuickBooks P&L reports directly?

QuickBooks report views — the pre-built P&L, Transaction List, and Vendor Expenses reports — are temporarily unavailable due to an upstream connector issue. Entity-level data syncs normally: invoices, bills, vendors, payments, and journal entries all come through on schedule. For a pricing analysis, that entity-level data is what you actually need to calculate COGS and gross margin — the report views are less useful than building the calculation yourself on top of clean line-item data.

Our Stripe invoices include one-off discounts and custom pricing for enterprise deals. Will Starch capture those accurately?

Yes. Starch syncs Stripe at the invoice and charge level, so it sees the amount actually billed — not just the plan's list price. That's exactly what lets you build the discount-rate analysis: list price is in your plan configuration, invoiced amount is in the Stripe data, and Starch calculates the gap by customer or segment.

We use NetSuite, not QuickBooks. Does the pricing analysis work the same way?

Yes. Starch syncs NetSuite invoices, expenses, journal entries, balance sheets, and income statements on a schedule. The recipe is the same — you're just telling Starch to pull COGS from NetSuite instead of QuickBooks. Both are scheduled-sync connections with the same depth of data.

Can Starch tell us what competitors are charging without us doing manual research?

Yes. If a competitor's pricing page is publicly accessible, Starch can navigate to it through your browser and extract the plan structure and prices — no API needed. Tell Starch which competitors to check, and it returns a structured comparison. It won't have data behind a login wall or inside a private sales process, but for published pricing pages it works well.

Is Starch SOC 2 certified? We're cautious about connecting our Stripe and financial data.

Starch is not SOC 2 Type II certified today. If your company's security policy requires SOC 2 Type II for any tool that touches financial data, that's a real constraint worth checking with your IT or legal team before connecting Stripe or QuickBooks. Starch is transparent about this.

How often does the Stripe and Plaid data refresh? We need current numbers, not week-old data.

Stripe and Plaid data sync on a schedule — typically daily. For a pricing analysis where you're looking at trailing 90-day or 12-month trends, daily refresh is more than sufficient. If you need a real-time snapshot mid-month for a live conversation, you can trigger a manual refresh before opening the dashboard.