# When delivery depends on unapproved tools > The work stalls because required software access, cost or data handling was never discussed. Diagnose the cause, choose a bounded correction and verify projects with approved tool and access dependencies. Source: https://saas-marketing.net/guides/agency-strategy-depends-on-unapproved-tools/ Topic: SaaS Marketing Agencies Type: guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/agency-strategy-depends-on-unapproved-tools/ ## Short answer The work stalls because required software access, cost or data handling was never discussed. Start with this check: List tool dependencies and identify who approves access, spend and data use. The corrective action is to resolve the dependency or choose an approved alternative before promising the schedule. ## Key takeaways - List tool dependencies and identify who approves access, spend and data use. - Resolve the dependency or choose an approved alternative before promising the schedule. - Do not place private customer data into a new service without appropriate authorization. - Review projects with approved tool and access dependencies. --- The work stalls because required software access, cost or data handling was never discussed. The useful response is a diagnosis that changes a decision, not another report describing the symptom. Use this play with the client owner and agency delivery lead. The working evidence should include agreed scope, acceptance criteria and account ownership inventory, with private or sensitive details removed from any shared example. ## Confirm the problem in the actual workflow List tool dependencies and identify who approves access, spend and data use. Start with one representative case and follow it from the original action to the reported outcome. Identify where the observed behavior first differs from the intended process. A screenshot of a final dashboard can be useful, but it may hide the source record, a delayed update or a decision made elsewhere. Keep the unit of analysis explicit: a comparable deliverable or operating outcome. The same label can conceal different populations or stages. Before comparing two results, check that they describe the same kind of work and have had a comparable chance to complete it. ## Separate the visible symptom from the cause Compare the actual work, internal effort and delivery dependencies rather than the retainer alone. Keep reporting definitions and asset ownership clear enough that the client can inspect the work and continue operating after the engagement changes. The symptom in this case is specific: the work stalls because required software access, cost or data handling was never discussed. Ask which piece of evidence would distinguish an operating failure from a measurement failure or a mismatch in the original plan. If the evidence is unavailable, record the missing source and its owner instead of treating the preferred explanation as established fact. ## A situation to work through A proposed enrichment workflow is not ready merely because the agency has a preferred vendor account. This is an illustrative situation, not a reported client case. Record the equivalent evidence and assumptions for your own workflow. ## Choose the smallest useful correction Resolve the dependency or choose an approved alternative before promising the schedule. Keep the change narrow enough that the responsible people can implement and inspect it. If a correction changes several things at once, describe it as a combined operating change; do not later claim that one small element caused the whole result. Assign the correction to the client owner and agency delivery lead. Agree which artifact will show that the work is complete. An owner without an observable acceptance condition can close a task while leaving the original problem unresolved. A detailed checklist without an owner creates the opposite problem: the evidence requirement exists, but nobody is accountable for producing it. ## Preserve the important limitation Do not place private customer data into a new service without appropriate authorization. This condition belongs beside the recommendation because it can change the decision. It should not disappear when the plan becomes a short presentation or a status update. An agency can complete a draft while the deliverable remains blocked on an agreed technical review. That is different from failing to produce the draft. A useful scope distinguishes responsibilities and acceptance criteria so the relationship can address the real bottleneck. ## Verification worksheet | Review item | What to record for this issue | Owner | Evidence | | --- | --- | --- | --- | | Observed symptom | The work stalls because required software access, cost or data handling was never discussed. | | | | Diagnostic test | List tool dependencies and identify who approves access, spend and data use. | | | | Proposed correction | Resolve the dependency or choose an approved alternative before promising the schedule. | | | | Guardrail | Do not place private customer data into a new service without appropriate authorization. | | | | Review measure | Projects with approved tool and access dependencies | | | Download a working copy and follow the [worksheet instructions](/resources/#using-worksheets). Keep unknown facts visible rather than filling gaps with guesses. ## Decide whether to keep, revise or stop the change Review projects with approved tool and access dependencies after the agreed observation period. Keep the correction when the intended behavior is verified and the guardrail remains acceptable. Revise it when the diagnosis was useful but the intervention did not resolve the cause. Stop and reassess when new evidence shows that the original problem was framed incorrectly. Record what changed in agreed scope, acceptance criteria and account ownership inventory. This gives the next review a stable starting point and prevents a definition change from being mistaken for a performance improvement. ## Related methods and next steps - [Choose a B2B SaaS agency for complex buying](/guides/best-b2b-saas-marketing-agencies/) - [How to Choose a SaaS Marketing Agency in Three Weeks](/guides/how-to-choose-a-saas-marketing-agency/) - [Agency retainer break-even calculator](/calculators/agency-retainer-roi/) - [SaaS agency offboarding checklist](/checklists/saas-agency-offboarding/) Return to the [saas marketing agencies topic guide](/saas-marketing-agencies/), browse its [complete resource collection](/topics/saas-marketing-agencies/), or use the [working resource library](/resources/). The [primary reference](https://www.ftc.gov/business-guidance) provides relevant platform or methodological context; the diagnosis and example here are original editorial guidance. ## Frequently asked questions ### What is the first diagnostic check? List tool dependencies and identify who approves access, spend and data use. Inspect the actual working record or customer path rather than relying only on a summary report. ### What should change after the diagnosis? Resolve the dependency or choose an approved alternative before promising the schedule. Record the owner and the evidence needed to verify the correction. ### What limit should the team keep visible? Do not place private customer data into a new service without appropriate authorization. A local improvement does not establish a universal benchmark or guarantee a commercial result. ### How should the correction be evaluated? Review projects with approved tool and access dependencies using a consistent unit and observation window. Keep the original evidence and record any measurement changes.