Entrepreneurs, Startups, and Companies come to us with all different types of backgrounds and experiences. We’re quite comfortable talking about almost every type of modern technology (We live, eat, and sleep it!) but know that generally things like apps, websites, or improving existing systems are what we’ll probably be talking about.
We’ll start off with a call or two, before we setup an in-person meeting. In our call(s) we will try to understand what you’re trying to build, who it’s for, and why you’re doing this. All this information + other information that we request will help us have better conversations going forward.
During our first in-person meeting, we typically do a bit of white-boarding, go over our process, and see if it’s a potential good fit for the both of us.
Regardless of what you’d like to make, we will challenge your assumptions. We will discuss if the product HAS to be built on your preferred platform (Native iOS or Android, Web, or potentially all 3), what your customer acquisition strategy is, and really just try and understand how we can position your business in the most competitive and best way possible.
Ultimately, we need to understand the two following things:
- Why are you building this?
- Who are you building this for?
- What are you trying to prove with this product?
- When do you want this to be launched? (Yesterday’s not an answer :P)
- Where will users be able to find this?
- What does success look like?
- Is it a specific # of sales?
- Is it higher engagement?
- Is it just product functionality, What is it?
After we understand these two things and after our discussions, we should both be on the same page. Don’t forget, we’re the product development, design, and technology experts, but you are the domain expert. We mesh those things together to make products that win!
After we understand what you’re trying to build, who it’s for, and why, we will send over a range in an estimated proposal. Why a range? We’ve built apps for too long to know that it’s impossible to give you anything but a range for the first build out of a new product. Morever, we haven’t done a proper product development sprint by this time, so we really just have a firm “idea” of the end product.
Here are a few things that might change over the months when we’re building your product:
- Competitive Landscape: Did a competitor launch before you? This is a great time to learn from their mistakes, and to see what is done well, or poorly for their product.
- Internal Business Needs: Depending on the estimated build time, your company might be introducing a new product line, or shifting its strategy.
- New Features OR UI/UX: It’s very likely a new app or product will launch that has a feature or UI/ UX that you prefer over what we agreed on months ago.
- New Platform specific things: Apple and Google introduce new product features all the time (Apple Wallet / Health, Pre-Built Social Sharing tools, etc) as well as other SASS apps we use.
- 3rd Party Apps: During our initial estimate, we might think we need to build custom analytic tracking (for example), but a paid service might come out that would eliminate this.
For all these reasons and many more, we will deliver a range. We do not ‘sell’ fixed bid projects, since all of our projects are custom made. It’s simply Effort * Rate.
If our two teams come to an agreement on this, then we will deliver a proposal. All we ask of our partner is that they sign the proposal, and send us a deposit (which is a % of the total project) This % is put into escrow, and is take out from the last invoice (or two).
We require a deposit because it’s the only way that we can properly allocate our team effectively for projects. Once we accept your deposit, we ‘lock-in’ that time period for the members of our team who’ll be working on it.
Yeah! Now that we’ve completed all of that, we will setup our sprint design meetings, and will have a rough roadmap of everything to come.