←back to thread

When did estimates turn into deadlines?

(domainanalysis.io)
318 points alexzeitler | 3 comments | 19 Nov 24 20:03 UTC | HN request time: 0.42s | source
Show context
stevage ◴[19 Nov 24 22:58 UTC] 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 #
1. kareemm ◴[19 Nov 24 23:06 UTC] 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 #
2. stevage ◴[19 Nov 24 23:11 UTC] 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?

3. intelVISA ◴[20 Nov 24 00:55 UTC] No.42189752[source]▶
Best way but hard to find clients open to this as it requires more trust especially if it starts to drag on.