Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · WhatsApp sprint
Customers served where they already are, in 14 days.
In much of the world WhatsApp is the internet. This is your business answering on it, day and night, without anyone typing.
Quick answer
A WhatsApp Business bot can be built and live in 14 days from a fixed $1,999, covering Business API setup, conversation flows, real actions such as orders or bookings, template notifications and handoff to a human agent. Meta's business verification runs alongside and its timing is not in my control.
The plan
Day one to day 14, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–2
Scope and access
What customers actually message about, and starting Meta business verification immediately, because that queue is the one thing I cannot speed up.
- 2
Days 3–6
Flow design
Conversation flows, template messages written for approval, and the escalation rule. Templates go to Meta early since they need review.
- 3
Days 7–11
Build
API integration, flows, actions against your systems, and the team inbox. Tested against real message patterns including the ones that make no sense.
- 4
Days 12–13
Test with real people
Colleagues and friendly customers messaging naturally — voice notes, emoji, half-sentences, three messages in a row. All of which real customers send.
- 5
Day 14
Launch
Number live, team trained on the inbox, escalation tested, and analytics running.
What from $1,999 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Businesses in markets where customers message rather than email
Teams whose WhatsApp inbox has become an unmanageable queue
Retailers and services taking orders or bookings in chat already
Real situations
Five ways this shows up, and what actually fixes it.
Not hypothetical — the shape of the problem before someone books this sprint, and the specific part of the build that resolves it.
Situation 1
The WhatsApp inbox has become an unmanageable queue
A business's WhatsApp has become the default customer contact channel, but message volume has grown past what staff can keep up with manually, and things are being missed.
Automated conversation flows handle common enquiries directly, with a shared team inbox and human handoff for anything that needs a person.
Situation 2
Customers message rather than email, and the business can't keep up
In this market, customers overwhelmingly prefer messaging over email or phone, but the business has no automated way to handle that volume outside working hours.
A WhatsApp Business API bot answers real enquiries — availability, orders, bookings — day and night, without anyone typing.
Situation 3
Already taking orders in chat, informally and inconsistently
A business already fields orders or bookings directly through WhatsApp messages, but the process is entirely manual and prone to messages getting lost or forgotten.
Real actions — checking availability, taking an order, booking a slot — are built against the business's actual systems, formalizing what's already happening informally.
Situation 4
Worried about getting the WhatsApp number banned
A business considering WhatsApp automation is concerned that sending too many or the wrong kind of messages could get their business number banned by Meta.
The build explicitly avoids bulk unsolicited messaging, using approved template messages for notifications — the difference between compliant automation and a banned number.
Situation 5
Meta business verification timing is a total unknown
A business doesn't know how long Meta's verification process will take and is worried it will hold up the whole project indefinitely.
Verification starts on day one of the sprint, in parallel with the build — the 14-day build finishes regardless, with the real timeline explained honestly rather than guessed at.
The honest part
When 14 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Bulk unsolicited messaging. Meta restricts it, customers report it, and it gets your number banned — which is unrecoverable.
Anything I cannot control the timing of, namely Meta's business verification. The build lands in 14 days; approval is their queue and I will tell you the current reality on the call.
Regulated advice delivered over chat — medical, legal or financial — which carries liability the channel makes worse.
Inside the 14 days
- WhatsApp Business API setup and number configuration
- Conversation flows for your real enquiries, not a generic script
- Real actions: check availability, take an order, book, look up a status
- Template messages for notifications — confirmations, reminders, updates
- Handoff to a human agent, with the conversation history intact
- A shared team inbox so several people can handle chats without collisions
- Analytics: volume, resolution, what it could not handle
- Source code and configuration yours at handover
Quoted as one number before day one. A week running long is mine to absorb.
Outside the line
- Bulk unsolicited messaging. Meta restricts it, customers report it, and it gets your number banned — which is unrecoverable.
- Anything I cannot control the timing of, namely Meta's business verification. The build lands in 14 days; approval is their queue and I will tell you the current reality on the call.
- Regulated advice delivered over chat — medical, legal or financial — which carries liability the channel makes worse.
Real work, sized and priced separately. You hear it before you book, not at handover.
Questions
Before you book
For automation, yes — the free Business app does not support it. The API runs through a provider, and setup plus Meta verification is part of this sprint.
Other sprints
14 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.