An agreed operating plan
Objectives, target markets, deliverable allowances, dependencies and responsible owners documented at kickoff.
Decision summary
A 365-day growth program gives research, content, website improvements and measurement a regular delivery process. It works best when your team can supply approved facts, make decisions and route qualified inquiries to an owner. TANTU AI organizes the agreed allowances into a prioritized backlog, records dependencies and reviews what should happen next. The program is a defined service term with 12 monthly service invoices and a separate setup fee. Clear capacity and approval rules help both teams understand what is ready, what is blocked and what has actually been completed.
Build a monthly queue that can be delivered
Separate candidate ideas from tasks that are ready for production. A ready task has a buyer purpose, agreed output, usable evidence, review owner and implementation route. When one of these is missing, record the dependency before committing the task to the delivery sequence. This reduces the risk that several partially approved drafts occupy the same limited production capacity.
An illustrative monthly queue might contain an approved product-page update, a comparison waiting for specifications and a proposed new language page with no confirmed reviewer. These tasks should not be treated as equally ready. Decide whether to resolve the dependency, select another agreed priority or discuss a scope change. Any allowance treatment, rescheduling or carryover follows the signed agreement; a blocked approval does not create an automatic entitlement to extra work or change the 365-day term.
Separate acceptance from later performance
Track research, draft approval, publication and verification as distinct states. A client-approved draft is not yet a live page. A published page is not yet evidence of search inclusion. Each task needs a completion condition appropriate to the work: an approved brief, a corrected live fact, a tested link or a report with traceable observations.
At the business review, examine accepted work, outstanding dependencies and the signals available since the previous period. Use that evidence to choose the next queue and identify decisions the client must make. Keep scope requests visible when they add a market, language, integration or engineering requirement. Near renewal, the delivery record should make it possible to assess what the program produced, which operating constraints remain and which priorities deserve a new agreement. A busy activity log alone is insufficient evidence for expanding investment.