Societas · The Stanley Studios partner network · In development · 2026

The partner and reseller network — where studios, advisers, and resellers join, onboard, and manage the relationship

Societas is the partner side of the platform: one relationship home for the photography studios, yearbook advisers, and resellers who work with and resell it. The name is the Latin word for partnership, and the idea is simple — a partner belongs to the network, not to a scatter of separate product accounts. The network platform is in active development. The one thing that works today is a request for a partner conversation; there is no live join button, no self-serve onboarding, no pricing, and no payment on this page.

Request a partner conversation How it works

In developmentthe network platform is in active build — this is the honest landing, not a live portal

Studios · advisers · resellersthree kinds of partner, one shared relationship home across the portfolio

Conversation-firsta partnership begins with a request, not a self-serve signup — no account is created here

No student dataa partner account is never granted access to any student-data module — a structural boundary

The idea — a network, not a scatter of accounts

A partner belongs to the network, not to a separate account per product.

The platform is a portfolio: school photography rails, a yearbook engine, records and commerce, and the software arm behind them. A studio, a yearbook adviser, or a reseller often touches several of those at once — and today each product is its own front door. Societas is the answer to that scatter: one relationship home where a partner joins once and is known across the portfolio, rather than re-introducing themselves to every product in turn.

That home is being built. The parts a partner will eventually use — a guided join, onboarding that sets them up with the tools they need, and a place to manage referrals, co-marketing resources, support, and the partner directory — are in active development or on the roadmap, not live. We are describing the shape of the network honestly while it is built, so a studio or reseller deciding whether to start a conversation knows exactly what exists today and what is still coming.

What exists today is deliberately small and honest: a way to raise your hand. A studio, adviser, or reseller can request a partner conversation, and a person on the partner team follows up. No account, no dashboard, no payment — a conversation. That is the honest starting point for a network that is still being built, and it is the one thing on this page that actually works.

Request a partner conversation What is built

How it works

A partner’s journey in four stages

The journey runs in four stages: express interest, the first conversation, onboarding handled directly while the portal is built, and managing the relationship. Only the first stage is live today; the rest are described honestly as in-development or on the roadmap.

Step 1 · Express interest — request a partner conversation

A studio, adviser, or reseller requests a partner conversation through the shared intake form. This is the live surface today: you self-identify (a studio, a school-side adviser, or another kind of partner), say what you are hoping to build, and the request routes to the partner team. No account is created and nothing is stored beyond a logged, optionally-forwarded record of the request. There is no signup and no commitment at this step.

Step 2 · The first conversation — fit, honestly assessed

The partner team reviews the request and, if it looks like a fit, opens a conversation. We describe the current state honestly: what the network is, what belongs in it, what is live today, and what is still being built. There is no pricing commitment, no signup, and no obligation on either side. The goal is a plain, accurate picture of the partnership before anyone signs anything.

Step 3 · Onboarding — handled directly while the portal is built

If the partnership goes forward, onboarding happens directly with the partner team — a person walking a partner through setup — because the self-serve onboarding portal is on the roadmap and not built. The terms are set in a partner agreement papered through the platform’s agreements engine: scope, any referral or revenue-share economics, data-processing terms, brand use, and the right to leave. Nothing about the economics is published on the site; it lives in the signed agreement.

Step 4 · Managing the relationship — the portal, on the roadmap

The ongoing relationship — referrals, co-marketing resources, support, and the partner directory — will live in a partner portal that is planned and not yet built. Until it ships, the relationship is managed directly with the partner team. A partner account never has access to any student-data module: the SIS, gradebook, records, consent ledger, and yearbook engine are outside a partner’s reach by design. A partner’s own records are owned by the partner and are never sold or handed to an outside company.

The network

Five parts — honest about what is live, what is in development, and what is on the roadmap

Every part is labelled honestly: Live today means it works right now. In development means it is in active build or on the roadmap and not yet live. We do not claim otherwise.

The network — one relationship home across the Stanley Studios portfolio

Societas is the partner side of the platform: the relationship home where photography studios, yearbook advisers, and resellers connect with the platform and manage that relationship over time. The name is the Latin word for partnership. Where the individual product sites sell the software, Societas is the membership and relationship layer that spans the whole portfolio — school photography, yearbook, and the software arm — so a partner has one place to belong rather than a separate account per product. The network platform is in active development. A partnership today begins as a conversation, not a self-serve signup: there is no live “join” button on this page and no account is created here.

Network platform in active development

Who belongs — photography studios, yearbook advisers, and resellers

Three kinds of partner belong in the network. Photography studios that shoot school portrait, event, and sports days and want the platform’s ordering, gallery, and yearbook rails behind their own brand. Yearbook advisers who run a book for a school or district and want a direct line to the people who build the tools they use. And resellers and integrators who sell and support the platform for the schools they serve. Each has a different relationship with the platform; the network is the shared home for all three. Membership tiers, verification, and the specifics of each relationship are being designed alongside the onboarding flow — described here, not yet live to join.

Open to studios, advisers & resellers · onboarding in development

