OKR Framework: FY2027–FY2028

Luminary Learning — Scaling from 220 to 800 School Districts

Date: 2026-05-30 · Prepared by: Resolvix · Status: Sample Deliverable
Deliverable type: Strategy & Business Planning — OKR Framework (~$650)
Industry: EdTech SaaS / K-12 Learning Management

About this sample. This is one example of what a successful Resolvix deliverable looks like at this scope and type — not a template that every engagement follows. Your expert brings their own expertise and judgment to the work: the structure, the emphasis, which angles they dig into, and how they organize their findings will all vary based on your industry, your specific question, and where the research leads. What stays consistent across every engagement is the standard: analysis grounded in evidence, prioritized recommendations, concrete action steps, and a phased implementation plan. All company names, figures, and scenarios in this sample are illustrative.

Context & Design Rationale

Luminary Learning is a K-12 LMS platform serving 220 school districts as of May 2026, with a target of 800 districts by December 2027 — an 18-month, 3.6x growth challenge. The company competes primarily against Schoology (now part of PowerSchool), Canvas (Instructure), and Seesaw, with a differentiated position around real-time teacher workflow automation and standards-aligned AI tutoring.

At 220 districts and ~$9.4M ARR, Luminary is entering the inflection zone where the systems that got it here — a scrappy sales team, manual onboarding, founder-led product — become constraints. The OKR framework below is designed to:

1. Focus the entire organization on the growth rate required to hit 800 districts without fragmenting effort across too many initiatives
2. Surface execution risk early — through leading indicators embedded in key results — rather than discovering misses at quarter-end
3. Distinguish between growth OKRs (new districts) and retention OKRs (keeping and expanding existing ones), which require fundamentally different capabilities and resources

OKR Operating Rules for Luminary:
- OKRs set at Company, Team, and Individual levels; this framework covers Company and Team
- Cycle: quarterly key result check-ins; objectives reviewed and reset annually
- Scoring: 0.0–1.0 scale; 0.7 is "good"; 1.0 is rare and may indicate insufficient stretch
- Owner: each OKR has a single accountable lead (not a committee)
- Dependency flags: OKRs that require cross-team coordination are marked with a 🔗 symbol

Company-Level OKRs

Company Objective 1: Achieve Growth at Scale Without Sacrificing Product Experience

Context: Luminary must prove it can onboard and retain districts at 3–4x its current pace. The risk is growth that creates a retention crisis in FY2028 — districts churned because onboarding was chaotic and product didn't deliver on the sales promise.

Company Objective 2: Build the Operational Infrastructure to Support 800 Districts

Context: At 220 districts, Luminary runs lean — founders are in Slack channels, onboarding is semi-manual, support tickets are handled by generalists. That model does not work at 800 districts. This objective is about building the systems, processes, and team capacity that make scale possible.

Company Objective 3: Win the Enterprise District Segment

Context: Luminary's 220 current districts are primarily small-to-mid-size (1,000–8,000 students). The path to $25M+ ARR requires winning larger districts (15,000+ students, state capital cities, county-wide systems). These are longer sales cycles, require procurement compliance, and demand enterprise-grade security and integrations — capabilities Luminary is currently building.

Company Objective 4: Make the AI Tutoring Differentiator a Proven Retention Driver

Context: Luminary's AI-powered tutoring module ("Luminary Spark") is the product's clearest competitive differentiator versus Schoology and Canvas. But adoption is uneven — only 31% of districts with access have activated it with more than 10% of students. If Spark becomes a true habit, it becomes a lock-in mechanism. If it stays a feature that districts underutilize, competitors can replicate it.

Team-Level OKRs

Sales Team OKRs

Team Objective: Fill and Close a Pipeline That Hits 800 Total Districts

Customer Success Team OKRs

Team Objective: Make Every Existing District a Reference Account

Product & Engineering Team OKRs

Team Objective: Ship Infrastructure and Features That Enable Scale

Marketing Team OKRs

Team Objective: Build Brand Authority That Pulls Pipeline Rather Than Pushes It

People & Operations Team OKRs

Team Objective: Build the Team Capacity to Support 3.6x Growth

OKR Calendar

Scoring Guidance

OKRs are not performance reviews. Scores are used to improve planning — not to penalize teams who set ambitious targets and fall short of 1.0.

Recommendations

1. Treat time-to-first-value (KR 1.4: 74 days → 35 days) as the most critical operational bet of H1 2027. At 3.6x growth, slow onboarding becomes an existential problem — it creates a backlog that CS can't clear, generates early churn signals, and poisons NPS before districts ever experience the product's real value. The automated provisioning work (P-KR 4) and the Certified Onboarding Specialist program (PO-KR 3) are both load-bearing here. Neither can slip past Q2.

