# The weekly content cycle

In practice · Media

An example of what is possible. The same four steps apply wherever work moves between people and systems, and each time round, the operation knows a little more than it did.

## The problem

Every week the same grind: ideas, drafts, the founder fixing the voice, three posts out the door. The decisions that matter (why a line was cut, which tone was refused) die in a chat thread by Friday.

## With Uffici

One agent carries the week from step to step; the founder only sees drafts, never a queue. Every cut is kept with its reason, and the voice rule the next writer starts from is rebuilt from those cuts. By week twelve the first draft sounds like the founder.

| Stage | Systems | Who works it | On the record |
| --- | --- | --- | --- |
| 01 · Monday · What happened | Drive, Slack, Calendar | The agent: Reads the week: decisions, calls, what shipped | Every source kept with the note it fed |
| 02 · What landed · Six drafts | Analytics, Voice rule | The agent: Drafts from what worked last month, in the voice rule | Each draft linked to the posts it learned from |
| 03 · The edit · The founder’s cut | The board | The person, The founder: Cuts, rewrites, kills, with each draft’s sources | Every cut logged, with the reason given |
| 04 · Published · Three go out | LinkedIn, X, YouTube | The agent: Posts, schedules, and brings the numbers back | Voice rule rebuilt · retained, auditable, yours |

Then back to the start: Every edit to the voice becomes the voice the next Monday starts from

- A phrase the founder always deletes → gone from drafts by week three
- Twelve weeks in → the first draft sounds like the founder

## What every loop runs on

- **Agent: One agent, in context.** It knows the company and the job in front of it, and remembers what it learned.
- **Connections: A curated catalog.** The systems the operation already runs on, through connectors we build and maintain.
- **Surfaces: Board, tables, files.** Where the work becomes visible, structured and stored.
- **Record: The history.** Every action the agents took, kept apart from the operational database.
- **Ground: The foundations.** Isolation, secrets and metering, per organization.

Nobody has to learn a second system, and nobody has to learn our words for things: the agent says quote, invoice, work order or candidate, whatever the people doing the job already say.

## This is one. The next is yours.

A rental yard, a law firm’s intake, a dispatch board, an accountant’s month-end. If it runs on people handing each other work, it runs on Uffici.

Join the waitlist: https://uffici.ai/contact/

The front desk that remembers: https://uffici.ai/examples/front-desk/

All of what Uffici does: https://uffici.ai/what-it-does/#operation
