SaaS vs Custom

A custom cake business in Australia (owner Sarah, 2 decorators, 1 delivery driver, 30 orders/month, avg $120 per cake, $43.2k/month revenue, $520k/yr) uses CakeBoss ($30/mo) or Bake Diary ($20/mo). Both offer recipe storage, basic booking calendar, cost calculation. But here's the chaos: order lands via DM ("Hi, I'd like a 3-tier wedding cake for 80 people, Saturday 15 June, chocolate sponge, raspberry filling, white buttercream, gold leaf, dietary: 2 vegan slices"). Sarah replies: "Lovely! Can you send mood board pics? Budget range? Any allergens?" Customer sends 5 Pinterest screenshots (via DM, hard to organize). Sarah opens notepad, types: "Wedding — 15 June — 80 pax — chocolate/raspberry/white — vegan option — Pinterest refs [5 links] — $250 budget — [add to calendar]." Deposit is due before design sign-off. Sarah sends invoice via email (separate system, customer opens email, looks for payment link, delays reply). Payment sits in "pending" for 3 days. Sarah chases: "Hi, deposit received yet? Design approval needed!" Customer replies: "Yes, sent. Can you confirm?" Sarah checks email history (20+ unread messages), finds receipt timestamp ("yes, hit your account, sorry!"). Design sign-off: Sarah opens CakeBoss or Bake Diary (generic "Notes" field). She types: "3-tier chocolate/raspberry/white/vegan/gold. Pinterest refs (links saved separately in phone notes, not in booking). Budget $250. Deposit $125 received." Design is not locked into the booking (Sarah has screenshots in her phone camera roll, customer approval is via email chain, not in the system). Production plan: Sarah knows cake is Saturday 15 June (4 days away). Baking schedule: when does she prep? Usually Friday morning, but she's booked 2 other cakes the same week. Sarah opens calendar: "Tue 11 June — order (cupcakes, small)." "Wed 12 June — order (birthday cake). Thu 13 June — order (3-tier wedding). Fri 14 June — ??? (flexible, but all 3 cakes need baking)." "Sat 15 June — wedding delivery + 2 other cakes decorating (tight)." "Sun 16 June — ??? (maybe birthday cake delivery?)." Sarah uses spreadsheet (separate from CakeBoss): "11 June: cupcakes bake (1 hr). 12 June: birthday cake bake (2 hrs), decorate (2 hrs). 13 June: wedding cake bake (3 hrs). 14 June: wedding cake decorate (8 hrs). 15 June: wedding delivery (1.5 hrs), birthday cake delivery (1 hr)." But she forgets: "Wait, the birthday cake needs 2 days to set. If I bake Wed, I can't decorate Thu—need Thu to chill. So bake Wed, chill Thu, decorate Fri morning (4 hrs), deliver Sat. But I'm also delivering wedding cake Sat, so I need to leave by 9am for wedding, and deliver birthday cake by 5pm. Delivery driver can handle both, but routes need planning." Production schedule is fragmented (calendar + spreadsheet + mental notes = chaos). Allergens & diets: wedding order mentions "vegan option: 2 slices only." Sarah adds to notes, but no flag (decorators see "3-tier chocolate/raspberry/white" and assume all vegan? No, only 2 slices). On Saturday, decorator pipes buttercream on 2 slices separately (last minute, delay). Vegan option is not tracked during baking (dairy butter used for most, but 2 slices need dairy-free). Sarah confirms with customer Fri: "Confirm: vegan buttercream for 2 slices?" Customer says "yes, what's the cost difference?" Cost difference is not tracked in CakeBoss (Sarah has to calculate manually: "vegan butter $5/kg, use 200g = $1 extra"). She texts customer: "Extra $10 for vegan option." Customer: "Done." Extra cost is logged in notes, not system (potential invoice discrepancy later). Delivery: Sarah loads wedding cake in van, drives to venue. She carefully places it, steps back, takes a photo with her phone (casual, no GPS, no timestamp). Venue manager: "Looks great!" Sets it on table. Sarah leaves. Next day, customer calls: "Cake was amazing! But there was a crack on the left side. Still tasted perfect though." Sarah checks photo (grainy, hard to see detail). Customer says "no worries, still happy." But Sarah has no proof-of-delivery artifact (no photo at venue time, no timestamp, no GPS). If customer disputes in future ("Cake arrived damaged"), Sarah has no evidence. Deposits: Sarah tracks deposits in a spreadsheet (separate from CakeBoss). "Order 1: $125 deposit received 8 June, order date 11 June, due 15 June, remaining balance $125 due 14 June." Customer doesn't pay balance until 16 June (after delivery). Sarah didn't chase it until after delivery (risky—customer could claim "cake wasn't right, shouldn't have to pay"). Deposits aren't tied to order status (no automated reminders, no milestone tracking). Recurring orders: corporate client "TechCorp" orders 12 cupcakes every month (first Friday). Sarah has this on a repeating calendar event. But every month she has to manually create a new booking: "TechCorp — cupcakes × 12, first Friday, chocolate + vanilla, same as last month." She copies notes from last month (tedious, error-prone). If flavors change, she has to track the change manually (risk of mistake—"they wanted red velvet this month, not chocolate"). One month, TechCorp changes order to "15 cupcakes" but Sarah doesn't update (delivers 12, TechCorp is short 3). Refund is issued (admin overhead). Compliance: Australia, food safety requires allergen labelling (FSANZ standards). CakeBoss stores "Notes" but no allergen matrix (gluten? dairy? eggs? tree nuts? sesame? lupin?). Sarah manages allergen flags manually on a separate document: "Wedding cake: dairy (buttercream), eggs (sponge), gluten (flour). Vegan option: no dairy, no eggs, still has gluten." When handing over cake, she reads from notes (no systematic check). If she forgets to mention "tree nuts were processed in kitchen" (cross-contamination risk), customer could have allergic reaction (liability). GST tracking: Australia, GST is 10% on cakes. Sarah invoices customers for $250 (inclusive or exclusive of GST?). She tracks manually: "$250 incl. GST, $227.27 excl. GST, $22.73 GST owing to ATO." At end of quarter, she calculates GST manually (error-prone, admin burden). Custom platform: order creation is self-service (customer fills form: "Order type: wedding cake / birthday / cupcakes. Date: 15 June. Pax/quantity: 80 people / 12 cupcakes. Design phase: upload mood board, select flavors, select fillings." Sarah sees intake in real-time. Design consultation: customer uploads 5 Pinterest screenshots directly in platform (not DM, not email). Platform auto-organizes (tagged "inspiration"). Sarah opens design view: "Mood board: [5 images], customer notes: 'elegant, gold accents, modern vibe.'" Sarah clicks "Design approval" and uploads mockup (sketch or AI-generated design preview). Customer approves online (signature captured, locked into booking). Cost is auto-calculated (3-tier + chocolate sponge + raspberry filling + buttercream + vegan option 2 slices = $252). Deposit is due (50% = $126). Platform auto-sends invoice link (payment gateway integrated). Customer pays (payment confirmed instantly, dated, no chasing). Remaining balance due: 2 weeks before delivery (automated reminder at 2-week mark: "Hi, remaining $126 due by 8 June"). Delivery address is locked in (Google Maps integration, address validated, autocomplete eliminates typos). Production schedule: system auto-builds timeline. Order due "15 June (Saturday delivery)." System calculates: "Bake: 13 June (Thursday). Decorate: 14 June (Friday). Delivery: 15 June (Saturday)." Staff calendar shows: "Thu 13: Wedding cake bake (3 hrs, 2pm-5pm). Fri 14: Wedding cake decorate (8 hrs, 8am-4pm)." But system also sees other orders in same week. Platform shows: "Capacity check: Thu 13 all bakers available 2-5pm? YES. Fri 14 all decorators available 8am-4pm? CONFLICT — decorator 1 booked Fri 8am-12pm (birthday cake 2nd day decorate). Capacity warning: add decorator 3, or move wedding cake decorate to Sat 1am (risky), or ask customer for Friday delivery instead (saves Saturday slot)." Owner sees conflict, adjusts: "Move birthday cake decorate to Thu evening (post-wedding bake, 6pm-9pm, allows Fri full for wedding)." System updates calendar, shows green (no conflicts). Allergens: order creation form has checkboxes: "Contains: dairy ☑ eggs ☑ gluten ☑ tree nuts ☐ sesame ☐ lupin ☐. Modifications: vegan option 2 slices (no dairy, no eggs, still gluten)." System auto-flags: "WARNING: This cake contains gluten. 2 slices modified: gluten-free? No. Customer aware?" Customer confirms (checkbox: "Yes, 2 slices are not gluten-free, customer aware"). On delivery, staff smartphone shows order: "Wedding cake: dairy, eggs, gluten present. Vegan 2 slices: no dairy, no eggs, gluten still present. WARNING: customers with gluten allergy should not consume." Staff verbally confirms with venue manager: "This cake has gluten. The 2 vegan slices also have gluten." Proof captured (voice memo: "Allergen confirmation recorded 15 June 9:32am at venue, staff confirmed gluten present"). Recurring corporate orders: TechCorp sets up "monthly recurring: 12 cupcakes, first Friday, flavors: Jan-Mar chocolate + vanilla, Apr-Jun red velvet + lemon, Jul-Sep carrot + cream cheese, Oct-Dec gingerbread + pumpkin." System auto-creates order on 1st Friday each month (no manual entry). If TechCorp needs to skip April or change quantity to 15, they edit online ("Skip April" / "Change to 15 cupcakes"). System auto-notifies Sarah ("TechCorp order updated: Apr skipped, May 5 cupcakes → 15 cupcakes"). No surprises, no missed orders. Delivery proof: staff open Velocity9 app on phone (iOS/Android). At venue, they take photo of cake in-situ (phone's camera + GPS + timestamp auto-logged). They tap "Delivery confirmed" (system records: "Wedding cake delivered 15 June 9:47am at [Venue Address, GPS coords]. Photo attached, timestamp verified, customer signature [digital or email confirmation]." App asks: "Any damage or issues?" Staff selects "None" or notes details ("Minor condensation on box, cake intact"). System creates delivery artifact (timestamp + photo + location + condition notes = proof-of-delivery, immutable). Customer later claims "cake had crack," Sarah pulls up delivery photo (timestamped, GPS-verified, shows pristine cake at handover). Dispute resolved (Sarah has proof). Deposits with milestones: system ties deposits to order status. Deposit due (50%): "Status = Design approved." Remaining (50%): "Status = 2 weeks before delivery." Milestone reminders auto-send. If customer doesn't pay remaining balance by 2 weeks, Sarah sees alert: "Order [Wedding] remaining balance $126 unpaid, due 8 June, 5 days remaining. Send reminder?" Sarah clicks "Send reminder," customer gets SMS + email ("Hi, remaining balance $126 due by 8 June. Pay here: [link]"). If balance isn't paid by due date, Sarah can choose to hold production (no bake until payment cleared). Compliance: GST is auto-calculated per order. Platform stores: "[Order] Wedding cake: $250 excl. GST. GST 10% = $25. Total = $275 incl. GST." At end of quarter, Sarah exports GST report (all orders, all GST amounts, ready to lodge with ATO). Food safety labelling: platform generates allergen label (printable). Order form shows: "Dairy, eggs, gluten. May contain traces of tree nuts (produced in facility where nuts are processed). Consume within 2 days of delivery. Keep refrigerated." Label is printed, affixed to cake box (FSANZ-compliant). Build cost: $50-80k. Year 1: $50-80k + $1.5k hosting = $51.5-81.5k. Year 2: $1.5k hosting + $2k part-time app support = $3.5k. Break-even month 14-18, then savings kick in. Annual ROI: ($520k revenue × 2% efficiency gain [fewer lost deposits, faster order intake, zero scheduling conflicts, zero delivery disputes] = $10.4k) + ($3k admin overhead saved [manual scheduling, deposit chasing, allergen tracking, GST calculation] = $3k) + ($2k zero-loss on lost orders due to capacity miscalculation) = $15.4k/yr net positive. Year 3+: $15.4k/yr pure profit. Competitive advantage: every cake delivery is backed by GPS-verified photo (zero disputes), every allergen is flagged (zero liability risk), every deposit is tracked (zero chasing), production schedule is optimized (zero overbooking, zero missed deliveries), recurring orders are automated (zero manual entry), GST is auto-calculated (zero ATO headaches).

Why CakeBoss & Bake Diary Fall Short for 30+ Monthly Orders

CakeBoss ($30/mo): offers basic booking calendar, recipe storage, cost calculator, to-do lists. Gaps: (1) No design consultation capture—customer mood boards are sent via DM/email, not stored in system. Sarah has to manually organize Pinterest links. No approval workflow (customer says "looks good" in text, not locked in platform). If customer later claims "that's not what I approved," Sarah has no artifact. (2) No deposit tracking—invoices are sent separately (email, Stripe, Square, PayPal). Deposits are not linked to order status. Sarah chases payment manually ("Have you paid?"). (3) No production schedule optimization—CakeBoss shows "due date: 15 June," but doesn't suggest bake/decorate timeline. Sarah builds timeline in spreadsheet (conflicts aren't auto-detected). If she double-books decorators, she doesn't know until scheduling crisis hits (Thu evening, realizes Fri is overbooked, calls decorator for emergency shift). (4) No allergen matrix—notes field is generic. "Gluten-free" is text, not a queryable flag. If Sarah needs "pull all nut-free orders for June," she manually scrolls every booking (tedious). Risk: Sarah forgets to warn customer about cross-contamination (liability). (5) No delivery proof—order is marked "delivered" manually (Sarah updates status later, no timestamp, no photo, no GPS). Disputes ("cake arrived damaged") are unresolvable (no evidence). (6) No recurring order automation—TechCorp monthly order is manually re-created every month (copy-paste, error-prone). If flavor changes, Sarah has to track manually. Bake Diary ($20/mo): similar gaps. It has inventory tracking (useful for bulk orders) but still lacks: design-approval workflow, deposit-status linking, production-schedule optimization, allergen-flag matrix, delivery-proof capture, recurring-order automation. Neither platform is built for custom-cake delivery operations with liability concerns. Both assume you're a micro-baker (1-2 orders/week) or a bakery chain (standardized products, no custom design). Sarah's business (30+ monthly, mixed wedding/birthday/corporate, custom designs, allergen flags, delivery disputes) isn't their target market.

