SMASHING FOUR STRATEGY FREE
Is it possible you will spend time working out the features required only to learn you haven’t won the work? Will you have given the client a free and detailed breakdown of their project for free? Absolutely, but this is the just nature of sales, some you win, some you lose - don’t get disheartened, try to get feedback from the client on why you didn’t win and use the advice given to refine your next estimation. Thorough web project estimating takes time, but it tends to inherit all the same rules that apply to coding, the more thorough you are, the more accurate you’ll be. If you’re not able to convince the client to pay for this initial functional planning stage, and can’t find a suitable expert in the technology, but want the work and have confidence in your ability and passion to learn what needs to be learnt, then the best advice is to do some initial research in your own time and just take your best guess! Estimating Takes Too Long You, and the client, get to find out how you work together, giving both the opportunity to part company before being locked into a lengthy project. You have completed foundation learning of a technology you previously didn’t know that you can sell to new clients, you generate revenue and the client has a comprehensive specification they can use in their tender process. You give the client confidence, have a much clearer understanding of the work required, re-estimate and are hired for the rest of the project. This way you can research the unfamiliar technology and deliver a functional specification to the client. Try to negotiate with the client a mini-project where you are paid to conduct a research and functional planning stage before committing to the whole project. Research in your own time and make your best guess.
Negotiate a paid for functional specification phase as a first step.There are three approaches you can take when confronted with a brief that requires a technology you have minimal experience with: Estimating time for a project is not funĭespite being true, rarely do we admit these reasons to others or even ourselves! The fact is, when working as a web professional, as a one man band or as part of a small busy web team, the secret reasons are an everyday reality that shouldn’t be hidden away.īy first identifying and admitting why underestimating is so common, can you then set about implementing changes to your estimating process that will reduce the barriers each reason creates and increase your accuracy.actual’ data analysis has been conducted to draw on Revenue needs for cash flow now trump the effects of not winning the new work now.The client needs an estimate for their project tomorrow or they will go elsewhere.However, there are also some secret reasons why web projects are commonly underestimated: Splitting the project down into the detail would require as much as work as the requirements gathering phase that is chargeable.The client operates in a specialized industry and the solution needs bespoke features that are not familiar to the supplier.At the time of estimating, there are grey areas or complete unknowns.The technologies required by the project have never been used before.There are several reasons, which are freely admitted amongst freelancers and web agencies, as to why web projects are so commonly underestimated - they include: How many times have you been completely confused at how that ‘small’ project turned into such a big one costing double and taking three times the length you estimated? Many of you will say estimating time for web projects accurately is an oxymoron, but by applying a few effective techniques it’s possible to dramatically increase the accuracy of most web project estimates.
0 kommentar(er)
