A customer submits an order on a Friday night and the baker is off the clock. By Monday morning, that customer may already have heard back from someone else. The longer someone waits after submitting an inquiry, the easier it is for doubt, distraction, or another vendor to step in.

For a business owner who is also the baker, bookkeeper, and delivery driver, that follow-up window is rarely free. This is what we built to fix that.

What happens next

The customer gets an instant confirmation, even if the baker is offline.

The baker receives a clean order summary with the details needed to quote.

A reviewed quote goes out with a deposit link, without rebuilding the email from scratch.

The customer gets a reminder before delivery, so payment and logistics are clear.

the tools, and why each one is here.

The whole thing runs on tools most small businesses already have or can get for free. Nothing here requires a developer to maintain.

Order intake

Jotform

The customer-facing form. Captures everything the baker needs to price and plan the order without a single follow-up email. File uploads, conditional logic, and Zapier connection built in.

Connection layer

Zapier

Connects the form to everything else. When Sarah submits, Zapier fires the confirmation email, creates the order record in Google Sheets, and notifies the baker. One trigger, multiple actions.

Order log

Google Sheets

Every order in one place. Date, status, delivery details, whether the deposit is paid. The baker opens it and knows exactly where every order stands. No dashboard to learn, no new login.

Automated emails

MailerLite

One option for the repeatable customer emails like the instant confirmation and delivery reminder. Also works if the business already uses it for email marketing. The confirmation can also come from a Jotform autoresponder or Gmail via Zapier depending on preference.

Personal emails

Gmail

The quote, the follow-up, the order recap. These are one-to-one emails that need a human touch. Zapier creates a pre-filled draft. The baker reviews, personalises if needed, and sends.

Invoicing and payment

Square

Handles the invoice, the deposit link, and the payment receipt. Square stays separate from the website by design. The site captures the lead. Square handles the money. Mixing those two jobs would add complexity without adding anything the customer actually needs.

* Square also doubles as the order record for invoices and payment history. The baker already logs in to create invoices, so the financial side of every order lives there without any extra steps.

Running a custom order business without a system isn’t free. It’s just paid in time instead of money. The “sorry for the delay” emails, the order details buried in a text thread, the Friday night inquiry that sat until Monday. A lean version of this typically runs somewhere around the cost of a couple of pounds of good butter a month. Often less, depending on what the business already has. This is one way to build it. Maybe you already have half these tools and just need the pieces connected. Maybe you need less. We figure that out together.

what Sarah experiences, step by step.

Click through each step below to see exactly what happens after Sarah hits submit. What she sees, what the baker sees, and why each piece of the system is doing what it is doing.

Before the sequence

The form Sarah fills out.

Before any automation runs, the form has to do its job. A well-designed intake form is the foundation of the whole system. It asks the right questions so the baker has everything she needs to price the order without going back and forth.

The inspiration photo upload is deliberate. Garden-style florals means something different to every baker. A photo removes the ambiguity before it becomes a problem.

Why this matters

Most custom order businesses use a generic contact form. The customer writes a vague message, the baker asks five follow-up questions, the customer takes two days to reply, and by then the date might be gone. A specific intake form front-loads that conversation so everyone starts on the same page.

Trigger Sarah hits submit. Everything else in this sequence starts here.
Custom Cake Inquiry
The Cake Co. · thecakeco.ca
First name
Sarah
Last name
Mitchell
Email
sarah.m@notarealemail.com
Phone optional
902-555-0147
Occasion
40th birthday
Date needed
August 9, 2026
Number of guests
30–35
Flavour preferences
Lemon lavender, vanilla bean
Dietary restrictions or allergies if any
None
Fondant
No fondant please
Pickup or delivery
Delivery
Delivery address
Main St. & Elm Ave., Wolfville NS
Design notes
Garden-style florals, soft colours, nothing too formal
Inspiration photos up to 3
Drop files here or click to upload · JPG, PNG, PDF
Inspiration link Pinterest, Instagram, etc.
pinterest.com/sarah/cake-ideas
Anything else we should know
How did you find us
Instagram

Step 1 of 5

Sarah gets a confirmation. Instantly.

