Start building
Ospyr Ventures learning libraryResearch file / published guide

Founder operations / approvals

Approvals should guardthe right decisions.

Move routine choices to named owners. Keep the few commitments that could materially change the company under deliberate review.

Written by
Ospyr Ventures editorial team
Published
14 November 2026
Link check
14 November 2026
Reading time
9 minute read

Ospyr Ventures has an interest in the topics covered. The article does not claim Ospyr client results or a named founder testimonial. The named editorial reviewer is pending. See our editorial standards and corrections process.

In brief / 40 to 60 words

The direct answer

Start by recording which approvals reach the founder and why. Give routine, reversible decisions an owner and a written limit; reserve decisions with material financial, legal, ownership or reputation consequences for explicit approval. Define what information an approver needs, when they must respond, and what happens if they are unavailable. Review exceptions and revise the rules.

How we would approach it

We would examine the last two weeks of approvals, not an idealised organisation chart. Ospyr's proposed matrix would give routine decisions named owners and limits, reserve material risk for founder approval and make exceptions visible so the rules improve with use.

See how Ospyr Ventures builds

Where is approval time actually being lost?

Measure the queue before redesigning it. For two weeks, record each approval request, its requester, the decision type, the amount or exposure, the time submitted, the time answered, and the consequence of delay. Group repeated requests. Ten small procurement approvals may be one missing spending rule. A single delayed contract may be an information problem because the reviewer was never given its term, obligations or alternatives.

Distinguish a permission request from an advice request. A team member may ask the founder to choose because the boundary is unclear, because the founder has previously reversed decisions, or because they want a second opinion. Only the first two require approval-system changes. An advice conversation can remain useful without transferring ownership back to the founder.

What should an approval matrix contain?

Build the matrix around categories and thresholds the team can apply. State the owner, the maximum exposure, the information needed, and the escalation route. A threshold can be monetary, but it can also concern customer harm, legal commitments, access to sensitive data or a promise that cannot easily be reversed. Keep the matrix short enough to use during real work. Attach a link to the relevant policy, not a folder of unread documents.

Avoid a rule saying every decision above a certain amount requires the founder personally. A named finance lead or board process may already be the right approver. Follow the company's legal documents and actual governance arrangements. The sample below is an operating design, not legal advice or a prescribed rupee threshold.

DecisionNormal ownerEscalate when
Routine customer remedyCustomer leadOutside agreed refund or reputation limits
Supplier choice within approved specificationOperations leadExclusivity, term or exposure exceeds the mandate
New debt, equity or material legal commitmentNamed governance approverAlways, before commitment
Small reversible experimentProject ownerIt touches protected data or regulated claims

What information lets an approver answer once?

Require a brief decision packet for reserved matters: recommendation, alternatives, expected benefit, downside, cost or commitment, deadline, and what happens if the decision is deferred. The approver should be able to say yes, no, or 'return with this missing fact.' Without a standard packet, founders receive a stream of messages that must be reconstructed into a decision.

Set an expected response window for each category and a backup approver where governance permits one. If a customer promise expires in four hours, an approval route that meets once a week is not a route. Where no lawful substitute exists, change the promise or prepare the decision earlier. Silence must not be treated as approval for high-risk commitments.

  • Recommendation and named decision owner
  • Two credible alternatives, including doing nothing
  • Cash, customer, legal and reputation exposure
  • Evidence known and uncertainty remaining
  • Deadline, default action and review date

How can approvals become lighter without losing control?

Review the queue monthly. Track median wait time, requests that exceeded the service window, decisions sent to the wrong approver, and cases that had to be reopened. Read a sample of decisions made below the approval threshold. If errors recur, improve the mandate or training rather than sending every routine choice upward again.

Tell the team when a rule changes and why. When a founder reverses a decision that was inside the owner's mandate, either identify a missed constraint or acknowledge that the mandate needs revision. Quiet reversals train people to seek permission even when the written policy says they can decide.

A useful next step

Log every founder approval for two weeks, then publish a one-page matrix for the three most common decision categories.

Terms worth knowing

Approval matrix
A table naming who can decide and who must approve each category of commitment.
Decision packet
A concise written recommendation with options, evidence, exposure and a deadline.
Escalation
Moving a decision to a specified reviewer when its risk or scope exceeds an owner's mandate.

Watch, read and test.

Team exercise

Run Atlassian's DACI play

Use it to draft one approval decision with a named owner and approver.

Open resource
Primary reading

Amazon's shareholder letter on decisions

Read the original explanation of reversibility before classifying choices.

Open resource