# A founder's guide to approvals, what should wait for you

Source: https://founder.nexxascreen.com/articles/founders-guide-to-approvals  
Updated: 2026-11-20  
Publisher: Sentient AI Inc

> An approval should wait for you only when the decision is hard to reverse, costly if wrong, or truly needs your judgement or authority, such as large spend, hires, contracts, prices and anything sent to investors. Everything else should be decided by the person closest to the work, inside written limits, with a record you can review.

An approval should wait for you only when the decision is hard to reverse, costly if wrong, or genuinely needs your judgement or authority. Large spend, hires, contracts, prices and anything sent to investors fit that test. Everything else should be decided by the person closest to the work, inside limits you have written down, with a record you can look at later. Across several companies, that rule keeps you from becoming everyone's queue.

## The key points

- Approvals belong where a decision is hard to undo, costly if wrong, or needs your authority.
- Everything else belongs with the person closest to the work, inside written limits.
- Unwritten limits mean everything comes to you.
- Clear your approvals at fixed times, smallest first.
- Treat agents like people: same limits, same need to ask.

## The test

Ask three questions about any kind of decision.

1. **Is it hard to reverse?** A signed contract, a sent investor update, a hire. If yes, it may need you.
2. **Is it costly if wrong?** In money, reputation, legal exposure or trust. If yes, it may need you.
3. **Does it need your authority?** Some decisions legally or contractually require a director or the founder. If yes, it needs you. Which decisions legally need a director depends on your company's documents and where it is registered. Ask your lawyer.

If the answer to all three is no, the decision should not wait for you. Someone else should make it, and you can review it later if you like.

## What usually should wait for you

| Decision | Why |
|---|---|
| Spending above an agreed limit | Costly, sometimes hard to reverse |
| Hiring, firing and pay changes | Hard to reverse, affects people |
| Signing contracts | Legally binding, often needs your authority |
| Changing prices | Visible to customers, hard to undo |
| Anything sent to investors or the board | Reputation and trust |
| Legal and tax filings | Authority and liability |
| Access to money or sensitive data | Hard to undo if misused |

Your list will differ by company. A company with a strong finance lead may need you only for the largest payments. A two-person company may need you for most of these.

## What usually should not

- Routine expenses under a limit.
- Small purchases of software or supplies the team already uses.
- Schedule changes and meeting moves.
- Internal documents and drafts.
- Ordinary customer replies.
- Bug fixes and small product changes inside an agreed plan.

Each of these has someone closer to the work who knows more than you about the details. Your approval adds delay, not judgement.

## Write the limits down

Unwritten limits default to "ask the founder". Write a short page per company:

- **Spending.** Who can approve what amount, by category.
- **People.** Who can hire, at what level, inside which budget.
- **Contracts.** Which contracts others can sign, and which need you.
- **Customers.** What pricing and terms the team can offer.
- **Communications.** What can go out without you.

Share it with the team. Review it every few months, and raise limits as people earn trust. Every limit you raise removes a kind of request from your list for good.

## Clear approvals at fixed times

The approvals that do need you should not wait days. Two habits help:

- **One list.** Keep every approval waiting on you, from every company, in one place. Otherwise you tour each tool and miss some. The article on [the waiting-on-you list](/articles/waiting-on-you-list) explains why this list matters most. In Operators, the Waiting on you section gathers approvals and signatures from each company's tools, and the [guide to tracking approvals](/guides/track-approvals-and-signatures) shows how.
- **Fixed times.** Clear the list two or three times a day, quick ones first. One approval at 9am can unblock a team for the whole day.

## Make requests easy to judge

Ask people to bring approvals in a form you can decide in a minute:

- What they want to do, in one line.
- Why, in one sentence.
- The evidence, as a link.
- What they recommend.

A request you cannot judge quickly is a request in the wrong format. Send it back with a note on what you need, rather than doing the work yourself.

## Agents follow the same rules

AI agents that work for you should follow the same limits as people. If a person would need your approval for a decision, an agent proposing it should too. Ask agents to bring requests in the same format: what, why, evidence. Let them make small, reversible decisions inside the rules, and review those after the fact.

The articles on [human-in-the-loop operations](/articles/human-in-the-loop-operations) and [delegating to AI agents](/articles/delegate-to-ai-agents) cover how to set this up.

## Signs your approvals need work

- The same kind of request reaches you every week.
- People apologise for asking.
- Work waits days for a decision that takes a minute.
- You approve most things without reading.

Each sign points to a limit that should be raised, a format that should be clearer, or a decision that belongs to someone else.

## Across several companies

When you run several companies, approvals pile up faster, and each company's team cannot see the others' requests in front of theirs. Written limits per company, one list of what is waiting on you, and fixed times to clear it keep you from becoming the slowest part of every company at once.

## What to do next

- [How to track approvals and signatures across companies](/guides/track-approvals-and-signatures)
- [The waiting-on-you list every operator should keep](/articles/waiting-on-you-list)
- [Approve, review or watch: human-in-the-loop at work](/articles/human-in-the-loop-operations)
- [Operators for fractional CFOs](/for/fractional-cfo)
- [Approval delay calculator](/tools/approval-delay)

## Questions

### What decisions should a founder always approve?

Usually spending above an agreed limit, hiring and firing, signing contracts, changing prices, anything sent to investors or the board, legal filings and changes to who has access to money or data.

### How do I stop being a bottleneck for approvals?

Write limits so small decisions do not need you, let the person closest to the work decide inside those limits, and keep a short list of what is waiting on you that you clear at fixed times each day.

### Should AI agents be allowed to approve things?

Agents can make small, reversible decisions inside clear rules. Anything that would need a person's approval should need yours when an agent proposes it too, with a reason and evidence attached.

### How often should I review my approval limits?

Every few months, and whenever you notice the same kind of request waiting on you again and again. Raise limits as the team earns trust.
