Content operations as infrastructure.
For agencies and marketing teams whose content volume, publishing workflow or procurement requirements need a conversation. Start with your client websites and agree the scope before committing.
Email hello@writegarden.com with your websites, CMS and content requirements.
Three shapes of buyer.
If you recognise one of these, Enterprise is where the standard plan stops fitting.
Agencies
Use a separate organisation for each client and switch between them from your account. Bring your portfolio size, publishing cadence and review process to the scoping conversation.
Multi-brand teams
Plan content for separate brands with their own business context and CMS connection. Discuss your access, billing and reporting needs before choosing a rollout.
Teams with procurement requirements
Share your security questionnaire, data handling constraints and contract requirements so we can assess fit before you connect client data.
Agree the scope before you scale.
The standard plan is priced per organisation. Enterprise requirements need an agreed proposal covering availability, limits, support and terms.
| Capability | Writegarden · €49 | Discuss during scoping |
|---|---|---|
| Article volume | 3 articles per week | Required monthly volume and delivery capacity |
| Tracked keywords | 5 | Monitoring requirements and available limits |
| Client workspaces | Separate organisations and subscriptions | Portfolio setup and billing requirements |
| Publishing | Supported CMS connections and webhooks | Your CMS, field mapping and approval workflow |
| Access | Organisation membership roles | Required access controls and provisioning |
| Onboarding | Self-serve | Migration, setup and support scope |
| Procurement | Published standard terms | Contract, data handling and invoicing requirements |
Bring the requirements that matter.
Content volume
How many client websites, articles and markets do you need to support? Agree capacity and pricing before increasing your publishing cadence.
Publishing workflow
Map how research becomes a reviewed article in your CMS. Include field mapping, authors, images and the approval steps your team needs.
Measurement
Define the search and AI visibility questions each client needs answered, then agree the monitoring scope and reporting process.
A separate organisation for each client.
The current workflow uses organisation switching. Each client organisation has its own company context, membership and subscription.
- Your account Organisation switching
A team member can belong to more than one organisation and switch the active workspace.
- Client organisation Membership and billing
Create a separate organisation for each client. Subscriptions and membership roles are managed here.
- Client company Brand and publishing context
Work with the client website, brand voice, articles and CMS connection in its organisation.
- Business context and target audience
- Brand voice and content topics
- Publishing integration
- Generated articles and imagery
- Organisation membership
- Subscription and usage
Discuss your client-facing requirements.
White-label branding and custom domains are requirements to scope, rather than included features. Confirm availability and delivery terms before offering them to clients.
- Explain what clients need to see and access
- Share any branding or custom-domain requirements
- Define billing and reporting expectations
- Agree supported scope in writing before rollout
Built for your security review.
Share your requirements before connecting client data. Data location, provider processing, retention and access controls need to be assessed against your use case.
Data handling
Request a review of storage locations, AI providers and data transfers for your intended workflow.
Procurement documents
Identify the contractual and data processing documents your team needs and confirm their availability during scoping.
Client access
Use separate organisations for client membership. Review the permissions each person needs before inviting them.
Authentication requirements
Organisation roles are owner, admin, member and billing. SAML SSO and SCIM provisioning are requirements to discuss; they are not included in the standard workflow.
From requirements to an agreed rollout.
Agree fit, scope and terms before scheduling onboarding.
-
Share your workflow
Describe the client websites, CMS platforms, content volume and review process you need to support.
-
Review the scope
Confirm supported capabilities, any development requirements, pricing and a proposed timeline.
-
Agree terms
Review contract, data handling, billing and support requirements before committing to the engagement.
-
Validate one client first
Connect a client workspace, review a complete article and verify the published page before expanding the rollout.
Include any security questionnaire or required contract terms with your inquiry.
What buyers ask.
Is Enterprise a published bundle of additional features?
Enterprise begins with a scoping conversation. Capabilities, pricing, support and delivery dates must be confirmed in the proposal.
How are client websites organised?
Use a separate organisation for each client and switch between organisations from your account. Each organisation has its own subscription and membership.
Can I offer a white-label portal?
White-label branding and custom domains need an explicit scope and availability confirmation. They are not part of the standard workflow.
Can you meet our data residency requirements?
Send the specific storage and processing constraints your team needs. Confirm provider locations and data flows before connecting regulated or restricted client data.
What are the contract and pilot terms?
Scope, duration, pricing and any pilot terms are agreed for the engagement. Contact us with your requirements.
Is SAML or SCIM included?
The current workflow uses organisation membership roles. Treat SAML and SCIM as requirements to discuss before choosing the product.
Tell us what you're shipping.
Bring your client websites, target markets, current CMS and any procurement constraints. We will assess the fit and discuss a practical scope.
Email Enterprise sales