Existing product audit
Describe the main usability or technical problems and the change you need.
Contact
Tell us about your project.
Briefly describe the goal, users, current solution and required functions. The first conversation will clarify the open questions and what discovery is needed before an estimate.
Send your enquiry
A useful starting point
New website or system
List the users, primary actions and content required in the first version.
Website rebuild
Identify content, URLs, data and functions that must remain.
Integration
Include system names, API documentation and the required data flow where available.
Continued development
Share the current technical state, immediate issues and accessible materials.
After the first conversation
Clarify the goal
Review materials
Bound the first stage
Explain dependencies
Agree the next step
Common questions
How much detail is needed in the first enquiry?+
The goal, current situation and primary user actions are enough. Details can be developed during discovery.
How is development cost estimated?+
An estimate needs bounded functions, content, integrations, dependencies and a delivery model, so it should not be set before the brief is understood.
Can we start with an audit?+
Yes. An audit is useful when the current product, technical state and priorities must be understood before development.