Identify whether the problem is bounded.
A defined audit or launch brief can have a clear end. A programme of recurring research, creative evaluation and market expansion may require repeated decisions. Describe the workload before choosing a billing cadence.
A monthly contract does not automatically mean active experimentation, and a project does not have to be superficial. Compare the actual scope.
Match cadence to implementation capacity.
If your team cannot produce or publish changes regularly, a large recurring recommendation pipeline may become backlog. If releases and acquisition conditions change often, a single handoff may leave important decisions unsupported.
Use capacity planning to identify who acts on recommendations. Agree the review cycle around the work and evidence rather than the calendar alone.
Define what continues after the first month.
Ask what recurring work will be done, how it is prioritised and what happens when there is insufficient evidence for a new test. Useful ongoing support can include investigation or holding a change; it should still have a clear purpose.
Use reporting standards to distinguish decisions from activity. Avoid requiring pointless edits simply to demonstrate that someone was busy.
Make project completion and ongoing review explicit.
A project needs acceptance criteria and a handover. A recurring engagement needs review points, scope boundaries and a way to revise priorities. Both should explain how new requests are handled.
Compare proposal terms and ask how unresolved dependencies are documented. A billing arrangement should not hide an undefined deliverable.
Choose a starting point and revisit it.
A diagnostic project can inform whether ongoing work is useful. An established team may already have enough context to define a recurring programme. There is no need to present either route as universally superior.
Use the brief guide and Gabriel’s process to make the initial engagement concrete. Review the arrangement against actual needs as they evolve.