What Custom Replaces: Six Features Cake Businesses Need

1. Design Consultation + Mood-Board Approval Workflow

Customer Sarah (bride): "I'd like a 3-tier wedding cake. Elegant, gold accents, modern vibe. Chocolate sponge, raspberry filling. White buttercream. 80 guests." She uploads 5 Pinterest screenshots directly in platform. Platform auto-organizes: "Mood board [5 images tagged 'inspiration']." Baker Sarah (owner) sees order intake (real-time notification: "New order: Sarah [bride] — 3-tier wedding, due 15 June"). Baker clicks order, sees: "Design notes: [5 mood board images]. Budget: $300. Dietary: 2 vegan slices." Baker uploads design mockup (sketch, or AI-generated cake design preview showing "3-tier white, gold leaf piping, raspberry visible on top"). Bride Sarah reviews design online (platform shows 1-1 comparison: mood board [left] vs. proposed cake [right]). Bride approves: "Perfect! Love the gold detailing." Approval is timestamped, locked (audit trail: "Design approved 10 June by customer [signed]"). Baker knows design is locked (no last-minute "can you make it more elegant?" after baking starts). Cost is locked too ($300 excl. GST, $330 incl. GST). If bride later requests changes ("Can we add more gold?"), baker can say "Approved design is locked. Custom changes = +$30." Change is tracked, invoice is updated (no ambiguity).

