FAQ · AIBS
Answers before you begin.
Find useful information to prepare your project and understand our support.
Frequently asked questions
Have questions? We have answers.
Understand our services and prepare your project with AIBS.
Which businesses does AIBS support?
We support leaders and teams with organisation, client acquisition and digital tools. We start with your situation: a business to structure, a process to improve or a project to develop.
Do you support businesses throughout Morocco?
AIBS supports businesses throughout Morocco. Remote or on-site work is arranged according to the project.
Where do I start if my need is not clear yet?
Tell us what takes up your time, holds your business back or what you want to develop. An initial discussion clarifies the need and whether an assessment would help.
What budget should we plan for?
Budget depends on scope, integrations and the level of support. A proposal follows scoping, separating service fees and any third-party tool costs.
How long does a project take?
Timing depends on complexity and the availability of data and teams. We agree stages and review points before starting, rather than one fixed duration for all projects.
Can you work with our current software?
Yes. We start by reviewing your environment. Depending on your tools, we can suggest better configuration, connections or complementary development.
Do you support teams after implementation?
Training, assistance and follow-up can be included. Their scope and arrangements are specified in the proposal to prepare adoption of new practices.
What does a prototype ready in 48 hours mean?
It means an initial preview to visualise an idea and discuss its workflow. Scope, required inputs and when the timeframe begins must be confirmed with AIBS. A prototype does not replace development, testing and production deployment of a complete solution.
What should I prepare before our first conversation?
Describe your activity, one concrete difficulty and the tools you already use. An anonymised document or workflow example can help. You do not need a finished specification; avoid sending passwords or unnecessary personal data.
How are access permissions for tools and data defined?
Access should match each person’s role. Scoping identifies the information needed, the accounts involved and expected approvals. Hosting, retention and security requirements must be reviewed in your context before deployment.
What happens after delivery?
Onboarding, documentation, fixes and future improvements are separate topics. Support scope, responsibilities and maintenance arrangements must be specified in the agreed proposal. We recommend defining a contact person and a request reporting procedure from the start.