Administrators & Principals How to pitch, what to say, and what to send.
Administrators aren't buying curriculum — they're buying outcomes, accountability, and peace of mind. They need to know FF will actually get implemented, teachers will actually use it, and they'll have the data to prove it's working. Speak to visibility, fidelity, and results — not features and frameworks.
Two Roles. Two Conversations.
Know Which Administrator You're Talking To.
Principals and district administrators have overlapping concerns but different scopes of authority. Your pitch, your proof points, and your ask are different for each. Never pitch a principal like a district admin — and never assume the district admin knows what the principal's day looks like.
Building Level
Principal / Assistant Principal
Head Chef™ Dashboard
Responsible for instructional quality inside one building. They care deeply about teacher performance, student outcomes, and whether implementation is actually happening in classrooms — not just on paper. They influence district decisions but often don't make them alone.
AI Tool Access: PD Pantry Assistant™ — manages and monitors teacher PD paths across the building.
District Level
Superintendent / Curriculum Director
Executive Chef™ Dashboard
Responsible for system-wide performance across multiple schools. They care about equity of implementation, district-level data, ROI, and whether a curriculum can scale. They hold budget authority and make final adoption decisions — but they often rely on building principals to advocate for what's working on the ground.
AI Tool Access: PD Pantry Assistant™ — system-wide PD oversight and implementation tracking across all buildings.
Who You're Talking To
Know Who's in Front of You.
Not all administrators come to this conversation the same way. Reading the room before you pitch saves you from speaking to the wrong priority and losing the meeting.
The Data-First Principal
Wants dashboards, reports, and proof. Skeptical of any curriculum that can't show them what's happening in real time. Lead with the Head Chef dashboard — teacher usage, student progress by framework, implementation fidelity — before you mention a single lesson.
The Teacher-Advocate Principal
Knows their teachers are stretched thin and will only support a curriculum their staff can actually use. They're the gatekeeper to teacher buy-in. Lead with how FF reduces teacher prep burden — the explicit lesson structure, the built-in differentiation, Chef's Chat™ for just-in-time support mid-lesson.
The Compliance-Minded Principal
Under pressure from the district to show Science of Reading alignment, MTSS documentation, and standards mastery data. They need FF to check the right boxes. Lead with SOR alignment, RTI/MTSS integration, and the standards-mapped curriculum architecture.
The Curriculum Director
Evaluating FF against other programs in a formal or informal review. They're analytical, thorough, and have probably seen dozens of pitches. Lead with the ecosystem angle — FF is not just curriculum, it's infrastructure. Then get them sample materials and a platform demo.
The Superintendent
Big picture, little time. They want to know: Will this work? Will it scale? What does it cost? How do we know it's working? Do not go deep on instructional frameworks in this meeting — keep it to outcomes, data, and ROI. Get them to delegate the evaluation to a curriculum director or principal champion.
The New Admin Taking Over
Inheriting an existing curriculum situation and looking for either validation or a fresh start. Be curious about what came before — don't assume they want to replace what they have. Listen first. If there are gaps, position FF to fill them. If they're open to a full adoption, lead with the transition support story.
What They Care About
Their Priorities. Your Talking Points.
Administrators are not reading the same research as classroom teachers. They're solving operational and political problems. These are the pressure points that make them move.
1
Implementation That Actually Sticks
Every administrator has bought a curriculum that ended up sitting in a closet. They need to know FF comes with the infrastructure to make implementation real — not just materials, but the Instructional Kitchen™ PD, the Head Chef dashboard to monitor it, and ongoing support built into the system.
2
Visibility Into What's Happening in Classrooms
Principals can't be in every room. The Head Chef dashboard gives them framework progress by teacher, student performance data by grade band, and implementation tracking — so they know whether FF is being used, not just whether it was purchased.
3
Teacher PD That Doesn't Add More to Teachers' Plates
Administrators are tired of PD that teachers complain about or ignore. The Instructional Kitchen™ is self-paced, curriculum-specific, and built into the same ecosystem teachers are already using. PD Pantry Assistant gives principals a coaching tool to guide teacher growth without scheduling another meeting.
4
Data They Can Show the Board or District
Whether it's a principal reporting up or a superintendent reporting to the board, administrators need documentation that FF is producing results. Lead with the standards-aligned assessments, the implementation portfolio, and the progress data the Executive Chef dashboard generates at scale.
5
RTI/MTSS Documentation and Tier Support
MTSS compliance is non-negotiable for most districts. FF's tri-level differentiated texts align directly to Tier 1 (whole class), Tier 2 (small group), and Tier 3 (intervention) — and the documentation lives in the platform. This is a significant operational relief for principals managing MTSS paperwork.
6
A K-12 System That Doesn't Need to Be Replaced Every Few Years
Curriculum transitions are expensive, disruptive, and politically complicated. Administrators want to adopt once and scale. The K-12 vertical alignment means FF is a long-term infrastructure investment — not another short cycle. That matters for budgets, for teacher morale, and for student continuity.
Platform Features for Admins
What They Get Inside the Digital Kitchen™.
Know these features cold. Administrators will ask what the platform actually shows them — have a specific, confident answer for each role. If they ask for a demo, direct them to the platform demo booking link.
Head Chef™ Dashboard Principals
Teacher progress tracking — framework usage, last login, lesson completion across every classroom in the building
Student performance data by framework, grade band, and text level — visible at a glance without pulling individual reports
Principal's Action Queue — surfaces which students need intervention and which teachers may need coaching support
Grade-level performance comparison — standards mastery percentages across all classes in the building
Teacher onboarding and PD assignment tools — assign Instructional Kitchen™ tracks and monitor completion
PD Pantry Assistant™AI — AI coaching tool for monitoring and guiding teacher professional development paths across the building
Executive Chef™ Dashboard District Admins
System-wide performance metrics across every school in the district — no manual report collection from buildings
Multi-school comparison — implementation fidelity and student outcome data side by side across all buildings
Teacher adoption and platform usage rates — see which schools are implementing with fidelity and which need support
Standards mastery data aligned to Florida B.E.S.T. and other state standards frameworks — ready for board reporting
Drill-down by school → grade level → classroom → individual student for investigation and intervention planning
PD Pantry Assistant™AI — system-wide PD coaching and implementation support, surfacing trends across buildings for district leadership
How to Frame the Conversation
The Opening That Works.
Administrators are busy and skeptical. They've been pitched a lot. Open with curiosity about their current situation — not a product presentation. Get them talking about their problems before you introduce any solutions.
The Opening Frame (Principals):
"Before I tell you anything about FF, I want to understand what you're working with. What does literacy instruction look like in your building right now — and what's the gap you're trying to close? I want to make sure I'm talking about what actually matters to you."
Listen for: implementation struggles, teacher inconsistency, MTSS documentation pressure, struggling student populations, science of reading mandates from the district. Then connect FF directly to what they said.
The Opening Frame (Superintendents / Curriculum Directors):
"I know you've probably seen a lot of curriculum pitches. I want to be direct about what makes FF different — and then get out of your way so you can evaluate it properly. Can I give you the 90-second version, and then we can go as deep as you want from there?"
The 90-Second Version: "FF is not a curriculum — it's academic literacy infrastructure. Six proprietary frameworks, K-12 vertical alignment, a dual-platform digital ecosystem, embedded professional development, and two AI assistants built into the platform. Districts aren't just buying lessons. They're building a system their teachers can grow inside for the next decade."
For Principals Focused on Teacher Buy-In:
"Teachers don't resist curriculum — they resist curriculum that doesn't support them. FF was designed so teachers spend less time planning and more time teaching. The lesson structure is explicit, the differentiation is built in, and Chef's Chat™ gives teachers just-in-time instructional support mid-lesson. The teachers who pilot it come back asking for more."
For Administrators Dealing with State or District Mandates:
"If you're under pressure to show Science of Reading alignment or MTSS documentation, FF checks both boxes — not as a marketing claim but structurally. SAVOR the Text™ is built on the five pillars of reading science. The differentiated texts align to all three MTSS tiers. And the documentation lives in the platform — it's not a separate reporting layer."
What to Say
Say This. Not That.
✓ Say This
✓"The Head Chef dashboard gives you visibility into every classroom — framework usage, student progress, implementation fidelity — without chasing teachers for reports."
✓"The PD is embedded in the same ecosystem teachers are already using. It's not another login or another platform to manage — it's built in."
✓"This is a K-12 system. You adopt once and scale — you're not replacing curriculum every three years because the vertical alignment degrades."
✓"The differentiated texts align to your MTSS tiers — Tier 1 whole class, Tier 2 small group, Tier 3 intervention — built in, not bolted on."
✓"We're the only K-12 literacy curriculum with dual AI assistants built directly into the platform — Chef's Chat for teachers mid-lesson, PD Pantry Assistant for administrators managing professional growth."
✓"Principals can assign PD tracks through the Head Chef dashboard and see exactly where every teacher is in their professional learning — no spreadsheet required."
✗ Don't Say This
✗Don't lead with framework names and descriptions. Administrators don't buy frameworks — they buy outcomes. Lead with what the frameworks produce, not what they're called.
✗Don't pitch the culinary theme to skeptical administrators. Some will love it, some will raise an eyebrow. Save the theme explanation until they ask about it or until you're in sample materials.
✗Don't go deep on student-facing features in an administrator meeting. They care about what they can see and manage — keep the student experience for the teacher pitch.
✗Don't assume a principal has budget authority. They're often influencers, not decision-makers. Ask: "Is this a decision you make at the building level, or does it go to the district?" before you talk pricing.
✗Don't oversell the AI features as futuristic or experimental. Frame them as practical, built-in tools that solve real operational problems — not as a selling point for its own sake.
Objection Handling
What They'll Say. What You'll Say Back.
We already have a curriculum we're using.
"What are you using, and how is implementation going?" Let them answer. "Is the PD piece built in, or is that separate? And do you have visibility into what's actually happening in classrooms day to day — or is that still a manual process?" Most administrators have gaps in one of those three areas. Find the gap and offer to fill it — even if that's a pilot in one building before a district decision.
My teachers are already overwhelmed — I can't add another new program.
"That's exactly the right instinct — and it's the reason FF was built the way it was. The explicit lesson structure means teachers spend less time planning, not more. The PD is self-paced and embedded in the platform they're already using. And the frameworks are designed to be repeatable — once teachers know the structure, it becomes their routine, not an added task. The schools that have had the strongest adoption are the ones where the principal introduced it as a support system for teachers, not a new requirement on top of everything else."
We need to see Science of Reading alignment documentation.
"Absolutely — and we can get you that. SAVOR the Text™ is built explicitly on the five pillars of reading science. We can provide standards alignment documentation for your state framework and walk your curriculum director through the instructional design. Most of what you need is visible in the sample materials — I'd encourage you to look at actual lessons rather than just alignment charts, because the SOR integration is structural, not cosmetic."
This seems like a lot — we're a small district and I'm not sure we have the capacity to implement it fully.
"Small districts actually have an advantage here — implementation fidelity is easier to achieve when you're not managing 40 schools. And FF scales in — you don't have to launch everything at once. A lot of districts start with one grade band or one school, prove it out, then expand. The platform and the PD infrastructure are the same whether you're running 3 schools or 30. What would a manageable first step look like for you?"
How do we know teachers will actually use it?
"That's the most honest question in this whole conversation — and it's one we take seriously. The Head Chef dashboard shows you exactly who's logging in, which lessons have been delivered, and how student performance is tracking against each framework. You'll know within the first month whether teachers are using it. But the more important question is whether teachers want to use it — and the ones who pilot it consistently come back and tell their principals it's the first curriculum that actually supports them mid-lesson. Chef's Chat™ is a big part of that."
What does implementation support look like — are we on our own after purchase?
"No — and this is a real differentiator. Implementation support is built into the ecosystem, not sold separately as an add-on. The Instructional Kitchen™ provides the PD layer. The Head Chef and Executive Chef dashboards give you visibility to catch implementation issues early. And the Lead Chef Circles™ track inside the Instructional Kitchen is specifically designed for principals and instructional coaches — it trains your building leadership to support implementation, so you're not dependent on an outside consultant to keep it going."
Resources to Send
The Right Document at the Right Time.
Administrators move slowly and deliberately. Give them the right material at the right stage — don't send everything at once. Follow up with a meeting after they've had time to review.
First — Always
District Overview
Send this immediately after first contact. It covers the full ecosystem, implementation model, dashboard features, and district pricing in a format built for administrator review. The most important document in this sale.
When an administrator is ready to see the Digital Kitchen dashboards in action, get them into a demo. The platform is the most powerful proof point — the dashboard walkthrough closes more than any document.
Curriculum directors and principals who want to evaluate instructional quality need to see actual lessons. Get them sample access — it's more convincing than any one-pager and moves review committees faster.
When a curriculum director needs to go deep on framework alignment, MTSS integration, and instructional design before a formal review, the Ecosystem Overview gives them the full picture in one place.
When administrators want to understand the professional development model — the four tracks, Lead Chef Circles for instructional leadership, and how PD connects to the platform — send them here.
District pricing is customized by size and adoption scope — don't quote a number without a conversation. Get them on a consultation call to build the right proposal for their district.