2. Deposit Auto-Billing + Milestone Tracking

Order created: 3-tier wedding cake, $330 incl. GST. Deposit due: 50% = $165 (due before design sign-off). Platform auto-sends invoice link: "Your custom cake order is ready! Design approved. Deposit due now: $165. Pay securely here: [Stripe link]." Bride pays ($165 charged, timestamp recorded). System confirms: "Deposit received 10 June, $165. Remaining balance: $165, due 2 weeks before delivery (2 June [wait, that's before 15 June, 4 days])." Milestone reminder: "14 June: Sarah [bride] — remaining balance $165 due TODAY before baking starts." Bride receives SMS/email reminder. She pays (balance confirmed). Both deposits are now secure (no chasing, no "payment received?" back-and-forth). If bride doesn't pay remaining balance by 14 June, baker sees alert: "Wedding [15 June] balance unpaid, due today. Production on hold." Baker contacts bride: "Hi, production starts tomorrow. Can you confirm payment?" Bride pays (or reschedules). Order is either locked or rescheduled (no surprises at delivery time).

3. Production Schedule Optimization + Capacity Conflict Detection

Week of June 11-15, Sarah (baker) has 4 orders: (1) Cupcakes 12, due Tue 11 June (bake Mon 10). (2) Birthday cake 3-tier, due Wed 12 June (bake Mon 10, decorate Tue 11, chill Wed pickup). (3) Wedding cake 3-tier, due Sat 15 June (bake Thu 13, decorate Fri 14, deliver Sat 15). (4) Corporate cupcakes 24, due Fri 15 June (bake Wed 12, deliver Fri). Platform auto-calculates: "Cupcakes 12: bake 1 hr. Birthday 3-tier: bake 2.5 hrs, decorate 4 hrs. Wedding 3-tier: bake 3 hrs, decorate 8 hrs. Corporate cupcakes: bake 1.5 hrs." Total: 7 hrs baking, 12 hrs decorating, 5 days available. Schedule built: "Mon 10: Cupcakes 12 bake (1 hr), Birthday bake (2.5 hrs). Tue 11: Birthday decorate (4 hrs). Wed 12: Corporate cupcakes bake (1.5 hrs), Birthday delivery (pickup). Thu 13: Wedding bake (3 hrs). Fri 14: Wedding decorate (8 hrs), Corporate delivery (1 hr). Sat 15: Wedding delivery (1.5 hrs)." Conflict check: "Fri 14: 9 hrs assigned (Wedding decorate 8 + Corporate delivery 1), but decorators are 8-5pm (9 hrs available). TIGHT but feasible if 1 decorator assigned all-day to wedding, no breaks." Alert: "Fri 14 is at capacity. Consider: (1) add 3rd decorator Fri (paid $120), (2) move corporate delivery to Sat, (3) move wedding decorate to Thu evening (emergency shift)." Baker chooses option 1: "Hire temp decorator Fri 8am-4pm." System updates: "Fri 14: Decorator 1 + 2 + temp assigned. Capacity: OK." Calendar is now conflict-free (no surprises Thu evening). All deadlines are met, all staff know their assignments.

