3 ms·
Don't charge hourly. It's going to cause friction and disappointment on both ends. Estimate how long it'll take you and give them a flat rate. 200-250 hrs is w
by smt88 8y ago
Don't charge hourly. It's going to cause friction and disappointment on both ends. Estimate how long it'll take you and give them a flat rate.
200-250 hrs is wildy optimistic, especially for a new developer. I built a booking system as an expert developer, and it took longer than that. You should at least double your best guess at a time estimate.
> they are taking a risk with a new developer
They, and you, shouldn't take this risk with sensitive data and payment info, unless you plan to have it reviewed by a security pro.
- dariuscosden 8y agoWell, I built a picture converter from scratch in 250 hours. It has a fully functional conversion system converting images to 9 different formats, it has a payment system and monthly subscription system through Stripe, it has its own custom REST api build from scratch to give access to other developers to use in their apps, and it has conversion tracking and measures in place to prevent abuse, to the best of my ability. The above is why I feel confident about this project as it is nothing I haven't seen before. I do agree about the sensitive data and payment info. Would that still apply given that I immersed myself in security for this specific purpose and do not actually keep anything on server? Stripe handles everything and it's all carefully encrypted. Maybe I'm missing something. And yes, this will be a flat fee. I'm trying to get to a flat fee based on an hourly estimate + rates. In that regard, would you have a recommendation?