The prospective client is creating a product and have decided to outsource their product development.<p>As a company, we decided to give it a try so that we can fund our own product which is under active development. Having said that, we are unaware of the economics of project development as we all have background in SaaS product companies.<p>I have come to the conclusion that we should charge them on manpower basis so that we don't get slowed down i.e
$x per developer per month + $y
where x is subjective to skills and experience
and y = cloud infrastructure cost.<p>This is in contrary to the hourly task based approach.<p>Please advise.
I have great experience with agreeing on the features to be delivered in a two-week sprint. You provide and estimate in hours and have a hourly rate for your work. This allows you a) to outperform your estimate and gives b) your customer some planning security. If you screw up, a the content of a two week sprint won't brake your neck. If you outperform you have more time for your project.<p>Additionally you get rid of the discussion if dev a is worth 1.2456 more than dev b.<p>Infrastructure is cost you bill additionally.
Add z, profit, to your calculation on top of your rates.<p>Monthly is good, weekly might be more flexible for the client without getting into task tracking.