Begin with the problem customers or staff encounter. Send a site address, the task that needs improving and an anonymised example if one helps. Keep passwords and customer records out of the first enquiry.
1. Agree a practical scope
We discuss the desired behaviour, existing tools, content, approvals and constraints. A proposal identifies the included work, business decisions and dependencies. Pricing and timing depend on that scope; this site makes no fixed-price or delivery-time promise.
2. Review a working journey
You review a representative path before every page or feature is completed. Feedback is most useful when it names the page, problem and intended answer. For Philippines teams, meeting windows and time zones are agreed explicitly with our US-based delivery.
3. Test the everyday work and exceptions
Acceptance may include phone and keyboard use, content editing, an enquiry handoff, incomplete information and a connected-service failure. The exact tests follow the project. A browser preview cannot prove every live dependency works.
4. Release and hand over
Publication responsibilities, recovery, account ownership, documentation and ongoing support are agreed. The business approves its claims, policies and operating rules. Qualified local review is needed where legal, tax or regulated requirements affect the work.
Read about remote project working or tell us what you need.