For agencies & studios
Your first client pays for your setup.
You write your clients’ docs in Markdown, in the repos you already work in — then the moment a client wants to see them, you’re emailing stale PDFs or standing up a wiki that drifts from the code the next day. ilumd fixes that for $29 a workspace: one always-current, branded portal per client, readers free, and your first paying client makes your own workspace free.
How it works
From scattered repos to client-ready in three moves.
Connect every client repo
Point ilumd at your GitHub org. It finds every Markdown doc across every client and repo — including the ones nobody remembered writing.
Govern and isolate
Set who sees what per doc and per folder. Isolation is default-deny at the data layer, so one client's material can never surface in another's.
Hand each client a portal
Publish a branded, self-serve portal per client — your logo, your colours, isolated to them. Their team finds answers without emailing yours, and it never drifts from the code.
The economics
Land one client, and your own workspace is free.
Everyone pays $29 for a workspace — your own org included. The moment your first client workspace actually pays, that $29 credits straight back against your bill. So your first client doesn’t cost you a workspace; it covers the one you already had.
| Where you are | Workspaces | Your bill | What’s happening |
|---|---|---|---|
| You, before any clients | 1 (your own) | $29/mo | One workspace, one 30-day trial, no card. |
| Your first paying client | 2 | $29/mo | Their $29 credits your own workspace — you carry it for free. |
| Six clients, client-billed | 7 | $0/mo | Your six clients pay ilumd $174/mo directly; your own bill is zero. |
First-client credit is $29/mo against your subscription. Every client after that earns pooled AI credits as the AI layer rolls out — readers stay free at every step.
Who pays, and no lock-in
You choose who’s billed.
Every workspace is paid for one of two ways — and either way, ilumd is the merchant of record.
Client-billed
The client becomes ilumd's direct Stripe customer and pays for their own workspace. You front nothing, and their $29 is what credits your own bill.
Self-billed
You pay for the workspace and fold it into your own fees at whatever markup you like. One relationship, one invoice, your margin.
No lock-in — the client owns the relationship
When a client is billed directly, they’re already ilumd’s customer, so their docs keep working even if you part ways. Their workspace, portal, and access survive the hand-over — your churn doesn’t take their documentation with it. That’s an easier “yes” for a client than any tool that only works while you’re in the middle.
The non-negotiable
Client A never sees Client B.
Isolation isn’t an enterprise upsell — it’s the foundation. Every access decision is default-deny and enforced at the data layer, on two axes: which workspace and which audience. There is no path for one client’s document to appear in another’s portal, search result, or AI answer.
- Default-deny: nothing is shared until you share it.
- Enforced at the data layer, not just the UI.
- Workspace × audience — isolation on both axes.
- The assistant only answers over docs the asker may see.
What it changes
What changes for the business.
Get your senior people back
The repeat questions get answered by the portal, not by a senior engineer on a Friday afternoon. Support load drops; billable hours come back.
Clients help themselves from day one
Every client gets a self-serve documentation portal — in your theme, isolated to them, always current because it’s served straight from the repo.
Your whole book of work, searchable
“How have we handled this before?” becomes answerable across every client you’ve served — governed and scoped to what each person may see.
Two seats at the table
What you get. What your client gets.
I'm an agency director
Answers take time to find. Time to write. Time you don't bill — and it shows in your timelines and your margin.
Simple questions stop eating the day — how / what / why gets answered by the portal, from the same docs your team already works from — not by a senior dev, again.
One source people actually trust — project truth spread across Slack, Jira, Notion, and the code means no one's sure what's current; ilumd makes your code docs the governed, up-to-date source of record.
Clients help themselves from day one — give every client a branded documentation and support portal — they find the answer themselves, without waiting on you.
Never pay per reader — per-workspace pricing; staff, clients, and the public read for free — share widely and protect your margin.
What your client gets
Every small question is an email to the agency — and your own customers send the same emails to you.
Answers without the email — a branded portal your team self-serves, always current.
Only ever what you're meant to see — access is scoped — no guessing, no oversharing.
Give your customers self-serve too — a branded help portal for them, so you're not their support desk either.
Right-sized now, scales later — start before you need a full CRM or help desk; it grows with you.