About · Classly.software

The roster is the product’s starting point, because capacity changes the booking law.

Classly.software is an independent studio-planning product being developed by Stanley Studios. Its foundation is built; its branded workflows remain in development.

The product idea

A class is not an appointment with extra names attached.

Many scheduling tools begin with a provider calendar and a single customer claiming a time. A group class begins with a different object: one occurrence, a capacity, and a roster of people who share the same time. Classly starts from that object. The distinction affects database locking, duplicate prevention, waitlist policy, instructor preparation, cancellation, and the language shown to customers.

The shared schedule decision core already supports capacity N. That made an independent adult-studio product plausible without pretending its product surface was finished. The remaining work is the work customers actually touch: schedule discovery, booking, roster, waitlist, attendance, studio configuration, support, and operations.

Who stands behind it

Classly.software is a for-profit Stanley Studios product in early development.

The site does not present a founding legend, staff count, investor story, named customer, testimonial, or adoption graph because there is no sourceable claim to make. It presents the operator, product thesis, built engine boundary, planned surfaces, and contact address. Those are facts a visitor can evaluate today.

Classly is marketed as its own product. It can share a booking law with sibling software without becoming a feature of those brands. The schedule-family links in the footer are peer navigation. An optional integration may be useful to some organizations, but no sibling product is required to use Classly.

The launch discipline is equally plain: test with synthetic adult-studio examples, label every surface by status, keep payment disabled until there is a real checkout and support process, and avoid claims about certification or outcomes that have not been established. Questions about fit can go to [email protected].

A dated session gives the commitment a clear size

Imagine a fictional adult drawing studio offering three independent evening sessions. A person may choose one evening because it fits their week without committing to the other two. Each evening has its own capacity and group. The Classly idea begins with that occurrence: a particular session that several people can join. It does not turn the three dates into one continuing enrollment simply because their titles are similar. Naming the unit clearly helps a studio explain what someone is choosing and helps a prospective customer compare that choice with a longer program.

Now change the example so the three evenings form a connected course that people are expected to complete together. That change is more than a different calendar layout. It changes the commitment and may make a whole-series model more appropriate. Classly's focus is a seat in one dated session; the neighboring Cohort product has its own explanation of a continuing arc. Mentioning that distinction is not a claim that either new product surface is live or that a shared account exists. It is a way to recognize a mismatch early, before the same scheduling vocabulary makes two different needs appear interchangeable.

The same distinction matters when a studio expands its catalogue. Adding another drawing evening might create another independent choice, while adding a second part to an existing workshop might change what the original offer includes. Those are different product questions even if the calendar gains one extra row in both cases. Classly's purpose is easier to assess when the studio can state which change it means. The brand is not a reason to force every learning activity into a dated-session model; it is an explanation of the model this proposed product is intended to make useful for operators and adults choosing a place.

The distance from a decision rule to a useful service is real work

A capacity decision can answer a narrow question about whether another place should be accepted. A studio operator still needs to publish understandable session facts, prepare for the group and explain a change. An adult participant still needs to understand whether they have a confirmed place and what to do if their plans change. Those are not decorative additions to the decision core. They are the experience a buyer would actually use. That is why the Classly page labels the branded booking, roster, waitlist and instructor surfaces as unfinished rather than treating the engine as a completed studio service.

The distinction also gives an early evaluation a practical purpose. Return to the fictional drawing session and ask what happens when one date changes after people expressed interest. A calculation about remaining capacity does not answer how the change is explained or which commitment was understood. The future interface needs an account of that work. These pages can make the unanswered decisions concrete without claiming they have been implemented. An evaluation is useful if it identifies what must be shown next, even when the result is that a studio should continue using its existing arrangement until a complete path can be demonstrated.

Interest in the idea is not the same as readiness to use it

