# Completed fictional seed and review brief

Harborline Ops is fictional. Every identifier, count, state assumption, budget, and decision rule below is an exercise input. This is a positive planning example; it contains no observed LinkedIn account result or platform receipt.

1. **Review request:** Review this fictional plan for a native Campaign Manager build handoff. No platform action requested.

2. **Business and offer:** Harborline Ops, a fictional workflow software company, offers a demo to US operations teams.

3. **Account and operator:** Fictional account HO-EXAMPLE; Maya, paid-media operator. These are exercise identifiers, not LinkedIn IDs.

4. **Business outcome and quality rule:** Sales-accepted demo: operations buyer at a US company with 50–500 employees, a documented workflow problem, and a scheduled sales meeting. Sales records acceptance in CRM.

5. **Source type and build route:** Contact list; native Campaign Manager. No API build planned.

6. **Source IDs and selection:** One fictional contact source HO-CUSTOMERS. Do not combine it with a form or conversion source.

7. **Source behavior and fit:** Closed-won customer contacts for the same product and operations buyer. This is a qualified acquisition hypothesis; customer similarity does not guarantee new qualified demos.

8. **Source window and cutoff:** Closed-won dates 2026-04-01 through 2026-09-30; source data cutoff 2026-09-30 23:59 UTC.

9. **Source version:** HO-CUSTOMERS v3, completed export. Version identifies the data, not when someone viewed it.

10. **Source observation and evidence:** Exercise record observed 2026-10-31 12:00 UTC. All source figures and states below are hypothetical inputs. No native screenshot, export, or receipt supplied.

11. **Source status and completed version:** Assumed Ready for this exercise; latest completed version v3. No refresh processing. Actual native status unknown.

12. **List rows and member counts:** 1,240 contact-list rows; 910 matched member accounts, both fictional supplied counts. Rows govern the list requirement; matched members are a separate population.

13. **Multiple-source member count:** Not applicable: one contact list. For multiple member-based sources, record the native combined member count and overlap; do not assume sums are unique members.

14. **Source eligibility assessment:** 1,240 rows is within the documented 300–300,000 list range. This supports a planning check only; native eligibility remains unknown.

15. **Data permission and account access:** Fictional supplied fact: source-use permission is documented for HO-EXAMPLE and HO-CUSTOMERS v3. This is an exercise assumption, not a real permission receipt. Actual account access remains unknown; Maya must verify it.

16. **Agreement and execution authority:** Unknown. Account owner must review the native agreement and authorize any build or spend separately. This request authorizes planning only.

17. **Modeled geography and size:** Proposed United States; desired modeled audience 100,000 members, a planning choice subject to available native slider values. Forecast and realized size unknown.

18. **Seed exclusion plan:** Exclude HO-CUSTOMERS at ad-set level to seek new prospects. Actual exclusion configuration unknown; Maya must verify it after setup.

19. **Other exclusions and overlap:** Propose excluding current customers and open opportunities using separate maintained lists. Confirm availability, versions, and application; compare overlap with the benchmark audience before interpreting results.

20. **Build handoff and proposed name:** HO | customer v3 | US | prospecting. Maya: Plan → Audiences → Create audience → Predictive audience; choose Contact list and HO-CUSTOMERS, set US and supported size, then seek the required agreement/build authorization. Record audience ID after creation.

21. **Account limits and source sharing:** Current counts unknown. Maya must verify fewer than 200 predictive audiences and room within 1,000 combined segments before creation. No sharing planned; predictive audiences cannot be shared across accounts.

22. **Build and Ready evidence:** Not built in this exercise; audience ID, creation time, Ready time, and desired-size observation unknown. Check daily refresh and allow up to five days after Ready to reach desired size.

23. **Campaign delivery evidence:** No campaign created or served in this exercise. Campaign/ad-set IDs, spend, impressions, and delivered cohort unknown. A forecast or Ready status cannot establish delivery.

24. **Comparable audience and controls:** Proposed existing US operations-role audience with the same 50–500 employee company range. Use the same demo offer, ads, form, optimization objective, schedule, and budget per arm; record differences and overlap. This is a descriptive comparison unless an appropriate randomized design is established.

25. **Budget and schedule proposal:** Proposed $100/day per audience for 28 days: $2,800 each, $5,600 total. Start date to be set after actual build and authorization; no spend approved here.

26. **Outcome cohort and maturity:** Group leads by submission week and audience/ad set. Review sales acceptance 30 days after each submission; exclude immature leads from mature-cohort rates and report their count separately.

27. **Results and denominators:** Not run. Spend, impressions, clicks, submitted leads, mature leads, sales-accepted demos, and opportunities are unknown, not zero. Calculate cost per accepted demo from comparable mature cohorts; define attribution and deduplication before reporting.

28. **Decision rule and review owner:** Maya and sales lead review mature cohorts. Proposed planning rule: expand only if qualified-demo cost is no higher than comparison and accepted-demo rate is no lower, with at least 20 mature leads per audience. Twenty is a team choice, not a LinkedIn requirement or proof of significance; otherwise extend or diagnose.

29. **Change and reevaluation record:** No changes yet. If account, source ID/type, count unit, version, or cutoff changes, reopen affected eligibility, fit, exclusions, permission scope, and comparison checks. Preserve earlier evidence. New reach or version never restores permission by itself.

30. **Handoff conclusion and next evidence:** Planning complete for this fictional exercise. Native eligibility/build, access and permission, exclusions, delivery, and outcomes remain unverified. Maya owns account/source checks and verification of the supplied permission scope; sales lead owns outcome definitions and CRM reporting. Return the proposed build and review handoff without claiming launch readiness.