Talk to an engineer
Tell us which contract is bothering you.
The most useful first message names the product, the seat count and the renewal date. You will get a reply from an engineer within one working day, and if we think replacement is the wrong answer for you we will say so before anyone books a call.
Prefer to just email us
Entirely reasonable, and the form does the same thing anyway. Write to support@conseiltek.com with the product, the seat count and the renewal date, and you will skip a round trip.
Security reports go to a separate address and are handled differently — see the trust page.
Before you write
Two things worth doing first, because they change the conversation completely:
- Run your own numbers through the calculator. If the payback there is over about 30 months, it will be over 30 months when we run it too.
- Find the seat quantity on your last invoice, not the headcount in the admin console. They usually disagree.
Not a sales pipeline
Nobody here is paid on commission, so there is no follow-up sequence and no nurture programme. If you go quiet, we assume the timing is wrong and leave you alone. Come back at the next renewal.
What happens next
Three steps, with the real timings.
These are the timings we hold ourselves to. If we miss one, chase us — the address is at the bottom of every page.
A reply from an engineer
Within one working day
Not an automated acknowledgement and not a sales development representative. Someone who has built one of these reads what you sent and replies to it. If your situation is one we think we would be wrong for, that is what the reply will say, and it will say why.
A 30-minute call
Usually within a week
One engineer, one of you, no deck. We ask what the contract is, what your people actually use it for, how many seats are real, and what is forcing the question now — a renewal, a price rise, an end-of-support date, or an audit finding. You should come away with a rough range and an honest read on whether the arithmetic works at your size.
A written shape, or a no
Within five working days of the call
A short written note: the capability picture as we understand it, an indicative cost model, and either a proposed two-week assessment with a fixed price and a start date, or the reasons we think you should keep paying your vendor. Both outcomes are common and neither costs anything.
The two-week assessment
Ten working days, fixed price, and you keep the report.
One contract, taken seriously. We are not trying to review your estate — we take the single line item you nominate and answer one question properly: should you still be paying for this, and if not, what does replacing it actually cost and take.
It is fixed price, agreed before we start, with a start date and an end date. The report is yours whether or not you engage us for the build, and it is written so that your own engineers could execute it without us. A recommendation to keep the licence is a normal outcome rather than a rare one, and it is the reason the assessment is worth doing before the build rather than instead of it.
Week one — measurement
- Ninety days of audit log exported and ranked by capability, with a headcount against each
- Invoice reconciled against the licence console: paid seats versus active humans
- Interviews with the three heaviest-using teams, watching the actual work
- The integrations and credentials pointing at the vendor, inventoried
Week two — arithmetic, architecture and refusal
- A parity matrix with the rows we would not match filled in first
- An architecture for AWS and one for Azure, priced against your own account
- A build estimate in engineer-weeks with the assumptions written down
- A three-year cost model, payback, and the conditions under which it fails
- A migration and cutover plan with a rollback, or a written recommendation to stay
What we need from you: a named sponsor, read access to the incumbent's audit log and admin console, and about four hours of your teams' time across the fortnight.