---
title: "Comment by Youngjun Yoon on \"How I quote a rescue job in 30 minutes without reading the whole codebase\" | Hashnode"
description: "Thanks — that is the right question, and it is the part of this process I had to learn the hard way. I draw the line at what changes the definition of done, not"
url: "https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f/comment/6af93ed990de5c4b0bac390b"
---

[Discussion](https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f)

Comment [How I quote a rescue job in 30 minutes without reading the whole codebase](https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f)

[Youngjun Yoon](https://hashnode.com/@cpcai)

[1d ago](https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f/comment/6af93ed990de5c4b0bac390b)

Thanks — that is the right question, and it is the part of this process I had to learn the hard way.

I draw the line at what changes the definition of done, not at what surprises me. The quote covers the six checks; inside that boundary, anything I did not expect I absorb, and then add it to the checklist so the next quote does not miss it. Invoicing a client for my own incomplete checklist would be the wrong bill.

What does trigger a re-scope is a surprise that moves the end state: the client does not own the Stripe or the DNS account, the auth model has to be rebuilt rather than finished, or the release itself depends on a third party — merchant verification, SMS sender registration, store review. Those are not hours I underestimated, they are a different job. I say so on day one with the evidence (the commit, the 401, the dashboard I cannot enter) so the client can judge the change instead of taking my word for it.

Absorbing everything is tempting because repricing mid-project costs trust, not just time. That is why the five questions carry the weight: when I know who owns the accounts and what "done" means before I quote, the greps have far less room to surprise me. When one still does, I would rather re-scope early and honestly than quietly shrink the scope.

Your framing of pricing the answer rather than the hours matches how I work. How do you handle the case where the definition of done is clear but the blocker sits with a third party — quote it as a range and hold the client to the same assumption, or stop at the boundary of what you control?
