So you have an idea for a website or a web application or a mobile app that you want someone to create for you and now you are wondering what to do.

We get asked this all the time. Because of that, We created this handy little guide of what you should do to get started.


Option A: You can call someone who can explain to you what it might cost, and maybe tell you what you need. But whatever call you will make it will be a sales call: they will always have some agenda to try and convince you of their process and their prices. 

OR 

Option B: You can do a bit of prep work and then call someone – and only get the answers that you really need. You will get a lot MORE value and a lot better answers the more you know about your idea before you call anyone. 

Technology is very hard to quote, especially if it is a new idea that requires custom work as there are so many ways to execute any vision. Application makers use different pricing models for different features and technologies. Knowing what you want before you ask for a quote, and arranging it in a way that vendors want, gives you the power to get quotes that can be easily compared to each other. It also protects you from vendors potentially selling you something you don’t need. For example, some app developers charge extra for an admin dashboard and sell you an app without one for a lower cost, and then when you ask they ask for more. Other vendors may lower the cost by outsourcing all their work, or by leasing you an app – where they own everything (the code and all the data) and they just let you use a customized version of a template.   

    

You might not be able to answer some of these questions on your own. And that is fine. You should think about the following for your idea before you call anyone to help you with it.

Just knowing the questions and knowing what to expect as an answer is enough to get you a lot more value from anyone you call to get help.

#1 What do you want?

This is the most important question to answer because it determines everything else. 

Some people will answer this question with  “I want an app like this one…”  or with “I want an app that does this”. That is too vague. To get good advice and to get a good quote you need to specify more details. You need to have the details available with you, but you don’t have to share them on the first call.

You can always ask the vendor to sign a non-disclosure agreement (NDA) before you share anything with them. 

You should also have a short high-level description of your idea that you can share with anyone for a quick quote.  

 

What you really want to do is decide what features you want and list them. Different features take a different amount of effort to create, and the more effort a feature takes to create the more expensive it is to develop

To decide on features you want think about the types of users you will have and what features each user will have on each of the components of the app. 

For example, you might want to decide what features you want to have as an administrator/owner of the app. Another example of a key decision to think about is will there be a website and will any of the users be able to login into it.

i. User type examples: drivers, customers, administrators (you who will be managing the app), readers, buyers, sellers, etc

ii. Features are the actions (verbs) that each user can do on each of the. For example: buy, sell, list, download, view map, manage map, edit. 

iii. Components of the app are the web-based admin dashboard, a website, a mobile app, or a specific mobile app – if different users will have different apps – or any combination of these. You can read more about the different types in the article by our Senior Client Advisor Boris: What is an application? What is included in an application?

iv. Other considerations could be: speed optimization, the ability to easily scale it later-on, just getting a prototype first (you don’t have to get a full app right away), where will the data be stored. 

You can write these in a simple high-level list or you can go into a lot of detail. The more detail you provide the more accurate your quote will be. It is common for startups to even do some very basic designs or user flows before asking for a quote. These are very powerful ways to help a vendor understand your vision

 

#2 How fast do you want it

What is your timeline horizon? Or do you even have one?

Do you have a deadline for when you need it built or by when you need to have a prototype finished? 

For example, do you have a deadline from an investor or from a grant or when your peak season starts?

Is there a general timeline you need or want to have for the project? For example 2 weeks or 4 months.

This a second key piece of information to think about, and to be able to provide on your first call. That is because not every vendor will have the resources to be able to complete your project within your timeline. 

This question also impacts the type of technology and features that a vendor will suggest to you. Template-based websites and mobile apps with simple features can be created within 1-2 months. 

Complex custom features and websites take longer to create and might not be possible to do within your timeline.

 

#3 How much do you want to spend on it?

Cost is a very important topic but it comes third on the list because you should always start with what you want. If you have a smaller budget and you are willing to compromise you might be able to get what you want within your budget.

This topic will be covered in length in future articles. For now, I will just say that you need to have a rough budget range for what you are looking for so that you can quickly learn if you can afford what you want.

Examples of budget ranges are $5,000 – $10,000 || $15,000 – $25,000 || $30,000 +

 

When you have a budget range you can get a very quick solid quote without revealing the exact amount you want to spend.