You are in control

We work with you to find out what your requirements are and what is important to you. We guide you through making the best decisions for you and your situation.

Philosophy

Our philosophy to running projects is that there should always be a focus on quality; even for a startup! As such, quality is effected by the relationship with the other factors of the project, namely: Cost, Time, Scope

• If the scope is out of control, it’s going to take a lot of time and money
• If you are limited on time then you better have money and a well defined scope
• If you have a detailed and narrow scope and lots of time, then it will be cheaper

Defining the job

After our initial consultation, we will go away and create a PRD (Product Requirements Document) which outlines exactly the work that will be done and approximately how long it will take and roughly how much it will cost.

Documentation

You may not think simple custom software or automation would require documentation — you would be wrong.

We take documentation seriously, so you don’t have to worry about who is going to work on your system and when; new users, future devs or in-house IT resources will be able to review the accessible and up-to-date system documentation that we create with you.

Mock-ups

Not always necessary, but large projects or projects with delicate user-interactions can benefit from our extensive UI and UX knowledge. We will create user-stories, wireframes and workflow scenarios as required/requested.

Getting work done

Work will be broken into “sprints” – a typical model for software development which means having smaller, more iterative chunks of work and deliverables (or mini-milestones) that work towards the end-goal in a measurable and flexible way.

Ensuring fidelity

Prototypes are built early and often; you have the chance to see your solution come to life early in the process so you can get a chance to vet the project before much investment is made.

Testing

You, (yes you!) will be responsible for testing and reviewing the work to ensure it has met all your requirements (don’t worry, we can get someone else to test it for you if you can’t). Just like a writer needs a copy-editor to proof-read her work, us developers also need some “other” eyes on the prize, and who better than you!? Actually, we find the best testers are the users who use the systems every day, especially the ones who are not very “technically savvy”.