Refund & Delivery Policy
This policy explains when delivery starts, what buyers need to provide, how refunds are handled, and how scope boundaries are enforced.
1. Delivery start
Delivery starts after payment is received and the required intake information is complete enough to begin work.
If intake is missing, unclear, contradictory, or outside the purchased scope, delivery may pause until the missing information is provided.
Success-page forms, intake forms, and follow-up questions are part of the delivery process.
2. Estimated delivery windows
Delivery windows shown on product pages are estimates, not guarantees.
Many starter products are designed for delivery within a short business-day window after completed intake, but timing depends on scope, buyer responsiveness, and required materials.
Large custom builds, managed agents, implementation bundles, or unclear requests may require additional scoping.
3. Digital products and service work
Products may include digital deliverables, AI-assisted plans, setup guides, workflow maps, dashboards, agent specifications, templates, operating documents, or implementation support.
Because work may begin soon after purchase and intake, refund eligibility can change once delivery work has started or a deliverable has been provided.
4. Refunds before work starts
If you request cancellation before work starts and before deliverables are created, a refund may be available, minus any non-refundable processing costs where applicable.
Refund requests should include the buyer name, email address, product purchased, payment reference, and reason for the request.
5. Refunds after work starts
Once review, planning, drafting, configuration, implementation, or delivery work has started, refunds may be limited or unavailable depending on the work performed.
If a request is outside scope, the work may be reduced into the purchased scope, quoted separately, paused for clarification, or declined as a bad fit.
A refund is not guaranteed because a buyer changes direction, does not use the deliverable, delays intake, withholds required information, or expects work outside the purchased scope.
6. No outcome-based refunds
Refunds are not based on whether a product produces revenue, leads, rankings, conversions, sales, cost savings, or a specific business outcome.
Products are sold as implementation support, planning, systems, workflows, digital deliverables, or related services, not as guaranteed business results.
7. Revisions and clarification
Reasonable clarification may be provided when it fits the purchased scope.
Revisions are limited by the product description, delivery materials, and scope boundary.
New requirements, new workflows, complex integrations, deployment requests, or additional deliverables may require a separate quote.
8. Scope boundaries
Each product includes only the work described for that product.
Unless explicitly included, purchases do not include unlimited custom software, live deployment, ongoing management, SMS or email sending, payment link creation, provider mutation, pricing changes, regulated compliance work, or crypto/wallet actions.
Any action involving customer-facing sends, payment actions, deployments, provider changes, pricing changes, or crypto/wallet activity requires explicit approval and may require a separate paid engagement.
9. Buyer delay or missing intake
If you do not provide required intake details, access materials, clarifications, or approvals, delivery may be delayed or paused.
If a buyer is unresponsive for an extended period, the order may be closed as incomplete while preserving the available record of what was provided.
10. Chargebacks and disputes
If there is a problem with an order, contact first with the buyer name, email, product, payment reference, and issue summary so the order can be reviewed.
Chargebacks or disputes may pause work, revoke access to pending deliverables, or require additional identity and order verification.
11. Contact
Refund or delivery questions can be sent through the contact form on jamesphillips.io or by using the contact details provided on the website.
This page is intended to provide plain-language buyer policy information for jamesphillips.io. If a written agreement signed by James Phillips conflicts with this page, the signed agreement controls for that specific engagement.