NewThe Command Center shows each person what needs them today, across every client. See it

Features

What is in it, and where each part stops

Every feature below is working software. The line under each one says what it deliberately does not do — which is usually the more useful half when you are choosing a system to run your agency on.

Creators

Creator records

Identity, audience, niche, geography, performance, product affinity, and the full history of every campaign, sample, message and post.

Audience data is only as good as what the platform legitimately exposes. Fields nobody supplied read as "not recorded".

Scoring

Seven weighted components against the client you are staffing. Weights configurable per agency, client and campaign.

A component with no data does not score zero — it is excluded and named, so a thin profile cannot look like a bad creator.

Discovery and filters

Structured filters across every recorded dimension, plus natural-language search that shows you the filters it understood before it runs.

Searches your own records and authorised sources. It does not crawl anything that has not permitted it.

Lists and tags

Saved lists, smart lists, tags and bulk actions across them.

Bulk actions that send anything still obey the same caps and stop-on-reply rules as everything else.

Outreach and conversations

Sequences

Multi-step outreach with templates, personalisation, AI drafting, scheduling, A/B variants and automatic follow-ups.

Stops on reply. Respects quiet hours, a daily cap and a suppression list, and records what it held back and why.

Unified inbox

One queue for every conversation, with the creator, campaign, samples, content and history beside it. AI classifies intent and drafts a reply.

A drafted reply is a draft. Sending is a person’s decision unless the agency deliberately configures otherwise.

Manual send queue

Where a channel does not permit automated sending, Kyrovane prepares the message and queues it for a person.

This is the compliant path, not a fallback. Nothing in Kyrovane sends through a channel that has not authorised it.

Campaigns, samples and content

Campaigns

Objectives, products, creators, commission, budget, dates, requirements and KPIs, with a live dashboard of what each is producing.

Campaign health is computed from recorded activity. A campaign with no data shows as unmeasured rather than healthy.

Samples

Request to approval to shipping to delivery to the post it produced, with product cost, shipping cost and expected content date.

Tracking depends on the carrier data you or your integration supply.

Content

Posts with their metrics, approval state and usage rights, joined back to the campaign and the product.

Metrics come from what the platform reports. Kyrovane does not estimate views it was not told about.

Analytics and money

Attribution

Campaign to creator to content to product to order, joined where the evidence supports it.

Direct, estimated and unknown are three separate columns. Kyrovane never merges them to make a chart look complete.

Forecasting

GMV, orders, creator revenue and client revenue, as conservative, expected and optimistic, with the assumptions on screen.

A forecast with too little history to support an interval is not produced at all.

Profitability

Contribution profit per client after creator costs, samples, shipping, campaign costs and your own internal cost assumptions.

It is only as accurate as the cost assumptions you configure, and the screen shows which ones are in force.

Client health

A 0–100 score from activity, performance, goals and profitability, with the reason for every point it deducts.

There is no churn probability. That would need a history of clients who left, and inventing one would be the exact failure this product exists to avoid.

Clients

Client CRM

Company, contacts, contract, fees, renewal dates, goals, notes, tasks and the full performance history.

Contract terms are recorded, not enforced. Kyrovane will not cancel anybody’s contract for them.

Client portal

Your client signs in and sees their own brand: performance, creators, campaigns, content, reports and goals.

Internal notes, margins, other clients and your AI context are invisible there — by construction, not by a filter somebody has to remember.

Reporting

Weekly, monthly, campaign and executive reports built from real metrics, read by your client in their portal or through a link you share, and downloadable as CSV or printed to PDF.

A report will not contain a figure the underlying data does not support, however much better it would read.

Automation and AI

Workflows

Trigger, condition, action, wait, branch, AI step, assignment and notification, with execution logs for every run.

Idempotent, rate limited, retried with backoff, and stoppable — per workflow, per tenant, or entirely.

Playbooks

Turn a way of working into a reusable, versioned template you can deploy to the next client.

A deployed playbook is a copy. Editing the template never silently changes a client’s live setup.

AI assistant and agents

Answers grounded in your own rows, with the source of every figure and a refusal when the data does not support one.

Agents hold explicit tool and scope permissions, a budget and an approval policy. None of them can act outside the tenant that invoked them.

Autopilot

Longer-running, supervised sequences of work towards an objective you set.

Material actions wait for a person. Unsupervised autonomy is not available by default and the approval is recorded.

Running the business

Billing

Monthly and annual plans, trials, checkout, invoices, upgrades, downgrades, cancellation, reactivation and refunds.

Card details are entered on the payment provider’s own page. Kyrovane stores a brand, four digits and an expiry — nothing that could charge a card anywhere else.

Usage and limits

Clients, creators, team members, AI usage, messages and workflows counted against your plan, enforced on the server.

A dimension this deployment does not measure is shown as unmeasured rather than as an empty bar.

Enterprise

SSO readiness, custom roles, API keys, custom domains, your name and colour on the client portal and printed reports, and an exportable, tamper-evident audit trail.

A custom domain is only live once its DNS actually verifies. Kyrovane does not claim a domain works because somebody typed it in.

Availability by plan

The heavier capabilities — forecasting, profitability, the client portal, custom domains, custom roles, API keys and autopilot — are on the larger plans. The pricing page lists which, and the product tells you plainly when something is not on your plan instead of failing in a way that looks like a bug.

See it against your own data

Import a creator list and run one campaign. That will tell you more in an afternoon than a feature list will.

Start free Plans and prices