how agencies use nihmbus
one platform, every client.
isolated workspaces, per-client voice models, reusable workflow templates, and transparent billing. scale from 5 clients to 50 without scaling your team.
one workspace per client
every client gets an isolated workspace with their own subjects, voice models, missions, and approval flows. data never crosses boundaries.
subject voice models
train a voice model per subject (the client's brand, their CEO, their product). the agent writes in that voice across every channel.
decision queues for clients
supervised missions file decisions to the inbox. set up client users who can approve/reject drafts without touching the strategy.
workflow templates across clients
build workflow templates once (e.g. 'new client onboarding', 'weekly content cycle'). fork them to each client's workspace.
CRM for influencer outreach
manage influencer and partner relationships in the contacts CRM. the agent sends outreach via the DM router and follows up automatically.
billing per client
each workspace has its own billing scope. AI costs bill directly to the client's workspace — transparent, per-client billing with no middleman.
faq
questions from agencies
can my clients approve content themselves?
yes. invite client users to their workspace with a reviewer role. they can approve/reject drafts in the inbox and view analytics — but they can't change the agent's strategy unless you grant that role.
how does billing work across clients?
each workspace has its own billing scope. AI costs bill to the workspace that generated them. clients pay for their own AI usage directly — no middleman billing required.
can I reuse strategies across clients?
yes. workflow templates, skills (playbooks), and engagement rule patterns can be created once and forked to each client's workspace. the instance runs in the client's context with their voice model.