It is Friday evening. Sarah hits submit and goes to bed. This email is already in her inbox. Nobody at The Cake Co. touched their phone.

The email plays her order details back to her so she can see everything was captured correctly. If something is wrong she can reply right then.

Why this matters

The silence after a form submission is where most custom order businesses lose people. Not because they are not interested. Because the customer has no idea if it went through. This email closes that gap before doubt has a chance to set in.

Trigger Jotform submission fires Zapier. Zapier sends the confirmation via MailerLite and adds Sarah’s order to the Google Sheet simultaneously.

Step 2 of 5

The baker reviews the order before quoting.

Saturday morning, the baker opens her notification email. It has Sarah’s full order details and a link to a short internal checklist. She clicks through, reviews the order, and answers a few quick questions before building the quote.

This step exists because pricing a custom cake takes a human eye. The checklist makes sure nothing gets missed before the quote goes out.

Why this matters

Most bakers price from memory and send a number without checking their calendar, confirming the delivery range, or clarifying the design. This checklist takes two minutes and prevents the kind of mistakes that are awkward to fix after a deposit is paid.

Trigger Zapier sends the baker an internal notification with Sarah’s details and adds the order to the Google Sheet. From there the baker reviews the order, works through the checklist, and chooses the next step.
New order — Baker checklist Internal
Sarah Mitchell — August 9 — Wolfville delivery
Occasion40th birthday
Servings30–35
FlavourLemon lavender, vanilla bean
DesignNo fondant, garden-style florals
Inspirationpinterest.com/sarah/cake-ideas

Before you quote, confirm:

August 9 is available in my calendar
Wolfville delivery is within my range
Design notes are clear enough to price
I need more information before quoting
If you need more info: check the box above, note your question, and submit. Zapier will create a Gmail draft to Sarah so you can ask without writing it from scratch.

Step 3 of 5

The quote lands in Sarah’s inbox.

The baker has reviewed the order and is ready to quote. Zapier creates a pre-filled Gmail draft with Sarah’s details, the line items, and a Square deposit link already populated. The baker reviews it, adjusts the pricing, and hits send.

This is not a fully automated email. Custom cake pricing needs a human. The draft does the heavy lifting so the baker is not writing the same structure from scratch every time.

Why this matters

The quote email does two things at once. It keeps Sarah warm and engaged after a night of waiting, and it gives her everything she needs to pay the deposit without a single follow-up. One email, no back and forth.

Trigger Baker submits the checklist with all boxes checked. Zapier creates a pre-filled Gmail draft. Baker opens it in Gmail, confirms the details, and sends.

Step 4 of 5

Sarah pays. The baker sends a personal note.

Sarah clicks the Square link and pays the deposit. Square handles the payment receipt automatically. That is Square’s job.

This email is something different. It is the baker’s chance to confirm the order details, make sure nothing has changed since the inquiry, and open the door for any last questions before she starts baking. Zapier creates the draft. The baker personalises and sends.

Why this matters

Square already told Sarah her payment went through. This email is not a receipt. It is a moment of genuine contact before the real work begins. It recaps the order so both sides are aligned, and it gives Sarah a natural opportunity to raise anything she might have been sitting on since the quote.

Trigger Square confirms the deposit. For the simplest version, the baker sends the confirmation note from a saved Gmail template. For a more connected setup, Zapier watches Square and creates a pre-filled Gmail draft automatically. Both work depending on order volume.

Step 5 of 5

48 hours before delivery, Sarah hears from them again.

This one fires on its own. MailerLite sends it automatically based on the delivery date captured in the original form. The baker does not have to remember.

Sarah knows the delivery window, what she owes, and how to pay. No last-minute texts, no confusion, no chasing.

Why this matters

The day of a custom delivery has a lot of moving parts. A reminder two days out means Sarah is ready, the balance gets collected without awkwardness, and the baker can focus on the cake instead of the logistics. The customer feels looked after. Nothing falls through the cracks.

Trigger MailerLite fires this automatically based on the delivery date field from the original Jotform submission. No human input required.

That is the full sequence. A few automated emails, a couple of human touchpoints, and a baker who can spend her Saturday morning actually baking. Want to build something like this for your business? Let’s talk.