1

Introductory Meeting

We believe we can build the best products when our engineers, designers and customers work together as one unified team.
We will walk you through our engagement process during the introductory meeting to learn how we can best help you. We will learn about your project, objectives, and target users through this process and will identify all the critical considerations to develop the solution you have in mind.

2

Discovery Session

We will do our research and gather information about your target market, end users and competitors. We will thoroughly analyze the project requirements to discuss your architectural options, UI/UX design process, development roadmap and cost estimates.

3

Product and Architectural Design

In this phase, we again go back to our whiteboards based on your feedback. We internally evaluate all technical and non-technical aspects of the project, including usability, scalability, security, reliability, performance, and budget constraints.

We will then, present you with a final overall architectural design which includes the choice of frameworks, tools, platforms, infrastructure, software components, storage, interfaces, communication protocols and many other aspects of building a rock-solid software solution.

We will prioritize what features to include, what functionalities are essential in the Minimum Viable Product (MVP) and what to keep in mind for future improvements of the solution.

4

Roadmap & Final Proposal

We will present you with a detailed proposal that would list deliverables, scope, backlog, sprints, milestones, customer and developer expectations, time and budget estimation, communication and change of scope protocols.

5

Development Kick-off

We start with UI/UX design – and feedback – iteration(s). We will provide you with wireframes and then move on to start UI designs and usability testing.

We set up the DevOps environment, adopt a project management methodology of your preference (e.g. Scrum or Kanban) and start the development-demo-feedback iterations.

We also configure our Test Driven Development, peer code-reviews, continuous integration and team collaboration and communication tools. Lastly, we schedule weekly progress, demo and feedback meetings as well as pre-launch and beta releases.

6

Launch!

Software development is an ever-evolving process. Launching the MVP is just another step towards building a solution that your customers truly love, and it does not end here. We need to plan the next steps to
maintain the MVP and need to plan for:

Monitoring: Usually for errors, up-time and performance

Analytics: User interactions, A/B testing

Experience Improvements: Continuous end-user behaviour learning, improvement iterations and bug fix cycles