41–50 of 89 posts
Earlier quoted context omitted.
As someone who isn't used to taking upfront payments, my question is, are people actually willing to do that?
Yes, definitely. I just did that for two projects in the past week; but it was 1/2 up-front. Albeit, they were close referrals. YMMV if it's potential customers who don't know you.
I've never had anyone walk away from a project after asking for 50% upfront at projects this scale.
I love the idea - but I wonder why the price? it does seem really low. At 19 bucks and hour pro rata, you are not storing up cash to get through the hours when you are not earning, like marketing, talking to clients, understanding what they want. It did get me thinking though - really good luck.
Hey, I remember you from robot game. Wish you the best with this new venture.
> I'll get half the site working, demo it to you, give you all the code thus far, and you'll pay me $1,172.50. You should ask for 1/4 up-front, before you write any code.
As someone who isn't used to taking upfront payments, my question is, are people actually willing to do that?
Chris, if you are reading this, please share your experience with us.
> I'll get half the site working, demo it to you, give you all the code thus far, and you'll pay me $1,172.50. You should ask for 1/4 up-front, before you write any code.
As someone who isn't used to taking upfront payments, my question is, are people actually willing to do that?
For ongoing projects that you bill hourly instead of fixed cost, try to do retainer instead of invoicing and then getting paid a month later model.
Cash flow is THE single most important thing in this business. Try to get paid as early as possible, and delaying paying others as much as possible (while still paying them reasonably soon, of course - just try to negotiate better terms upfront, i.e. get paid Net/15 and pay others Net/30).
Also, never EVER work without a contract. For every project, have client sign MSA and SOW. I bought mine from here: http://msabundle.com/ and modified per my needs.
Earlier quoted context omitted.
Interesting, what happened that made you lose money? Were you pouring more time into the projects than you were getting paid for?
I didn't actually go ahead and implement it - I just couldn't make the math work. In my opinion, there are too many unknowns with this model - you're quoting the price of a project without knowing all features, talking about design iterations, supported browsers, and a million other things. And if you substantially increase the price after getting the requirements, clients won't like that, because the most important…
There are a lot of unknowns, the only known is that it costs 5$, that's all some people need to know.
Maybe you can roll the numbers up a digit for each successive job… Having done "MVP" work before, I wouldn't undervalue your work like this for to long or you'll be facing burnout quickly.
Hm, I'm hearing that a lot. Is $2,345 really that little? I've been living near the poverty line by choice, and $2,345 lasts me about two months. In either case, I guess it would turn off half the visitors if I just changed the price right now.
Good Idea. But your own website looks little lame. Hope you update it soon.