Autonomy, earned.
Burq never asks for the keys. Every segment of your operation climbs from Manual to Autonomous on its own record, at your pace. And a segment that breaks a rule climbs back down.
Scroll to climbLeading brands let Burq decide
ClearJet
...and 14,000+ businesses, from single stores to national platforms.
Four modes. Every one earns the next.
Your team decides. Burq records. Every dispatch your dispatchers make is written to your Decision Ledger: the pick, the price, the runner-ups, the reasons. The record starts on day one.
Burq decides beside you. Its call is written next to yours, order for order. The delta between your calls and Burq's becomes the case for the next mode.
Burq proposes. Your team approves. One tap to accept, one to override, both recorded with reasons. Your overrides are respected and remembered: each one teaches the next decision.
Burq executes inside your policies. Full authority within the rules you set: caps, windows, provider constraints. Step outside policy and the order comes straight back to your team.
Climbing the ladder is a settings change, not a new integration. Authority is granted per segment.
Autonomy granted, or autonomy earned.
Two ways to hand an AI your dispatch. One is a switch. One is a ladder.
Autonomy granted
Most platforms in this category ask for the keys on day one. Set the objective, trust the machine, audit later, if ever. The pitch is relentless autonomy; the proof is a demo.
Autonomy earned
Burq starts with nothing. Authority arrives one segment at a time, on thresholds you can read, and leaves the moment a hard rule breaks. The pitch is the ladder; the proof is yours.
One operation, every mode.
Meet Bluepine Home, an example home goods brand, on an ordinary Tuesday. Their in-house fleet runs Autonomous. Parcel runs Review. Big and bulky is still in Shadow. One ladder, climbed segment by segment, and it runs both ways.
The fleet runs itself Autonomous
Every crosstown drop on the in-house fleet runs on full authority, inside policy. Nine weeks in, zero breaches. Holding.
Parcel, one tap away Review
Each day's parcel batch is proposed and confirmed in one tap. Four weeks above 90% accepted. Ready to promote.
Big and bulky, watched ◐ Shadow
Burq's calls are written beside the team's, dashed, unable to act. 96 decisions in, the case is building.
Born in Manual Manual
Scheduled installs arrived last week. New segments start in Manual, evidence clock at zero.
The demotion Auto-demoted
Evening orders broke a hard rule: two frozen on one run. Demoted on the spot, evidence attached. The ladder runs both ways.
Your whole operation, one board.
Every segment, its mode, its record, its threshold, and its readiness. Promotion is offered when the record clears the bar. Demotion happens the moment a hard rule breaks. This board is the state of trust between you and Burq, at a glance.
Burq reads your orders into segments.
Send Burq your orders and Burq Intelligence draws the map itself: local under 10 miles, big and bulky, parcel on 2-day promises, scheduled installs. Each segment is a slice of your operation with its own decisions, its own record, and its own mode on the ladder. Local providers, your own fleet, and parcel climb the same ladder. Draw your own segments when you know something the orders do not.
Drawn from your orders
Segments come from how your orders actually behave, not from a settings wizard. Burq proposes the map; you rename, split, or merge it.
Born in Manual
A constraint edit that changes feasibility redraws the map on the spot. The new segment inherits the safest mode, and both events are in the ledger.
Promoted on the record. Demoted on the spot.
Every segment carries a threshold for it to be promoted.
The ladder runs both ways. Breach a hard rule and the segment demotes itself immediately, evidence attached.
The promotion
The parcel segment cleared 90% acceptance over four weeks and 480 decisions. Burq surfaces it, states the evidence, and waits. You promote it, or you do not.
The demotion
No meeting, no grace period. It broke a hard rule, lost Autonomous on the spot, and the ledger shows exactly why.
Your rules, enforced.
Each segment runs on your rules: when to dispatch, what jumps the queue, what can never happen. Burq checks each rule against your live orders while you write it and blocks anything that would break a promise.
Every rule change is written to your Decision Ledger.
Autonomy, earned in your operation, segment by segment.
Get a demoFAQs
Burq Intelligence, the same engine across every mode. Every call is made against the Decision Graph, Burq's record of how every provider, zone, and hour has actually performed, and every call is written to your Decision Ledger. The modes change who holds authority, never how carefully the decision is made.
A slice of your operation that behaves like one thing: local orders under 10 miles from one store, big and bulky across all stores, parcel on 2-day promises. Burq draws the map from your live orders, and you can rename, split, merge, or add segments of your own. Each segment carries its own policy, its own record, and its own mode on the ladder.
One tap keeps your call. The override is recorded with its reason, counted against the segment's acceptance, and fed back into the model, so the same disagreement gets rarer. Overrides never expire as a right: they exist in every mode, including Autonomous, and every one is in the ledger.
Yes. Parcel segments carry parcel-shaped policies (daily batches, pickup cutoffs, volume commitments) and climb the same ladder on the same evidence. On the example board above, the 2-day parcel segment is four weeks into Review at 92% acceptance, marked ready to promote. One ladder governs local providers, your own fleet, and parcel alike.
Yes, and that is the point. Every mode change, threshold, promotion, demotion, override, and constraint version is written to your Decision Ledger under SOC 2 Type II controls, so an auditor can replay which rules governed which decisions on which day. Your order data stays your order data.