> Are you not maybe specifying too much too early on? > Back when I did some freelancing gigs, the general advice I got was to spec a high level, general propo

> Are you not maybe specifying too much too early on? > Back when I did some freelancing gigs, the general advice I got was to spec a high level, general proposal which included all the client's requirements. Broadly. Then decide on iterables, with the spec (and timeline and effort and payment) for each iterable being done prior to commencing work on it. The key being to have a working system after each update. Sound familar ;D This is exactly how I want to work! The pushback I get is that the company's board of directors won't sign off on a project where the total cost isn't known. I have explained all in your third paragraph, and even when the manager/CTO/CEO 'gets' this, the board don't. Because it's beyond their understanding as non-technical, and sounds like being taken for a ride (and I get it; if my garage did this, I would expect I was being fleeced). This is what I need to break-through.