Consulting path
First we understand how you work. Then, if needed, we talk products
The question we get most often is “you have a lot of applications, which one is right for me?”. It is the right question, and the answer is not in a price list: it comes from looking together at how your company works today.
The questions you contact us with
These are the messages our contact form brings in almost every week. If at least one sounds like you, you are in the right place: that is exactly where we start.
-
“I saw you have many products and I would like to understand what could be useful for us.”
We do not know yet either, and that is normal. We find out by looking at what your team does in a typical week: where people wait, where the same work is done twice, where documents get lost.
-
“We are evaluating other vendors too: what makes you different?”
We tell you where we are strong and where we are not. If someone else covers a part of your process better, we write it in the proposal before you sign, not after.
-
“We already use an ERP and other tools: do we have to throw everything away?”
Almost never. We look at what is worth keeping, what we connect through APIs or webhooks and what is genuinely worth replacing. Kamzan often fills the gaps between the systems you already have.
-
“How much does it cost? We cannot work it out from the website.”
After the analysis you get a number, not a range: applications, users, rollout and training itemised, with any bespoke development quoted separately.
How we do not work
We would rather say it up front, so you know what to expect from the first call.
-
We do not start from the price list
The first call is not a demo with prices at the end. It is a conversation about your process: who does what, which documents change hands, where manual work piles up.
-
We do not sell you applications you will not use
Turning on the whole ecosystem on day one is the fastest way to have it abandoned. You start with one or two tools on the problem that hurts most; the rest is added when it is genuinely needed.
-
We do not ask you to change your process to fit the software
If the way you work works, it is the software that gets configured: permissions, folders, approvals, notifications. When the process really should be revisited we say so, but the decision stays yours.
-
We do not say yes to everything
If Kamzan does not do what you need and building it makes no sense, you find out during the analysis and not once the project is under way. It has happened before, and we will keep saying it.
How the path works
Four steps, no commitment until the quote. From the first call to the proposal usually takes one or two weeks, depending on how many people we need to talk to.
-
Discovery call
You tell us about the company, how many people are involved and the two or three things that hurt most today. No corporate pitch: we ask questions.
-
A map of how you work today
We write down the processes you described: documents, approvals, deadlines, tools already in house. It is the document you correct us on before we talk solutions.
-
Proposal: what you need, what can wait, what you do not need
For each need we name the tool, or we write that nothing is needed. The quote separates subscription, rollout and training, and prices any bespoke development on its own.
-
A pilot with one team, then the rest of the company
You start with a small department on real data. When those people work without asking for help any more, you extend: that is the sign the setup holds.
What you keep after the analysis
Even if you decide not to go ahead, what we wrote together is yours and we leave it with you.
- The map of your processes, written down and ordered
- The list of recommended tools, alongside the ones we ruled out and why
- A quote with scope, timings and a fixed price
- The rollout plan: who starts first, with which data, by when
- If needed, the scope of the bespoke development, quoted separately
Who you talk to
On the call you meet the people who build and install the platform, not a salesperson who then hands the file to a technician. It is the same contact who follows the rollout and stays your point of reference afterwards. We are an Italian team, the servers are in Europe and support answers in Italian.
Frequently asked questions
Does the first call cost anything?
No, and it comes with no commitment. The process map and the proposal that follows are free too: you pay only if you decide to go live.
How long does the whole path take?
From the first call to the proposal is usually one or two weeks. The pilot normally runs four to six weeks, then extends to the rest of the company at the pace you set.
Do we have to activate the whole ecosystem?
No, and we advise against it. Each application is activated on its own; logins, users and data stay the same, so adding one six months later is not a migration.
What if after the analysis you conclude Kamzan is not for us?
We tell you, with the reason. You still keep the process map we wrote together: it is useful for talking to another vendor too.
Do we need to prepare anything before the call?
No. Having a list of the tools you use or an org chart to hand helps, but it is not required: we ask the questions.
Alex