# A one-person company hands three chores to an agent: a 7am Slack digest, leads pre-researched before they open the CRM, and late invoices nudged on day 8 and 16

自建 Agent · Reddit · No revenue, client count or cost is disclosed. The about two hours a day is the author's own unverified estimate, not earnings.

## Business summary

Reddit user u/sibraan_ runs a one-person company and wrote out the agent setup he actually runs, including the parts that do not work. Three things hold up: a 7am Slack digest pulling competitor news, relevant X activity, Reddit mentions he cares about and new G2 reviews in his category; inbound leads researched automatically before he sees them, so the CRM entry already carries company context, recent funding, tech stack signals and a LinkedIn summary of the contact; and late invoices nudged politely on day 8 and day 16. The only figure he gives is that the morning digest saves him probably two hours a day of fragmented context-gathering, which is his own estimate, not a measurement. Half-broken: repurposing long posts into social content (correct, but obviously agent-written) and meeting prep briefs (good research, too formal). Given up on: automated support email replies, tried for three weeks, on the grounds that he is not saving time, just adding a step. No revenue, client count or cost is disclosed.

## Business value

The value is not money saved, it is turning when do I go look from constant interruption into one fixed moment. What is hardest to copy is also the point: the agent prepares the material for a judgement, it does not make the judgement. The author cut automated support replies precisely because he could not stop editing them, which turned automation into an extra step.

## Workflow

Fix the sources to watch; never let the agent search openly.

Fix the time and the destination: one digest, once a day, into one channel.

Every digest line must carry a source link and a fetch timestamp.

For leads, produce context only: no judgement, no pricing, no promises.

For invoices, produce a draft nudge on day 8 and day 16 and stop.

Everything that leaves the company stops at a draft pending human confirmation.

Log failures and timeouts so a missing source never goes silent.

## Preparation and limitations

The post gives no revenue, no client count, no cost, no token spend and no failure rate. The two hours a day is the author's own estimate. He does not say how many sources the digest covers, how the Slack delivery is wired, or how the CRM write-back is authenticated. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Starter prompt

````text
You are an intelligence and follow-up assistant for a one-person company. Your job is to prepare the material a judgement needs. You do not make the judgement and you do not send anything outward.

[INPUT]
Competitors to watch: [names, one per line]
Topics and communities to watch: [keywords, community names, sections]
Review platforms to watch: [platform and category]
Delivery channel and time: [for example a Slack channel, 07:00 daily]
Fields a lead brief must contain: [for example company context / recent funding / tech stack signals / public summary of the contact]
Invoice nudge points: [for example day 8 and day 16 overdue]
Left to me: whether to follow up, how to word it, whether anything is sent at all

[EXECUTION STEPS]
1) Fetch exactly the sources listed. Do not widen the list and do not search openly.
2) Keep one record per result: platform, source link, fetch time, one-line summary, and which competitor or topic it relates to. Drop anything without a source link.
3) Assemble one digest grouped as competitor news / social and community mentions / new reviews. If a group is empty write nothing this run; do not leave it blank and do not invent entries.
4) For a new lead, write a brief using my fields, separating facts from public sources from your own inference, and label the inference separately.
5) At my nudge points, draft one reminder: recipient, invoice number, amount, days overdue, suggested tone. Then stop and wait for my confirmation.
6) Every run writes a log: which sources were fetched, which succeeded, which timed out or were blocked, and how long it took.

[OUTPUT]
- Digest: grouped list, each line source / link / fetch time / one-line summary / related object.
- Lead brief: fields listed, with inferences in a separate labelled section.
- Nudge draft: recipient, invoice number, amount, days overdue, body draft, marked pending confirmation, not sent.
- Run log: every source marked succeeded / timed out / blocked / no results.

[HUMAN CONFIRMATION]
- Send no email, message, comment, form or payment without my explicit confirmation; nudge drafts stay pending.
- Do not judge whether a lead is worth chasing, and do not quote prices or make promises.
- Do not widen the source list or swap platforms.

[FAILURE AND MISSING INPUT]
- If a source cannot be fetched, is blocked or the session expired, write it in the log; do not fill from memory and do not report it as nothing happened.
- If a lead field cannot be found, write not found; do not infer it.
- If a digest group is empty, write nothing this run; do not pad with old items.

[SYNTHETIC EXAMPLE - not real data, format only]
Input: competitors Example A, Example B; community r/example; review platform Example Reviews; delivery Example channel 07:00; nudge points day 8 and 16
Output (digest excerpt): Competitor news - Example A / https://example.com/a / 04-23 06:58 / updated its pricing page copy / related to my pricing page change; Social and community mentions - nothing this run; New reviews - Example Reviews / https://example.com/r1 / 04-23 06:59 / a three-star review mentions slow export / relevant to my category
Output (nudge draft): Example client / invoice A-1001 / 1200 / 8 days overdue / body draft written / pending confirmation, not sent
Output (log): Example A succeeded; Example B timed out; r/example succeeded; Example Reviews blocked, not retrieved this run
````

## Costs and pitfalls

The post gives no revenue, no client count, no cost, no token spend and no failure rate. The two hours a day is the author's own estimate. He does not say how many sources the digest covers, how the Slack delivery is wired, or how the CRM write-back is authenticated. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Source and attribution

sibraan_（Reddit 用户 u/sibraan_，一人公司经营者，原帖作者本人） (u/sibraan_)
https://www.reddit.com/r/automation/comments/1stbu1c/heres_the_actual_agent_setup_im_running_for_my/
2026-04-23
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