4. Allergen + Dietary Flag Matrix with Auto-Warnings

Wedding cake order includes: "Sponge: wheat flour (gluten). Filling: raspberry jam (no allergens). Buttercream: butter, cream, eggs, powdered sugar (dairy, eggs). Vegan option: 2 slices only, vegan butter, dairy-free cream (no dairy, no eggs, still gluten). Special request: nut-free (customer concerned about tree nut cross-contamination)." Platform stores allergen matrix: "Cake contains: [☑ gluten, ☑ dairy, ☑ eggs, ☐ tree nuts, ☐ sesame, ☐ lupin]. Vegan slices: [☑ gluten, ☐ dairy, ☐ eggs, ☐ tree nuts, ☐ sesame, ☐ lupin]. Customer notes: 'Customer concerned about nut cross-contamination. Assure customer our facilities prep nut-free separately on different surface/utensils.'" Auto-warning for staff: "⚠️ This order contains GLUTEN and DAIRY. 2 slices are vegan (no dairy, no eggs, but STILL GLUTEN). Customer concerned about nut cross-contamination—use dedicated nut-free prep zone." Decorator sees this warning when opening order (no forgetting allergen specs). At baking stage: baker uses nut-free prep zone (buttercream for vegan slices made separately, away from any nut residue). Before delivery, driver sees alert on phone: "Allergen summary: This cake contains gluten, dairy, eggs. Vegan slices contain gluten. Customer concerned about nut cross-contamination—verbally confirm with customer on arrival: 'Your cake is nut-free as requested.'" Driver confirms with bride at venue, logs confirmation (timestamp). Bride can request allergen label (platform auto-generates PDF): "Wedding Cake Allergens: Contains gluten, dairy, eggs. May contain traces of tree nuts. Prepared in facility where nuts are processed. Suitable for: [☑ vegan (2 slices only), ☐ gluten-free, ☑ nut-free]." Label can be printed and placed on cake box (FSANZ-compliant, customer has written proof of allergens).

