How we work
From the first review
to a working release
Each stage produces something you can review: priorities, a project brief, working features and a release plan.
The stages of a project
Review the current setup
We look at the task, existing website or tools, sample data and technical dependencies.
You receive: priorities and a list of questions that need resolving.
Define the work
We set out the features, data work, content and access needed, with review points for your feedback.
You receive: a brief with deliverables, an estimate and a delivery plan.
Build, test and review
Working pages and features are available for review in a separate environment where the setup allows. Imports and integrations are rehearsed with sample data.
You receive: a test version and recorded checks against the brief.
Release and hand over
We prepare the final transfer, backup requirements and switch-over steps, then document how to operate the delivered system.
You receive: release instructions, access and clear maintenance responsibilities.
Before release
Check the tasks
people will actually use
Customer journeys
Navigation, forms and mobile layouts. For stores: product options, checkout methods, stock changes and order emails.
Data and permissions
Imported fields, media and record relationships, plus who can view, edit or export information in an application.
Connected tools
Field mapping, repeated events and failed updates. Release checks also cover configuration, backups and the final transfer sequence.
Planning the work
How are the cost and schedule agreed?
The estimate covers the features, data work and integrations in the brief. It also records when content, access and feedback are needed from you. An unresolved technical issue may need a separate investigation before the full project can be estimated.
What if the project needs an additional feature?
We describe the change and its effect on the estimate and delivery plan. You review those changes before the additional work starts.
How does the existing site stay in use?
Development uses a separate environment where possible. For migrations, the release plan specifies the final data transfer and any editing or order pause needed to avoid missing new records.
What happens after launch?
Handover covers operating instructions, access and the tasks your staff will perform. Hosting, backups and update responsibilities are recorded. Ongoing maintenance and further features can then be arranged around the system in use.
Discuss your project
Describe what happens today, what should change and any deadline or budget constraints.