RunbookLabs
Book a call

Products / the ones people hate most

We start with the work nobody wants to do twice.

A runbook is a workflow written once and run every period by automation you own. These are the ones that eat the most time at consumer brands. Scroll sideways to see them.

  • 001

    ASN automation

    Builds every ASN from what actually shipped and checks it against the PO and carton labels before it goes out. Works alongside the EDI provider you already have.

    Runs: On every shipment

    1. Read the shipment
    2. Build the ASN
    3. Check PO and labels
    4. Send on time
  • 002

    AI order entry

    Reads customer POs from email and PDF and creates the sales orders in your ERP, so nobody retypes them line by line. Flags price, item or quantity mismatches before anything ships.

    Runs: On every PO

    1. Read the PO
    2. Match customer and items
    3. Create the order
    4. Flag mismatches
  • 003

    Deduction matching

    Matches every retailer and distributor deduction to its promo or proof of delivery, and queues the invalid ones for dispute.

    Runs: On every remittance

    1. Read remittance
    2. Match to backup
    3. Flag invalid
    4. Queue disputes
  • 004

    Trade spend accruals

    Accrues every promo in the month it runs, from the promo calendar, then releases it when the deduction lands months later. Margins stop swinging.

    Runs: Close day 2

    1. Read promo calendar
    2. Accrue by period
    3. Match deductions
    4. Release the accrual
  • 005

    Inventory reconciliation

    Ties what your 3PL, Amazon and your books each say you have, and explains every difference instead of plugging it.

    Runs: Weekly, and at month end

    1. Pull 3PL counts
    2. Pull Amazon and ERP
    3. Match by SKU
    4. Explain variances
  • 006

    Commission accruals

    Pulls sales, applies each rep's, broker's or affiliate's terms, books the accrual and the true-up. Nobody rebuilds the spreadsheet again.

    Runs: Month end, before payroll

    1. Pull sales
    2. Apply terms
    3. Book accrual
    4. True up next period
  • 007

    AR aging

    Builds the aging from open invoices and payments every week, so you always know what retailers and distributors still owe.

    Runs: Weekly, Monday 06:00

    1. Pull invoices
    2. Apply payments
    3. Age balances
    4. Flag overdue
  • 008

    Marketplace payouts

    Ties Amazon and Shopify payouts back to orders, fees, refunds and reserves, and books the entry.

    Runs: On every payout

    1. Fetch payout
    2. Split fees
    3. Match orders
    4. Book the entry
  • 009

    Landed cost and COGS

    Spreads freight, duty and co-manufacturer charges across the units they brought in, so COGS per SKU is real, not an estimate.

    Runs: On every receipt

    1. Read the receipt
    2. Pull freight and duty
    3. Allocate by SKU
    4. Update COGS
  • 0010

    3PL invoice audit

    Checks every warehouse invoice against your rate card and actual activity, and flags storage, pick and pack charges that don't add up.

    Runs: On every 3PL invoice

    1. Read the invoice
    2. Apply the rate card
    3. Compare to activity
    4. Flag overcharges
  • 0011

    Sell-through reporting

    Pulls sales and inventory from retailer portals into one weekly view by store and SKU, so you see what's moving before the reorder.

    Runs: Weekly, Monday 07:00

    1. Pull retailer data
    2. Normalize SKUs
    3. Build the view
    4. Send the summary
  • 0012

    Month-end close

    Walks the close checklist in order and holds any step that needs a person.

    Runs: Close days 1 to 5

    1. Cut off
    2. Run sub-ledgers
    3. Collect sign-offs
    4. Lock the period

Also: MCP servers for your software

Your AI can talk. We give it hands.

MCP, the Model Context Protocol, is the open standard that lets AI assistants connect to real software. We build MCP servers for the tools you already run, so Claude, ChatGPT and Copilot can read your ledger, post the entry and update the record, not just describe it.

  1. 001 / What it is

    A small, secure adapter that turns your software's actions into tools an AI can call.

    Read an invoice, post a journal, update a deal, send the Slack message. Each action is exposed with your permissions, and every call is logged.

  2. 002 / Why you need one

    Without it, Claude, ChatGPT and Copilot only know what you paste in.

    With it, they work inside NetSuite, Stripe, HubSpot or your own database. Your team stops copying data into a chat window and starts asking for the work to be done.

  3. 003 / Why it matters for agents

    It is the same plumbing our runbook agents use to get work done.

    Build it once and every assistant your team uses, and every agent we ship, runs through the same tools, the same permissions and the same audit log.

Runbook agent / tool calls over MCPLive
NetSuiteMCP
StripeMCP
Bank feedMCP
HubSpotMCP
SlackMCP
Google SheetsMCP
Runbook agentidle
  1. readnetsuite.ledger.lines{ period: "2026-09" }→ 18,412 lines
  2. readstripe.payouts.list{ since: "2026-09-01" }→ 37 payouts
  3. readbank.feed.transactions{ accounts: 4 }→ 2,906 transactions
  4. writenetsuite.journal.post{ id: "je-1187" }→ posted, approver: controller
  5. readhubspot.deals.closedWon{ month: "2026-09" }→ 61 deals

Products / built to order

Don't see your workflow? We build it.

The products above are the ones we build most often, not the limit. If your team does something by hand every week, bring it to a call. We scope it with you, quote a fixed price before any work starts, and build it in three to six weeks depending on scope, the same way as everything else.

  • A report someone stitches together from three systems every Monday
  • Price list or catalog updates pushed to every customer and marketplace
  • Vendor and customer onboarding paperwork
  • Reorder alerts before a SKU runs out
  • Data copied between your ERP, CRM and spreadsheets
  • An AI assistant that can look things up and act inside your own software

If it repeats and it touches your systems, it can probably run on its own.

Book a call

A run, end to end

Every run leaves a trail you can read.

An agent reads the runbook, does the work in your systems, and writes down what it did and why. You review the exceptions, not the routine.

  • 01Runs start on a schedule or an event, never on someone remembering.
  • 02Anything unusual stops and waits for a person, with the reasoning attached.
  • 03Every entry links back to the source records it came from.
sample run: close, september 2026queued
  1. 06:00:00Pull yesterday's shipments (3PL)
  2. 06:00:09Check ASNs against POs and carton labels
  3. 06:00:22Pull retailer and distributor remittances
  4. 06:00:47Match deductions to promos and proof of delivery
  5. 06:01:05Queue invalid deductions for dispute
  6. 06:01:20Route two items for approval
  7. 06:01:41Update AR aging
Lines matched0
Deductions queued for dispute0
Waiting on a person0

Set it. Let it run.

Bring the one workflow your team hates most, from ASNs to the close. We will quantify what it costs you, build it in three to four weeks, and hand it over for you to own.

Book a call

Built by an AI engineer who ships automation inside a $100M+/yr consumer brand.