Sample weekly proof report

# What the $1,000/month Telegram operator proves each week

The Bux Managed Pilot is not sold as a chatbot. It is sold as an always-on operator that leaves a weekly trail of handoffs, checks, escalations, and time saved.

Apply for the pilot Pilot terms

43

Telegram threads reviewed

18

Clean handoffs prepared

12

Browser or system checks completed

9.4h

Estimated human time saved

## Weekly report structure

Every pilot should produce a short weekly report that the buyer can forward internally. The goal is to make renewal obvious: show what was handled, what escalated, what was blocked, and what tuning happened.

- Threads reviewed and categorized.
- Qualified leads or support requests handed to the right owner.
- External checks completed through browser, GitHub, docs, CRM, calendar, or status pages.
- Follow-ups scheduled so open loops are not forgotten.
- Clear misses, blockers, and improvements for the next week.

## Renewal test

If the report cannot show saved time, recovered opportunities, fewer missed handoffs, or cleaner owner decisions, the workflow needs to be tightened before expanding.

The first month should prove one narrow workflow. Expansion comes only after the operator has a reliable operating log.

## Example handoffs

Lead qualification

### Partner lead triaged

A new Telegram inbound asked about an integration partnership. The operator collected project size, current stack, timeline, owner, and blocker, then handed a two-paragraph summary to sales.

Ops check

### Status verified before escalation

A customer asked whether a deployment failure was still active. The operator checked the status page and GitHub issue, then escalated only the current failing step.

Blocked

### Payment question escalated

A refund request was detected and escalated without drafting a commitment. Human-only areas stay human-only: pricing, legal, compliance, spend, refunds, and production access.