question.company · the venture behind the question.* family · Powered by question.technology

The company that builds the question.* family.

Who builds the question.* family, how we operate, and what we are honest about — including what is not true yet.

Question is a founder-led venture inside the Stanley Studios estate, built on a response engine already running in production that any signed-in staff or studio account can author on. It is not a funded startup: no outside investment, no leadership-team roster, no press, and no customer logos — and this page names each of those plainly rather than let an absence read as an accident. Money is off here. Nothing here is AI.

Engine in productionrunning today; any signed-in staff or studio account can author on it

No identity columna response row has no name, email, IP, account, or session field

Hour-coarseneda response stores only the hour it arrived, enforced by the database

Founder-leda small team inside Stanley Studios, self-funded, no outside investment

One engine, several front doors, one company

The question.* family is not several companies. It is one shared response engine with front doors aimed at different readers, all built by one team, on one security model, one support operation, and one roadmap.

question.technology is the engine: the shared question-authoring and response-collection surface the whole family runs on.

question.software is the classroom front door: the place a teacher writes questions, runs them with a class by a class code, and reviews the responses.

question.company — this page — is the venture behind both. It does not re-pitch the product. It answers the question a product page cannot: who builds this, how do they operate, and what are they honest about?

Powered by question.technology. A school pays for the underlying platform and the capabilities it selects, so it does not pay repeatedly for the same engine wearing different brands.

The story, without the myth

Question did not start as a pitch deck. It started as a working response engine — a way to ask a question, collect an answer in a known shape, and read back what came in, without collecting a pile of personal data along the way.

That engine runs in production today inside the Stanley Studios estate, and any signed-in staff or studio account can author questions and question sets on it. What does not exist is a public signup form: an account is opened by us, by hand, after we talk. Building the engine first, and the company page second, is the opposite of the usual order, and it is on purpose.

The wider estate is a vertically integrated school platform: student records, publications, picture day, the health office, communications, and commerce, on one roster. Question is the part of that estate concerned with asking things and collecting answers cleanly, and it is being spun into its own product and brand rather than staying an internal tool.

So there is a real thing under the name. There is also a great deal that is early. This page treats both as facts a reader is entitled to, and refuses to average them into one reassuring sentence.

Provable now

What is actually running

A company is easier to trust when it can point at code. Everything in this section is a property of the response engine that runs today, read off the real database and shared library — each card names where it is enforced so you can check it, rather than take our word.

Five answer shapes at authoring, three that accept answers today

Running in production · open to signed-in staff and studio accounts

The database CHECK admits five question types at authoring -- open text, a 1-to-5 scale, single choice, ranking, and conjoint. Three of them accept a submitted answer today: text, scale, and choice. Ranking and conjoint refuse answers until their answer wall lands, so the submit lane does LESS than the authoring wall allows, and we say so rather than average the two. That is not a preference a browser can be talked out of — it is a database constraint that rejects anything else, so a survey, a poll, an intake form, an RSVP, and a plain feedback form all compose cleanly from shapes the database itself guards.

Evidenceqt_question.type CHECK IN ('text','scale','choice'); the shared question-technology library pins the scale to 1 through 5.

A response carries no identity column

Running in production · open to signed-in staff and studio accounts

The row a response is written to has four columns and none of them names a person: no name, no email address, no IP address, no account, no browser fingerprint, and no session. The column was never created, so there is nothing for a later bug to accidentally fill in. This is a property of the schema, not a promise layered on top of one that could hold identity if something slipped.

Evidenceqt_submission columns = id, owner_org_id, submitted_at, moderation_state. No identity column exists.

The response time is coarsened to the hour, in the database

Running in production · open to signed-in staff and studio accounts

A stored response keeps only the hour it arrived, not the minute or the second. A precise timestamp on a low-volume set can be lined up against the moment a link went out to work out who most likely answered; the hour-level value cannot do that. The coarsening is a wall in the database, so a route that tries to store a precise time is turned away rather than quietly recorded.

Evidenceqt_submission.submitted_at DEFAULT date_trunc('hour', now()) with CHECK submitted_at = date_trunc('hour', submitted_at).

Moderation and rate limits run before a response lands

Running in production · open to signed-in staff and studio accounts

Every incoming response passes a server-side check for likely foul language or spam and a rotating rate limit before it reaches any feed. A flagged response is labelled as flagged — there is a record of what came in and why it was set aside — rather than being silently thrown away. Both checks are server-authoritative: a client cannot skip them.

