Sector — media agencies
For Dutch media agencies running multiple client accounts at once: client management with SLA visibility a partner can see, content production at velocity (drafts in five styles, podcast workflow, image gen), newsletter dispatch from the same workspace — all with governed AI and a credit ledger you can pass back to the client.
The operating view
One operating view from first signal to next decision.Presence, delivery, evidence, and decisions stay connected.Five connected systems
Capabilities are grouped by the outcome they support, not by the provider behind them.
One workspace, multiple clients. Each client carries their own facility records, recurring-task lists, SLA compliance percentage. Partner portal at /portal lets the client see their own data — no data bleeds across clients (workspace-isolated). Account managers see their assigned clients via permission-based access.
Drafts in five narrative styles across formats — blog posts, LinkedIn threads, X threads, IG carousels, video scripts — for every client account in the workspace. source-reviewed facts. Author profiles per-client so bylines and bio cards reflect the right brand voice. Manual editor for hand-finishing.
Each client can run their own show with custom cloned voice for brand-owned audio identity. Music intro / bed / outro library scoped per workspace, but episode metadata can carry per-client branding. Per-episode locale (EN/NL/AR within one show). RSS-ready for the client to submit to Spotify / Apple Podcasts directly.
Audiences and templates per client. Welcome / nurture / re-engagement automations triggered by a publishing event or a subscription event. managed delivery with verified event tracking. Per-client GDPR posture, per-client retention windows.
Every AI call (drafts, image gen, TTS, podcast mix, SEO enhancements) writes a row to the workspace reviewable usage history denominated in auditable usage records. For client-billed work, the ledger is the back-up document — you tell the client "AI work this month was €X" and they see the underlying transactions. No estimates, no surprise margins.
Newsletter and booking popup templates with EN/NL/AR localization. Exit-intent + timed triggers. Schedule windows for client-specific seasonal campaigns. Conversion tracking integrates with the same analytics pipeline that runs the rest of the workspace — popups don't need a separate Sumo or OptinMonster.
Public system
There is no published anonymized iSystem media-agency case study yet — but the closest live deliverable is iSystem itself. The platform's own client / SLA module, content production stack, and newsletter automations are running on isystem.ai right now; the changelog and the Opportunity Engine on the dashboard are a public demonstration of the same shape an agency operator would use. Hossam can demonstrate the full agency-shape workflow live in a free 30-minute Systems Fit Call.
Scope and boundaries
Replaces: Asana / Monday for client-facing project visibility · Mailchimp · separate content-tooling stack · Riverside / Descript / Anchor for podcast · Sumo for popups · ad-hoc Google Drive client folders. Note: this is not a full PM replacement (Asana / Linear stay that lane for internal sprint work) — this is the client-facing operational layer.
The offer
Growth Operating System at €7,500 setup + €699/month (metered AI) is the right starting point for media agencies — the full content + SEO + podcast + newsletter + client/SLA + governance stack. Multi-client workspace setup may incur additional configuration time, confirmed on the Systems Fit Call.
Foundation
Standard €7,800 setup + €498/month
€3,900 setup
Growth
Standard €15,000 setup + €1,398/month
€7,500 setup
Systems Blueprint. €490 · 90 minutes · credited to implementation within 30 days.
Embedded Systems Engagement. Proposal-only when the operating scope requires it.
Prices exclude 21% VAT, third-party services, and metered AI usage.
A sensible fit
The system is most useful when someone owns the next decision and is willing to review the evidence.
Keep specialist tools specialist
Keep specialist systems where they are needed; iSystem connects the layer around them.
