PHILADELPHIA / WEBSITES + BUSINESS SYSTEMS
Corvian connects the moment a customer acts to the work your business needs to do next.
ONE ORDER, 23:16 — AND EVERY PLACE IT HAS TO LAND
ORDER 0118 · AWAITING ACTION
Example route. A Corvian Systems Lab demonstration, not a live client order.
OPERATIONAL PROOF
The same event has to land in every place the business actually runs. A form that only sends an email leaves the rest of the work to you.
A late order that pays for itself before the kitchen sees it.
CUSTOMER
Order placed from a phone, 23:16
PAYMENT
$18.00 captured, card on file
KITCHEN
Ticket accepted, ready in 12 min
INVENTORY
Dough portions 24 → 23
OWNER
One record, closed and countable
Order flow selected. CUSTOMER, then PAYMENT, then KITCHEN, then INVENTORY, then OWNER.
CORVIAN SYSTEMS LAB / 001–002
These are Corvian Systems Lab builds — working demonstrations, not commissioned client history. Open either one and put an action through it yourself.
A restaurant ordering system with the operation attached to it: guests order and pay, the kitchen works a real ticket queue, and the owner side holds the records the business is run from.
A barbershop front door where the booking is the product: the customer picks a service and a real slot, the confirmation is issued, and the schedule behind it stops offering what is already taken.
APPROACH / WHAT HAPPENS AFTER THE CLICK
Most small-business websites end at the click. The interesting design problem starts one step later: the action exists, and now something has to happen to it. Corvian designs that part first and works backwards to the button.
This describes how Corvian designs and builds these systems. It is not a study of research participants, and it does not report outcomes for a client.
The action has to be completable by a person standing outside a closed shop at 23:16, on a phone, with one hand. That constraint sets the whole interface: few decisions, no account, a price visible before the commitment, and a state the customer can trust once they let go of the phone.
CONSTRAINT / ONE HAND, ONE MINUTE, NO ACCOUNT
An unvalidated action is a liability: it can ask the kitchen to make something nobody paid for, or hold a chair that was never really free. Validation is payment for an order and availability for a booking, and it happens before the operation is told anything at all.
RULE / VALIDATE BEFORE YOU DISPATCH
Someone in the building has to receive work in a form they can act on mid-shift: large, ordered, one state at a time, and safe to touch with flour on their hands. A notification is not a response. A queue with states is.
SURFACE / BUILT FOR A BUSY SHIFT, NOT A DESK
The record is what still exists tomorrow. It has to carry the money, the time, the items, and the state, and it has to be written once so the totals cannot disagree with each other. This is where most stitched-together tools fail quietly.
RECORD / WRITE ONCE, COUNT ANYWHERE
Not a dashboard of everything. The owner needs the short list of things that require a decision, and enough history to answer what happened last night. Everything else should stay quiet until it is asked for.
VIEW / DECISIONS FIRST, HISTORY ON DEMAND
Nothing reaches the operation. The customer is told immediately and can retry without re-entering the order.
The action is refused at the door rather than accepted and silently dropped. A closed shop should not be able to take an order it cannot fill.
The hold fails, the schedule is re-read, and the customer is offered the nearest genuinely free time instead of a confirmation that will have to be undone.
The money and the operational state are never allowed to disagree. The order is not treated as complete until the record exists.
THE LEAK
Actions that never reach a system you own — missed calls, lost messages, orders on someone else’s platform — have a monthly value. Put your own numbers in.
Orders, bookings, or inquiries in a normal month.
What one of those actions is typically worth.
ESTIMATED MONTHLY LEAK
$2,100/ month
$25,200 / year
A $5,000 connected commerce system breaks even in about 3 months.
This is an illustration built from the numbers you entered, not a projection of recovered revenue. What a connected system actually recovers depends on your operation.
TWO WAYS IN
STARTING AT $750
For a business that needs one clear, owned place to be understood and contacted.
Connects the front door.
STARTING AT $3,500
For a business whose customer action needs to reach booking, ordering, fulfillment, records, or owner controls.
Completes the route into the business.
Additional pages, integrations, third-party fees, content, photography, and ongoing support are quoted separately when relevant.
ACCOUNTABILITY
Corvian is built and run by Leo Sutter in Philadelphia. I direct the experience, build the software, and stay responsible for the result from first frame to working system.
You work with the person doing the work.
Founder-led and taking on its first commissioned projects. Bella Forno and Sharp & Sons are Corvian Systems Lab demonstrations.
The composition, the language, and the order things are understood in. Decided before anything is built.
The route from the customer action to the operation and the record. Built as software, not assembled from plugins.
One name on the result. You are not handed between a salesperson, a designer, and a contractor.
START
Five questions. Each answer connects another leg of the route, and the finished map is what I read before I reply.
BEGIN WITH THE OUTCOME — 1 / 5
Question 1 of 5: What should work better?