Once your website, app, or loyalty rewards program is built and handed over ready for implementation, the sale is final. Before that point, you're protected by a written deadline for each deliverable — and if we miss it, you get your money back.
A deliverable is either sitting in your build queue with a clock running on it, or it's finished, tested, and in your hands. What refund applies depends entirely on which one is true.
Once your website, app, or loyalty rewards program has been fully built, tested, and delivered ready for implementation, the engagement is considered complete and the fee is non-refundable.
This applies whether or not you have launched the system publicly, connected it to your domain, or begun using it — delivery, not launch, is what closes the engagement.
If we have not delivered a working, reviewable version of your website within 21 days, your app within 60 days, or your loyalty rewards program within 90 days of the build start date, you can request a full refund for that undelivered piece.
Each clock runs independently, and each guarantee applies only to the deliverable it names.
Each guarantee is measured from the agreed build start date for that piece of the system, not from the date of your first payment or your first phone call.
If no working, reviewable website has been delivered within 21 days of build start, you're entitled to a full refund of the website portion of your investment.
Clock starts once the mapping stage is complete and build begins.
If no working, reviewable app has been delivered within 60 days of build start, you're entitled to a full refund of the app portion of your investment.
Runs independently of the website and loyalty program timelines.
If no working, reviewable loyalty rewards program has been delivered within 90 days of build start, you're entitled to a full refund of the loyalty program portion of your investment.
Applies to the loyalty and retention build specifically, not the wider system.
We define delivery clearly so there's no ambiguity about which rule applies. A deliverable is considered delivered, and therefore final, once all of the following are true:
Every deliverable is custom-configured to your menus, locations, services, or membership structure. Once it's built and handed over ready for implementation, it can't be resold or repurposed for another business — so, as with most custom development work, the fee becomes final at that point.
This is separate from ordinary post-launch support, bug fixes, and revisions, which continue under the terms of your build agreement.
Filing a claim under any of the three guarantees is a short, direct process.
Confirm the build start date for the deliverable in question, listed in your build agreement and mapping summary.
Email [email protected] stating which deliverable missed its window and the original build start date.
We verify whether a reviewable version was delivered within the window. If it was, that portion is excluded from the refund.
Once confirmed, the refund for the affected deliverable is issued to your original payment method within 10 business days.
A few conditions apply to every guarantee above.
If you're partway through a build and want to check where your deliverable stands against its guarantee window, we'll tell you plainly.
Or email us directly at [email protected]
