HomeHow we work
How we deliver your project
Every project follows the same stages in order. We assign responsibility, document the output and agree a decision at each stage before the next one starts.
Most projects go wrong before development when scope is unclear, budgets have not been modelled or decisions lose continuity. We have seen these issues in our own projects and elsewhere. Our delivery process applies that experience to reduce avoidable problems from the start.
We document your scope and provide a proposal with deliverables, dates and costs. You sign an agreement before work starts. The same project lead stays involved from your first conversation through support after launch. At the end of each stage, you receive a written output to review before we begin the next one.
We follow every stage in order to control project costs.
01. First conversation.
We sign an NDA if you need one. You explain your business problem, users and constraints. We ask questions to assess whether our team is right for the work. This first meeting does not involve selling you anything.
02. Proposal.
Our project management, design and engineering leads review your requirements together. We recommend a solution with the same care we would give our own budget. You receive written scope and deliverables, with timelines and costs. Resolving unclear requirements here prevents extra costs later.
03. Agreement.
We resolve your questions, then turn the proposal into your contract. It identifies the project lead responsible for delivery on our side.
04. Analysis.
Our engineers question the requirements and learn your business goals. They group requirements as operational, functional or technical to keep the analysis efficient. You receive a solution designed to meet both your brief and your business strategy.
05. Strategy.
We develop a long term strategy for development and marketing, either separately or within your build. This looks beyond launch, because most applications are assessed in year three.
06. Prototyping.
Before development, we provide design mockups and an interactive prototype of your application. You compare them with the specification and either approve them or request changes. Our interface designers check that the application is intuitive before we write code.
07. Build.
We build prealpha, alpha and beta versions. Prealpha is deliberately rough and incomplete. Alpha includes all features and server connectivity. Testing improves the beta before release.
08. Testing.
We assign one QA engineer for every developer. From prealpha onward, each version is tested manually and with the automated tools we have built over the years. Testing during development keeps us on schedule, including quality work.
09. Evaluation.
We submit the release candidate for user acceptance testing. We can test it with you, using your use cases and our test protocols. After approval at every stage, we deliver the application with its technical specification document.
10. Support.
After launch, our support and development packages keep your application safe as web and mobile environments change. We can also develop its next version with new functionality.
Three commitments throughout every project
You have one project lead who makes delivery decisions and stays available for the full duration of your project.
We document the scope, budget and timeline before development. Any change to them is recorded before we write code.
Our QA team tests during development. Its sole job is finding faults in the software that we build.
Discuss your project delivery requirements.
Share the problem and its constraints with us, and our project team will reply to discuss it.