Catering / Quoting Software
Catering Connection
Catering Connection (Catering): A quoting portal moved to a new platform, with every total matching the old system to the cent.
Overview
Catering Connection quotes catering events in a web portal. We moved that portal to a new platform, so the team can keep quoting with every total matching the old system to the cent.
Business
Catering Connection
Sector
Catering / Quoting Software
Restaurants
What we build for this trade →
The brief
The quoting engine had to come across unchanged: same formulas, same totals. Everything outside quoting stayed hidden until a later build.
What we built
Quoting engine
The pricing engine was copied across as it was, with one added setting for what the service fee is charged on. The server reprices every quote on save and send, and approving a proposal recomputes its total from the pricing rules stored with that quote.
Custom Systems Architecture →Proof by replay
All 23 stored quotes were replayed through the new engine. 22 match to the cent. The other was priced by an earlier version of the engine, and replaying it with that version's setting reproduces its total exactly. Twelve engine tests cover deposit edge cases and menu option math.
Back-End Development & Infrastructure →Data move
14 clients, 21 events, 23 quotes, 24 proposals and 12 menu items moved across. Proposal links already sent to clients still open.
API & Third-Party Integration →Access
Sign-in only, with no self-signup. Owner, manager and staff permission sets. New users get a one-time set-password email.
Back-End Development & Infrastructure →Email sends through Resend from the business's verified domain.
API & Third-Party Integration →How it helps
- Clients keep using the proposal links they already have.
- Any stored quote can be replayed through the engine and compared with its saved total.
Every figure on this page is a count from a build record or a test run. A business result goes on this site only when it traces to a source we can open on a call: Results.
What it runs on
Cloudflare Pages with Functions, Supabase Postgres in its own schema with row-level security, and Resend for email from the business's verified domain.
How the work ran
This is how we run every engagement. It describes the process, not a timeline for this project.
The audit
We map what you already run and show you where it leaks. You keep the map either way.
The plan
What we would change, in what order, what it costs, and what number we will judge it on. You approve before anything is built.
The build
Each piece goes live on its own, so you see progress weekly instead of waiting for a big reveal.
The run
Managed, measured, month to month. Every channel judged on what a booked job costs you.
Builds are quoted once and built once; retainers you can stop any month. The full process and the published prices: How we work.
Questions
Is there a long-term agreement?
What does a build like this cost?
Do you use AI on this kind of work?
Read the full charter: The AI Charter.