Customisation
Over 400 business rules are already implemented in AlibeeZ. When your work needs one that does not exist yet, we talk it through: our teams scope it with you rather than asking you to change how you operate.
The foundation
These are not options to be built: they ship, they are tested, and they are switched on through configuration. Most of the specifics you believe are unique are already covered.
Entry and its controls, entity by entity, country by country.
One engine for time-and-materials, fixed price, and everything in between.
Profitability computed continuously, and commitments kept under control.
A few examples from the 400+ rules available.
Workflows
A workflow in AlibeeZ is not just “who approves what”. It is also how a request enters the system, who it notifies, and what it triggers next.
One or several levels, triggered by role, amount, entity or project type. Every step is recorded, and delegations are handled.
Your teams make requests that fit no standard box. The form is built, routed to the right approver, and feeds the tracking — instead of getting lost in an email thread.
Every step is recorded: who, when, and on which version.
Tailored
No vendor can anticipate every specific of a business. What we can do is not leave you alone with the problem: the rule is scoped with our teams, who know both the product and your sector.
To be clear about the terms: a configuration adjustment is handled within your subscription. Bespoke development is quoted and discussed before any commitment. In both cases the starting point is the same conversation.
You describe the real case, not a specification. Our teams turn it into a business rule and first check whether existing configuration already answers it — it often does.
Depending on the request, it is either configuration or development. You know which before committing, with the timeline and, where relevant, the quote.
Once delivered it is maintained and follows the product’s updates like everything else. You are not left carrying a bespoke branch in a corner.
FAQ
They are configurable product behaviours: how time is rounded, when an invoice may be issued, the threshold above which a purchase needs a second approver. They are shipped and tested; you switch them on and tune them rather than building them.
It depends on the scope. A configuration adjustment is handled within the subscription. Bespoke development is quoted and agreed with you before it starts. We tell you which side your request falls on at the scoping stage.
Yes. A delivered rule joins the product foundation and is maintained with it. That is an important difference from an isolated customisation: you are not pinned to a frozen version.
Common approval chains are configured from the administration area by your own teams. For specific request forms, we set them up with you during deployment, after which you evolve them yourself.
Configuring the foundation is part of deployment, which is counted in weeks — under a month at Zenika. Specific rules are scoped afterwards, once you see the product running on your own data.
Other industries
Because every sector has its own rules, we support IT services, consulting and engineering firms, communication agencies, audit and actuarial practices with a tailored approach built on real field experience.
Cut bench time and keep consultant utilisation high.
Learn moreSecure fixed-price projects and hold utilisation above 80%.
Learn moreTrack technical micro-tasks and protect your margins.
Learn moreStructure creative projects without losing profitability.
Learn moreRun regulated engagements with full traceability.
Learn moreDeploy scarce expertise and de-risk fixed-price work.
Learn moreLet's talk about your business
AlibeeZ is also a team dedicated to listening to you. We map out your business processes end to end and help you solve your issues with a digital solution that fits the way you work.