Request a partner conversation — the one thing that works today

The working surface today is the request form. A studio, adviser, or reseller can express interest and request a partner conversation through the platform’s shared intake. The form routes the request to the partner team and nothing more: no account is created, no browser identity is set, and nothing is stored on this server beyond a logged — and optionally forwarded — record of what you typed. What you enter is used solely to route your request; it is never sold and never handed to an outside company, and there is no tracker, enrichment, or third party in the path. This is the honest front door while the rest of the network is built.

Interest & conversation request · live today

Join, onboard, and manage — the partner portal, on the roadmap

The portal a partner will eventually use to join, onboard, and manage the relationship is on the roadmap and is not built. Planned surfaces include: a guided join and verification step; onboarding that sets an approved partner up with the tools they need; a relationship view for referrals, co-marketing resources, and support; and a partner directory. Until the portal ships, every one of these is handled directly by the partner team after the first conversation — a person, not a dashboard. We describe the portal as a plan because that is what it is; we do not show a screenshot of a thing that is not built.

Join / onboard / manage portal · roadmap, not built

The partner agreement — terms in writing, papered through the platform’s agreements engine

When a partnership becomes real, its terms are set in a partner agreement — the scope of the relationship, any referral or revenue-share economics, data-processing terms, brand use, and the partner’s right to leave. The platform already runs an agreements engine with a tamper-evident ledger and a single-path signing flow for its other agreement kinds; the partner-agreement kind will ride that engine rather than a separate paper chase. That kind, and the live partner onboarding it belongs to, are in active development. No economics appear on this page: the specifics of any referral or revenue-share arrangement are a matter for the signed agreement, not a published figure, and are never quoted here.

Partner-agreement kind in development · no economics published

Who belongs

Built for the studios, advisers, and resellers who work with the platform

Photography studios

A studio that shoots school portrait, event, and sports days can run the platform’s ordering, gallery, and yearbook rails behind its own brand. Societas is where a studio joins the network and keeps a direct line to the people who build those rails. Studio work is white-labelled: a studio’s families see the studio, not the platform. Onboarding for studios is in development; today a studio starts with a conversation.

Yearbook advisers

A yearbook adviser who runs a book for a school or district can join the network for a direct relationship with the team behind the yearbook engine — a channel for feedback, early looks, and support that is closer than a help ticket. An adviser’s relationship with the network is about the tools, not about student data: a partner account has no access to any student-data module. The adviser side of the network is in development; today it starts with a conversation.

Resellers and integrators

A reseller or integrator that sells and supports the platform for the schools it serves belongs in the network too. The K-12 platform’s reseller program lives at k12.partners; Societas is the broader relationship layer across the portfolio, where a reseller manages the ongoing relationship rather than just the initial program pitch. Reseller onboarding and the relationship portal are in development and on the roadmap respectively; today it starts with a conversation.

Boundaries & data

The partner network handles no student data, and a partner’s information is never sold.

Societas is a business-to-business channel surface. A partner account is never granted access to any student-data module — not the student information system, the gradebook, records, the consent ledger, or the yearbook engine. That is a structural boundary, not a policy preference: the capability that would grant a partner account access to a student-data module does not exist for that account type. No minor’s data touches the partner network. A studio that runs school photography does so through the studio product’s own consented rails, not through the partner network.

The information a prospective partner submits through the request form is used solely to route their request. The marketing server is stateless and stores no row: a submission is written to a structured log line and may be forwarded to a public intake endpoint the operator runs. It is never sold and never handed to an outside company. There is no tracker, no enrichment, and no third party in the path, and no browser identity is set when you submit.

A partner’s own records — once the network is built and a partner has an account — are owned by the partner and are never sold or handed to an outside company. Consent for follow-up communication can be withdrawn at any time. These are the boundaries the network is being built inside, stated now rather than after the fact.

What is built and what is coming — plainly

One surface is live. The rest of the network is in development or on the roadmap.

Live today: the shared interest form that routes a partner conversation request. It is the only working surface on this page. It creates no account, sets no browser identity, and stores no row on the marketing server beyond a logged — and optionally forwarded — record of the request.

In active development: the network platform itself; the membership model and its tiers; and the partner-agreement kind on the platform’s existing agreements engine (which already runs a tamper-evident ledger and a single-path signing flow for its other agreement kinds).

On the roadmap and not built: the self-serve join, onboarding, and relationship-management portal, and the partner directory. There is no pricing, no signup, and no payment on this page, and no published revenue-share, commission, or margin figure. We say so directly because a studio, adviser, or reseller deciding whether to start a conversation deserves to know exactly what exists today and what is still being built.

Across the portfolio

Societas is the relationship network. k12.partners is the K-12 reseller program. associate.network is the community-fundraising side.

k12.partners is the reseller program page for the K-12 school platform specifically — the program pitch and terms for studios, integrators, and resellers who sell and support that platform. Societas is broader: the portfolio-wide relationship network where a partner joins, onboards, and manages the ongoing relationship across school photography, yearbook, and the software arm. k12.partners is the program’s front door; Societas is the membership and relationship layer. They are cross-linked as siblings.

