K-12 vendors, sold direct to one building.

K12.Direct is the single-building face of the K-12 brand family: photography, yearbook and school-software vendors most schools reach through a district's central purchasing office, made reachable by one principal, one office manager, or one PTA chair acting on their own -- no RFP, no district procurement portal, no multi-building minimum.

It exists because "K-12 vendor" and "district vendor" are not the same buyer. A district technology director runs a formal bid process across forty buildings. A single elementary school picking its own picture day photographer, or a charter campus choosing its own yearbook platform, is a different transaction with a different decision-maker -- and most vendor sites are built for the first buyer only.

A typical inquiry looks like this: a charter campus of a few hundred students needs picture day scheduled before the fall enrollment count locks, the office manager already tried the district's approved-vendor list and found nothing sized for one building, and the fastest path is a direct conversation this week rather than a purchasing-committee slot next quarter. That is the buyer this page is built for.

Who buys here

• Independent and charter schools that are their own purchasing authority and have no district office to route through at all.
• One building inside a larger district whose principal has building-level discretionary budget for picture day, a yearbook platform, or a front-office tool, and does not want to wait for a district-wide contract cycle to try one.
• PTA and booster-club buyers running a fundraiser, a spirit-wear photo day, or a year-end recognition book on their own line item, separate from the school's own procurement.
• Small private and parochial schools below the size where a formal vendor-management process exists at all.
• Growing micro-school and hybrid-learning networks whose enrollment moved past "one classroom" but who have never had, and do not want, a district-style purchasing office standing between them and a vendor.

One relationship, three product lines

"Buying direct" is not one transaction shape -- photography, yearbook and school software each have their own building-level specifics. What is constant is that all three are the same product line a district-scale buyer gets, and all three can be started from one relationship instead of three separate vendor searches.

You can start with one line and add another later, or start with more than one at once -- see "What buildings usually ask first" below for how combining lines into a single agreement actually works.

How buying direct actually works

1. You tell us the building, not the district. One school name, one enrollment size, one decision-maker -- not a district-wide rollout plan.
2. We quote at building scale. Pricing, scheduling and contract terms are sized for a single campus, not padded for a forty-school negotiation neither side is having.
3. No procurement-portal detour. You are not asked to register in a district vendor system, submit a W-9 to a central office, or wait on a purchasing committee meeting date that may be months out -- the agreement is between your building and us.
4. The product itself is the same product a district buys. Direct purchase changes who signs and how fast, not what you get: the same photography crews, the same yearbook platform, the same school software the district-scale buyer gets, sized to one campus instead of a portfolio.

The typical shape of a direct conversation

Described as a typical arc, not a guaranteed timeline -- your building's calendar, the product line involved, and how quickly you reply all move these dates.

1. You email us. Building name, approximate enrollment, and which product line (or lines) you're looking to buy -- see "Talk to a person, not a form" for exactly what to include.
2. We reply with what we need to quote at your scale. For photography, that is usually a proposed picture-day date range; for yearbook, an enrollment count and a target ladder; for software, which modules matter to your building first.
3. You get a building-sized quote and contract, not a district-scale document. No multi-building addendum, no central-office signature line that doesn't apply to you.
4. Work starts on your building's calendar, not queued behind other buildings' rollout dates, because there are no other buildings on this agreement.

What a building-scale agreement actually contains

We don't publish a price list here -- a fair quote depends on enrollment, product line, and timing, and a number posted on a page without that context is more likely to mislead than to help. What we can say plainly is the shape of a direct agreement, which is different from a district contract in ways that matter to a single building:

• Sized to one building's numbers. The quote is built from your enrollment and your product selection, not a district-wide per-pupil rate averaged across buildings of very different sizes.
• No multi-year district lock-in required. A direct agreement covers the building that signed it, for the term that building needs -- it is not a rider on a district's multi-year master contract.
• One signature, one point of contact. The person who requested the quote is the person who signs, without a chain of district approvals in between.
• Combining lines is one conversation, not three vendor relationships. If a building wants photography, yearbook and software together, that's addressed as one quote request, not three separate procurement threads.

How this compares to going through the district

Some districts require any purchase charged to a district-level budget code to go through central purchasing regardless of building size -- see "Our district requires vendors to go through central purchasing" below for how to tell which path applies to your purchase.

What buildings usually ask first

"Our district requires vendors to go through central purchasing."

Some do, for anything charged to a district-level budget code. A building-level or PTA-level purchase, on a line item the building itself controls, is frequently outside that requirement -- check your own building's purchasing threshold before assuming you need the district process. If your district does require central approval for this purchase, K12.Direct is the wrong door; the same product line is available through the standard district-vendor path.

"Is this a smaller or lesser version of the district product?"

No. It is the identical product line, contracted at one-building scale. Nothing is downgraded to make it sellable direct.

"What if we grow past one building later?"

A direct agreement does not block a future district-wide contract -- it is a standalone agreement for the building that signed it, and expanding later is a new conversation, not a renegotiation of what you already have.

"Can we buy photography, yearbook and software together?"

Yes -- tell us all three in the same email and we quote them as one building-scale agreement. You can also start with one line now and add another later; adding a line is a new quote, not a renegotiation of what you already signed.

"What happens to our students' data if we buy direct?"

The same company-wide handling applies regardless of how you bought: student data is used only for the product your building purchased, is not sold, and is not made public. See "Student data, at building scale" below for the specifics.

"Who do we actually talk to?"

A person, by email, today -- see "what's live here" below. There is no ticket queue and no sales portal login in front of that conversation.

Student data, at building scale

What's live here today