Corporate licence

One licence for the whole organisation. You supply your own template and house style per document type, and those become the standard for everyone. Staff sign in with their work email and land on your licence automatically.

What a licence gives you

What we need to get started

The intake below is what a proper setup requires. Blocks 3 and 5 are strictly necessary; the rest sets the terms. Work through it and send what you have — we will fill in the gaps together.

1. Organisation and contract

   • Registered name, chamber of commerce number and VAT number
   • Invoice address, invoicing email address and any purchase order reference
   • Contract contact person
   • Preferred start date and term
   • Expected number of users and documents per year
   • Licence model: per user or per document

2. Identity and access

   • Which email domains fall under the licence
   • Who will place the DNS TXT record we use to verify the domain
   • Automatic joining by domain, or invitation only
   • Who becomes an administrator — at least two people
   • Whether staff may see each other’s projects (default: no)
   • Whether single sign-on is a requirement now, or later

3. Documents and templates

   • Which method and documents you are taking: PRINCE2, PMBOK or Agile
   • A template per document type as .docx — not as PDF, because fonts, colours and margins cannot be read reliably from a PDF
   • Whether the chapter structure is mandatory or indicative
   • Your numbering convention
   • Sections that must always be present, such as a DPIA or information security
   • Fixed wording that must be reproduced verbatim

4. Method, governance and terminology

   • House standard: PRINCE2, PMBOK/PMI, Agile or hybrid
   • Standard tolerances for cost, schedule, scope and quality
   • Fixed reporting cadence and the names of your reports
   • Risk scale: three or five points, and the words you use
   • Standard RACI roles and what you call them
   • A term list: which term do you use where we would say something else

5. House style

   • Logo as SVG or high-resolution PNG
   • Heading and body font, named as they appear in Word
   • Whether those fonts may be installed on our server — a commercial font requires a licence on your side. If not, the document falls back cleanly to a comparable font
   • House colours as hex codes, for headings and accents
   • Page margins, header and footer
   • The document classification that must appear on every page

6. Privacy and compliance

   • Whether a data processing agreement is required, and on which template
   • Which data classification staff may upload and which they explicitly may not
   • Agreement to Anthropic as a sub-processor
   • Any processing region requirements
   • Preferred retention period, if it differs from the standard 30 days
   • Your internal privacy or security contact

7. Onboarding and pilot

   • A real pilot project to start with, and its brief
   • The project manager running the pilot
   • What makes the pilot a success — concrete enough to be testable
   • Preferred go-live date
   • Who handles the internal introduction to staff