Compare
Both use AI on your work, and both can run without you sitting there. The difference is what happens before: a chat assistant works out what to do on the day and does it, and Faber shows you a full run first, then does only what you approved.
| Faber | A chat assistant | |
|---|---|---|
| When it works | On a schedule, the moment work arrives, or on demand. | On a schedule you set, while you are in the conversation, or on activity in a short list of supported apps on their paid plans. |
| Before it runs | A full preview run you approve, with nothing sent or changed. | There is nothing to preview. The first run is the real one. |
| Approvals | Mark the actions that need your say-so before the run. Those wait for you, and the rest of the run finishes without you. | An action it decides needs approval stops the run. Nothing else in that run happens until you come back to it. |
| What decides the actions | Decided once, when the task is built, and you approve them before anything is real. | Decided fresh, every time it runs. |
| Recurring follow-up | Reads the reply, acts on it, and keeps going until the job is done. | Each run starts again from the prompt. |
| Record of each run | A plain-English record of what it checked, did, set aside, and skipped. | Chat history. |
| Setting it up | Describe the work once and the AI builds it. You answer a couple of questions. | Write the prompt yourself, and rewrite it when the work changes. |
| Built for | Recurring work you would rather stop doing yourself. | Thinking, drafting, and answering, with you in the loop. |
When not to use Faber
Faber is not built for one-off work and does not try to be. Open a chat for the thinking, the drafting, and the thing you need an answer to before lunch. Faber earns its place when the same work comes back next week, and the week after, and you would rather it just happened.
If it already runs on a schedule
When the AI picks each action as it goes, a job is only as good as the whole chain, and a scheduled run picks them again every time it fires. Get nineteen actions in twenty right, and a twenty-action job still comes out right only about a third of the time.
The AI works out the actions when it builds the task. After that it follows them, using AI only where an action needs judgment, like reading a reply or drafting a message.
A preview only tells you about tomorrow if the actions are settled. You read the whole first run before any of it is real, and that is what keeps happening. Only the mail and the rows change.
Describe the work once, read the full preview run, and mark what needs your say-so.