Planning help for districts, before there's a product to sell you
k12.consulting is advisory work under the K-12 name — for schools that want a plan, not another vendor pitch.
What this is
k12.consulting is Stanley Studios' independent advisory practice for K-12 operations decisions: switching photo/yearbook vendors, evaluating an SIS migration, standing up parent communications, or scoping a school-safety tip-intake process. The deliverable is a written plan and a vendor-neutral recommendation — not a software seat.
Every engagement runs on one of three named tracks (see "Engagement tracks" below), is scored against the same five-dimension methodology regardless of category, and ends in a document the district owns outright — there is no software license, no seat count, and no renewal to negotiate.
What this isn't
Not a software product. It has no login, no dashboard, and nothing to configure. If a district already knows which product it wants, this page is the wrong page — go straight to that product's own site.
Not a commissioned sales channel. No vendor pays for a favorable mention in a written plan, including Stanley Studios' own products — see the conflict-of-interest objection below for how that disclosure actually works.
Not the k12.associates roster. k12.associates lists many implementation and migration firms; this page is one firm's own site, not an entry in that directory.
Not a compliance auditor or legal counsel. Where an engagement surfaces a data-privacy, FERPA, or consent gap, the recommendation is to engage the right specialist by name — this practice does not certify legal compliance on a district's behalf.
Not a staffing agency or fractional CTO retainer. There is no ongoing headcount and no monthly retainer model — each engagement is scoped once and ends when the plan is delivered.
Who it is for
A district technology director who has three vendor demos booked and no framework to compare them.
A school business office replacing a photo/yearbook contract mid-cycle and needs the transition mapped before signing anything.
A principal's office that wants a safety-tip intake process reviewed by someone who did not build the tool being reviewed.
A curriculum or operations lead standing up parent communications for the first time and needs the rollout sequenced against the school year calendar, not against a vendor's sales quarter.
It is not for a district that already knows which product it wants — go straight to that product's page. See "What this isn't" above for the full list of what this practice deliberately does not do.
Engagement tracks
"Planning help" is not one shape. Every engagement starts on one of three named tracks below so the scoping call has a concrete target instead of an open-ended conversation. A district can start on one track and the written plan can recommend moving to another — that recommendation is stated explicitly, never assumed.
Vendor decision
For: A district with two or more vendor demos booked (photo/yearbook, SIS, parent-comms, or safety-tip intake) and no shared framework for comparing them.
Deliverable: A written options table scoring each vendor on cost over the contract term, data-export rights at exit, minors'-data handling, staff training load, and integration burden with existing systems — plus a single ranked recommendation and the reasoning behind it.
Boundaries: This track does not run the vendor demos for you and does not negotiate contract terms on your behalf; it produces the framework and the recommendation you take into your own negotiation.
Migration readiness
For: A school business office or IT director replacing a system mid-cycle (SIS, photo/yearbook, or comms platform) who needs the transition mapped before anyone signs anything.
Deliverable: A sequenced migration plan: what data has to move and in what order, which records are minors' data and therefore need a named data-handling step rather than a bulk export, where the two systems must run in parallel, and a rollback point if the migration stalls.
Boundaries: This track does not perform the migration or write integration code; it is the plan a technical team (yours, the vendor's, or an implementation partner's) executes against.
Safety-tip intake review
For: A principal's office or district safety lead who wants an existing or proposed tip-intake process reviewed by someone who did not build the tool being reviewed.
Deliverable: A written review of the intake path a student or family actually walks: whether it requires sign-in, whether the anonymous claim on the page matches what the serving path can deliver, and where the review found the copy over- or under-claiming a capability.
Boundaries: This track is a review of process and public-facing claims, not a security penetration test or a legal compliance certification — where the review surfaces a data-handling gap, the recommendation is to engage the right specialist, named plainly, not to paper over it.
How an engagement works
Scoping call. One conversation to establish which of the three engagement tracks fits, what decision is actually being made, and by when.
Written plan. A document naming the options, the real tradeoffs (cost over the contract term, data-export rights at exit, staff training load, minors'-data handling where relevant), and a single ranked recommendation — structured around the five-dimension methodology below, not a free-form memo.
Vendor-neutral review. Where Stanley Studios products are a fit, that is stated plainly as a conflict of interest to weigh, not hidden.
Delivery and handoff. The district receives the plan as its own document — no license, no login, no expiration. Acting on it, ignoring it, or acting on only part of it are all the district's call.
No ongoing retainer required. A single engagement can be the entire relationship. If a district later wants implementation help, that is a separate, explicitly named referral (see "Related Stanley Studios hosts" below) — never an automatic upsell.
How an evaluation is scored
A vendor-neutral recommendation needs a fixed scoring frame, or "neutral" just means "whichever vendor talked last." Every engagement scores the same five dimensions, in this order, regardless of product category:
Total cost over the actual contract term — not the first-year discount price, and not a number that omits the renewal-year increase most contracts have written into them.
Data-export rights at exit — what format the district's own data leaves in if the relationship ends, and whether that format is usable without the outgoing vendor's cooperation.
Minors'-data handling — whether the vendor's own data-processing terms name who can see a student record, how long it is retained, and whether consent is collected before or after the data starts flowing. A vendor that cannot answer this in writing is scored as a risk, not skipped.
Staff training load — how many hours of staff time the rollout actually consumes, counted against the staff the district has, not the staff a sales deck assumes.
Integration burden — what the new system has to talk to (SIS, comms, existing photo/yearbook pipeline) and how much of that integration is the vendor's job versus the district's.
The scoring frame is the same whether or not a Stanley Studios product is one of the options being scored — see the conflict-of-interest answer below for how that gets disclosed when it applies.
Your data during an engagement
An advisory engagement on the Vendor decision or Migration readiness track does not require access to your student information system, your photo/yearbook roster, or any other system holding minors' data to produce a plan. The scoping call and the written plan are built from what you tell an advisor about your situation, not from a data export.
If a later phase of an engagement genuinely needs to see minors' data — for example, to validate a migration plan against real record counts — that is a separate, explicitly consented step with its own written data-handling terms naming who can see the data, how long it is retained, and when it is deleted. It is never bundled into the scoping call or assumed as part of the initial plan.
The Safety-tip intake review track looks at the intake process and its public-facing claims, not at the content of any tip already filed. A review does not require reading real student tip records, and does not ask for them.
Objections, answered
Isn't this just a sales funnel for Homeroom?
The written plan discloses the conflict explicitly whenever a Stanley Studios product is recommended, and names competing products when they are the better fit. Nothing here is commissioned or hidden. The scoring frame in the methodology above is applied the same way whether or not a Stanley Studios product is in the running.
What about our students' data during the engagement?
An advisory engagement does not require access to your student information system or any minors' data to produce a plan. If a later phase needs it, that is a separate, explicitly consented step — never assumed as part of scoping. See "Your data during an engagement" above for the full boundary.
How is this priced?
Scoped per engagement after the first call, because "planning help" for a two-school district and a forty-school district are not the same job. There is no published flat rate because publishing one before scoping would be a guess wearing a price tag. A district's engagement track (see above) sets the shape of the work before price is discussed.
Can you also implement the plan, not just write it?
No — implementation is out of scope by design, on every track. A plan that recommends its own author to build it has an incentive to recommend more work than the district needs. If implementation help is wanted afterward, that is a separate, explicitly named referral, not something this engagement bundles in.
What happens if we disagree with the recommendation?
The plan is advisory, not binding, and there is no ongoing fee tied to whether the district adopts it. The district owns the document and can act on all, part, or none of it. Disagreement with a recommendation is not a reason to extend the engagement — it's information for the next conversation, if there is one.
Do you have case studies or client references?
Not published, and this page will not invent any. No engagement has been booked through this page yet, per the section below — that is a statement about this page's current wiring, and it would be dishonest to paper over it with a testimonial that doesn't exist.
Is this only for large districts?
No. A two-school district gets a shorter scoping call and a shorter plan, not a discounted version of a plan written for a larger one. The engagement tracks above scale by scope, not by district size.
What's true today
No booking system is connected to this page today. Nothing you type into a form here reaches a person — email [email protected] directly and a person reads it.
No engagement has been booked through this page, no advisor roster is public, and no automated scheduling exists. That is a statement about this page's current wiring, not a promise about what is coming — when an intake pipeline exists, this section is replaced by a description of what it actually does. Every "no client references" and "no track record" answer on this page above follows from this same fact, not from a separate excuse.
Related Stanley Studios hosts
k12.direct — the district-facing intake surface this advisory work often feeds into once a plan is set
k12.exchange — where districts compare vendor offers after a planning engagement scopes what they actually need
k12.associates — a roster of vetted implementation or migration partners for after a plan is set — the roster itself is a separate, many-firm directory, and its own page states plainly whether any partners are listed today; this page does not restate that on its behalf
schedule-software (Homeroom) — one of the specific platform products an engagement here might end up recommending — never assumed
k12.consulting does not resell or white-label any of these, and is not a listing on the k12.associates roster — it is a single firm's own site, not a directory entry. If an engagement recommends one of the hosts above, that recommendation is written into the deliverable you receive, not routed automatically.
Start a conversation
Email [email protected] with the decision you're facing, which of the three engagement tracks above sounds closest, and a rough timeline. A person reads it.