Grow the revenue

Because the value is not in the number of chairs. The whole company uses the Operations Suite and two people use Marketing, and charging the same for both would be wrong in both directions. A plan is capacity: seats are already in it, and you can add as many more as you need.

The cap counts automations that are switched on, not how often they run. Anything you no longer need can be switched off with one toggle — the run history stays and the slot frees up. The cap itself is a term of the Automations module's own plan rather than of a suite plan: how many you may keep switched on at each level is written on that module's pricing page. If a level's cap runs out, that is a reason to move up the module rather than to keep part of your processes in someone else's service. What a run spends out of the shared capacity is on the AI capacity page.

That is exactly the intent. If you came for marketing, you take the Marketing Suite and do not pay for the operational one. If you later need a second, it is 15% cheaper, and a third is 25%.

Marketplace modules are bought on top of a suite you already have rather than instead of one — and that holds for all of them except Sintora Meetings, which works and is sold without a platform subscription, on a price list of its own. Inside a suite the modules are not sold separately: the suite is the unit, 22 modules across 4 suites, and the plan sets the capacity rather than the contents.

Every marketplace module has a price page of its own, and it states exactly what has been published: a plan grid, a starting price per seat, or that there is no price yet. A module's price is on that page rather than here. Sintora Meetings is an exception to the question itself: it is not bought on top of a suite but sold without a platform subscription, on a price list of its own — Lite, Standard and Advanced. Where there is no price we do not name one until we can name it for good, and we do not offer a "price on request" instead.

Take Sintora Meetings on its own. It is the one marketplace module that works without a platform subscription: its own price list, its own levels, priced per user. You do not need a suite for it. If you need the platform later, Meetings stays where it is and works on the same data.

A brand is a completely separate workspace: its own Brand Voice, its own knowledge, documents, SEO, calendar and publishing. Data is isolated between brands, so an agency can run ten clients without mixing a single fact between them. Lite has one brand, Standard has three, and Advanced is uncapped.

30% of what you pay each month for suites goes into a development hours bank at a fixed rate, which the Calculator tab prints beside the number of hours. It is not a discount: the money does not come back, it turns into work you would otherwise have commissioned separately. The hours do not expire at once — they accumulate through the quarter, so they can be pooled into one substantial piece of work. It is counted off the subscription: implementation is a one-off sum, separate, and outside the base. It covers tailoring to your processes: new fields and reference lists, changes to approval routes, reports, integrations with your systems, configuring an industry module. It does not cover support or fixing platform bugs, which are our job anyway.

At any time. Moving up takes effect immediately with the remainder of the period prorated; moving down takes effect from the next one. No data is lost either way. And separately: adding a person, a brand or capacity does not require a plan change at all.

A structured export is available from the product at any time, not only on termination. Deletion timelines and the switching mechanism are set out in the DPA and the Terms — we deliberately signed up to the right to switch under the Data Act.