Information Output

Let's get started.  We have 6 ways to be a better client.  We're trying to help you help us help you.  So go along with us and keep an open mind!

1. You're the only one that knows your problem.
   • Do your best to describe everything that you need.  In the greatest detail.
   • When in doubt, ask the developer what their vision of the problem is.
   • Don't assume that everyone knows the technical jargon of your industry.  If you make widgets don't think for a second we will know what a hargonflusionheimer is!
   • If your developer asks a lot of questions, be sure they all get answered.  Don't leave anything flailing in the wind or it will get lost.
2. Developers probably know the best solution to the problem.
   • If you could do it yourself you would.  No one wants to spend money if they can do it themselves.  We're here to solve the problems you can't.
   • A direct quote: "Programming is hard.  if it looks easy, it's because I'm good at it."  Trust in those who make it look easy.
   • Don't assume that you know the best way to go about getting a site.  Sure, WordPress is good and your brother's cousin's aunt's sister-in-law's web site looks good in it.  But nothing is ever the same.  Her site is a regular blog with a good style.  It's not good for managing your corporate site with ecommerce and live support system.
   • Give and take.  You want your developer to listen.  Right?  When they give you your best options.  Listen.
3. Don't sell out.
   • YinYang.  You must have balance.  Make sure the developer understands your problem completely before having the solution presented.
   • A contract should not be handed to you in your first meeting.
   • Believe that your problem is unique and deserves time, thought and effort.  Not a cookie cutter template.
4. Deadlines Milestones
   • Set regular milestones based on the estimated length of the project.  This will help everyone keep track of the actual progress that's being made and can fix problems before they arise.
   • Sometimes deadlines slip.  milestones help you see that earlier than the last minute.
   • Problems do come up.  Don't assume that everything will run smoothly.  Just be hopefully, energetic and helpful.
   • Things can be difficult some times especially if you have a large problem.  Milestones may be pushed a little but if things are way off it's usually a sign the developer doesn't understand the problem.
   • If something is pushed back, everyone needs to be a little clearer about the problem.
5. Budgeting.  Oh yes.  We went there.
   • Know what you can spend.  Don't guess.  The developer needs to know what you are able to allocate to the project.
   • Knowing helps the developer use tools in the right range and even let's them know if they can take the project on.
   • After giving the budget, ask for references.  And check them.
   • Ask for an estimate and a maximum charge guarantee.  This is usually 10%-20% over the estimate.  It will ensure that should the project go over-budget it can only go so far while still getting it completed.
   • Know that once that guarantee is in writing, you can't make changes.  You can't claim that you missed something in your last meeting and slide it into the project after you've got the price you want.
   • A good developer will refuse even small changes once the contract is signed. Honor their refusal and respect it for what it is.  Professionalism.
   • If you need something added, ask to have an estimate specific to the change written and added to your client file.
6. Paper-Pushing.
   • The agreement between you and your developer should contain precise non-vague terms about every feature you need.
   • Remember that if it's not in the contract, it's not part of the project.
   • Don't assume that because it says "shopping cart" that your web site will include shipping through the major carries, product management, discount system, secure login, payment processing...