2. Invest in evidence before you need it — start the learning outcome studies now. KR 4.3 and M-KR 3 require independent, credible outcome research. These studies take 12–18 months to design, run, and publish. Commission at least one immediately using data from districts that have had Spark active for 2+ years. Luminary needs published evidence by late 2027 to compete for enterprise and SEA contracts — which means the research must begin in Q1 2027 at the latest.

3. Win state procurement contract vehicles (S-KR 6) — they are the multiplier on everything else. A single state contract vehicle (e.g., Texas DIR, Florida PRIDE, California's PEPPM equivalent) can give hundreds of districts the ability to purchase without an RFP process. Three such placements could add 150–200 districts through a channel that requires almost no incremental sales effort per district. Assign CRO Nakamura personal ownership of this with a dedicated budget.

4. Don't let the 🔗 dependencies silently fail. Six key results are cross-team dependencies. Each one needs a named coordination owner who is not the team leader of either team — someone explicitly responsible for making the handoff work. Assign the COO (or equivalent operator) to own all dependency coordination as a standing Q1 responsibility.

5. Build and publish the district health score before adding new districts at scale. CS-KR 4 (health dashboard) enables everything else in customer success — it tells the team which districts are at churn risk before the renewal conversation happens. Launching it in Q1 means the CS team will have two full quarters of health data before the heaviest onboarding load hits in H2. Delaying it to Q2 or Q3 is a false economy.

6. Set a company-level "OKR health" review — separate from the business review. Many companies score OKRs once a quarter and move on. At Luminary's growth rate, a quarterly cycle is too slow to catch execution drift. Establish a monthly "OKR pulse check" — a 45-minute CEO-led meeting where each KR owner gives a 60-second update on status, confidence, and any blocker. This is not a full scoring session; it's an early warning system.

7. Protect product NPS (P-KR 6) as a leading indicator of retention. District admin NPS and teacher product NPS are different signals. Teachers are the daily users; their satisfaction drives classroom adoption, which drives renewal conversations. A teacher NPS of ≥ 51 should be treated as a proxy for whether the product is actually working at ground level — not just whether procurement is happy with the relationship.

Action Steps

Implementation Plan

Phase 1: Foundation Quarter (Q1 2027)

Objective: Get the OKR system operational, close the most critical infrastructure gaps, and ensure every team understands their targets before the growth engine accelerates.

Outputs / Milestones:
- All Company and Team OKRs finalized and published by January 7
- All individual OKRs completed and approved by January 15
- Monthly OKR pulse check cadence on CEO calendar by January 7
- District health score model designed by January 31
- First learning outcome study commissioned by January 31
- State procurement contract application filed for at least one vehicle by February 15
- District health dashboard live in CS tooling by March 15
- Automated provisioning sprint underway; completion projected for Q2
- SOC 2 Type II audit scheduled; in-progress

Success Criteria:
- 100% of OKRs published and owned by January 15
- Cross-team dependency pairs all have named coordination owners
- Q1 pulse checks happening monthly (3 of 3 completed by April 1)
- District health dashboard live and in weekly use by CS team
- Provisioning automation on track for Q2 release

Dependencies:
- CEO commitment of time to monthly OKR pulse check (non-negotiable)
- Engineering capacity to run SOC 2 audit prep and SIS integrations concurrently
- VP People hired or in seat to own the onboarding specialist program

Phase 2: Growth Execution (Q2–Q4 2027)

Objective: Execute the growth plan — add 580 net new districts, retain and expand existing ones, and close the year with OKRs scored and FY2028 targets in place.

Outputs / Milestones:
- Automated district provisioning shipped and live (Q2)
- SOC 2 Type II certified (Q2)
- All 5 SIS integrations complete (Q3)
- CS team at 44 FTE; Certified Onboarding Specialist program complete (Q3)
- District NPS ≥ 58 confirmed (Q3 NPS survey)
- Luminary Spark activation ≥ 72% (Q3)
- Total districts ≥ 800 (Dec 31)
- ≥ 1 learning outcome study published
- 3 state procurement vehicles secured
- Annual OKR retrospective published; FY2028 OKRs drafted (early Jan 2028)

Success Criteria:
- Total active districts ≥ 800 by December 31, 2027
- District NPS ≥ 58 (Q3 2027 measurement)
- Gross revenue retention ≥ 91%
- Spark activation ≥ 72%
- Company-level OKR average score ≥ 0.72 across all key results
- Voluntary turnover ≤ 10%

Dependencies:
- Phase 1 infrastructure (provisioning automation, health dashboard, SOC 2) complete on schedule
- Sales pipeline of ≥ 350 qualified opportunities maintained from Q2 onward
- Learning outcome study data available from districts with ≥ 24 months of Spark usage
- State procurement vehicles filed in Q1 and approved in time for Q3/Q4 selling season

Document owner: COO · Review cadence: Monthly OKR pulse check (CEO-led); quarterly formal scoring and publication · Next scheduled review: April 5, 2027