---
title: "Comment by Ascendra Ventures on \"How I quote a rescue job in 30 minutes without reading the whole codebase\" | Hashnode"
description: "Asking whether they own the accounts before reading a single line is the most useful step here. A rescue where the database or payment account sits with a forme"
url: "https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f/comment/6af91ba1f4bbaa1e980c33e3"
---

[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)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

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

Asking whether they own the accounts before reading a single line is the most useful step here. A rescue where the database or payment account sits with a former contractor is a different job, and you learn that in one sentence. "Stripe works in test mode and returns 401 in live mode" versus "it doesn't work" is the same idea applied to the symptom.

It lines up with how we think about pricing at Ascendra Ventures. We price the answer to one problem rather than the hours spent on it, and if we size it wrong, that is our loss, not the client's invoice. That only works when "done" can be defined and checked, which is exactly what your five questions force. Open-ended discovery is a different thing and has to be priced another way, which I suspect is why you refuse to read the repo at the quoting stage.

When the greps turn up something you did not expect after you have already quoted, do you reprice, or absorb it and tighten the checklist?