5. Delivery Photo Proof + GPS-Verified Handover

Saturday 15 June, 9:30am. Driver arrives at venue (wedding cake in insulated box, temperature-controlled). Driver opens Velocity9 app on phone. At the front door, driver taps "Start delivery" (app activates GPS, camera, timestamp). Driver: "Hi, I'm here with your wedding cake! Just taking a quick photo for our records." Takes photo of cake in box, venue in background (GPS auto-logs: Latitude/Longitude, timestamp 9:47am). Bride approves: "Looks beautiful!" Driver taps "Delivery confirmed" (system records: "Delivered 15 June 9:47am at [Venue Address]. Photo attached. Signature: [bride's email/phone number or digital signature]"). Driver notes: "Cake appears undamaged. Left with venue manager [name]." System auto-saves artifact: "Delivery Proof: Wedding cake, 15 June, 9:47am, [Venue GPS coords], [Photo], [Condition: OK], [Recipient: Venue Manager]." This artifact is immutable (dated, timestamped, GPS-verified). If bride later texts: "Hey, cake had a crack on the left, wanted to let you know," baker can pull up delivery photo (shows pristine cake at handover). Baker replies: "Thanks for letting me know! Our delivery photo at 9:47am shows the cake was perfect at arrival. The crack likely occurred after setup. Glad it still tasted amazing!" Bride can't dispute (proof is timestamped). Baker's liability is protected.

