# Audience Intelligence: Cumulative attention-burden scores for school software

District administrator accountable for the software portfolio's total effect on students is the first audience because the report already names a repeated pain, reachable channels, and a validation test that can be run before software is complete.

## Segments
- **District administrator accountable for the software portfolio's total effect on students**: Each classroom app clears review alone, but stacked across a school day their autoplay, streaks, notifications, and variable rewards build an always-on attention load nobody measures - and the administrator who signed the contracts has to account for the total. Trigger: Common Sense Media and similar services rate apps individually; no tool models how engagement mechanics compound across a student's daily stack. Budget signal: Annual district subscription scaled by enrollment, plus per-review procurement-gate pricing.
- **Budget owner who feels the operational cost of the broken workflow.**: The compounding methodology must survive expert scrutiny or the score is dismissed as pseudo-measurement. Trigger: AI-assisted product work and managed infrastructure reduce the first-version cost. Budget signal: $49-$499/month
- **Hands-on operator willing to pilot a narrow tool before a full rollout.**: District sales cycles are slow and grant-dependent. Trigger: Annual district subscription scaled by enrollment, plus per-review procurement-gate pricing. Budget signal: $99-$1,000/year add-on
- **District administrator accountable for the software portfolio's total effect on students who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: Each classroom app clears review alone, but stacked across a school day their autoplay, streaks, notifications, and variable rewards build an always-on attention load nobody measures - and the administrator who signed the contracts has to account for the total. Trigger: The wedge is specific enough to test without claiming the whole market. Budget signal: Custom

## Channels
- **Reddit / forums**: Look for complaints, workarounds, and repeated questions. First move: Post a problem teardown for K-12 edtech procurement and ask how people solve it today.
- **Launch communities**: Launch traction shows whether the promise is legible. First move: Ship a narrow demo and watch which promise gets clicks.
- **Review and alternative pages**: Pricing and alternatives expose buyer objections. First move: Write an alternatives page that owns one narrow use case.
- **Community pain posts**: Use communities and forums where District administrator accountable for the software portfolio's total effect on students already describe the painful workflow. First move: Problem teardown, interview ask, and short demo clip
- **Direct outreach**: Direct conversations are the fastest way to verify budget ownership and switching cost. First move: Concierge pilot offer with a manually prepared sample

## Intent Keywords
`cumulative workflow`, `attention validation`, `cumulative ai`, `attention automation`, `education`, `screen-time`, `K-12 edtech procurement`

## Messaging Angles
- Cumulative attention-burden scores for school software should be tested as a narrow first-win workflow for District administrator accountable for the software portfolio's total effect on students.
- Replace a narrow workflow that reaches value without configuration-heavy onboarding. with a focused first-win workflow.
- Promise proof around problem resonance: 5+ calls or 10+ detailed replies..
- De-risk adoption with concierge review or paid template.

## Objections
- The compounding methodology must survive expert scrutiny or the score is dismissed as pseudo-measurement.
- District sales cycles are slow and grant-dependent.
- Needs real buyer access, not only desk research.
- Needs proof of budget or repeated urgency.
- Needs a crisp wedge before broad product work starts.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.