Our approach
We get to know how your business works, talk through the options with you and build what the project needs. You work directly with the people making the decisions and doing the work.
Start a conversationStraightforward conversations
You can ask a rough question, share a concern or think something through with us. We explain the options in plain language and give you a recommendation, including the reasons behind it.
We learn enough about your business to contribute to the discussion. If an existing tool can do the job, we will say so. If we think a proposed feature will create more work for your team, we will explain the concern and work through an alternative with you.
Regular updates and walkthroughs keep the conversation going. We agree a practical rhythm with you, record the decisions and make clear who needs to do what next.
A useful project update tells you
Judgement, scope and responsibility
We talk to the people who will use what we build. We look at the steps they take, the systems they rely on and where things get difficult. You can bring an unfinished brief; working out what needs to change is part of the work.
What you have: A shared understanding of the problem, the users and the constraints.
We work through the options with you, including what your existing tools can already do. We explain our recommendation, the trade-offs and what can wait. The proposal records the scope, cost, responsibilities and assumptions, so you can make an informed decision.
What you have: A written scope and plan, with the outstanding questions made clear.
Trying an early version often brings new ideas. We discuss how a change affects the work, the budget and the schedule before agreeing it. If a dependency or risk puts the plan in doubt, we raise it while there is still time to act.
What you have: An agreed next step, with its effect on the project understood.
Define the requirements and review the existing systems. Agree the scope, cost, responsibilities and schedule before development starts.
Review and test working software with your team. Agree how any scope changes affect the budget and schedule before proceeding.
Plan the launch, train the people who will use the system and hand over the code, accounts and documentation.
Complete the agreed launch checks and support. Arrange ongoing maintenance or further development with the responsibilities and costs agreed in advance.
For projects with several moving parts, the plan, updates, files and decisions stay together in a shared project workspace.
More about working togetherBuild it together
A working preview gives everyone something concrete to discuss. We use reviews to check that the website, integration or tool makes sense to the people who will rely on it.
01
Review the design and try the developing website or tool at agreed points. We walk through the important journeys together, explain what is ready and make it clear what still needs work.
02
We bring the relevant people into the decisions: sales, accounts, operations or whoever will use the result. We plan data, content and connections alongside the build, with clear owners for the information and access needed.
03
We check the agreed journeys with representative tasks and data. That includes the permissions, integrations and exception cases the project depends on, followed by a review with your team before launch.
04
Launch includes preparing the people who will run the system. We agree the training, documentation, account access and aftercare as part of the scope, so you know how to use what has been built and where to get help.
Beyond launch
Once your team is using the system, you learn what needs attention and what would make the next useful improvement. We can keep working with you, carrying the knowledge of the business and the build into those decisions.
You don’t need a brief or a solution in mind. Tell us what’s proving difficult or what you’d like to improve. We’ll explore the options together and agree where to start.