associate.network is a different model entirely: the community-fundraising side, where school community organizations become named fund beneficiaries in a subscription-split model. Societas is the commercial partner and reseller network, not a fundraising program. stanleystudios.software is the software arm, and stanleystudios.llc is the full house-of-brands directory if you want to browse the whole portfolio.

k12.partners stanleystudios.software stanleystudios.llc

Request a conversation · Studio owners, yearbook advisers, resellers & integrators

Request a partner conversation to see the current state honestly

Societas is in active development. A conversation is where it starts: we describe what the network is, what belongs in it, what is live today, and what is still being built — and we hear what you are hoping to build. There is no pricing commitment and no signup. If it looks like a fit, onboarding is handled directly while the portal is built. The request form self-identifies you as a studio, a school-side partner, or another kind of partner, and routes your request to the partner team; nothing is stored beyond that logged, optionally-forwarded record.

Request a partner conversation

Or email [email protected] directly.

FAQ

Common questions

What is Societas?

Societas is the partner and reseller network for the platform — the relationship home where photography studios, yearbook advisers, and resellers join, onboard, and manage their relationship with the platform. “Societas” is the Latin word for partnership. It is the membership and relationship layer that spans the whole portfolio rather than a single product. The network platform is in active development; this page is the honest landing, not a live portal.

Who can join the network?

Three kinds of partner: photography studios that shoot school portrait, event, and sports days and want the platform’s rails behind their own brand; yearbook advisers who run a book for a school or district; and resellers or integrators who sell and support the platform for the schools they serve. Membership tiers and the specifics of each relationship are being designed alongside the onboarding flow — described here, not yet live to join.

What can I actually do today?

One thing: request a partner conversation through the shared intake form. That surface is live. You self-identify, say what you are hoping to build, and the request routes to the partner team. No account is created, no browser identity is set, and nothing is stored on this server beyond a logged — and optionally forwarded — record of what you typed. There is no signup, no payment, and no commitment.

Is there a live join, onboarding, or relationship portal?

Not yet. The portal where a partner would join, onboard, and manage the relationship — verification, setup, referrals, co-marketing resources, support, and a partner directory — is on the roadmap and is not built. Until it ships, all of that is handled directly by the partner team after the first conversation. We describe the portal as a plan because that is what it is; there is no live join button on this page.

How is Societas different from k12.partners?

k12.partners is the reseller program page scoped to the K-12 school platform — the program pitch and terms for studios, integrators, and resellers who sell and support that platform specifically. Societas is broader: the portfolio-wide relationship network where a partner joins, onboards, and manages the ongoing relationship across school photography, yearbook, and the software arm, not just the K-12 reselling pitch. Think of k12.partners as the program’s front door for the school platform and Societas as the membership and relationship layer that spans the portfolio. They are cross-linked as siblings.

Is this the same as associate.network?

No. associate.network is the community-fundraising side of the platform: school community organizations — parent-teacher organizations, booster clubs, and community groups — that become named fund beneficiaries in a subscription-split model. Societas is the commercial partner and reseller network: photography studios, yearbook advisers, and resellers who work with and resell the platform. Different audiences and different models — one is a community fundraising split, the other is a business-to-business channel relationship.

What does the partner agreement cover, and how is it signed?

When a partnership becomes real, its terms are set in a partner agreement: the scope of the relationship, any referral or revenue-share economics, data-processing terms, brand use, and the partner’s right to leave. The platform already runs an agreements engine with a tamper-evident ledger and a single-path signing flow for its other agreement kinds; the partner-agreement kind will ride that engine rather than a separate paper chase. The engine exists platform-wide; the partner-agreement kind and the live onboarding it belongs to are in active development.

Does Societas handle any student data?

No. The partner network is a business-to-business channel surface. A partner account is never granted access to any student-data module — not the student information system, the gradebook, records, the consent ledger, or the yearbook engine. That is a structural boundary, not a policy preference: the capability that would grant a partner account access to a student-data module does not exist for that account type. No minor’s data touches the partner network.

What happens to the information I submit through the form?

It is used solely to route your request to the partner team. The marketing server is stateless and stores no row: your submission is written to a structured log line and may be forwarded to a public intake endpoint the operator runs. It is never sold and never handed to an outside company. There is no tracker, no enrichment, and no third party in the path, and no browser identity is set when you submit.

Is there pricing or a revenue share published here?

No. There is no pricing, no signup, and no payment on this page, and no published revenue-share, commission, or margin figure. Any partner economics are a matter for the signed partner agreement, set in a conversation and put in writing there — not a number quoted on the marketing site. If you want to understand the economics, that is one of the things the first conversation is for.

What is built, and what is still being planned?

Live today: the shared interest form that routes a partner conversation request. In active development: the network platform itself, the membership model, and the partner-agreement kind on the platform’s existing agreements engine. On the roadmap and not built: the self-serve join, onboarding, and relationship-management portal, and the partner directory. We label the state of each surface honestly rather than showing a portal that does not exist.