Project Terms
How accepted projects work after a build request is reviewed, including scope, deposits, client responsibilities, revisions, launch, handover and support.
When these terms apply
These project terms apply only when dwalton29 accepts a project and both sides agree a confirmed scope, price and payment plan in writing.
The quote builder is not a checkout. A project starts only after we confirm the scope, you accept the proposal/project terms, and the agreed deposit or upfront payment has been received.
Project scope
Every accepted build should have a written scope that explains the package, selected extras, pages, features, integrations, timeline, price, payment schedule and included support.
Anything not listed in the confirmed scope is not included. Extra pages, redesigns, new features, additional integrations, urgent work, major copy changes or extra support may be quoted separately.
Payments and deposits
Payment terms are confirmed per project. For smaller builds, this will usually be a deposit before work starts and a final payment before launch. Larger builds may be split into milestone payments.
Unless agreed otherwise, work starts after the first payment clears. Launch, handover, source-code transfer, final deployment and removal of build restrictions may be held until final payment is received.
If a monthly support plan is selected, support billing starts after launch or at the date agreed in writing.
Consumer cancellation rights
If you buy as a consumer, you may have a 14-day cancellation period for distance/online service contracts. We will explain any cancellation position in the project proposal or payment terms where it applies.
If you ask us to start work during a cancellation period, you may be charged for work already completed if you later cancel. If work is fully completed during that period with your agreement, cancellation rights may be affected. This does not affect statutory rights that cannot be excluded.
Client responsibilities
You are responsible for providing accurate information, content, brand assets, logins or collaborator access, images, copy, product details, legal information, pricing, policies, business details and feedback needed to complete the build.
You confirm that you have the right to use any content, logos, names, images, videos, fonts, music, text, trademarks, product information or other materials you provide.
Timelines depend on timely content, access and feedback. Delays in providing these may delay the project and may require timeline or price changes.
Third-party accounts and costs
Some builds require third-party services such as domains, Vercel, Supabase, Stripe, GitHub, email hosting, analytics, Google Search Console, social platforms or payment processors.
Unless specifically stated in the confirmed proposal, third-party subscriptions, domain renewals, platform fees, app-store fees, payment-processing fees, email fees and premium tool costs are not included in the project price.
As a default, clients should own their domain, Stripe/payment account and any account holding customer/user data. dwalton29 can help set up or manage technical services, but ownership and billing should be clear before launch.
Revisions and feedback
The number of included revision rounds should be confirmed in the project scope. A revision means adjusting agreed work, not replacing the agreed direction with a new concept or adding new features.
Feedback should be provided in a clear, consolidated way. Repeated small changes, contradictory feedback, new stakeholders, or late changes after approval may require additional time or fees.
Launch and handover
Before launch, we will carry out reasonable checks for mobile layout, key links, forms, selected analytics, selected payment flows and agreed core features.
Every build includes a handover guide or notes covering the site, hosting, domain, forms, selected services, access, support period and known maintenance responsibilities.
Once the final payment is received and the project is launched or handed over, you are responsible for day-to-day business use, content accuracy, legal compliance, third-party bills and account ownership unless you have an active support or management agreement with us.
Support and critical fixes
All sites include one month of general support and critical issue fixes after launch unless agreed otherwise. Critical issues usually mean things like the site being down, a broken contact form, a broken payment flow, a serious mobile layout issue, or an account/login issue for builds that include accounts.
Support does not include unlimited redesigns, new features, extra pages, major copywriting, new integrations, ongoing social posting, paid ads, full business consultancy, or work caused by third-party platform changes unless agreed separately.
The optional Monthly Basic Support plan provides continued advice and small support work on a rolling basis. It is not unlimited development.
Ownership and portfolio use
After final payment, you own the agreed final website content and deliverables created specifically for your project, subject to any third-party licences, open-source licences, platform terms, unpaid invoices and agreed limitations.
dwalton29 may retain reusable know-how, code patterns, components, processes, internal tools and general methods developed during the project, provided they do not disclose your confidential information.
Unless agreed otherwise, dwalton29 may show the completed project, screenshots, name, logo and a short description in its portfolio, case studies, social posts and marketing materials.
Ending a project
Either side may end a project in line with the agreed proposal/payment terms. Amounts already paid may be retained to cover work completed, booked time, third-party costs, planning, consultation, design, development or project management already provided.
If a client becomes unresponsive, fails to provide required materials, misses payments, or asks for work outside scope without agreement, we may pause or end the project.