- Before work starts: Full refund may be provided if the project has not yet been started.
- After work starts: Refunds are considered based on the amount of work already completed and delivered.
- Completed/accepted work: No refund for work that has been completed and accepted by the client.
- Scope changes: A request that materially changes the original requirements may require a new quote. The original payment does not automatically cover substantially different architecture, integrations, testing, or data sources.
- Client-requested cancellation: If the client cancels after development has started, the refund—if any—is based on the unfinished portion of the original scope.
- Third-party limitations: Problems caused by hosting, Cloudflare, external websites, APIs, source feeds, or other third-party systems do not automatically qualify for a full refund when the agreed development work has been completed.
- Revision period: Reasonable corrections to bring the delivered work into conformity with the agreed scope should be handled as revisions. New requirements are not revisions.
- Refund requests: The client should first identify the specific agreed requirement that was not delivered so it can be reviewed against the original scope.
Important: a refund policy should not imply that a client can receive a full refund simply because they later become dissatisfied or introduce substantially different requirements. A refund generally means returning money, but the actual entitlement depends on the applicable contract/policy and circumstances.
