A project’s defining factor is its’ budget, whether the project is a house, a holiday or an app. You always build to your budget. If you don’t tell your builder/travel agent/developer what your budget is, they don’t know where to start.
There are houses with in-built coffee machines and views and there are houses that you see on Hoarders. Most people can value a house on the spot to within 20% accuracy, but it’s rarely the case with web projects.
In our experience budget is the least favourite topic when discussing a new project. Nobody likes talking about money, but unfortunately that’s generally how you pay for things. The conversation is often left until the last item in the meeting or danced around without any definite indication.
Me: What’s your budget for the project?
Prospect: Oh we don’t really have one. We were hoping you could tell us.
Me: Well, we built something like this for the Government a few months ago for $80,000
Prospect: What!? Oh no. That would bury our business?
Me: If we changed X and Y and moved Z to Stage 2, we could cut that down to $50,000
Prospect: Oh that’s still way out of our range. We couldn’t spend more that $20,000 on this.
Me: So … $20,000 is your budget? Great! Let’s find a solution within that budget.
Often the worry is “if I tell you my budget, that’s what the project will cost”. There’s no need to worry – because you’re absolutely right! That’s probably about what it will cost.
Stick with me. It gets better.
Your budget will guide the solution. It’s like shopping in a guitar shop. You come in with that sheepish grin on your face and a pocket full of cash. You tell them your budget and they show you the instruments you can afford. After a few more questions about the type of playing you like, they will guide you to some ‘pretty sweet axes’. If you don’t tell them your budget, you’ll be stuck in the custom section for two hours falling in love with things worth more than your car.
With web projects in particular, there are always numerous ways to solve a problem. A clearly defined budget tells your developer:
and, if they are working with you rather than for you,
The budget is critical to the solution – not necessarily in a limiting way, but it determines how the project is approached.
With one simple question, we already have a better conversation – “How do we solve this problem within this budget?” See? Not so hard.
It doesn’t need to be an awkward conversation. If it’s up front initially, your web team can ask better questions and you can find a solution together. Most of the apprehension lies around not knowing the value of vague things like strategy, design, development or reliable relationships. That uncertainty creates fear that you might get ‘ripped-off’.
Having been in the industry since 2002, the most common cause of web project failure occurs when either the project is badly managed or the budget isn’t clear from the start.
A good way to avoid getting ‘ripped-off’ is to work with a company that has come recommended. Ask around for recommendations. Do some research and find a style you like. You could even call a business and ask who did their website. They are more often proud to tell you. Find out if the project went smoothly. Then you can worry less about getting the wool pulled over your eyes.
Estimates will be loosely based on an hourly rate. The development team will know roughly how long each element will take based on past experience, but there are other factors involved too. For example;
Most firms will either say no thanks, or somehow make it work.
So, next time you go hunting for web services follow these 3 easy steps:
You will almost always get a better result with this approach. If not, you’ll have saved yourself and your prospective web team a whole lot of time and effort and you can move on.Posted by Chris Garrett on 2 March 2015