Review the supplied cross-channel account-advertising plan as a planning document. Do not launch, upload audiences, spend money, or contact anyone. Do not invent facts, permissions, evidence, campaign IDs, results, or approvals. The user will paste a completed plan below this prompt; if none is supplied, ask for it.

Reference summary: account-based advertising is paid media around selected companies and buying roles. LinkedIn company targeting uses company scope; contact targeting matches known people. Meta customer lists match person identifiers rather than company-name lists. Website/engagement retargeting does not prove employer identity or prior comprehension. Expansion can turn a supplied list into a suggestion; strict-list intent requires actual configuration evidence. Eligible audiences and delivered reach differ. Platform conversion credits can overlap and must stay separate from deduplicated CRM people and opportunity IDs. Company-level engagement does not identify a named person. Revenue association is not causal proof.

Reference URLs (supplemental; no browsing required to understand this prompt):
https://business.linkedin.com/advertise/ads/targeting/matched-audiences
https://www.facebook.com/business/ads/meta-advantage-plus/audience
https://maestrogtm.com/account-based-advertising/

Check these fields. Preserve supplied values and distinguish Unknown, measured zero, and explicitly justified Not applicable:
1. Business/product facts; segment, countries, fit reason, source/date, distinct account count/IDs, buyer roles/problem evidence, customer/open-opportunity treatment, account/sales owner.
2. Real shared offer and contents; proof/permissions; destination and expected action.
3. For EACH route: platform/account/campaign; route type; observation unit and cutoff; source count and permitted-use evidence; matched count if applicable; final eligibility and dated evidence; actual audience mode/expansion/boundary and receipt; geography/roles/exclusions/lookback; message/proof/CTA; successful destination and CRM-response test; ceiling/currency/dates; approving owner and explicit launch authorization for exact scope; campaign owner; unresolved evidence with owner/action.
4. First channel/reason; condition for adding second; total media ceiling and production/management costs; reserve treatment; creative/destination/operations/sales owners.
5. Review period/time zone/owner; delivery and attribution settings; account-exposure definition; response and person/account identity rule; held/qualified meeting definition/owner; opportunity ID/stage/value/existing-opportunity treatment; self-reported source; cross-platform deduplication; sales response action/timing; repair decisions.

Output:
A. A concise proposed first-channel decision and why; do not force both platforms.
B. A table of each route's audience boundary, message, owner, budget, and exact unresolved checks. A positive audience size marked unusable stays positive and unusable.
C. Measurement definitions and any arithmetic correction. Never sum overlapping platform conversions into unique leads. If overlap/identity data are absent, unique total remains Unknown.
D. Draft Ready or Draft Hold, with reason. Draft can be Ready with unresolved native launch checks if the business, account fit/problem, real offer, route purpose, proposed budget, and owners support concrete preparation. Missing essential business/offer/fit facts require Draft Hold and focused questions.
E. Launch Ready or Launch Hold FOR EACH ROUTE. Launch Ready requires actual same-scope audience/configuration evidence, permissions, tested destination/CRM path, dates/budget, and explicit launch authorization. Empty fields, placeholders, pending approvals, denied permissions, historical irrelevant receipts, and unknown settings do not pass. Supplied approval for another scope cannot pass. Changing platform/account/campaign/boundary/unit/cutoff requires rechecking evidence and authorization.
F. Exact missing input, named owner if supplied (otherwise ask), next action, and whether it blocks drafting or that route's launch. Another route's hold does not erase valid evidence for an independently complete route.

Worked reasoning: fictional ServiceLedger has 80 selected firms, operations roles, and a real checklist planned. LinkedIn company targeting is a sensible route to evaluate; Meta retargeting awaits a real visitor audience. Draft Ready is possible, but both routes stay Launch Hold without real receipts and authorization. A proposed USD 1,500 Meta reserve stays unspent if the route is not eligible. Four LinkedIn credits plus three Meta credits with two verified shared people gives five unique people, not seven; without identity reconciliation the unique total is Unknown.

PLAN TO REVIEW: