Answer to: How do I push back on an impossible scope?

Put the list of "must-haves" and "should-haves" under revision control Have key stakeholder confirm (in writing), that this is indeed the complete list. Instantiate a change control process. Who can request changes and who gets to review and approve them (with the associated price tag, that is). Build realistic schedules for the "must-haves" and the "should-haves" off the approved list Present your schedule(s). While you are at it, you might also add an estimate for the post-launch ongoing maintenance and support cost. Home-made tools are not cheap to keep running. Offer a few options: delay the due date, cut features to hit the due date, add more resources. Ask on how to proceed Additionally I would do a little market research as well. There is probably a reason, why that license is so expensive. Maybe they have a monopoly or its a niche product, but perhaps its expensive because it was a lot of work to develop it (which would back up your schedule estimates). Maybe there is a cheaper competitor?