OUR APPROACH
Understand the situation. Agree the work. Build, review and hand it over with clear responsibilities.
Discuss your situationTHE COMMERCIAL ENGAGEMENT
This is how an engagement is defined and carried through. The exact stages, deliverables and review points depend on the work and are agreed with the customer.
We discuss the desired change, who it affects, existing constraints and whether Williams is an appropriate fit. You do not need a finished specification.
A shared problem statement and a decision about the next assessment.
Review the relevant systems, data, permissions, integrations and operating constraints within agreed access. Identify assumptions, risks and dependencies before proposing an implementation. Any assessment fee is agreed before that work begins.
Findings, open questions and a practical basis for the proposed scope.
Agree deliverables, exclusions, acceptance criteria, responsibilities, review points, pricing and payment terms.
An agreed proposal and engagement terms before implementation starts.
Sequence the agreed work, review progress and test the connections. Discuss material changes to scope, cost or timing before proceeding with the changed work.
Reviewable software or systems, with test results and known limitations.
Use the agreed criteria and representative customer journeys to review the result. Record exceptions, resolve agreed issues and establish whether the scoped work is accepted.
A recorded acceptance decision, or an explicit account of what remains.
Confirm ownership, access, operating instructions and recovery routes. Include training, maintenance or ongoing support where agreed in the engagement.
A usable handover and separately defined support responsibilities.
PRICING & CONTRACTS
We do not publish a standard project price or delivery duration. A proposal is based on the agreed scope, technical dependencies, integration complexity, delivery stages and support requirements.
The proposal states the charges, payment schedule, timing assumptions and treatment of changes. Scope, confidentiality, ownership, customer responsibilities and support are addressed in the engagement agreement.
This page explains the process; it is not a customer contract. Binding commitments are reviewed and agreed separately before work begins.
Describe your projectCUSTOMER RESPONSIBILITIES
Identify the person who can make scope decisions, coordinate the people involved and approve the result.
Provide the agreed information and authorized access to relevant systems. Confirm the right to use supplied data, assets and software.
Make relevant users available for agreed reviews, check representative work and participate in the acceptance decision. Dependencies and review timing are part of the proposal.
Confirm who will operate the system, retain access and manage ongoing responsibilities. Any Williams maintenance or support commitment is defined separately.
Support coverage, response expectations, maintenance and availability commitments depend on the engagement. They are not assumed from a website inquiry. We establish the applicable contact, escalation and recovery arrangements during handover.
Support informationDescribe the outcome and the current situation. We can discuss the next useful step.