Local Nerds FASCO SOW
FASCO Alignment Hub

Give FASCO clients one place to run the work

Local Nerds will turn the approved FASCO model into a secure operating hub that helps school-system admins run the rhythm, helps embedded integrators see where work gets stuck, and gives FASCO implementation insight it can use across schools and systems.

One operating rhythm Less integrator friction FASCO-owned insight
Proposal thesis

The real ROI is implementation intelligence FASCO owns

The Hub reduces friction for embedded integrators and school-system admins. The larger advantage is becoming the source of truth for what schools are trying to solve, where they get stuck, and which issues repeat across systems.

Integrator friction drops

Embedded FASCO integrators can see priorities, blockers, follow-through, and engagement without stitching together email, spreadsheets, and memory.

School systems get one rhythm

Administrators work in the same operating model FASCO teaches, with clear tasks, Huddles, scorecards, priorities, and accountability.

FASCO owns pattern data

The system shows which problems teams are solving, which blockers recur, and which support needs appear across schools and districts.

Operating data layer

What FASCO learns that it cannot see today

Once the operating rhythm lives inside one system, every implementation starts producing structured signals. FASCO can see what teams are solving, where support is needed, and which patterns repeat across schools and systems.

Problem categories

Which issues school systems are actively trying to solve through Rocks, Later List items, Huddles, Tasks, and scorecard conversations.

Repeated blockers

Where implementation stalls: missing owners, unclear handoffs, delayed decisions, unresolved tasks, and low follow-through.

Adoption signals

Which accounts are using the rhythm: login activity, invite activation, Huddle cadence, scorecard updates, and task closure.

Support priorities

Where FASCO should refine coaching, training, templates, product guidance, and expansion conversations.

Every implementation makes the next implementation smarter.
Product surface

What the Hub becomes in v1

The approved prototype becomes a database-backed operating platform for the FASCO weekly rhythm.

Dashboard

Assigned work, open priorities, Vitals, Rocks, Tasks, and upcoming Huddles.

Accountability Circle

Circular accountability model adapted for school and district leadership roles.

Vitals / Scorecard

Owned metrics, targets, status checks, and weekly review patterns.

Rocks

Quarterly priorities with owners, due dates, milestones, progress, and updates.

Later List

CLEAR workflow support for important items that should not derail the week.

Weekly Huddle

Agenda runner that brings Vitals, Rocks, Later List, Tasks, notes, ratings, and recap history together.

Tasks

Assigned follow-up work tied to Huddles, Rocks, Later List items, and manual entry.

Vision and Methods

Core direction, annual goals, values, and lightweight process resources.

Settings and Notifications

Users, roles, coach assignment, reminders, invites, and launch account setup.

Build reality

Production work is mostly below the interface

The prototype shows the experience. The launch build adds the infrastructure that makes the experience safe, persistent, and usable.

Access and identityGoogle SSO, Microsoft SSO, invites, weekly magic links
Tenant and permission modelFASCO, districts, schools, teams, users, admins, coaches
Data and workflowsStructured operating data, audit trail, imports, engagement and pattern indicators
Launch operationsCloudflare deployment, backups, monitoring, QA, support handoff
Scope discipline

Admin operating platform for school systems

This boundary protects timeline, compliance risk, and price. The v1 build supports FASCO, district, and school-system administrators, leaders, and coaches.

Included in v1

  • FASCO system admins, FASCO coaches, district administrators, school administrators, and site leaders
  • SSO, invites, magic links, roles, account setup, permissions, and coach read-only visibility
  • Core FASCO modules with persistent data and launch-ready testing

Explicitly out of scope

  • Learner accounts, learner-facing workflows, learner data, or classroom record systems
  • SIS, LMS, OneRoster, LTI, ClassLink, Clever, or other classroom-system integrations
  • AI features, native mobile apps, public API, full Ninety parity, payment portal, or advanced reporting
Launch plan

Timeline starts with late June v1 confirmation

The schedule assumes final v1 confirmation in the last week of June, then a July production build start with timely access to brand assets, SSO coordination, and starter launch data.

Late June

Confirm v1 scope, launch definition, priorities, access model, and client inputs required for build start.

July

Start production build: hosting, database, deployment, tenant model, roles, access, core workflows, and emails.

August

Launch usable v1 for early districts, resolve blockers, verify roles, emails, data persistence, and Huddles.

Year one

Managed platform stewardship, routine maintenance, backups, monitoring, support, and controlled improvements.

Commercial terms

Investment aligns build and managed year-one support

The monthly component is part of the year-one productization and managed platform obligation. It is not an unlimited feature-development retainer.

$7,535Due at project start
$5,555Due at launch
$1,215Per month for 12 months
$27,670 total build investment
Definition of done

Acceptance is tied to live user workflows

Access works

  • District admin signs in, accesses the right district, invites users, and manages roles.
  • Google SSO, Microsoft SSO, invites, and weekly magic links work for launch users.
  • FASCO admin can see launch accounts, adoption indicators, problem themes, and blocker patterns.
  • Coach can view assigned district data and cannot view unrelated districts.

Workflow works

  • Vitals, Rocks, Later List, Tasks, and Weekly Huddle persist across sessions.
  • Weekly Huddle can generate or preserve recap and history content.
  • Production deployment is live on the agreed Cloudflare-hosted environment.
Decision path

Approve scope and start foundation work

The cleanest path is to confirm the v1 launch definition in the last week of June, then start the July production build.

Proposal deck

Editable PPTX for the buyer-facing conversation.

Download deck

Detailed SOW PDF

Scope, exclusions, responsibilities, payment schedule, acceptance criteria, support, and signature block.

View SOW PDF