The process of estimating time in our business is broken. At most, we typically have a document of basic requirements, alongside a few calls with the client to go over questions about a project. In turn, we are expected to provide a budget/timeline and stick to it for what can easily be 3-6 months or more.

For many projects this is enough, but for larger or more custom work, estimates in many ways are just a shot in the dark. The process is often inaccurate and risky. It's like remodeling a house. The project often takes longer and costs more than you originally planned. Since we're committed to meeting both the timeline and budget, there are times when an inaccurate estimate can present a bit of a pickle.

An incorrect estimate isn't good for anyone. Overestimating isn't in the client's best interest and can keep you from getting the project, but underestimating almost ensures that the project will not promise to be your best work and it can be very frustrating for both sides. Ick.

Recently we have begun suggesting a paid "exploratory" period (needs a cool name). We spend all the time necessary to define a clear project scope, write out written requirements and estimate the time needed to complete the project. An accurate quote can easily take at least a few days when done properly, and it is only fair to be compensated for that kind of time.

Since the client pays for the time, they own the work that we do to define the scope and create written requirements. That way, getting bids from other companies should not only be easier, but all the bids should be more realistic.

Another benefit of paid exploratory periods is being able to partner with a client/company before diving in head first. It is very important for both sides to get to know each other, and get a good feel for what it's like to communicate together. If it does not work out, you can look elsewhere without being empty handed.

We don't do this on many projects, but it is extremely helpful for some. Here is a list of questions I consider when deciding whether the project needs further exploration:

1. How well do I know the client? How quickly do they typically communicate and get things done? Do they trust our expertise or value the same things we do in a quality website?
2. How long will the project take?
3. Have I done this before? How much of the work is new for us or custom?
4. With what we know about the project now, is it enough to provide a very accurate quote or do we need more information?

I'm definitely most comfortable with this approach right now, but it took nearly 4 years to figure it out. I believe it is perfectly reasonable to ask for compensation if it will take a significant amount of time to provide an accurate bid on a project. If you can master the art of pricing and estimates in web development, you are on your way to building a very successful business.

For additional thoughts and ideas on estimating time as a web designer/developer, our friends at Smashing Magazine published a very informative article about it.

After nearly two months without a post on this blog, I'm pleased to come out of hibernation this week. One of the reasons I was unable to make time for blogging recently is because my spare time has been dedicated to a side project that we launched about 3 weeks ago.

Our team is never short on inspiration or ideas for the web, and our outlet is a little software company called Brightwurks. Linkpatch is the name of our second web application, and it is our way of solving a problem we deal with every day at Project83.

One of the more frustrating things a user can run into on the web is a broken link. Often times, it leaves the user stuck, forcing them to wander the site aimlessly looking for what they need, or become frustrated and go elsewhere.

We do a number of things when launching a website to minimize dead ends like that. We always check the site for broken links between internal pages, and setup redirects (when applicable) from any old URLs to the appropriate location on the new site.

While most geeks stop there, I don't believe that's enough. There aren't any tools that are constantly watching, monitoring when and why people run into a broken link on your site. If another website is linking to your website, but the URL is broken or out-of-date, you have no way of knowing ... until Linkpatch.

The idea behind Linkpatch is simple. It is a small script that is always watching your website's error pages. If a user ends up on an error page as the result of a broken link, the script records all kinds of information about what happened, and sends an email to the webmaster so it can be fixed.

Linkpatch has been an incredible resource, as we have been using it internally for quite some time. We have it installed on many of our websites, and if a user or customer runs into an issue, we're able to diagnose and fix it very quickly. If we make a mistake in building the site, Linkpatch usually lets us know before the client does.

Here are just a few of the uses we have had for Linkpatch recently:

• One of the URLs in a recent client newsletter had a typo. We were able to add in a redirect from the misspelled URL to the correct one.
• The shopping cart page on a client site was broken after a recent update, and Linkpatch found it very quickly.
• Links from blogs, twitter, search engines and affiliate websites that were all wrong or out-of-date were able to be caught and corrected within minutes after the first sign of an error.

Linkpatch has definitely been a big help to us in keeping our client websites error-free. We think other webmasters and web design shops will enjoy it too. Feel free to check out the site if it sounds appealing, and we always welcome any feedback. For the next 2 days, you can get a free 5-site Linkpatch account for mentioning the app on twitter. Check out this page for more info.