Forty-three states now restrict phones in schools. Districts were told what outcome to produce and handed no instrument to produce it. Ockham Logic builds that instrument, and the compliance record that proves it worked.
State counts as of January 2026 (Newsweek tracker). Settlement figures from the August 26, 2026 attorneys-general announcement. Enrollment is NCES fall 2022, the most recent published actual.
None of them is a trend we are betting on. All three have already happened.
State phone laws name an outcome: devices restricted during instructional time, exceptions honored for IEP/504 and medical need, compliance reported annually. They do not name a product, fund a product, or say how a principal is supposed to make 1,800 devices obey a bell schedule. Every district in 43 states now owns an unfunded implementation problem with a statutory deadline attached.
On August 26, 2026, Meta settled with the attorneys general of nearly every state: at least $12.1 billion, up to $17.1 billion if the other platforms follow, paid to states over roughly a decade. Many states must spend at least half on youth social-media harms, a category that names phone-free school grants alongside mental-health support and after-school programming. For the first time the compliance obligation and the money to satisfy it are landing in the same place. Districts that had a mandate and no line item are about to have both.
Jamf, Intune, and Google Admin manage devices as assets: inventory, imaging, OS updates, app catalogs. They are not geofenced, not schedule-aware, and a fleet-wide policy change moves on a polling cycle measured in minutes. A district asked to prove that phones were restricted between 8:05 and 3:10, on campus only, with 41 documented exceptions, cannot produce that from an MDM. This is not a feature gap inside an existing product. It is a missing layer.
It decides, continuously, whether a device is inside a managed campus boundary during an instructional window, then applies or releases policy accordingly, across every platform in the fleet.
A silent push applies a policy change, or Emergency Lockdown, across the entire fleet. No polling cycle to wait out during a drill.
Always-on without the drain that gets monitoring tools uninstalled by week three.
Per-device enrollment by QR scan, policy baked in. Rollout day does not become a help-desk event.
No rip-and-replace, no displacement fight with the incumbent, no new hardware. The shortest path through a district procurement office.
Enforcement is bound to the geofence and the bell schedule by design, and location logging defaults to lockdown-only. This is the clause that survives the board meeting.
Every decision is logged and exports as the compliance report a state reporting office, or a grant administrator, will ask for.
A U.S. provisional patent application covering the geofenced, schedule-aware enforcement method behind Focus is on file with the USPTO.
The iOS, Android, and ChromeOS clients resolve policy against a single shared truth table, verified by both native test suites. A decision made on campus at 10:14 a.m. cannot come out differently on an iPad than on a Chromebook. Cross-platform consistency is the part competitors underestimate and then cannot retrofit.
Enforcement is scoped to campus and school hours; location history defaults to off; content, messages, and browsing are never collected. That posture is what gets a program past parents, unions, and school boards: the three places competing tools die.
Once a district's geofences, bell schedules, exception roster, and multi-year audit trail live in Focus, the reporting obligation itself becomes the switching cost.
Recurring per-device subscription with volume tiers, plus a flat license for single buildings and a managed tier for districts that want the rollout run for them.
| Motion | Price | Who it is for |
|---|---|---|
| Free pilot | $0 · 60–90 days | One or two schools, configured in an afternoon. The district decides with its own compliance data in hand. |
| Per device, self-serve | $4 / device / yr | Districts running their own IT. $3.50 at 5,000+ devices, $3.00 at 15,000+. |
| Per-school license | $1,750 / yr | Private schools and single buildings. Unlimited devices, one number to approve. |
| District enterprise | $5 / device / yr | Managed rollout, Jamf/Intune/Google integration, priority-support SLA. $30K annual minimum. |
49.6 million US public school students, at the published $3–$4 per managed device per year, is on the order of $150M–$200M of annual recurring revenue at full domestic penetration of public K-12, before roughly 4.7 million private-school students and before international. We would rather show you the arithmetic than a billion-dollar slide. The point is not that the ceiling is enormous; it is that the category is compulsory, newly funded, and currently unserved.
Shipping across three surfaces: native iOS and Android student clients, and the web admin console, covering geofencing, bell schedules, policy tiers, enrollment, alerting, analytics, and Emergency Lockdown.
Deployed on AWS with infrastructure defined in Terraform, SSO/SAML, encryption in transit and at rest, and a full audit log.
Free 60–90 day pilots open to districts now, with published pricing and self-serve onboarding behind them.
Built to FERPA and COPPA expectations, with a SOC 2 track and district-ready privacy, security, and compliance one-pagers.
U.S. provisional patent application filed on the core enforcement method.
Small and deliberate, led by a founder with twenty years in modular system design and legacy modernization. Meet the team →
If the thesis lands, we are glad to walk through the product, the pipeline, and the roadmap in detail. Reach the founder directly.
hello@ockhamlogic.comImportant notice. This page is provided for general informational purposes only. It is not an offer to sell, or a solicitation of an offer to buy, any security, and it is not a recommendation to make any investment. Nothing here constitutes investment, legal, tax, or accounting advice.
Product performance figures describe intended and tested behavior and are not audited results. Statements about markets, funding, litigation, regulation, and future plans are forward-looking and reflect current expectations; actual outcomes may differ materially. Third-party figures, including state policy counts, settlement amounts and terms, enrollment data, and pending litigation, are drawn from public sources as of the dates noted and may since have changed. Nothing here is endorsed by, or implies any relationship with, any state, agency, district, or platform referenced.
Patent pending status refers to a filed U.S. provisional patent application. A provisional application is not an issued patent, confers no enforceable rights on its own, and no assurance can be given that any patent will ultimately be granted.