---
title: "Discussion on \"How I quote a rescue job in 30 minutes without reading the whole codebase\" | Hashnode"
description: "Discussion on \"How I quote a rescue job in 30 minutes without reading the whole codebase\". A triage process for half-finished AI-generated apps: what I ask for, what I run, and the three classes every project falls into."
url: "https://hashnode.com/posts/how-i-quote-a-rescue-job-in-30-minutes/6af8075b70ba34ed06c5962f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I quote a rescue job in 30 minutes without reading the whole codebase](https://cpcai.hashnode.dev/how-i-quote-a-rescue-job-in-30-minutes?utm_source=hashnode&utm_medium=feed)

A triage process for half-finished AI-generated apps: what I ask for, what I run, and the three classes every project falls into.

2d ago · 6 min read · cpcai.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#freelancing](https://hashnode.com/tag/freelancing)
-   [#productivity](https://hashnode.com/tag/productivity)

## Written by

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

@cpcai

  
[View profile](https://hashnode.com/@cpcai)

Solo developer shipping AI and full-stack MVPs in 3-5 days | founder of CPC AI, Seoul

I run a one-person software studio in Seoul (CPC AI). I build and ship production-ready web/app and AI MVPs in 3-5 days, and I write about the pipeline behind that: stack choices, automation, and where AI agents actually help. Studio: https://cpcai-studio.netlify.app/en/

## Responses 2

Markdown supported · ⌘↵ to post

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

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