Evidenceqt_submission.moderation_state CHECK IN ('accepted','flagged'); server-side moderation + salted rotating rate limit.

Three separate axes, measured separately. AUTHORING: any signed-in staff or studio account can create questions and question sets today. SIGNUP: there is no public self-serve signup that opens a Question account — the public account-creation route we measured provisions a school bound to the fundraiser, photo, or newsroom module, so a Question account is opened by us, by hand, after we talk. FOUNDER-ONLY: exactly one view is, the cross-owner submissions feed that reads every owner’s responses; a creator reads their own responses on their own feed. And a custom question-type catalog is not provisioned — that route answers 501 rather than fake a success.

Radically legible about our stage

What we are, and what we are not

The easiest place to mislead is a company page, because a reader fills every gap with the flattering default. So here is the ledger, out loud. The left column is what a company page usually implies it has. The right column is the honest version for Question.

The left column is what a company page usually implies. The right column is the honest version for Question, stated so an absence never reads as an accident.
What a company page usually implies	The honest version for Question
A leadership-team page with headshots and titles	Question is founder-led and built by a small team inside Stanley Studios. There is no separate executive roster to show, and we will not invent one to look larger than we are.
A funding announcement and investor logos	Question has taken no outside investment and closed no venture round. It is self-funded inside the Stanley Studios estate. If that ever changes, it will be stated here plainly, not implied by a wall of logos.
Press coverage and industry awards	There is no press coverage and no award to cite. When there is something real, it will be linked to its source here, never paraphrased into a badge you cannot check.
Customer logos, testimonials, and adoption counts	We show no customer logos, no testimonials, and no counts of schools or users, because there are none to cite, and a fabricated one would be the fastest way to lose you. What we can point at instead is the running authoring surface any signed-in staff or studio account reaches today.
An office address, a map pin, and a headcount	Question is built remotely inside the estate. There is no office to tour, and we do not publish a headcount we would then have to keep true week to week.
A five-year roadmap presented as a promise	We describe what the serving path does today and we name what it refuses. We do not commit to a date we have not earned, and we do not narrate a future as though it already shipped -- so this page carries no dated promise at all.

None of this is modesty for its own sake. A page that hides its stage teaches you to distrust everything else on it. Naming the gaps is how the provable parts above stay believable.

Which reader are you?

A company page is read by a school, a would-be hire, a partner, a reporter, and a parent, and they do not want the same thing. So here is where each should start, rather than a single pitch aimed at no one.

Who you are, where to start on this page, and why.
You are	Start with	Because
A school or district weighing us	What is running, then Trust & data	Decide against the provable engine and the scoped custody register, not a promise.
Someone who might build here	Careers, then Team & operation	See the real stage before you consider joining an early, founder-led venture.
A partner or integrator	The family, then Contact	Learn which surface you would integrate with, then reach a person directly.
A reporter or analyst	Our honest stage, then the FAQ	Check a claim against what we state plainly, then ask us to confirm it.
A parent or guardian	Trust & data	See how a minor's record is handled: consent-gated and not publicly browsable.

How we operate

Six principles that make the honesty a rule, not a mood

Everything above only holds if there is a discipline underneath it. These are the operating principles the venture is run by — the reason a claim on these pages is scoped, checkable, and labelled by its stage.

Provable over persuasive

A claim on our pages should be checkable against real code, or it should not be made. That is why the engine section names exact tables and constraints instead of adjectives.

Name the gap

An absent team, funding round, or customer is stated out loud, never left to a flattering default. A page that hides its stage teaches you to distrust the rest of it.

The least data that works

We design for the smallest amount of personal data a job needs, and we enforce it in the schema where we can — a response row simply has no identity column to fill.

Keep the scope on the sentence

A true statement with its scope stripped off is how careful people still mislead. So we say which layer, which surface, and which stage a claim belongs to, every time.

The present tense of the latch

A capability sentence here is the present tense of the thing that refuses it, never a promise about a switch we hold. Two examples: there is no public signup, so an account is opened by us; and a custom question-type catalog is not provisioned, so that route answers 501 instead of faking a success.

Money stays off until it is set

No price appears before it is real, and no card is captured on a marketing page. When there is pricing, it will be written down in one place with the terms beside it.

The team, and how we operate

There is no leadership-team page here because there is no leadership team to photograph — and inventing one would be exactly the kind of thing this page exists to avoid. What there is, instead, is a plain account of who does the work and how.

