Finance & FP&A

How to track gross margin by channel and sku as Small Finance Teams

Finance & FP&AFor Small Finance Teams3 apps12 steps~24 min to set up

You're a three-person finance team and every quarter someone from product or sales walks into close week asking 'what's our gross margin on the enterprise channel versus self-serve?' You don't have a clean answer. Revenue lives in Stripe by product and plan. COGS — hosting, payment processing fees, support headcount — is buried across NetSuite journal entries and Plaid bank transactions. Reconciling the two means a half-day in Google Sheets, pulling exports, manually tagging SKUs, and hoping nothing changed since the last time you did it. By the time you have a number, close is over and the question has evolved.

Build this on Starch → See the apps used

Finance & FP&AFor Small Finance Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live gross margin dashboard broken down by sales channel (self-serve, enterprise, partner) and by SKU or product line, pulling directly from Stripe revenue data and NetSuite or QuickBooks COGS — no manual exports required

An automated alert that flags when any channel's margin drops more than a defined threshold month-over-month, so you catch a pricing anomaly or COGS spike before the board deck is due

A scenario model that lets you test 'what happens to margin if hosting costs rise 15% or we reprice the mid-tier plan' — grounded in your actual revenue and expense mix, not a static spreadsheet assumption

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 Transaction Insights

Data sources & config

Starch syncs your Stripe data on a schedule (charges, invoices, subscriptions with product metadata) and syncs your NetSuite data on a schedule (invoices, expenses, journal entries, income statements). For teams on QuickBooks instead of NetSuite, Starch syncs QuickBooks entities — bills, payments, vendors, journal entries — on a schedule as well. Plaid bank feed data syncs on a schedule to catch any COGS payments that clear outside the ERP. Slack is connected from Starch's integration catalog for alert delivery; the agent queries it live when an alert fires.

Prompts to copy

Build me a gross margin dashboard that pulls Stripe revenue broken out by product (use the product metadata field) and maps it against COGS from NetSuite — show margin percentage by channel (self-serve vs enterprise) and by SKU, updated daily

Add a margin alert: if any channel's gross margin drops more than 5 percentage points month-over-month, send me a Slack message with the delta and the top COGS line item driving the change

Build a scenario model starting from my current Stripe revenue and NetSuite expense baseline — let me adjust hosting cost, payment processing rate, and headcount COGS as separate sliders and show how each scenario affects gross margin by channel

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

Walkthrough

Step-by-step

1 Connect Stripe as a scheduled-sync provider. Starch pulls charges, invoices, and subscription records including product and plan metadata — this becomes your revenue layer, segmentable by SKU and channel.

2 Connect NetSuite (or QuickBooks) as a scheduled-sync provider. Starch syncs expenses, journal entries, bills, and income statement lines on a schedule. Map your COGS accounts — hosting, payment processing, support — during setup so they're tagged correctly from day one.

3 Connect Plaid as a scheduled-sync provider for your operating bank accounts. This catches COGS-adjacent spend that hits the bank before it's posted in the ERP, especially useful during close week.

4 Tell Starch to build the gross margin dashboard: describe the channel segmentation you want (self-serve vs enterprise vs partner, or however your Stripe product metadata is structured), the SKU groupings, and the COGS accounts to subtract.

5 Starch builds the app. Review the margin calculation logic it generates — verify that it's using the right Stripe product fields and the right NetSuite expense account codes for your COGS definition.

6 Customize the channel definitions if your Stripe metadata doesn't map cleanly. Tell Starch in plain language: 'Plans tagged 'growth' or 'starter' are self-serve; plans tagged 'enterprise' or 'custom' are enterprise channel.' It updates the logic.

7 Set the margin alert threshold. Tell Starch: 'If any channel's gross margin drops more than 5 points month-over-month, Slack me in #finance-alerts with the delta and the top expense line driving it.' Starch wires the automation against your Slack workspace from the integration catalog.

8 Fork the Scenario Analysis starter app and connect the same Stripe and Plaid data sources. Set your baseline as the current month's actual revenue and COGS mix.

9 Add the specific COGS levers your CFO asks about most — hosting cost per unit, Stripe processing rate, support headcount loaded cost. Each becomes an adjustable assumption that flows through to channel-level margin.

10 Run the 'hosting costs up 15%' scenario before the next board meeting. Export the scenario comparison table directly from Starch instead of rebuilding it in Sheets.

11 During close week, use the Transaction Insights app on your Plaid feed to flag any anomalous COGS vendor charges — a $40K hosting invoice that's normally $28K will surface automatically before it hits the margin dashboard as an unexplained swing.

12 Share a view-only link to the gross margin dashboard with the CEO and CFO so the 'what's our margin by product line?' question has a self-serve answer that doesn't require you to stop what you're doing during close.

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

March 2026 close — gross margin review

Sample numbers from a real run

