Sites, storefronts, booking flows, intake forms, and the integrations behind them.
A site is a set of handoffs. A tap has to reach a payment processor, a calendar, an inbox and sometimes a printer in the back. Every one of those hops is a place an order can go quiet. We build the hops first and then try to break them. The part you look at is the last thing we do.
This is one request, from a thumb to your bank account. The webhook and the notification can both fail without producing an error anywhere a person would look, which is how a month of orders goes missing.
Neither of these produces an error anywhere a person looks.
The order is written to your system and the receipt sends the moment the processor confirms the charge, not on a schedule and not by hand. If the confirmation never arrives, that is a state the system records.
The slot is held in the calendar itself, not in a form that emails you, so a conflict is caught by the calendar at the moment of booking. Bookings taken by phone still have to reach that calendar, and we will show you where that gap sits.
Routes by service type, so the quote request and the complaint land in different places.
The price is calculated on the page from the options selected, so a customer gets a number without you answering the phone.
Set from your phone in one tap, with the page stating when they were last set.
One product record drives the page, the cart and the receipt, so a price change happens once.
One code carries the customer's discount and the promoter's commission, and the payout record survives a refund. Designed and presented; not yet run for a client.
Submissions are stored at the endpoint as well as emailed, so a mail problem is usually a delay and there is somewhere to go and look. Nothing is lossless. This is the version where you can check.
The hard part: attribution that still balances after a refund.
The hard part: hours that change by the day, set by somebody whose hands are full.
The hard part: a number that has to be right without a person checking it.
If your current store is taking orders and the numbers are fine, a rebuild is an expensive way to change the font. Custom is worth paying for when the logic is unusual: attribution that survives a refund, a quote that has to be right without a person, hours that change by the day, inventory living in a system nobody wants to replace. When it is none of those, we will tell you to keep what you have and spend the money on the listing.
A full build is $249 up front and $35 a month after that. A single page with the listing set up properly is $149, bought outright with nothing recurring. What pushes it over: money changing hands on the site, an integration with a system you already run, or logic that has to be right without a person checking it. Operations is the monthly line that keeps it alive, and that number is published.
No date before discovery. After discovery, the written scope carries dated milestones, and if we miss one, the monthly line does not start until the thing is running.
Before any money moves you get the written scope, one named person who owns the account, a change log, and the terms for leaving.
Fifteen minutes gets you the range it sits in and what would move it, or the name of someone better suited to it.