A one-time project has a finish line.
A fictional household with several years of scattered digital records may need one agreed cleanup and a handoff guide. If new material is infrequent, ongoing service may add little.
A recurring workflow has repeated decisions.
A fictional contractor receives homeowner documents and supplier quotes across active projects each week. Reusable intake, stable rules, and an exception list may suit a monthly desk.
Estimate a pattern before counting everything.
Describe a typical week, the number of active projects, the document types, and where finished records should go. Unknown volume is acceptable for a fit review. Actual usage can inform the agreed allowance.
Keep backlog and maintenance separate.
Setup establishes the workflow; it does not absorb unlimited historical records. Agree any backlog project separately. Choose monthly support only after the recurring scope, capacity, and activation point are clear.