Stripe revenue — self-serve plans (Growth + Starter)	312,000
Stripe revenue — enterprise plans (Enterprise + Custom)	487,000
NetSuite COGS — hosting and infrastructure (AWS)	94,000
NetSuite COGS — payment processing fees (Stripe)	21,500
NetSuite COGS — support headcount (loaded)	68,000
Gross profit — self-serve channel	168,000
Gross profit — enterprise channel	337,500

In March, the gross margin dashboard flags that self-serve channel margin dropped from 62% in February to 54% — a 8-point swing. The Slack alert fired on March 18th, mid-close. You open Starch and the margin app shows the top driver: AWS infrastructure costs in NetSuite jumped from $71K to $94K, while self-serve revenue was flat at $312K. The enterprise channel held at 69% margin. Without the dashboard, you'd have caught this in the board deck review on April 4th and spent two days backtracking through journal entries to explain it. Instead you pull the scenario model, run 'hosting costs stay at $94K going forward' versus 'we renegotiate back to $78K,' and have a concrete margin impact to bring to the infrastructure conversation before close is even done. The CFO gets a Notion link to the scenario comparison instead of a Google Sheet with seventeen tabs.

Measurement

How you'll know it's working

Gross margin percentage by channel (self-serve vs enterprise vs partner), tracked monthly and trended over 6 months

Gross margin percentage by SKU or product line, to identify which products are subsidizing others

COGS as a percentage of revenue broken out by category (hosting, payment processing, support headcount) — to see where cost pressure is actually coming from

Month-over-month margin delta by channel — the number that triggers an investigation or a conversation with the CFO

Blended gross margin vs board plan, updated daily through close so you're not surprised by a miss on reporting day

Comparison

What this replaces

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

Google Sheets with manual NetSuite and Stripe exports

You already know this workflow: 2-3 hours per month pulling CSVs, VLOOKUP-ing SKU codes, and hoping someone didn't change a plan name in Stripe. It works until close week, when it becomes the most fragile thing in your process.

NetSuite built-in reporting (P&L by class or segment)

NetSuite can segment a P&L by department or class, but only if COGS is coded correctly on every transaction — and it won't pull Stripe revenue at the product level without a custom integration or saved search that someone has to maintain.

Mosaic, Pigment, or Cube (dedicated FP&A platforms)

These tools are purpose-built for multi-dimensional margin analysis and are genuinely good at it — but they're priced and scoped for larger finance teams, typically require a multi-week implementation, and add another vendor to manage. Starch is composable from the same data sources your team already uses.

Looker or Tableau connected to a data warehouse

Accurate and flexible, but requires a data engineer to build and maintain the pipeline from Stripe and NetSuite into the warehouse. A three-person finance team usually doesn't have that resource in-house, and the BI license cost assumes more users than you have.

On Starch RECOMMENDED

One platform — runway analysis, 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

NetSuite's P&L report sync is mentioned as temporarily limited — does that affect the gross margin dashboard?

QuickBooks P&L report views (Transaction List, Vendor Expenses) are temporarily disabled pending a connector fix. However, entity-level data — bills, invoices, journal entries, vendor records, payments — syncs normally from both QuickBooks and NetSuite. The gross margin dashboard is built off entity-level COGS data, not a pre-aggregated P&L view, so this limitation doesn't block the workflow. You're getting the underlying transactions, not a report summary.

Our COGS definition is non-standard — we include certain S&M headcount in channel margin. Can Starch handle that?

Yes. Describe your margin definition in plain language when you set up the app — 'Include NetSuite expense accounts 5100 through 5180 as COGS for the enterprise channel; exclude account 5200 which is corporate overhead.' Starch builds the calculation logic to match your definition. You can revise it any time by describing the change.

Stripe has product metadata in our case — plan names, not SKU codes. Can Starch map those to our internal product taxonomy?

Yes. Tell Starch how you want the groupings: 'Plans named Growth-Monthly, Growth-Annual, and Starter are self-serve. Plans named Enterprise-*, Custom-*, and anything with an ARR above $50K in the invoice amount are enterprise channel.' It applies the logic at query time against your synced Stripe data.

Is Starch SOC 2 Type II certified?

Not yet. Starch is not currently SOC 2 Type II certified. If your company requires it for new financial data tools, that's worth knowing upfront. It's on the roadmap.

We also use Ramp for expense management. Can Starch pull COGS data from Ramp directly?

Ramp doesn't appear in Starch's scheduled-sync provider list, but if Ramp has a web interface you can log into, Starch can automate it through browser automation — no API required. Alternatively, if your Ramp transactions flow into QuickBooks or NetSuite (which most do), the ERP sync covers them. Describe your setup to Starch and it'll tell you the cleanest path.

How fresh is the data? We need this for month-end close decisions, not just board reporting.

Stripe and NetSuite data syncs on a schedule — typically daily. Plaid bank feed data also syncs on a schedule. For close week, this means your margin dashboard reflects yesterday's state, not real-time. If you need intraday precision on a specific transaction, you can query live from Starch's integration catalog for certain apps. But for the gross margin by channel workflow, daily sync is usually sufficient — you're catching the pattern, not the millisecond.