Briefing & Brainstorming

The first thing we’ll do before getting started on a project is to do some basic requirements analysis.

You may want to come up with some new ideas for software tools, or you may already have a good idea of what you want – this phase in the process is to help us start to understand and document the scope of the development task.

This typically involves a series of face-to-face brainstorming or briefing sessions where we start making notes and solidifying ideas.

If you don’t have a brief in place already, we’ll aim to have an overview of the project requirements ready by the end of this phase.


The next task is to write some specification. During this phase, we aim to pin down exactly what your app will do in a detailed, comprehensive set of documents.

We can typically include the following in our spec:

  • Wireframes (functional requirements)
  • Data Model (functional requirements)
  • Use Cases / Business Rules (functional requirements)
  • Software Compatibility (functional requirements)
  • Acceptance Tests and Test Data
  • Suspected Edge Cases
  • Proposed Software Stack
  • System Design Overview
  • Testing Approach

Scheduling and Resource Allocation

Now that we know what we’re building, we can quote a fixed cost for the development of the app.

As part of the costing, we can put together an estimated development schedule that breaks the tasks down into a set of milestones. This will give you a good idea of how long the project will take to complete.


This is where all the good stuff happens: we work through our development schedule, implementing the requirements that we defined in the specification phase.

We value communication and working closely with our clients. We aim to produce a write up of our progress every 2 weeks and release regular development versions of the app for you, keeping you informed on exactly where the project is at.


At this point we should have the first ‘alpha’ version of the application ready. As well as writing automated tests during development, we also conduct some manual quality assurance and user acceptance testing. This might involve publishing a version of the app to your team or a group of beta users so that they can feedback on potential issues.

By the end of the testing phase, we expect to be able to verify all the acceptance tests defined in our specification.

Maintenance and Support

We love to see the software that we helped build grow, and are always keen to stick around to maintain and support your app. Our yearly maintenance package includes a number of days set aside for bug fixes, as well as tech support.

We have a daily rate of £300 and an hourly rate of £50.

Check out our Working Practice Guidelines for in-depth documentation around how we enforce quality in the work that we do.