Usage review
Actual sign-ins over the last three months, modules in use, dormant accounts still in the name of former staff. Closing five unused seats sometimes changes the tier you need.
A fifteen-person consultancy pays an annual subscription for twenty-five users: accounts were created as people joined, nobody closed them when the interns left, and the invoice simply followed along unnoticed. The opposite happens too, with a team paying for a full tier on a portal where only the CRM and tasks are ever opened. We look at who signs in and what they open, then set that against what the publisher sells today. We resell no licences and take no commission: the recommendation rests on your usage and nothing else.
The first question to settle: does the portal run at the publisher, or on a machine you nominate inside a European data centre. That answer drives the price and the location of your data alike.
Actual sign-ins over the last three months, modules in use, dormant accounts still in the name of former staff. Closing five unused seats sometimes changes the tier you need.
Today's tiers weighed against the features in daily use, plus whatever you expect to add this year. Nobody should buy headroom on the off-chance.
Cloud starts quickly and needs no administration. On-Premise earns its keep when data has to stay on a machine you choose, at OVHcloud or Scaleway for instance, or when deep development work is on the cards.
The subscription is taken out by you, under your own billing details. We point out which boxes matter so the invoice lands with the right people.
Expiry dates are logged on our side and flagged early, so a renewal never falls in your busiest period or during the August shutdown.
We identify the owning account and help pull back rights stranded with a member of staff who has left, or with an earlier supplier.
A review with a recommendation takes a few hours. A migration between the cloud and a machine of your own runs as its own project, quoted once we have looked inside the portal.
Active accounts, modules genuinely in use, volume of stored data, plus whatever the next twelve months hold.
One named tier, the argument for it, the yearly cost in euros excluding VAT, and a comparison with the levels above and below.
We stay with you through the purchase, then confirm that the paid features are live and correctly configured.
A few weeks ahead of renewal we revisit the numbers, because twelve months change a company more than anyone expects, and the plan has to keep up.
Your portal has to sit under your own name, never your supplier's. A Bitrix24 created on an integrator's email address leaves with that integrator the day the relationship ends, carrying off the client history, the deals and every conversation. Checking takes ten minutes: open the list of administrators and see which address sits at the top. Whenever we set a portal up, the owning account is held by a member of your own staff.
On the cloud side the portal falls back to whatever the publisher provides for a lapsed subscription: fewer features, tighter limits, data still present but harder to reach. Those rules shift over time, so we confirm them at source ahead of each expiry. An On-Premise install mostly stops receiving updates, and that becomes a security concern within months and an awkward moment during an audit.
Often yes, and it starts with tidying up the account list. Looking at roles nearly always uncovers staff who open the portal monthly to glance at a single task, and a notification by email covers that need perfectly well. Once the portal is in order, dropping a level happens without anyone noticing.
Two reasons. We hold no partner status with the publisher, so there is nothing in it for us, and we would rather nothing at all sat between you and your own portal. The subscription stays yours, the invoice comes from the publisher, and our part is advice plus a diary of dates. Our time is the only line you pay, EUR 95/hour excl. VAT, or nothing extra when a managed services contract already covers it.
The publisher states where its data centres are, and that is worth reading before any customer personal data goes in. We read it with you, draft the matching entry in the register of processing activities and prepare the answer you would give the CNIL. Where location rules are strict, On-Premise in Europe remains the easiest position to defend.
Yes, as soon as the portal holds personal data, which is true of any CRM. Under GDPR the publisher acts as a processor and the arrangement has to be documented. We collect the paperwork on offer, flag the clauses worth watching and tell you what belongs in your own register.
Send over the number of people signing in, the modules in daily use and the end date of the current subscription. You get a recommendation and a costed comparison.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.