Practical billing expectations
Small advice or first-response work
Project work
Retainer or ongoing work
Hourly or on-demand work
Third-party costs
Scope matters more than package names.
A WordPress fix, SEO review, Cloudflare cleanup, AI workflow, or managed tech issue can be tiny or complex. The billing model should follow the actual risk, access needs, urgency, and amount of diagnosis required.
If something is unclear, ask before approving the work. Written questions are preferred because they leave a clear record of scope, assumptions, and next steps.
Common questions
When is payment due?
Payment timing depends on the work. Small tasks may be billed immediately. Projects may require an upfront payment or milestone plan. Retainers are normally billed for the agreed period.
Can you give a fixed price?
Yes, when the scope is clear enough. If diagnosis is needed first, the sensible first step may be a smaller paid review before a fixed implementation price is possible.
What if the work changes?
If scope changes materially, the billing expectation should change too. The right approach is to pause, explain the change, and agree the next step.
Who pays for external services?
External costs such as hosting, domains, plugin licenses, APIs, ads, or third-party tools are normally paid by the client directly unless another arrangement is agreed in writing.
Ask before work starts.
If a billing question affects scope, timing, cost, or responsibility, use the email button before the work begins.