Payment methods
DaveTheWeb.guru generally collects project payments through Stripe invoices or Stripe payment links sent after scope is discussed and approved.
DaveTheWeb.guru
Billing
How project payments, deposits, final payments, and optional support blocks are handled.
Last updated: May 15, 2026
No public checkout link
Payment links are sent directly after the project scope or support request is reviewed. This helps prevent unapproved payments before the right scope, timeline, and next step are clear.
Project payment structure
Most projects use a simple staged structure: an initial payment to begin work and a final payment before launch, production domain connection, code handoff, repository transfer, or Cloudflare handoff. Specific amounts are provided in the proposal or invoice for each project.
Deposit and deliverables
A deposit or initial payment starts project work and reserves time, but it does not transfer ownership of drafts, concepts, source code, repositories, deployment access, or final deliverables. Previews may be shared for review before final payment.
Support blocks
Post-launch support may be handled through prepaid one-time support-hour blocks or separate quotes. Support blocks are not subscriptions and do not renew automatically.
Third-party costs
Domain registration, hosting, Cloudflare paid features, email services, stock media, booking tools, payment processor fees, and other third-party services may be billed separately or paid directly by the client.
Questions?
Send questions about these pages, billing, project scope, or support to Dave.
hello@davetheweb.guru