← All sample plans Get my plan & price →
Example

An illustration of the document we send within 24 hours of your call, so you can see the detail, the structure and the way we price. Yours would be about your business, with your numbers.

The Build Plan

Support Autopilot
for a DTC brand.

Everything we would build, everything we deliberately would not, what it connects to, how long it takes and exactly what it costs.

Written forA DTC brand, ~2,400 tickets a month
IndustryEcommerce
FromOne 30-min call
Valid for30 days
01

What you told us

“Three people spend their whole day answering where-is-my-order. We’re hiring a fourth for peak and I can’t see how that scales. And I still don’t really know what people are complaining about.”

Head of Operations · ~2,400 tickets/month

The volume is not complicated, it is just relentless. Order status, returns, sizing, delivery timing and discount code problems are the overwhelming majority of what lands in Gorgias.

Peak makes it worse in a way that is expensive — you staff up for November, train people for six weeks, and let them go in January.

The second problem you raised matters more than the first. Nobody is reading the tickets in aggregate, so recurring product and delivery issues only surface when someone happens to notice a pattern.

02

What this is costing you now

Numbers from your own figures on the call, not industry averages. These are the basis for the plan, so if any of them are wrong, tell us and the plan changes.

The aim is not to remove your support team. It is to stop them spending the day on the repetitive majority, and to make the pattern in the remainder visible.

03

What we would build

It sits inside Gorgias rather than replacing it, so your team keeps the tools and the history they already have.

Part 01

Resolution on your policies

Answers the repetitive majority using your actual returns policy, shipping terms and tone of voice — not a generic support bot script.

Part 02

Live order awareness

Reads Shopify directly, so order status, tracking and delivery answers are real rather than templated.

Part 03

Escalation with context

Anything it should not touch goes to a human with the order, the history and a suggested reply already attached.

Part 04

The insight dashboard

What customers are actually contacting you about, grouped and trended — which is usually a product or logistics problem in disguise.

04

What peak looks like after

Today

  • Ticket volume triples, queue blows out to 12+ hours
  • Seasonal hires trained for six weeks, gone in January
  • Pre-purchase questions answered too late to convert
  • Recurring product issues surface weeks after they start

After

  • The repetitive majority answered in minutes, around the clock
  • Your permanent team handles the exceptions, not the queue
  • Pre-purchase questions answered while the customer is still on site
  • Recurring issues visible on a dashboard as they emerge
05

What it connects to

06

What is not in scope

Listed as plainly as what is, because this is the part that quietly becomes an extra invoice elsewhere. None of the below is in the price. All of it can be quoted separately later.

07

Timeline — 21 days from approval

Days 1–3

Policies and tone

We take your real policies, your best existing replies and your voice, and agree exactly what it must never answer on its own.

Days 4–11

Build

Resolution, Shopify awareness, escalation and the dashboard. Working version at the end of week one, tested on your own ticket history.

Days 12–16

Shadow mode

It drafts replies to live tickets without sending them. Your team reads every one and corrects it, so customers never see the learning curve.

Days 17–21

Go live and handover

Switched on for the ticket types you approve, starting narrow. Walkthrough for the support team, documentation, accounts in your name.

08

What you get at handover

From that point it is yours. You can extend it, hand it to another developer, or take it in-house. There is no licence and nothing stops working if you stop talking to us.

09

The price

One number.
Fixed · + GST · scope exactly as written above

On a real plan, this is where your figure sits — one number for everything above, agreed before a line of code is written. We do not publish it on the samples, because a price list would mean pricing your business before we have spoken to you.

On approval50%before we start
At handover50%when it is live and yours

This number does not move. If the build takes longer than we estimated, that is our problem, not your invoice. If you want something added mid-build, we quote it separately and you decide — it never arrives as a surprise line item.

Ongoing is optional. After the included 30 days, hosting, AI usage, monitoring and improvements are a monthly if you want them. Cancel whenever you like; you keep the software either way.

10

What we need from you

That is the whole commitment. No workshops, no specification documents to review, no weekly status meetings.

11

Assumptions and risks

Stated up front, because the ones nobody mentions are the ones that blow up a fixed price.

Other sample plans

Same structure, different businesses — so you can see how the scope and the number move with the job.

Your plan would look like this.
It would just be about you.

One 30-minute call. A document like this within 24 hours, with your numbers and your fixed price. Free, and yours to keep whether you go ahead or not.

Get my plan & price →

Figures are illustrative. The structure, the level of detail and the pricing approach are exactly what we send real clients. M3 — Brisbane & Vancouver.

Your plan, your numbers, within 24 hours. Free, whether you go ahead or not.

Get my plan & price →