A clear first step. A clear agreement.
Start by describing the problem and the material you already have. We define the deliverables, dependencies, timing and commercial terms before the project begins.
No public fixed price is quoted here. The proposal reflects the actual scope, review needs and third-party costs.
Ways to work together.
Choose the shape of the engagement around the work that needs doing.
Discovery and scope
Map the problem, existing tools, people and constraints. Define a practical next project and how to review it.
Project delivery
Build the agreed website or workflow, check the key paths and prepare the operating handover.
Ongoing improvement
Agree a recurring scope for maintenance, content, workflow changes or measured experiments after the initial release.
What the proposal should make clear.
A shared understanding of the work makes review and handover easier.
- Deliverables and the work outside the scope.
- Client inputs, access and review responsibilities.
- Milestones, acceptance checks and a change process.
- Development fees and separate third-party costs.
- Currency, invoicing and payment arrangements.
- Ownership, access handover and ongoing support boundaries.
A few practical questions.
Do I need a full specification?
No. Start with the problem, the current process and any material you can safely share. Discovery can help turn those inputs into a scope.
Can we start with one part of a larger project?
Yes. A focused website section or one customer workflow can be a useful first engagement when it has a clear owner and acceptance criteria.
Can you give a delivery date before reviewing the work?
A useful schedule depends on scope, access and review dependencies. These are clarified before a date is committed.
Start with one useful change.
Tell me what your business does, where the current process gets stuck, and what you want to make work better.