Business Accounts
Turn business enquiries into recurring orders.
Qualifies business account enquiries against your delivery zone and minimum order, then coordinates a sample or proposal on owner-approved terms. Once the customer explicitly agrees a schedule, it creates the recurring orders and rechecks price and production capacity whenever a quantity changes.
A real customer situation
A local office asks a bakery for breakfast for 25 people every Tuesday. The owner needs to know the office is real and inside the delivery area, that the order clears the minimum, and that Tuesday production can take it — then wants a schedule the office has actually agreed to, not a verbal ‘sounds good’.
Where the owner wants to be
Business enquiries become verified accounts with approved terms and a visible recurring schedule. Out-of-area and below-minimum requests are handled without false promises, and one-off changes are rechecked and applied only to the week asked for.
What it handles
- Verifies the business from a directory and checks the delivery zone and minimum order
- Drafts terms for owner approval and coordinates an optional sample and revised proposal
- Creates four weeks of recurring orders only after the customer agrees the schedule
- Rechecks price and production capacity for a one-week quantity change
- Flags production conflicts to the owner instead of overcommitting
What it deliberately does not do
- Never promises delivery outside the zone
- Creates no recurring orders from an unaccepted proposal
- A change to one week never alters other weeks unless the customer explicitly agrees
Interactive demo
Try it with sample data
No sign-up needed. Pick a scenario, change the inputs, then play the customer and the owner. The right-hand panel only shows what the workflow actually recorded.
Interactive simulation using a fictional business directory, delivery zones and production calendar. No message is sent, no order is created in a real system and no invoice is raised.
Choose a scenario
25 people every Tuesday in Surry Hills. Week 2 rises to 35 for one week.
Try Larkspur Planning Co., Fernhill Legal, Quarry Lane Studio or Westbrook Logistics.
Parramatta and Manly are outside the delivery zone.
A$12 per head; minimum A$150 per delivery.
Production capacity is 130 portions per Tuesday across all accounts.
Customer side · Email thread with the office
Press “Run scenario” to start. Every message and record here comes from sample data.
Workflow and harness
How Business Accounts runs
Reference schematic for the proposed workflow. Blue steps do the work, purple paths handle exceptions and returns, and amber checks are the harness controls that a step cannot pass without.
Overview — business stages
Read the full flow as text
- Business enquiry (business step)
Business, location, quantity and start required. Output: Enquiry. Leads to: Verify account and delivery fit. - Verify account and delivery fit (business step)
Directory lookup; delivery zone. Output: Prospect account record. Leads to: Scope quantity and frequency; Outside delivery area. - Scope quantity and frequency (business step)
Price list × quantity; minimum per delivery. Output: Costed requirement. Leads to: Approve sample or proposal. - Approve sample or proposal (business step)
Owner approves versioned terms; optional sample. Output: Proposal vN sent. Leads to: Customer agrees recurring schedule; Sample feedback. - Customer agrees recurring schedule (business step)
Explicit agreement to terms and schedule. Output: Agreement reference. Leads to: Create orders and fulfilment plan. - Create orders and fulfilment plan (business step)
One order per occurrence; capacity per Tuesday. Output: Four recurring orders. Leads to: Quantity change. - Outside delivery area (exception or return path)
No delivery promise; owner handoff. Output: Collection-only reply draft. - Sample feedback (exception or return path)
Change mix; reprice from price list. Output: New terms version. Leads to: Scope quantity and frequency (revise proposal). - Quantity change (exception or return path)
Recheck price and capacity for the selected order. Output: Accepted change or flagged exception. Leads to: Scope quantity and frequency (recheck selected order). - Business and zone checks (harness check)
Verified or labelled; in zone; ≥ A$150 per delivery. Output: Pass / blocked. Leads to: Verify account and delivery fit (required check). - Approved commercial terms (harness check)
Owner approval before sending. Output: Approved version. Leads to: Approve sample or proposal (required check). - Agreed schedule and capacity (harness check)
Occurrence qty ≤ free portions. Output: Orders or flagged occurrence. Leads to: Create orders and fulfilment plan (required check).
Harness controls
- Verified business details, with unverified details labelled
- Delivery zone and minimum order checks before any proposal
- Owner-approved commercial terms for every version
- Explicit customer agreement before recurring orders exist
- Capacity checked per occurrence; changes apply only to the selected occurrence unless explicitly agreed
Systems and data
Production uses an account CRM, delivery zones, production schedule, price list, ordering and invoicing. The demo uses a fictional business directory, a sample production calendar and an outbox that holds every message.
Demo boundary
External calls, customer messages, payments and business writes use synthetic fixtures and an on-screen outbox. The demo shows only verified demo state. Custom production connections are a paid implementation deliverable.
What gets delivered
The records your business receives
Approved terms and proposal
Versioned commercial terms — price per head, per-delivery value, delivery window, minimum, change notice and invoicing — approved by the owner.
Owner exception
Capacity conflicts, below-minimum changes and out-of-area enquiries arrive as tasks with the numbers behind them.
Account and recurring orders
Verified account record, customer agreement reference and four scheduled orders with order numbers and any one-week changes.
Custom deployment
Configured for your business during a paid implementation. Integrations are confirmed during discovery, never assumed.
Your business rules
- Delivery zones, delivery windows and any collection options
- Price list, per-delivery minimums and change notice periods
- Production capacity per day and how conflicts are resolved
- Who approves account terms and invoicing arrangements
Systems we connect
Measurement
We measure completed business against a baseline, not messages sent. No results are promised before discovery.
Business results
- Active recurring accounts
- Fulfilled recurring revenue
- Account contribution after delivery and production cost
Operational reliability
- Recurring orders created without customer agreement (target: zero)
- Deliveries promised outside the zone (target: zero)
- Occurrences scheduled beyond production capacity (target: zero)
Want this setting up recurring accounts from your own enquiries?
Book a call about Business Accounts. We start with discovery: your current process, volumes, systems and who handles exceptions. The proposal then defines the integrations, approvals and acceptance tests before anything goes live.