Standardise how every business unit specifies work
The problem at scale is not writing one specification. It is that forty of them are written forty different ways, and procurement has to price all of them.
Forty specifications, forty formats
The problem at scale is not writing one specification. It is that every business unit writes its own, in its own shape, and procurement has to price forty documents that cannot be compared with each other.
One structure across all of them makes a call-off comparable, an estimate checkable, and a rejected proposal explainable.
- An audit log of every privileged action.
- A signed DPA and terms your legal team can redline.
- SAML SSO and SCIM are on the roadmap, not available yet — ask sales if that is what is blocking you.
What enterprise adds
The parts your security and procurement teams ask about first.
SSO and SCIM (roadmap)
SAML single sign-on and directory provisioning are not available yet. Talk to sales if this is what you need before you can sign.
Role-based access
Per-project permissions with an audit log of every privileged action.
DPA and custom MSA
A signed Data Processing Agreement, and terms your legal team can redline.
Invoicing and PO (roadmap)
Purchase-order billing is not built yet — today's billing is a card on file. Talk to sales about timing if PO terms are a requirement.
Data residency
UK and EEA region pinning across the services that support it.
Private reviewer pool (roadmap)
A named, NDA'd reviewer pool for work that cannot go to the open marketplace is not built yet. Talk to sales if that is a requirement.
What your security questionnaire will ask, and where the answer is
All of it is written down before you ask.
- Data Processing Agreement — published, and signed on request.
- Sub-processor list, with locations and the notice period for changes.
- Encryption in transit and at rest, and who inside Moksy can reach what.
- Breach notification timeline, and the incident process behind it.
- Retention and deletion, including what survives an account closure and why.