Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · loyalty sprint
Regulars who come back more often, live in 21 days.
Your own customer list, your own reasons to return, and a push notification that does not cost you 20% of the order.
Quick answer
A customer loyalty app can be designed, built and live in 21 days for a fixed $1,999, covering sign-up, stamps or points, reward redemption, staff scanning at the counter, referrals and push campaigns. It works best when the reward is genuinely worth returning for, which is a business decision rather than a build one.
The plan
Day one to day 21, 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–3
Design the economics
What earns a reward, what the reward costs you, and whether it is worth returning for. A loyalty scheme with bad maths fails no matter how good the app is.
- 2
Days 4–9
Design
Sign-up and the counter interaction first, because both happen with a queue behind them. Then rewards, campaigns and the dashboard.
- 3
Days 10–16
Build
Accounts, earning, redemption, scanning and campaigns. Fraud prevention on redemption is built in rather than discovered later.
- 4
Days 17–19
Run it at the counter
Real staff, real customers, real queue. If sign-up takes longer than fifteen seconds it does not survive a busy hour, and this is where you find out.
- 5
Days 20–21
Launch
Live, staff trained, signage or QR codes in place, and the first campaign scheduled.
What $1,999 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Cafés, salons and shops with regulars they cannot contact
Multi-site businesses running loyalty on paper cards
Any business whose repeat rate is the number that actually matters
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
Loyalty still runs on paper stamp cards
A café or salon rewards repeat customers with a physical stamp card, which gets lost, forgotten, or simply isn't tracked in any way that tells the business who its regulars actually are.
Digital sign-up in seconds at the counter — no app download needed — replaces the paper card and finally gives the business its own customer list.
Situation 2
Regulars exist, but there's no way to message them
A business has loyal repeat customers but no channel to reach them directly with an offer or update, relying entirely on them walking back in on their own.
Push and email campaigns to the business's own segmented list — by visit frequency or last visit — cost nothing per message and reach regulars directly.
Situation 3
Multiple sites running loyalty on inconsistent paper systems
A multi-site business has each location running its own informal loyalty approach, with no shared programme or combined view of customer activity.
One system runs loyalty consistently across sites, with a dashboard showing members, frequency and redemption across the whole business.
Situation 4
Worried the reward math doesn't actually make sense
A business is considering a loyalty programme without having worked out whether the reward being offered is actually worth what it costs to give away.
Days 1-3 explicitly work through the economics — what earns a reward, what it costs, whether it's worth returning for — before any building starts.
Situation 5
Concerned about staff or customers gaming the rewards
A business hesitant to launch loyalty has heard stories of staff over-awarding points to friends or customers exploiting a poorly verified redemption process.
Redemption is verified at the counter rather than self-declared, with awards attributed to a staff account and unusual patterns visible in the dashboard.
The honest part
When 21 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.
Coalition loyalty across unrelated businesses with shared points liability, which is an accounting and legal structure before it is an app.
Loyalty programmes where the reward is not worth having. I will tell you if the maths does not work rather than build something your customers ignore.
Deep two-way integration with an unusual legacy POS. Some integrate cleanly; I check yours before quoting.
Inside the 21 days
- Customer sign-up in seconds at the counter, no app-store detour needed
- Stamps or points, whichever fits your business, with your own rules
- Rewards and redemption, verified at the counter so it cannot be gamed
- A staff scanner for awarding and redeeming, on a phone
- Referrals — the mechanic that actually grows a loyalty base
- Push and email campaigns to your own list, segmented by behaviour
- A dashboard: members, visit frequency, redemption, repeat rate
- Source code, design files and 30 days of support at handover
Quoted as one number before day one. A week running long is mine to absorb.
Outside the line
- Coalition loyalty across unrelated businesses with shared points liability, which is an accounting and legal structure before it is an app.
- Loyalty programmes where the reward is not worth having. I will tell you if the maths does not work rather than build something your customers ignore.
- Deep two-way integration with an unusual legacy POS. Some integrate cleanly; I check yours before quoting.
Real work, sized and priced separately. You hear it before you book, not at handover.
Questions
Before you book
No, and for most businesses they should not have to. A web-based pass added to the phone's wallet gets far higher sign-up than an app-store download at a counter. A native app makes sense once you have a base worth notifying.
Other sprints
21 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.