Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Be normal
Understands most of it
Clear your doubts
Domt hurry to sign the contract
Get confirmation over email.
Always get written in email. -
Wack61917yDon't say yes to every thing but tell them, that you'll have to calculate it and get back to them with a offer, if they have additional things.
Agree to a scope and have it in written form.
If you have a design, have them sign it.
State in your contracts a period, where you'll fix bugs for free, and state that things they discover afterwards will be billed. Also state that new features and such will be billed.
Fix a timeline and plan some buffer time in there too. Also make clear, that if they add or change features, the timeline won't apply anymore and you'll send them a new one.
State your hourly salary for additional stuff.
Don't have "clean" numbers. Instead of for example $100, estimate it at $93 or $113, the client will feel like you "calculated" an actuall amount of work and other expenses, while a "clean" $100 can feel arbituary, and they're more likely to question it/negotiate.
These are just my rules of thumb. It's not science. -
Bresson937yDefine well both what you want/need to do. I would recommend to use a Kaban board or Scrum methods. Trello is quite usefull too. Transparence and trust is really important, that's why you have to define everything clearly. Don't go too fast, don't sell yourself cheaper to get the contract if it's not worth it. Good luck! :)
Related Rants
So today is my first meeting with my first client for my first ever project...
Any suggestions?
rant
client meeting
exited