How we do Roadmapping
Why you're here
Whether it's v0.5 or v3.0, You need a web product built, and you don’t have all the technical skills required to get to first launch. Your product needs a robust platform to handle both changing needs of your team and also grow with your business.
You want software you're proud of, and also need it live before your competitors. A platform that's reliable, thoughtfully architected and adaptable, able to support each role through software. A platform able to manage complex integrations through user-friendly workflows. You need your users to love the product.
And you'd like to understand what it would take to build and launch it. Cost, features, and time. Enter Roadmapping.
What is Roadmapping?
Roadmapping is, at its bare minimum, laying out a plan for your project.
It's a discovery phase, during which a thoughtful outsider (us) gains perspective on your idea. Here's what you get:
- Determine core features for MVP (Minimum Viable Product)
- Lay out project timeline and technical recommendations
- Identify high or costly risks to implementation
- Deep dive on your business values and translating those into the software foundation for your product
- Deliverables: a refined estimate and spreadsheet breakdown, meeting notes, recordings, and a proposed timeline to completion
- Bonus: What it's like to work together
What does the process look like?
1. Regular meetings
We usually meet weekly or twice a week, over 2-4 weeks. This depends on your project size and complexity. During these calls we carefully examine assumptions made, gather requirements, investigate libraries and platform support, and break features down into more manageable, detailed pieces.
2. Research and strategize
Between calls, we research any highly complex or risky features (often those not available through 3rd party libraries). We discuss and clarify potential solutions at length, and evaluate strategies to accomplish the business goals with the usual tradeoffs: time, budget, resources. We will ask you to elaborate or provide materials that help us understand the product goals, how features are intended to work, industry background, and more. This helps us estimate, design, and build keeping in mind with what's most important.
3. Estimated time, cost, and technical architecture
At the end, you receive all our meeting notes and research, along with any recommended strategies for moving forward. This deliverable can be taken to any consultant who would build the project for you. Although clients generally choose us to do the implementation, you are not locked in to do so.
4. Get to know the team
During this process, we also get to know you and the product, and you get to know our people. Toghether, we are able to plan ahead to assign the right consultants to architect, design and develop the project.
I'm interested! What's next?
If this sounds like a good fit for you, Contact Us to schedule an initial call.
Typically, we ask for a deposit upfront, and the remainder is due after delivery. The cost is usually a flat rate determined upfront, and highly depends on the size of the project, whether Uplift creates wireframes, and any other requested deliverables.