Marketing teams

One brand kit, nothing live without a yes

The brand kit sets the fonts, colours and voice once. The team turns webinars, interviews and product demos into clips, posts and emails inside it, every item waits for approval, and the API feeds the rest of your stack.

Free plan · No credit card · Works in the browser

What you get

Splicora for marketing teams, in practice

Brand kit, enforced

Fonts, colours and caption presets set once and applied to covers, quote cards and captions, so the output is on brand because of how it was made rather than because somebody checked.

Approval before publishing

A read-only link anyone can open without an account. They approve each item or ask for changes with a note, and a change request raises a notification on the project.

Seats and shared workspaces

Teams $79 includes 5 seats with their own logins, 10 workspaces and 25 accounts per platform, so a product line can have its own everything.

An API and automations

The same operations the app performs, behind a key you issue yourself, plus rules that watch a source and hold what they make for review.

One week, one source

One recorded product webinar, and what comes out of it.

One recorded product webinar

One recorded product webinar

Where team content goes wrong

Team content fails in two places, and neither of them is the writing. The first is drift: four people making posts in four tools, and by the third month the fonts, the tone and the colours have quietly become approximations of each other. The second is the approval, which usually lives in a thread, with the asset attached twice and the final version named final-2.

Both are process problems rather than quality problems, and both get worse with headcount. A tool that only makes the content faster makes them worse faster.

What this page is about is the two guardrails: the brand kit that makes drift hard, and the approval that makes publishing deliberate.

Where team content goes wrong

The brand kit as the guardrail

The brand kit holds the fonts, the colours and the caption presets, and it applies to what the product makes rather than sitting in a PDF somebody reads once. A cover comes out in your typeface. A quote card comes out in your colours. A caption comes out in the preset the team agreed on.

Alongside it, brand voice profiles hold the writing: tone, vocabulary, the phrases to avoid, built from copy you have already approved. Teams $79 carries 25 profiles, which is enough for a house voice plus one per product line or region.

The point of both is that being on brand is the default rather than a review step. The review step is for the things a style guide cannot catch.

The brand kit as the guardrail

Content approval workflow: review, approve, publish

Turn sharing on for a project and you get a link. It is read-only and it needs no account, which is the property that matters: a reviewer who has to create a login will instead ask for the files by email, and the approval goes back into a thread.

The reviewer sees every clip, every written piece and every visual, and marks each one approved or asks for changes with a note. Those decisions land on the project next to the item they are about, and a change request raises a notification, because that is the one outcome somebody has to act on.

Nothing publishes on its own. Scheduling is a deliberate act, and an automation that produces a week can be set to hold every post for review rather than send it, which is the setting to leave on.

Content approval workflow: review, approve, publish

Seats, workspaces and the API

  • Seats. Teams $79 includes 5, each with its own login and permissions, drawing on one shared pool of 1000 credits a month.
  • Workspaces. 10 of them, each with its own projects, connected accounts and calendar, so a product line or a region is properly separate.
  • Accounts. Up to 25 per platform per workspace, so two brands with a LinkedIn page each are two connections rather than one overwriting the other.
  • The API. Create a project, find its clips, generate, publish, schedule, read the library and subscribe a webhook, behind a key you issue and revoke yourself. See the API.
Read more

The API is the part that matters if content is a stage in a pipeline rather than a destination. The same operations are available to an agent over MCP, behind the same key and the same limit, and both spend the same credits at the same prices as the app.

Seats, workspaces and the API

What it costs on Teams

Teams $79 is 1000 shared credits a month, 5 seats, 10 workspaces, 25 brand voices, priority processing and everything on Pro $39.

A product webinar turned into a week of posts costs roughly what it is made of: 10 credits to find the clips and 2 credits a clip kept, 2 credits a clip for captions, 3 credits for a blog post, 2 credits for a newsletter, 1 credit a social post and 1 credit a quote card. Every one of those is shown before it runs.

Credits are shared across the seats rather than divided between them, so a heavy week for one person does not need a second subscription. The pricing page has the table, and Pro $39 at 500 credits is the honest answer if the team is one person who wants the workspaces.

What it costs on Teams

Questions

The things people ask first.

Yes. Share the project as a read-only link and they approve each item or request changes with a note, without an account and without a seat. Their decisions come back onto the project, and a change request raises a notification.

Yes. Teams $79 carries 10 workspaces, each with its own projects, connected accounts and calendar. Nothing crosses between them, which is what makes two brands on one account safe.

Yes. Create a project from a link, find its clips, generate media, publish, schedule, read the library and subscribe a webhook, behind a key you issue yourself. The API page has the operations, the samples and the rate limit, and the same operations are available to an agent over MCP.

Yes. The brand kit takes your fonts and colours and applies them to covers, quote cards and captions, and it is included from Starter $19 upwards. Caption presets are saved per brand so the team is picking from a list rather than setting type.

One pool. Teams $79 is 1000 credits a month for the whole account rather than per seat, so a week where one person does most of the producing costs the same as a week where everybody does a little.

Most marketing teams start on Teams at 79 a month. See what each plan includes.

Also in Splicora

You do not have to start with a recording.

The same workspace generates images, video, voices and avatars from a sentence, with the price of each shown before you spend a credit. Whatever it makes lands in the project beside the clips, captions and posts, ready for the same scheduler.

Start with what you have.

A link, an upload, or a sentence. Every price is shown before you spend a credit.

We use cookies for analytics. Necessary cookies always run. Cookie Policy