6. Recurring Corporate Orders + Automated Order Creation

TechCorp (corporate client) orders 12 cupcakes every first Friday: "Flavors vary by season. Jan-Mar: chocolate + vanilla. Apr-Jun: red velvet + lemon. Jul-Sep: carrot + cream cheese. Oct-Dec: gingerbread + pumpkin. Budget: $120/order (incl. GST). Delivery: 8am, TechCorp office." Baker sets up recurring order: "Order name: TechCorp Cupcakes. Recurrence: First Friday of month, every month, indefinitely." Template: "Qty: 12. Flavors: [Jan-Mar] chocolate 6 + vanilla 6, [Apr-Jun] red velvet 6 + lemon 6, [Jul-Sep] carrot 6 + cream cheese 6, [Oct-Dec] gingerbread 6 + pumpkin 6." Deposit: pre-authorized (first order charged $60, recurring orders auto-charge $60 on first Friday, 14 days before delivery). System auto-creates order on 1 June (first Friday of June): "Order: TechCorp cupcakes ×12, red velvet + lemon, Fri 6 June delivery, balance due 23 May." Deposit auto-charged (payment confirmed). Baker sees order in calendar ("Fri 6 June: TechCorp cupcakes, bake Thu 5"). If TechCorp needs to change in April: they log in, edit recurring order ("Change Apr to vanilla + strawberry instead of red velvet + lemon"). System updates ("Edit approved, Apr order updated, payment adjusted if flavors have different cost"). Baker sees change (alert: "TechCorp order updated: Apr flavors changed to vanilla + strawberry"). No manual re-creation, no error. Recurring orders are set-and-forget (saves baker 5 min/month × 12 months = 1 hour/yr, plus zero ordering mistakes).

Australian Cake Business Context & Growth Model

