Straight answers, in plain Aussie.Five baskets, fourteen questions, two-minute read.
The questions that arrive in our inbox before kick-off — install time, costs, where your data sits, what happens when a workflow breaks, and how changes work after launch. Anything these don’t cover, send through /contact or hit /start for a written scope.
Install time
How quickly the work gets from “yes” to live, and what fills the week in between.
- 01
How long does a workflow install take?
Six questions on /start, a reply inside one business day with a written scope, a twenty-minute call, a one-page sign-off, then most installs are live inside two to four weeks. A single-light workflow (one inbox, one trigger) can ship inside a fortnight. Multi-system integrations — booking, CRM, invoicing, all wired together — take the longer end of that bracket.
- 02
What happens during the install week?
We connect the tools you already pay for, write the small automations against your live data, and run the workflow in shadow before we flip it on. You see everything that runs — triggers, drafts, sends — and you keep the credentials the whole way through. The first ninety days are bundled into setup, so any tuning that surfaces after go-live is part of the same invoice.
- 03
Do installs run on weekdays only?
The build work happens in our hours; the workflows themselves run whenever you need them to. After-hours lead replies, weekend booking reminders, knock-off invoice chases — that’s the whole point of most installs.
Costs
What it costs up-front, why two clients pay different numbers, and what the monthly invoice looks like.
- 01
How much does a workflow cost?
Most scopes land between $4k and $7k setup. We give you a written number after a twenty-minute discovery call, never before — the band is built from recent installs, not a rate card. If we can’t scope your workflow inside that band we’ll say so up front, before we’ve taken any of your time.
- 02
Why does pricing vary between clients?
The bottom of the band covers a single light workflow — one inbox, one trigger, one notify. The top covers multi-location operations or heavy integrations across booking, CRM and invoicing. The shape of your week is the price, not the size of your business.
- 03
Are there any ongoing fees?
Only the maintenance you opt into once the first ninety days are up. Setup and maintenance are separate invoices — you can run on pilot-style ad-hoc support for as long as you like, nothing rolls on autopilot. Plenty of our clients stay that way for years.
Data & privacy
Where your client list, emails and call logs sit, who can see them, and how to get them back.
- 01
Where is our business data stored?
On the tools you already pay for — your CRM, your mailbox, your booking system. Spokedraft just wires them together; we never hold a copy of your client list, your invoices or your call logs. If we disappear tomorrow, your data is still where it was yesterday. Every tool we install on is Australian-hosted by default — we’ll flag anything in the discovery call that isn’t.
- 02
Who can see our client data?
A small in-house team — the same humans who scope your workflow build it and support it. No offshore call centre, no silent syncs to overseas SaaS, no "we’ll get back to you" piping through a vendor. Credentials stay with you, accounts stay with you, logs stay with you.
- 03
Can we export or delete our data?
Yes, on either side of that word. Every workflow sits on your own accounts, so the export is the same one you’d run if we’d never existed. If you want everything torn down we hand back the credentials, revoke the integrations, and walk you through the off-ramp on a call.
Uptime & monitoring
What happens when something breaks, who’s watching it, and the uptime you can plan around.
- 01
What happens if a workflow breaks?
We find out before you do. Monitoring is part of the maintenance bundle — the workflow that’s meant to send at knock-off sends a test pulse on a quiet cadence, and if that pulse misses we get paged. You hear from us with a fix or a status note, not a customer complaint.
- 02
Do you monitor workflows after hours?
Yes — the after-hours lead reply is the most-monitored workflow we ship, because a missed triage at nine o’clock is the failure mode our whole segment is built around. Weekend reminders, booking confirmations and invoice chases run on the same watch.
- 03
What uptime can we expect?
Whatever the underlying tools give you — the workflow is only as available as the CRM, the mailbox and the booking system it sits on. We design around that: every workflow has a soft-fail path that tells a human when the upstream tool isn’t responding, so a downstream outage doesn’t become a silent one.
Edits & changes
Tweaks after go-live, bigger restructures, and what happens when you want to plug in a new tool.
- 01
Can we change a workflow after launch?
Yes — and small changes come inside the monthly change-bundle. Rewording an SMS template, adding a field to the form, swapping a notification channel: that’s the everyday maintenance. Bigger restructures (a new integration or a new step in the flow) get a fresh one-page scope and a one-off quote, and nothing happens without you seeing the diff first.
- 02
How quickly can a small change ship?
Most small changes — a wording tweak, a new SMS template, an extra field — ship inside a few business days, often faster. We batch the change-bundle at the start of each week so you can see the queue, and we don’t make you chase for a status update.
- 03
Can we add a new tool later?
Yes — the workflows are built so a new tool joins as another spoke on the same hub, not a rebuild. Adding a booking system six months in, or an accounting tool at year-end, is a one-page scope conversation, not a from-scratch project.
Still weighing it up?
Six questions, ninety seconds. We reply inside one business day with a written scope or a polite no — no chasing, no drip campaign.