Founder-led, and small

Question is led by its founder and built by a small team inside Stanley Studios. The same people who build the wider school platform build this. That is the whole org chart, and we would rather state it than pad it.

One team, one roadmap

The family shares one engine, one security model, one support operation, and one roadmap. There is no separate company per front door, so there is no hidden headcount behind a brand you cannot see.

Built inside the estate

Question is built remotely inside the Stanley Studios estate rather than from an office you could visit. We do not publish a headcount or a map pin we would then have to keep accurate.

Decisions are the founder's

There is no board beyond the founder and no outside investor whose approval gates a decision. When something changes about ownership or funding, it will be said here in plain words.

Support is a person, not a queue theatre

A small team answers directly. We will not advertise a support tier or a response-time promise we cannot keep at this size; the honest channel is email.

We build the engine before the brochure

The response engine ran in production before this page existed. We would rather show you a working thing that is narrow than a broad promise that is not built.

Trust & data

How a response is treated

Trust in a venture is mostly trust with data. Rather than an absolute promise, here is the scoped custody register: exactly what happens to a response, stated in terms you can check against the engine above.

A response carries no identity column

The response row has no field for a name, email, IP address, account, fingerprint, or session. It was never built, so there is nothing to leak.

The response time is coarsened to the hour

Only the hour a response arrived is stored, enforced by a database check, so the exact moment cannot be matched against the moment a link went out.

Data is stored on our own infrastructure

Responses and sets are held on infrastructure we run inside the estate. A school retains control of its own education records; we hold them to run the service, not to sell them.

A minor's record is consent-gated

A minor's name, face, and record are consent-gated and not publicly browsable, and consent can be withdrawn. This is the standing rule across the estate.

Operational logs, not advertising profiles

We keep the short-lived operational logs a service needs to run and protect itself. We do not build advertising identifiers or device profiles, so this is not a claim of zero logging — the distinction is deliberate.

No certification claim

FERPA does not certify products, so we claim no certification and make no blanket compliance claim. The product is designed to support a school's obligations, and the data practices are documented for review.

This is the response-collection path specifically. A creator’s own account and, once it exists, billing detail obviously identify that creator; it is the person answering a question who can stay free of an identity requirement. This page describes the intended data model — it does not promise certified compliance, zero logging, or automatic deletion, and it claims no FERPA or COPPA certification.

Data governance

What we will do with a response, and what we will not

The trust register above says how a response is treated. This is the same commitment at the level of an action: a plain will-and-will-not list, so there is no ambiguity about the parts that matter.

What we will do with a response, and what we will not.
What we do	What we do not
Store a response in a known answer shape the database enforces.	Attach a name, email, IP address, or account to that response row.
Coarsen the stored response time to the hour.	Keep a precise timestamp that could re-identify a respondent by timing.
Run moderation and rate limits server-side and label a flagged response.	Silently discard a response with no record of what came in.
Keep the short-lived operational logs a service needs to run and protect itself.	Build an advertising identifier or a device profile from a response.
Hold a school's records so the school retains control of them.	Sell a school's data or use it to train a model.
Document the data practices for review before a school adopts.	Claim a FERPA or COPPA certification, or a blanket compliance promise.

These are commitments about the response-collection path. They describe the intended data model and the current engine behavior; they are not a certification, and where a control is still being finalized the FAQ says so.

Careers, honestly

Question is a small venture, so hiring is occasional and specific rather than a standing board of open roles. We would rather leave a role unlisted than post one we are not actually filling to look busier than we are.

If you build carefully, care about handling other people’s data as little as the job allows, and want to work close to the whole of a product rather than a corner of it, we are worth an email even when nothing is posted.

What we can promise a candidate is the same thing we promise a school: a plain account of the stage we are at. You would be joining an early venture on a working engine, not a funded company with a filled org chart, and you should decide with that in view.

Reach out at [email protected]. Tell us what you would want to build.

Money, said plainly

Money is off on this page

There is no price on this page and no checkout on it. Nothing here takes a payment, captures a card, or converts anyone to a paid plan. This is a for-profit venture — not a nonprofit and not a tax-deductible arrangement — but its pricing is not something we will post before it is set.

When there is pricing, it will be written down in one place, with the included capabilities, the terms, and the exit process, before anyone is asked to pay. Today the only actions on this page are to talk to us or to read the family’s own product pages.

FAQ

Questions a careful reader asks about a young company

Is Question a real company?