A reader may like the proposed pricing, the independent studio brand or the focus on a group roster. None of those preferences creates a working booking account. The planned zero-commission model is a commercial commitment about the intended product, and the displayed tiers are not a live checkout. A useful About page keeps that distinction visible because a buyer often encounters the story before inspecting a capability table. The next conversation should concern whether the session model fits the work, not assume that enthusiasm is authorization to move a studio's records or change its process.

For an adult operator considering the fictional three-session studio, a clear fit statement might be that each evening needs its own capacity decision and a simple explanation of each participant's outcome. An equally clear objection might be that the business actually depends on a multi-session membership or a working export that is not available here. Either statement helps define the product boundary. Neither requires a customer list, a testimonial or an invented adoption figure. Classly's public story should leave the reader better able to choose a next step, including waiting, without filling the gap between an idea and a service with claims the source cannot support.

The mechanism underneath the plan

Capacity-N is built in the shared decision core; the Classly product surface is still being made.

A group session differs from an appointment in one decisive way: several people claim seats in the same scheduled occurrence. The underlying engine treats that as a capacity decision keyed to the person and session. It counts confirmed bookings while holding the session row under a database lock, then accepts or refuses the next claim inside the same transaction. A partial unique index prevents one person from holding the same session twice. Capacity one and capacity thirty use the same law at different values of N.

That decision core exists. A Classly-branded public schedule, roster, waitlist, instructor console, attendance workflow, payment page, and self-serve setup do not exist as a live product today. The distinction is repeated because a polished marketing page can otherwise make a database capability sound like a service someone can buy. Early access starts with a conversation; this site creates no account, charges no card, and books no seat.

The planned public flow is simple enough to inspect: an adult customer chooses a session, sees an honest seat state, identifies themself, and receives either a confirmed place or a waitlist position. A studio operator sees the same occurrence as a roster with capacity, schedule details, and status. An instructor sees only the practical attendance view needed for the session. Those surfaces share a decision but have different disclosure and editing rights.

Waitlist promotion is planned. It must be transactional for the same reason booking is: releasing one confirmed place and promoting the next eligible person cannot be two unrelated writes. Notification delivery must follow the committed decision and remain retryable without creating a second booking. Until those paths and their operator controls exist, this site describes them as planned rather than demonstrating a fake queue.

For evaluation, use a synthetic studio and synthetic adults. A useful example might contain three instructors, six weekly session types, capacities between four and twenty, a cancellation window, and invented attendee names. That is enough to test schedule shape, capacity pressure, waitlist policy, and instructor visibility without bringing real customer records into an early product conversation.

Commercial and operational boundary

Zero commission is a pricing commitment for the planned product, not evidence of a live checkout.

The planned tiers do not take a percentage of session fees. A studio may still choose a payment provider whose processing terms apply, but Classly does not plan to add a marketplace commission. Prices shown on the overview are display-only. There is no subscription checkout, payment token, active trial, or automatic renewal on this website.

White-label presentation, custom domains, roster export, attendance tools, waitlist promotion, and the multi-location console are planned product surfaces. The capacity decision beneath them is built, but that fact does not prove the branded workflow, accessibility review, support process, or operational monitoring around them. Each feature becomes available only when its whole path can be exercised and supported.

Classly makes no adoption, outcome, uptime, or customer-count claim. It presents no testimonial and claims no FERPA, COPPA, SOC2, or VPAT certification. The site contains ordinary product documents and an email link. It sets no marketing cookie, accepts no roster upload, and asks prospects not to send identifiable participant data during evaluation.

An operator also needs a recovery story before a booking surface opens. Session changes must preserve the prior occurrence long enough to explain what attendees originally accepted. Cancellations and capacity changes need named actors and timestamps. Notification delivery can be retried, while the committed roster remains stable. Support staff should be able to inspect a synthetic reproduction without gaining broad access to every studio. Backups, exports, and operational logs need retention and deletion rules. These are ordinary service responsibilities, but none can be inferred from the presence of an atomic booking function. They belong in the readiness decision for each planned surface.