Practical guide
Clear payments for your web projects
Break discovery, development and delivery into requests your client can understand.
Reviewed on
Tie each request to a milestone
For a website or app, separate discovery, a testable version and final delivery. Describe the milestone’s scope: pages, features, acceptance criteria and exclusions. A request should help the client recognize the stage they are paying for.
Keep secrets out of attachments
A progress report or quote often provides enough context. Do not attach environment variables, passwords, production dumps or user data. Share technical access through an appropriate channel separate from payment.
Maintenance without automatic charging
A scheduled request can prepare the next maintenance payment. It does not turn the service into an automatic debit: the client confirms each payment. The timeline separates received payment, scheduled transfer and bank payout.