Quoting & Planning – What WebDev Projects Really Look Like, Part 2

Quoting & Planning – What WebDev Projects Really Look Like, Part 2
After you've gotten through the Discovery process to find out what your objectives should really be for a webdev project, next steps include:

Quote Submission

Your "quote" should actually be more of an estimate. We're all familiar with the concept of "scope creep" and—as with any act of creation—it rarely ends up being exactly what we anticipate. Allow yourself flexibility to compensate for this next point:
Allocate enough time and money for concepting and ideating about UX and testing, and reworking things according to what you find out during testing.
With any quote, you are setting client expectations. Write it with the thought in mind that you will need to stick to whatever promises you express or imply, so leave room to over-deliver.
Check out Muffin Group's great web design suggestions and quotation templates to figure out the best way to price your services.

Planning

If you're going to put the project in front of end users and act on feedback (and hopefully you are), you need to plan for the time and money to do this. All sustainable webdev projects are iterative.

This takes us up to the start of creative production work, which we'll cover in our next post.