Enterprise · contact card
What to say when a team asks for the enterprise things
7 asks, with 3 of them answered “not available” in plain words. A static build has no SSO to federate, no data to protect and no entity to invoice from, and pretending otherwise wastes a procurement team's afternoon.
No sales contact exists in this build
No payment processor is wired into this build. Nothing here can charge a card, store a receipt or email an invoice — every paid surface below is a working demo of the flow, and the prices are this site's own plan copy.
What teams ask for, and what is true today
Seven asks, sorted by how a procurement conversation actually goes. 1 is available now, 3 are partly answerable, and 3 cannot be answered truthfully at all — each with the work it would take. Most enterprise pages list features; the useful ones list the gaps first.
Nothing. Sign-in is not implemented at all — there are no accounts, so there is nothing to federate.
To answer it properly: Identity provider support, which is a week of work only after accounts exist.
No uptime commitment can be meaningful here: the site is a static build served by a host, and no measurement of it is recorded.
To answer it properly: Monitoring, an incident process and a legal review of the wording.
A short, honest answer: the build collects nothing, sets no analytics cookies and has no user table, so the data-processing surface is nearly empty.
To answer it properly: A privacy review of the host's logs before signing anything binding.
The quality bar publishes its own scans — dependency, licence, image and spelling audits are public pages.
To answer it properly: A named security contact and evidence from real infrastructure rather than a static site.
No invoice can be issued, because there is no company billing entity behind this build.
To answer it properly: A legal entity, tax handling and an accounting system.
The seats demo adds and removes names in your browser; nothing is provisioned.
To answer it properly: Accounts, then a seat ledger, then directory sync.
Team is priced in the open: 3 seats included, $12 per seat after that, computed on the seats page.
To answer it properly: Nothing for the arithmetic — only a checkout to take the money.
The contact card itself
To: Motif UI (team enquiry)
Subject: Team plan — <company> (<seats> seats)
What we can do today:
· Team is priced in the open: 3 seats included, $12 per seat after that, computed on the seats page.
What we cannot do yet:
· SSO/SAML, an SLA with credits, a signed DPA, invoicing against a PO.
No accounts, no monitoring and no billing entity exist in this build.
What we need from you to answer properly:
· Which of the above is a blocker, and which is a preference?
· If seats are the only question, the team page computes the price.There is no address to send that to. It is printed anyway because the alternative — a “contact sales” button that opens a form which goes nowhere — is the exact pattern this section exists to avoid.