The first step to knowing what the software will cost is discovering the problem statement. This is done in conjunction with our expert technology consultants. The Brief meeting is a 2 hour workshop between your team and our consultants which provides the necessary information to create a Brief document.
This allows us to prescribe a timeframe for step 2 (scoping). We find that problem statements can fit within three buckets; small, medium and large. The size varies based on the complexity of the problem and the information already known. Our consultants will recommend the scoping bucket after a brief workshop.Okay, what's next?
During a formal scoping phase (where the timeframe has been recommended after step 1) the focus is on finding a solution. The WorkingMouse product success team uses the discovery kit to create a backlog of requirements in the form of epics and user stories.
At the end of scope we conduct a scientific estimations process. The outcome is a timeframe against every piece of functionality so that you as a customer can make an informed decision of what to prioritise as part of the MVP.
*the IP of these artefacts remains with the client and can be used outside of the engagement with WorkingMouse.Okay, what's next?
During development we build in iterations. The functionality is then demonstrated and reviewed by the customer after every iteration. You can fix the time and the cost (by varying the scope) after step 2. This means there is certainty in the price.Okay, what's next?
Support is provided by Rogue Two. They offer a basic support model which keeps costs low ($500 per month) and gives control to the customer. This entitles customers to log tickets, with each ticket triaged using a two hour time-box. As the development work may fall outside this timeframe we would recommend saving 20% of the development cost to set aside for support.
Be sure to take into account other operational expenses. Services like hosting and App Store costs, while small should be included when budgeting.Get in contact