Yes. Question is a founder-led venture inside the Stanley Studios estate, built on a response engine that is already running in production today, and any signed-in staff or studio account can author question sets on it. There is no public self-serve signup: an account is opened by us, by hand. This page states each of those separately rather than average them.

Is Question funded, and who owns it?

There is no outside investment and no venture round. Question is self-funded inside Stanley Studios, which owns it. If a funding or ownership change ever happens, it will be stated here in plain words rather than implied by a logo wall.

Who is on the team?

Question is founder-led and built by a small team inside Stanley Studios — the same people who build the wider school platform. There is no separate executive roster, and we will not publish invented titles to look larger than we are.

Do you have customers I can call for a reference?

There are no customer logos, testimonials, or adoption counts, because there are none to cite. What we can show instead is a working engine, the authoring surface a signed-in staff or studio account reaches today, and exactly how a response is treated.

What can Question actually do today?

The response engine is running in production: five answer shapes the database enforces at authoring, three of which -- text, scale, and choice -- accept answers today, while ranking and conjoint refuse answers until their answer wall lands; responses with no identity column, response times coarsened to the hour, and server-side moderation and rate limiting. Any signed-in staff or studio account can author questions and question sets on it today. Two things it does not do: there is no public self-serve signup, so an account is opened by us; and a custom question-type catalog is not provisioned, so that route answers 501 rather than fake a success.

How do you handle student data?

A response carries no identity column; its time is coarsened to the hour; data is stored on our own infrastructure and the school retains control of its records; and a minor’s record is consent-gated and not publicly browsable. We do not claim a FERPA or COPPA certification — the product is designed to support a school’s obligations.

Is any of this AI?

No. Nothing here is AI. No model writes a question, scores a response, or grades a student. The engine validates and stores answers in known shapes; a person reads what came back.

What does it cost?

There is no price on this page and no checkout anywhere on it. Money is off here. When there is pricing for the self-serve product, it will be written down in one place before anyone is asked to pay, along with the terms.

Will Question still be here in a year?

We cannot promise the future and we will not pretend to. What we can show is a response engine already running in production and an owner, Stanley Studios, that builds the wider school platform this sits beside. We would rather offer that than a slogan about longevity.

How is question.company different from question.technology and question.software?

question.technology is the shared response engine. question.software is the classroom front door a teacher uses to run questions with a class. question.company is the venture behind them both — who builds it, how it operates, and how to reach us.

Do you use subprocessors, and where is data hosted?

Data is held on infrastructure we run inside the estate. Where a subprocessor is used, it is named in the data documentation we provide for review before adoption. We do not publish a subprocessor list on this page, because a page-level list is the one we would fail to keep accurate.

What is your data retention and deletion policy?

Retention periods, school-configurable deletion, and export are being finalized and will be stated in the terms before a school is asked to adopt. A response already carries no identity column and stores only an hour-level time, so the smallest case is small by construction.

What happens to our data if Question shuts down?

A school retains control of its own records, and export and account-closure procedures will be documented in the terms before adoption. We would rather write that down than promise a permanence we cannot honestly offer at this stage.

Can I verify the claims on this page?

The engine section names the exact tables and constraints so those claims can be checked rather than believed. Any other claim on this page can be raised with us directly, and we would rather be asked than taken on faith.

Contact

Talk to the people who build it

Whether you are a school weighing whether to rely on us, someone who might want to build here, or a reporter checking a claim on this page, the door is the same one, and a person reads it.

Email [email protected]. There is no form on this page, no card asked for, and no student data requested — please do not send any.

Email [email protected] Read the FAQ →

What this page does not claim

Question is a real, founder-led venture on a response engine that runs in production today, open to any signed-in staff or studio account for authoring. That is the strongest true thing here, and it is the only claim of maturity the page makes.

It is not a funded startup. There is no outside investment, no venture round, no board beyond the founder, no leadership-team roster, no office to tour, and no published headcount.

There is no press, no award, no customer logo, no testimonial, and no adoption count, because none exist and none may be invented to fill the space.

There is no public self-serve signup: the public account-creation route provisions a fundraiser, photo, or newsroom school and never a Question account, so an account is opened by us, by hand. And a custom question-type catalog is not provisioned — the type vocabulary is a fixed set and the route that would add one answers 501 rather than fake a success.

Money is off: no price and no checkout. Nothing here is AI. A minor’s record is consent-gated and not publicly browsable, and we claim no FERPA or COPPA certification.

Talk to us Back to what is running →