Common questions

We start with a short conversation about the audience, the problem and the constraints. If the fit is right, we write a scope with deliverables, review points, responsibilities and an estimated schedule before any paid work begins.

Yes. We first review what is useful and where the current system creates friction. The proposal distinguishes work we can retain from work that needs to change, with ownership and access agreed before implementation.

We do. A focused discovery or prototype engagement can answer a specific question before a larger build. The aim is a clear decision and useful deliverables within an agreed budget.

Each phase has a named decision maker and a focused review. We collect feedback in one place, explain the trade-offs and record approvals so the next stage begins with a shared understanding.

The project agreement defines ownership and any third-party licenses. Our standard handover includes the agreed editable design files, source code, content and operating notes after the engagement’s payment terms are met.

We can agree a separate care plan covering a defined amount of review, maintenance or improvement work. Response expectations, exclusions and the process for requesting changes are documented before the plan starts.

We agree permitted data and providers before using an AI service. Sensitive client material is not sent to a model by default. Access is limited to the people who need it, and evaluation includes failure handling and human review.