Australian custom-cake market: 8,000+ independent bakeries, $2B+ annual market, 60% growth YoY (wedding/event cakes, corporate gifting, hobby bakers going pro). Business models: home-based baker (1-3 orders/week, $200-500/week revenue), small studio (2-4 staff, 30+ orders/month, $40-60k/yr revenue), commercial kitchen (5+ staff, 100+ orders/month, $200k+/yr revenue). Revenue mix: 70% custom cakes (wedding 35%, birthday/anniversary 25%, corporate recurring 10%), 20% cupcakes/small items, 10% wholesale (bakery supplies, cakes sold to cafes). Seasonal peaks: wedding season Sep-Dec (60% of annual wedding orders), holiday baking Oct-Dec (corporate gifts), Mother's Day/Easter pulses. Allergen liability is critical (Australia, HSE regs require proper allergen disclosure; one mistake = legal liability + reputation damage + potential $20-50k fine). Deposit management is pain point (custom cakes cost $50-300 in ingredients, baker can't afford to lose money if customer cancels last-minute). GST compliance is tedious (10% on cakes, must track per-order for quarterly ATO lodgement). Delivery coordination is manual (no Uber for cakes, baker or staff drives + delivers, no real-time tracking, no proof-of-delivery until recently). Recurring corporate orders are underexploited (most bakers don't have systems to track repeat clients automatically, miss upsell opportunities). Custom platforms are rare (no "Stripe for bakeries," no turnkey booking + deposits + compliance). Opportunity: Australian custom-cake businesses are severely underserved. CakeBoss and Bake Diary are basic (calendar + notes, no deposit workflow, no allergen tracking, no delivery proof, no compliance automation). A custom platform would immediately: (1) lock design & budget (approval workflow), (2) automate deposit collection (50% upfront, 50% at milestone), (3) optimize production schedule (avoid double-booking, zero surprises), (4) flag allergens (zero liability risk), (5) prove delivery (GPS + photo, zero disputes), (6) automate recurring orders (TechCorp cupcakes every month, zero manual re-entry), (7) auto-calculate GST (zero ATO headaches).

Six FAQs

What if a customer wants to change the design after approval?

Wedding cake approved "3-tier white with gold leaf." 2 days before delivery, bride texts: "Can you add more gold? Like, a lot more?" System shows approved design is locked. Baker can respond: "Our approved design is locked. Custom changes (more gold leaf) would be +$20 labour. Can I apply this change and update your invoice?" If bride agrees, baker re-designs, new invoice is sent (+$20), bride approves, payment is collected. If bride declines, cake proceeds as designed. Clear, documented, no surprise costs.

How do we handle cancellations?

Bride cancels wedding cake order (personal reason, 10 days before delivery). System shows: "Deposit paid: $165 (50%). Remaining balance: $165. Cancellation policy: Cancellations 14+ days before delivery = 50% deposit non-refundable. Cancellations 7-14 days = 75% forfeited. Cancellations 0-7 days = 100% forfeited (ingredients already purchased)." 10 days out: bride forfeits $165 (50% deposit is baker's cost-recovery for design + setup). Remaining $165 is refunded. Invoice is marked "Cancelled 5 June, refund $165 processed." Clear, fair, documented.

Can customers self-customize the cake design in the platform?

Platform includes "Cake Builder" (optional feature): customer drags sponge type (vanilla, chocolate, red velvet), filling (raspberry, lemon, cream cheese), frosting (buttercream, ganache, cream cheese), topping (berries, sprinkles, gold leaf). Real-time cost updates ("Your cake: 2-tier + vanilla + raspberry + buttercream + gold leaf = $95 + $15 (gold) = $110 excl. GST = $121 incl. GST"). Customer finalizes, baker reviews (some built-it-themselves are viable, others need baker refinement: "Platform suggestion = OK, but customer doesn't realize 2-tier vanilla might be too soft for 40 pax. Baker suggests 3-tier."). Design approval workflow is the same (customer design → baker refinement → approval lock). Saves baker intake time (less "what flavors?" back-and-forth).

How do we track ingredient costs and margins?

Baker enters: "Vanilla sponge: $2.50/cake (flour, eggs, sugar, butter, vanilla). Buttercream: $1.50/cake (butter, cream, powdered sugar, vanilla). Raspberry jam: $0.75/cake. Gold leaf: $0.10/serving (20 servings = $2). Labour: $25/hr." Platform auto-calculates: "3-tier vanilla cake with buttercream + raspberry + gold leaf (for 80 pax / 3 slices each = 27 servings): ingredients $2.50 + $1.50 + $0.75 + ($0.10 × 27) = $8.20. Labour (bake 2.5 hrs + decorate 4 hrs = 6.5 hrs × $25 = $162.50). Total cost: $170.70. Margin @ $300 selling price: $129.30 (43% margin)." Baker can adjust price based on margin (if target is 50% margin, selling price should be $341). At end of month, baker exports "Profit Report" (all orders, costs, margins, net profit). Tells baker whether business is healthy (or if certain cake types are underpriced).

What about custom cake flavours that take longer to bake?

Bride requests: "Multi-layer cake with lemon curd filling (homemade, 3 hrs to make + cool)." System shows: "Lemon curd filling adds 3 hrs labour. Standard buttercream is 30 min labour. Baking timeline adjusts: if bride wants Sat delivery, baking must start Thu (lemon curd takes 3 hrs to cool, needs overnight chill, bake sponge Fri, assemble/decorate Sat morning). Timeline is tight." System alerts baker: "This order's custom filling requires early-start. Can you bake Thu? Or suggest Fri delivery instead?" Baker confirms Fri delivery is OK, bride agrees, order reschedules, no issue. Prevents baker from overcommitting (no "oops, lemon curd needs 3 hrs but I thought it was standard").

How do we track customer preferences across repeat orders?

TechCorp has ordered cupcakes 12 times (monthly recurring). Platform stores preference history: "Flavors: red velvet + lemon preferred (ordered 4 times). Previous dislike: lemon drizzle (ordered once, didn't reorder). Delivery: always 8am, always TechCorp reception. Recipient: always Sarah [office manager], contact sarah@techcorp.com. Feedback: 'Always on-time, always fresh, team loves the red velvet.' Upsell opportunity: tried 1x carrot cake, medium feedback (3/5), haven't reordered." Baker sees this when reviewing recurring order ("TechCorp due 1 July: their top choice is red velvet + lemon, but maybe try pitching the upgraded buttercream [+$10] since they like the red velvet?"). Baker sends message: "Hi TechCorp team! Your July order is ready. Thought you might enjoy our new salted-caramel buttercream on the red velvet (upgrade +$10). Still your classic vanilla if you prefer!") Customer experience is personalized (not generic), increases loyalty + upsell.

The Bottom Line

CakeBoss or Bake Diary: $20-50/mo × 12 = $240-600/yr licensing. Plus deposit chasing overhead (5 min per order × 30 orders/month = 2.5 hrs/month × $30/hr = $900/yr). Plus allergen manual tracking (5 min per order × 30 orders = 2.5 hrs/month × $30/hr = $900/yr). Plus delivery dispute liability (1 unresolved dispute per 100 deliveries, $300 loss avg, 30 orders/month = 3.6 disputes/yr × $300 = $1.08k/yr). Plus GST calculation overhead (4 hrs/quarter × $30/hr = $480/yr). Plus recurring order re-creation (5 min × 12 recurring orders/month = 1 hr/month × $30/hr = $360/yr). Plus capacity scheduling errors (1 overbooking per 100 orders = 36 hrs conflict resolution/yr per conflict × $30/hr = forget it, too high). Total friction: $240 licensing + $900 deposits + $900 allergen + $1.08k disputes + $480 GST + $360 recurring = $3.96k/yr in overhead + hidden losses (unresolved disputes, scheduling chaos). Custom platform: $50-80k upfront, $1.5k/yr hosting. Year 1: $50-80k. Year 2: $1.5k hosting + $1k support = $2.5k. Break-even month 14-18, then pure savings ($240 licensing + $900 deposits + $900 allergen + $1.08k disputes + $480 GST + $360 recurring + $2k avoided overbooking chaos = $5.96k/yr). By year 3, cumulative: –$70k (build) + $0 (year 1) + $5.96k (year 2) + $5.96k (year 3) = –$58.08k. Year 4: breakeven. Year 5+: $5.96k/yr pure profit. 30 orders/month, $120 avg margin, $43.2k/month revenue. 2% efficiency gain from custom platform (fewer lost deposits, faster intake, zero disputes, zero compliance fines) = $10.8k/yr extra profit. Build custom. Own your deposit workflow (50% upfront, no chasing). Own your allergen tracking (zero liability risk, FSANZ-compliant). Own your delivery proof (GPS + photo, zero disputes). Own your production schedule (zero overbooking, zero last-minute chaos). Own your GST tracking (auto-calculated, zero ATO headaches). Own your recurring revenue (TechCorp cupcakes automated, easy upsells). Ready to build a custom cake-ordering + production-management platform? Check Aidxn's custom software packages, or book a call to discuss your bakery (how many monthly orders?, typical order value?, staff size?, peak season?, allergen liability concerns?, recurring corporate clients?, current tools?, deposit payment method?, GST lodgement pain points?, growth targets?), licensing costs, and scale-up roadmap (second baker?, online design studio?, subscription box for corporate gifting?, franchise model?).