a Weekly, Monthly Price • Have a minimum charge / engagement, deposit. • Have an broad estimates. • Separate pricing for QA, Testing, Written Tests, mobile, hosting….
Be very detailed and specific • No vague terms. • Include QA and Bug fixing terms, maximum iterations. • Responsibilities of Client and Developer • Separation clauses for end of contract • Get a lawyer for contracts above 100k
even if the client doesn’t reply. • Set an expected response date/time (24-72hours) • If possible, email an acknowledgement • Reply within a strict timeline • If the client follows up, you fail
a contract • You are building a relationship, not a one night stand • See the project through the eyes of the client • Develop the idea first if possible • Make your life easier
real idea of how long it takes • Say yes we can do this but always mention a price • If you do something for free, make it known you are doing it for free this time, but not next. • Don’t be abused
WITHOUT A DEPOSIT • Host on your own Dev machine • Do not upload to their servers unless balance is paid, make this in your contract • You own all the code until they pay in FULL • Once you give them the files, you lose your advantage • Have milestones to ease collection. 50, 20, 20, 10 etc. • Base it on the relationship.
Stick with the good clients • Fire the bad clients • Look for partnerships, recurring revenue, % deals. Passive income. • Don’t have to be the entrepreneur.