FIRST 100 MAC APP USERS — WORKSHEET
Suggested working exercises, not acquisition forecasts.

1. DEFINE THE USER AND RESULT
App:
Audience:
Task and situation:
Current workaround:
Reason to switch:
One-sentence promise:
First useful action that counts as activation:
Natural next-use opportunity (daily / weekly / task-based):
Current unique activated users:
How that count is measured (or why unknown):

2. FIND EVIDENCE
Record five relevant discussions. These are research leads, not permission to DM.
Discussion URL | Audience | Their wording | Current workaround | Appropriate contribution

3. CHECK THE EXPERIENCE
[ ] Download/store link works
[ ] Price and trial limits are clear
[ ] macOS and processor requirements are visible
[ ] Signing/notarization checked for direct distribution
[ ] Permissions explained when needed
[ ] Real demo shows input, action and result
[ ] Support and privacy information accessible
[ ] A new user attempted the task without coaching
Biggest blocker:
Fix and date:

4. CHOOSE TWO INITIAL CHANNELS
Channel:
Audience-fit evidence:
Current rules/eligibility URL and date checked:
Submission route / posting format:
Free or paid; spending cap:
Message and offer:
Campaign URL (only where allowed):
Time budget:
What is being tested:
What result would justify another test:
Review date:

5. USER NOTES — use anonymous local IDs; don't log private document contents
User ID | Known source or unknown | First useful result | Assistance needed | Next-use opportunity | Returned? | Paid? | Main friction
Record only what the person voluntarily shares or appropriately disclosed measurement supports.
Keep counts aggregated if identifying individual people isn't necessary or reliable.

6. CHANNEL REVIEW
Channel | Dates | Hours | Spend | Website visits | Downloads | Activated users | Returned at next use opportunity | Purchases | Attribution limits
Leave unknown values as unknown; don't enter zero for missing data.
Activation rate = activated users / compatible measured installs in the same cohort.
Visit-to-download rate = downloads / website visits for the same measured cohort.
Cost per activated user = campaign spend / reliably attributed activated users.
Report denominators and dates. Don't combine unrelated cohorts or infer app usage from UTM visits.

7. WEEKLY DECISION
What worked, and what supports that conclusion?
Where did people stop?
What did users say in their own words?
One change for next week:
One channel to repeat:
One activity to pause:
Who needs an answer or an agreed follow-up?

8. BEFORE PAYING FOR PROMOTION
[ ] Audience and first useful result are clear
[ ] Fresh installation works
[ ] Some real users have reached that result
[ ] Placement, duration and price are documented
[ ] Spending cap and review date chosen
[ ] Attribution limits understood
[ ] Cost can be compared with actual purchases, refunds and support effort

Illustrative traffic planning only:
Needed relevant visits = remaining activation goal / assumed visit-to-activation rate.
For 100 activations: 2% implies 5,000 visits; 5% implies 2,000; 10% implies 1,000.
These are hypothetical scenarios, not industry benchmarks or expected channel performance.