Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Well that smelled bad from the start and obviously ... it was bad.
Like if you can't communicate that you want something cookie cutter / basic from the start, that's suspicious.
The folks who ask for a cookie cutter type site / app but refuse to use services that provide them... I think they know they want more / aren't willing to say / would rather just keep some person on the hook for it when they ask you to turn that WordPress site into Google....
100110111107011d@N00bPancakes like that's the thing here - I'm well aware they want more. They've said they want to add a webshop in phase 2, so I recommended them services which have they capability built-in. I do suspect they might want something even more, but having no clue whatsoever what's their business anyways, I have no idea what that would be. Someone is going to end up moving their WP or whatever to Google or some such eventually...
get paid upfront. non refundable,
Make req changes really expensive. 300% of original estimates.
Make sure feedback on issues timeframe is short, and issues reported after that period is in a scale: 200% for one month, 300% for 2-6, 500% after 6 month.
Meetings, and calls are in the estimates.
If they stick around after that... well. take the job. it will pay.
100110111107010d@magicMirror normally I'd take that advise. But in this case my correspondence is with a friend I actually owe a favour, so I'm not going to start being "an a-hole" now.
I've told them I'll do their site at a contract rate, given the reqs remain unchanged. However, I think I'll give them the rest of your suggested rates as per hour for work on req changes and issues reported after an arbitrary but reasonable timeframe.
If they stick, I'll take the job. Otherwise, someone else takes the fall.