Keep your costs down without sacrificing control.
Cost can be a prohibitive factor when deciding whether to build custom software or implement an off the shelf system. The MVP engagement allows you to keep your costs down while gaining all the benefits of owning the intellectual property of your application.
Scale your business fast & grow your revenue.
With custom software you can scale up knowing you have an application that can scale with you. Whether that means upgrading those time-consuming spreadsheets or monetising a new product and earning that all important recurring revenue, an MVP can help you reach your goals.
Validate with user testing.
User testing is completed during the 5 day workshop using a hi-fi, interactive prototype. We send this prototype out to a selection of your users and gather as much feedback as possible. This feedback is then collated to inform the final look and feel of the MVP.
Detailed Product Backlog.
A product backlog tells your development team what will be built. This creates the direction and structure you need to deliver a successful project. With estimations against every piece of functionality in the backlog, you can prioritise it to get the greatest possible value for your MVP, within your budget.
When is MVP
best for you?
The MVP engagement is quite versatile. But there are situations where the POC or Product Development offerings may better suit your needs.
We’d recommend MVP if you match one of the following points:
- You’re looking to move quickly and are negotiable on the scope of the project.
- Your solution is technically feasible and you’re ready to commercialise.
- You only need one of either a web platform or a mobile app.
At A Glance
3 day workshop
+ 2 weeks development
- Web platform only
- AWS set-up
- One integration
- One user group
- Hi-fi designs
- Lite backlog
- Automated test plan
- Three months Product Success consulting
5 day workshop
+ 4 weeks development
4 week scope
+ variable development
- Web and/or mobile app
- Any hosting environment set-up
- Unlimited integrations
- Unlimited user groups
- Discovery interviews
- User journey maps
- Hi-fi prototype
- Unmoderated/Moderated user testing
- Custom UI
- Manual test plan
- Three months Product Success consulting
Let us tailor a package for youContact us
Read more about MVP
Apply to Secure Your Spot
We take on a limited number of MVP engagements every month. Projects are scheduled on a first in, best dressed basis. It’s highly recommended to apply as soon as possible, in order to secure your spot.
5 Day Workshop + 20 Development Days
Start rapidly prototyping your MVP over the course of a 5 day workshop. This leads straight into a lean 4 week build to get you a product ready to start testing!
An MVP should be lean enough to only include the bare minimum needed to validate the solution. However it still needs to be good enough to leave a positive impression on your early adopters. There is a range of theory on how long it takes to build an MVP but we’ve found a 5 day workshop and 4 weeks of development is enough time to produce a valuable application.
This structure emphasises the importance of varying your scope. By staying flexible on your features but concentrated on your problem statement, your MVP will be valuable. The last thing you want from any engagement is to come out of it with something you and your users don’t find valuable.
Apply for the MVP engagement and benefit from rapid workshopping with four-weeks of fast paced development.
Up to 2 API integrations
An API (application programming interface) integration is how different systems communicate with each other. Connect your applications to reduce data entry, automate tasks, reduce human error and save costs.
An API (application programming interface) integration is essentially how different systems communicate with each other. If system A needs to send data to system B then they will do so through an API integration.
An API reduces the amount of data entry across your software landscape. Secondly, you can trigger automations in a different system based on actions taken on the MVP. For example, if you create a job on your new job management MVP, you may want to prompt an invoice to be created in your payroll system. Lastly, you may want to leverage pre-existing functionality built in another product. This is done through an API.
Integrate with up to two existing systems and create your unified software landscape.
A product backlog tells your development team what will be built. This creates the direction and structure you need to deliver a successful project.
It helps align every stakeholder on what has been built and what is likely to come next. A full product backlog includes a description of the feature to be built, alongside implementation steps, acceptance criteria and scientific estimations.
Acceptance criteria ensures that the whole team knows what is expected from every requirement. For example, this feature is done when a user can create an account and a record is created in the database.
With a product backlog you gain the gift of visibility. You know what has been built, what will be built and how long it will likely take. If for any reason development must stop, the product backlog can be picked up by another team who understand the state of the product.
Up to 2 User Groups
A user group is a type of user likely to interact with your application. With multiple user groups you can connect one audience, with another.
Let’s say you built a health monitoring application catered to doctors and nurses. Doctors may use the application for one purpose, and nurses use it for a different reason. This effectively means you have 2 End User Groups — Doctors and Nurses.
An admin user group is how you control the application. If your prices ever change or you need to export data into a CSV format, those actions are generally performed on the admin side of your application.
An MVP focuses on up to two user groups while still providing admin control. Creating a product that connects multiple user groups is in many circumstances necessary to solving your problem.
2nd Level Priority for Service Desk Support
You won’t be left stranded after the build is done. Support is provided to save the day, with MVP products getting second level service desk priority.
A service desk is the conventional way for a product to be supported. For example, a bug is discovered on a particular device type, using a certain browser. Through the service desk, the product owner would log the behaviour that led to the bug as well as the device and browser that they were using (or for a mobile app, the version of the application).
This enables the support team to immediately replicate the bug that you discovered. Without that information, there is plenty of back and forth that delays the resolution time. All MVP projects are prioritised second for service desk support, before POC’s but after Product Development engagements.
Web or Mobile App
It’s impossible to great at everything. Avoid diluting your focus by concentrating on a single platform for your MVP. The best part, you get to choose what that platform is!
A web platform is highly accessible - anyone with access to Chrome or Safari can use a web app. It comprises a front end (what you see) and a backend (the database and everything that happens behind the scenes). Its versatility and accessibility makes it the best platform to test and validate any solution.
A mobile app on the other hand is only accessible on mobile devices. The key advantage is that it can utilise your phone’s native device settings (like your location or microphone) which can lead to a much better user experience. Build an MVP and choose the platform that helps you best connect with your user base without diluting your focus.
AWS Environment Setup
Amazon Web Services (AWS) is the worlds largest cloud hosting provider. After creating your account a specialist DevOps engineer will setup your public cloud environment.
The setup is a dual-node which means you will have a backup database instantly kick in if the application or server crashes.
The server is backed nightly meaning your application’s data is safe and will not be lost.
Lastly, it is scalable and optimised, so your hosting can grow as your user base does. You’re not paying for processing power when its not needed.
This setup is the outcome of years of effort. If you were to hire a specialist DevOps engineer or third party hosting provider to create your AWS environment it would likely cost tens of thousands of dollars. This is included in the engagement so you can start testing your application.
A production release means your application is live! It has all the benefits of going through testing environments and gives you a clean slate to start growing your user base.
When building software there are usually multiple environments that an application will progress through. A production environment is the final staging environment and this is how your users will interact with your application.
Most commonly there will be a beta environment (beta.yourapp.com.au) that is used until a larger development build is completed. The MVP engagement ensures that your application is ready for real world users with a production release.
A full production setup gives your MVP that extra credibility amongst your early adopters and promoters. You have the freedom to test and validate your MVP on your own cloud environment, knowing you own and control your data.
Manual & Automated Test Plan
Testing is the ultimate quality control mechanism. With manual and automated testing, there are contingencies and quality checks for every piece of functionality in your app.
Testing comes in two forms, manual test plans and automated testing. Even though there is an element of speed when developing an MVP, manual test plans are still a key inclusion.
A manual test plan will ensure that a developer has linked each requirement to a correlating test, improving the quality of your product. A key benefit of the Codebots technology that we use is that it comes with out of the box automated testing. This means that the bots are testing their own code quality to ensure it is functioning as expected. Your team is able to build fast while knowing that automated tests come out of the box.
Don’t be a cowboy. Benefit from an offering that prioritises quality with thorough testing plans.
Unmoderated user testing
With unmoderated user testing an expert product designer will validate your prototype through feedback from your target personas. This reduces the risk upfront of building a solution people don’t want to use.
You can build the best product in the world, at the end of the day if no one uses it, then your product is destined to fail. User testing is the closest you’ll get to being able to read your user’s mind.
User testing is completed during the 5 day workshop using a hi-fi prototype. The key benefit is that you’re getting feedback early and often on the product from people likely to use it. It also helps the team get into the mindset of your user — who are they, what do they like, what frustrates them?
Given the tight timeframe, unmoderated testing is favoured. This means there is no one present to guide the user through the prototype. This has obvious upside – there is no one present to influence the user with their bias.
A high-fidelity (hi-fi) prototype is your ultimate safety net. By creating an asset that shows exactly what your app looks like and how users interact with it, you can remove ambiguity and mitigate risks before starting development.
A prototype is a representation of the product in static form. This entails a product designer mocking up each screen of the application and linking each page based on the navigation.
For example, a dashboard page is designed. By clicking on a graph on that page, it pulls up more specific data that has been used to create that graph. The application isn’t actually built or functioning, it is a series of screens linked together to give the user a sense of how it will look and feel when built.
There are so many benefits to starting with a hi-fi prototype. It visually shows you and the development team what will be built. Text is great to an extent – sometimes it’s more important to see it. It also allows the team to conduct early-stage user testing. Start your project on the right foot with a hi-fi prototype.
3 Months of Product Success Consults
Just because something is built, doesn’t mean it will succeed. A customer success consultant will walk you through activities and platforms that can help you find your product market fit.
This is the difference between building a product successfully and building a successful product. In order to effectively measure the success of your application, certain metrics need to be captured and reported on.
With a customer success consultant, you’ll benefit from a domain expert that will help manage and monitor your progress towards your goals. Because your product is unique, so too are the measurements of success. You’ll be stepped through a goal setting activity which will help form the basis for your consults going forward. It’s common for clients to use these reports for their board meetings and/or investor updates.
In simple terms, from most important to least important. It’s vital to continuously review it as it forms the order that the features will be built. So, when the four weeks of development concludes, it is the features at the bottom of the backlog that don’t form part of the MVP.
Yes. This is the purpose of the MVP engagement. By building a minimum viable product and testing it, your market will tell you what to build next.
Yes. While the aim of the MVP engagement is to be flexible with your scope, if it is critical that a feature form part of the MVP then you can extend development to include it in the production release.
There will be multiple opportunities to review your MVP. At the end of each iteration (two weeks of development) there will be user acceptance testing. This is your opportunity to review the features built and re-prioritise the backlog.
An MVP is not your entire roadmap or backlog. The minimum viable product is the leanest version of your product that will solve your problem statement. If you need your entire backlog built then the Product Development engagement may be a better fit.
You will be billed in weekly increments on the Wednesday preceding the start of the engagement, with 7 day payment terms.
Maybe. It’s a difficult question to answer now since we don’t yet know what you want. Chances are, if you have a big list of requirements, you won’t get everything in an MVP. We will know more at the end of the five day workshop and we’ll guide you on what is reasonable to expect. If you’re not happy at that point in time, you can end the engagement (see the FAQ below for more details).
There is a natural break point at the end of the workshop if both parties aren’t aligned on realistic objectives. In the event of a misalignment, the engagement can be terminated after the workshop and only the days worked are billable.
Well that’s an easy one for all the basketball fans out there. It’s Kevin Durant’s mum.
How might we better protect tradies who have had their tools stolen?
Tool Protect needed to quickly validate their MVP with real users. A mobile app available on iOS and Android helped them better connect with their user base. The app was based around a central workflow which saved and retrieved an individual tools serial number. This quickly allowed the user to generate a police report and meet the insurance requirements for a stolen asset. The app has since been featured on major news programs across Australia.
How might we help construction specialists find short term job opportunities?
The application was a result of the parent company, HTD Australia recognising that the problem that existed in their business, likely existed across the broader construction industry. Onsider is a web application which enables Project Managers to search for candidates or request Onsider Management to recruit an Onsider on their behalf. Company Admins are able to create Project Managers who then hire Onsider’s on the company’s behalf.
My Career Groove
My Career Groove’s vision is to fundamentally redefine the way talent and recruiters are matched. They came to WorkingMouse seeking a platform to validate, automate, and build traction for their process. The MVP will allow users to complete their profile to best receive a recruitment package match, upload their resume and link to the online user profiles. The project was structured around the fixed cost, variable scope methodology in order to test and validate the MVP.
Apply to start your MVP