How approvals work
Your co-founder handles most day-to-day work on its own, but anything that spends money, is hard to undo, or files something legal always waits for your explicit OK first — nothing like that ever happens without you saying yes.
What needs your approval
Things like: sending a marketing campaign, placing a legal/formation order, or committing to a paid custom app. Simple reversible things — reading your inbox, checking on a build's status, looking up your payout status — don't need approval; your co-founder just does them. A website change is different — see Approving website updates.
Where approvals show up
Anything waiting on you shows up as a card in your chat conversation — including the reply to the request itself — and in "Waiting on you" in your co-founder panel. Ask "what's waiting on me?" any time for a straight, current answer.
Once you approve or skip something, that decision sticks — approving doesn't ask twice, and skipping means it doesn't happen.
Approving from chat
Approve or Decline on a card, in chat or in "Waiting on you", does the same thing; the first tap counts and nothing runs twice. A stray "yes" or "ok" typed under a card doesn't count on its own; tapping the card is the sure way, though a clear "go ahead" about a specific request still reaches me. If I'm waiting on another answer first, the card says "I will come back to this one."
Each request is one action, described exactly
What you read on a request is what that one action does — nothing more. If it says it will save a draft, approving it saves a draft; if it says it will send, approving it sends. Your co-founder won't describe a request in bigger terms than the step actually takes.
A request you asked for in one breath can come back in two: "draft and send my launch email" is write it, then send it. You approve each separately, and approving the first never triggers the second.
Reading the actual copy before you approve a send
When what's waiting on you is an email to your contacts, you don't have to take your co-founder's word for what it says. The request carries a "Review what this says" link — open it and you'll see the real subject line and the body of the email, exactly as your contacts would read it, before you decide.
This is a read, not an editor: you can look it over and then approve or skip. If you want the wording changed, skip it and tell your co-founder what to change — it'll write you a fresh version to look at.
You'll see this on email campaigns. A website change works differently (see Approving website updates): you approve the real, finished result, not a description of it.
If you approve something while a build is already running
It's common to approve a change while an earlier one is still building.
While it waits you'll see it in your co-founder panel's list of builds, numbered by its place in line; website and app work queue separately. Each item says why it is waiting — behind a running build, waiting on a publish, or held by a limit, with roughly when it clears if known. I tell you once that it's waiting behind the current build, then start it the moment that build finishes, however long that takes — no second approval needed.
If something you approved runs into a problem
For a build or a custom app, an occasional snag on the first try isn't the end of it — I give it a few more tries on my own, and you don't need to ask. If those don't work, I flag it for the team and tell you so — never asking you to approve it again. Nothing more is needed from you.
For anything that spends money or sends something on your behalf, your co-founder never quietly retries — it tells you plainly that it didn't go through, rather than leaving you guessing or promising a follow-up that never happens. If you'd like another attempt, just say so and it will try again. Either way, you can always reach a real person if you're stuck.
If an Approve or Skip click never reaches me, you'll see a note that it didn't go through — nothing was decided, so just try again.
Always-approve
For a small number of low-risk, reversible actions (today, replying to customer messages on your behalf), you can tell your co-founder to "always approve this" so you're not asked every single time. You can see and undo any always-approve rule you've set from "Auto-approved actions" on your Dashboard at any time. Anything that spends money or can't be undone always asks first.
Your approval history
Your Dashboard also has an "Approval History" section — a running record of everything you've approved, skipped, or that failed — so you can look back at what happened and when.