Question 1

How are you actually billing me — per kitchen, per brand, or per order?

Accepted Answer

Braiseflux bills per kitchen, per month — the price is anchored to the production footprint that runs the agents, not to how many virtual brands you spin up in that kitchen. A kitchen running six virtual brands on Starter is on one Starter bill; add a second kitchen (even for one shared brand) and it shows up as a second line on the workspace. Marketplace commissions, payment processing and per-order platform passthroughs are not part of the bill — Braiseflux never marks those up.

Question 2

Which delivery platforms and POS systems are actually wired in — and does my stack fit?

Accepted Answer

DoorDash, Uber Eats and Grubhub are on every plan alongside Square POS. Multi-Brand adds Clover, Toast and Otter, and Portfolio opens the full 40+ delivery, POS and distributor library (Yelp and Google for reviews, MarketMan / BlueCart / Sysco & US Foods for distributor punch-outs). If your kitchen runs a connector we don't ship, Portfolio+ is the on-ramp for bespoke connector builds — opens by application rather than self-checkout.

Question 3

What actually happens when a SKU goes 86’d in the middle of rush — and how do I keep the storefront honest?

Accepted Answer

Prep-level signals from your POS feed the inventory agent the moment a SKU drops below par. The agent pauses that SKU across every marketplace storefront that runs out of the same kitchen, raises a restock draft against your distributor punch-out, and surfaces the throttle event in /dashboard/home's morning read. Republish is a single approve in /dashboard/rules — guardrails you set per brand decide whether the SKU comes back automatically when prep recovers or waits for a human ack.

Question 4

Review replies are AI-drafted — but who actually pushes Send, and can I overrule tone?

Accepted Answer

Every reply is drafted, never auto-sent. They land in /dashboard/reviews as a queue: Approve & Send keeps the draft as-is, Edit lets you own the voice, Reject drops it. Anything that breaches a guardrail (a negative-rating escalation, a refund ask, a mention of an allergen) is flagged before it ever reaches the inbox. The audit trail stays in the thread so a brand-owner two levels up in the workspace tree can see exactly which replies you shipped and which you vetoed.

Question 5

Is there a contract, and what happens if I cancel mid-month?

Accepted Answer

Month-to-month, no minimum term and no auto-extension. You cancel from the billing screen at any time; the workspace stays readable until the end of the cycle, and we email a renewal reminder 7 days before the next charge so a missed billing email doesn't turn into a surprise renewal. Workspace data (brands, guardrails, review history) is exportable as JSON on cancel — there is no hostage-tier.

Question 6

If the agents run the day, what exactly do I still do?

Accepted Answer

Three minutes a day, plus a Monday morning read. You open /dashboard/home for yesterday’s portfolio (revenue, top movers, low-stock events, replies you owed a decision on); you change rules when a brand or kitchen needs to behave differently (/dashboard/rules); and you review the reply queue (/dashboard/reviews) when a draft breaches a guardrail. Everything else — demand watching, menu shifting, restocking, courier routing, in-voice replies — runs without you.

Operator pricing, transparent and month-to-month

Frequently asked questions

Want a guided walkthrough?

From one operator to a multi-workspace operation — pick the tier that fits and we will show you the rest.