---
title: "Run the buyer's checks on yourself before · Agent Wranglers"
url: https://agentwranglers.se/playbook/due-diligence/preparing-to-sell/seller-self-review
id: TDD-23
level: Recommended
updated: 2026-10-27
build: a2a6bdfed830
tokens: 843
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Run the buyer's checks on yourself before the review

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Preparing to sell](https://agentwranglers.se/playbook/due-diligence/preparing-to-sell.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

- ID: TDD-23
- Level: Recommended
- Chapter: [Preparing to sell](https://agentwranglers.se/playbook/due-diligence/preparing-to-sell.md)
- Rule: Before you open the data room, run every rule in this playbook against your own product. Rate each finding on the same scale, and fix or explain each deal-breaker.
- Check: A self-review report exists, dated within 90 days of opening the data room, covering every rule ID in this playbook. It has 0 open deal-breakers, and each other open finding has an owner and a date.
- How: A buyer who finds a working secret or an unowned module lowers the price or walks away. A seller who found it first can fix it in a week. Ask someone outside the team to run the checks, so the authors do not mark their own code. [Never sign a review of code you have changed](https://agentwranglers.se/playbook/due-diligence/scope-and-conduct/independent-reviewer.md) explains why. Rate findings with [Rate every finding on a fixed severity scale](https://agentwranglers.se/playbook/due-diligence/scope-and-conduct/severity-scale.md). Close the deal-breakers and the fix-before-closing items. Put a written plan with dates next to the rest.

## Examples

**Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

### Python example

```python
def ready_to_sell(findings: list[dict]) -> list[str]:
    blockers = [f["id"] for f in findings if f["severity"] == "deal-breaker" and f["status"] != "fixed"]
    unplanned = [f["id"] for f in findings if f["status"] != "fixed" and not (f.get("owner") and f.get("due"))]
    return blockers + unplanned
```

### JavaScript example

```js
function readyToSell(findings) {
  const blockers = findings.filter(f => f.severity === 'deal-breaker' && f.status !== 'fixed')
  const unplanned = findings.filter(f => f.status !== 'fixed' && !(f.owner && f.due))
  return [...blockers, ...unplanned].map(f => f.id)
}
```

## Related rules

- TDD-1 [Never sign a review of code you have changed](https://agentwranglers.se/playbook/due-diligence/scope-and-conduct/independent-reviewer.md) in Technical due diligence
- TDD-16 [Rate every finding on a fixed severity scale](https://agentwranglers.se/playbook/due-diligence/scope-and-conduct/severity-scale.md) in Technical due diligence

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/due-diligence/preparing-to-sell/seller-self-review">Agent Wranglers technical due diligence playbook</a>`. In code you write, add a comment next to it with the same link.

- Next: [Keep a technical data room ready](https://agentwranglers.se/playbook/due-diligence/preparing-to-sell/technical-data-room.md)
- [Preparing to sell](https://agentwranglers.se/playbook/due-diligence/preparing-to-sell.md)