Crew memos · Engagements
Fixed blocks and monthly blocks
Use a fixed block when the job has a shape. Use a month when the queue does not end.
On this page
A fixed block is a landing page, a discovery, a workflow, an AI pilot. The hours are the price of that shape. When it is done, the block is done.
A monthly block is care, support, content, or engineering capacity. You receive a fresh allocation each month. Unused hours do not roll into the next one. That is deliberate: a rollover turns a retainer into a vague balance nobody can explain.
If a monthly request is really a new project, we say so before the hours are spent and point you at a fixed bundle. The two are allowed to sit next to each other. They are not the same engagement.
Core · v10
A test you can apply to the thing you want.
If you can describe done, it is a fixed block. A page is done when the offer, the proof, and the enquiry are live. A workflow is done when one real item moves and the exception reaches a person. A pilot is done when you can continue, narrow, or stop.
If you can only describe a week, it is a month. Edits, small breaks, a writing queue, a backlog of varied tasks. The allocation refreshes. Unused time does not become a savings account. That would turn the month into a vague balance.
The mistake is using a month to avoid writing the edge of a product. The other mistake is using a fixed block for a queue that will still be there next month. The engagements page separates them so the mistake is harder to make by accident.