# Running a business on your own

Running alone changes one thing structurally: you are the only approver, so every setting that says 'a person decides' means 'this waits until you look'. The arrangement that works is a ladder — watch, then approve, then release — applied channel by channel, with the queue as the single place anything unfinished can hide.

- **Status:** Available
- **Audience:** both
- **Channels:** email, phone, whatsapp
- **In the app:** #/home, #/needs-you, #/autonomy, #/follow-ups
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/use-cases/solo-operator/

## The ladder, and how long to stay on each rung

1. Start every channel on `draft_only`. Connect prepares replies and does not even ask.
   - Result: You see exactly what would have gone out, with no queue building and nothing to say no to. This is the cheapest week of learning available.
2. Move the highest-volume, lowest-stakes channel to `ask_before_send`.
   - Result: Replies now wait in Needs You. Watch how quickly you actually work that queue: that number, not your intention, is what the customer experiences.
3. Release that one channel to `autonomous` once the drafts have stopped surprising you.
   - Result: Replies go out on arrival. The audit trail still records every decision and the rule behind it, so releasing control is not the same as losing sight.
4. Keep the narrow exceptions narrow. Autonomy resolves contact, endpoint, channel, workspace — narrowest wins.
   - Result: One difficult account can be held for you while everything else runs, without turning the channel back off.

## The single-approver problem

A held draft is not a slow reply. It is no reply: nothing has been handed to any provider, there is no message in flight, and the customer waiting on it is counting from when they wrote. For a team that is an inconvenience; for one person with a van, a clinic list or a site visit it is the failure mode.

- Anything you would rather answer late than answer wrong belongs on `ask_before_send`. Anything a customer will take elsewhere within the hour does not.
- Phone follow-ups are unforgiving of a busy day: one more than 24 hours late is closed as `missed:` and never rung, because a very late call-back is worse than none.
- The runtime can be turned off deliberately, which is a better answer than leaving replies queued while you are away for a week. Off is a state you chose; a silent queue is one that happened to you.

## Working through the Assistant

The Connect Assistant is where one person gets leverage: 66 tools, read-only ones like `find_anything`, `customer_360`, `next_best_action` and `list_followups`, and writing ones like `create_followup`, `approve_draft`, `send_draft_now`, `remember` and `create_opportunity`. Each tab keeps its own conversation, record, draft and files.

Its rights are narrower than yours on purpose. The Assistant cannot set a price and cannot clear a do-not-contact entry — the two actions where an agent being helpful is exactly the wrong outcome. Ask it for either and you get the refusal and the escalation, not a workaround.

> **Note** The screen context the model is given is checked against the database before it is trusted, so an answer about what is on your screen is an answer about what is actually in your workspace.

## A configuration that holds up alone

| Decision | Setting | Why this one |
|---|---|---|
| Enquiry email | `autonomous` after a fortnight on the ladder | Volume, repetition, and a customer who leaves if nobody answers |
| Anything about money | `ask_before_send` | Commercial terms are refused anyway; what remains still deserves your eye |
| Phone | Answered always; escalations become follow-ups | You cannot take a call on a ladder, and the caller does not care why |
| Follow-ups | Due times inside your working day | A commitment due at 02:00 is a commitment nobody will honour |
| Task follow-ups | Used freely | The `task` channel is work for a person and no drain ever sends it — the honest place for what only you can do |

## What it costs one person

Voice is the line to watch. A call is priced on audio tokens and runs until somebody rings off or the thirty-minute ceiling stops it, so a handful of long calls outweighs a month of mail. Every call is priced and charged, and one the remaining budget cannot cover is stopped rather than allowed to run on.

Mail is bounded by the daily allowance instead. When it is spent, work is held and the read cursor does not advance, so a busy Tuesday defers into Wednesday rather than vanishing.

## Questions

### Is it safe to let Connect send without me seeing it first?

On a channel where you have already read a fortnight of drafts and stopped being surprised, usually yes — and the safety comes from the refusals rather than from your reading. A price, an SLA or a warranty that Knowledge cannot support is refused and escalated whatever the autonomy mode says, so the sentences that create obligations are never the automatic ones.

### What happens while I am away for a week?

Inbound is still handled and calls are still answered. Held drafts accumulate and their recipients see nothing; phone follow-ups that go more than 24 hours late are closed as missed. If nobody will work the queue, either move the channels you trust to `autonomous` before you go, or turn the runtime off deliberately — an ambiguous middle is the option that costs customers.

### Can the Assistant just approve things for me?

It can approve, send or reject a draft when you ask it to, using `approve_draft`, `send_draft_now` and `reject_draft`. What it cannot do is widen its own authority: setting a price and clearing a do-not-contact entry are outside its rights no matter how the request is phrased.

## Related

- [Connect Assistant](https://connectbyjbrh.com/docs/assistant/)
- [What Connect may do](https://connectbyjbrh.com/docs/autonomy/)
- [Covering a small team's inbox](https://connectbyjbrh.com/docs/use-cases/small-team-coverage/)
- [Follow-ups in Connect](https://connectbyjbrh.com/docs/follow-ups/)
- [A business whose people are not at a desk](https://connectbyjbrh.com/docs/use-cases/field-service/)
- [Separating the agent's authority from the person's](https://connectbyjbrh.com/research/authority-separation/)

## What this page is based on

- docs-source/sources/GENERAL.md §5 — autonomy modes and scopes
- docs-source/sources/GENERAL.md §8 — the Assistant and its narrower rights
- docs-source/sources/GENERAL.md §7 — follow-ups and the task channel
- Connect capability registry (docs-source/facts.py) — runtime_on_off