←back to thread

317 points alexzeitler | 1 comments | | HN request time: 0s | source
Show context
stevage ◴[] No.42188979[source]
I definitely relate to the basic issue of estimates with my one-person consulting projects. The bit they didn't mention is: who pays for the cost of the inspections and analysis? In software, it can take a long time to analyse the requirements and the solution, in order to come up with an estimate (or fixed quote), and I find it awkward trying to get paid for that time.
replies(1): >>42189028 #
kareemm ◴[] No.42189028[source]
Do a roadmap. Fixed scope small project that you get paid for where you define requirements. Deliverable is a functional requirements doc. It derisks the project for them, and gives you more confidence when quoting a fixed scope fixed price project. You just don’t guarantee timeline. I’ve been doing it for over a decade - it works wonders.
replies(2): >>42189060 #>>42189752 #
1. stevage ◴[] No.42189060[source]
What is the total cost of these projects and how much are you typically charging for the requirements doc?

I'm skeptical that most of the clients I work with would go for something like this. Generally my projects are in the $7k-20k USD range (though with some clients the total spend is much greater with additional phases of work...)

Also, what do you mean "you just don't guarantee timeline"? Why not?