Honesty over a vague promise
Our Guarantee & Revision Policy
This page is blocking, not just incomplete.
Any guarantee we publish needs to state precise conditions, a clear timeframe, and whether it varies by tier — no absolute claims that can't actually be honored. Real guarantee terms haven't been defined yet, so this page intentionally has no guarantee language rather than a vague or invented one, since a vague or invented guarantee is worse than none at all.
Why We're Not Filling This In With Generic Language
It would be easy to publish something that sounds reassuring — a “100% satisfaction guarantee” or a “money-back promise” — without actually working out what that means in practice: how a dispute gets resolved, what counts as reasonable dissatisfaction versus a scope disagreement, and what the actual timeframe is for raising a concern. Publishing that kind of language before it's genuinely true isn't a guarantee, it's a marketing line that could break trust the first time someone actually tries to use it.
[Revision policy per tier — round counts, what counts as a revision vs. a new request]
[Refund/satisfaction terms, if any, stated in exact conditions]
[What's explicitly not covered]
What Is Already Real
While the formal guarantee language isn't finalized, the revision rounds themselves are a real, functioning part of the process — see the Pricing page for the current round count per tier. Each round is a genuine opportunity to give feedback on a live preview and get a revised draft back, not a one-shot take-it-or-leave-it delivery.
Questions about this in the meantime? Reach out via the Contact page directly.