AI and automation
BDC builds AI into the systems a company already runs, and it comes down to three things: process automation inside Odoo or ERPNext — routing approvals, classifying transactions, cutting manual entry; document extraction that turns incoming invoices and contracts into records; and assistants that answer from your own company data. What gets built is decided after a diagnosis of where work repeats or decisions stall, and often the honest answer is a plain rule in the system rather than a model.
supplier-invoice.pdf
Read and matched
Draft entry in your ERP
Most of what is sold as AI today is a solution looking for a problem.
We start from the other end. During the diagnosis we find where work repeats or decisions stall, then ask whether AI is the right tool for it or whether a plain rule in your system would do. When AI is the answer, we build it inside the system you already run — not beside it, where it would only need syncing back.
What we build
Not shelf products. Capabilities built into your operations and scoped to the process that is costing you time.
Approvals that route themselves to the right person, transactions classified as they arrive, and the manual re-entry between those steps removed — inside Odoo or ERPNext, using the data already there.
Incoming invoices, purchase orders and contracts read and turned into records in the system, instead of being retyped by hand and corrected weeks later.
An internal assistant that answers your team from your own policies, files and records, or a chat surface that handles the questions customers keep repeating.
The other half of the advice
A recommendation is only worth something if it can also be no. These are the cases where we say it.
If a condition inside the system solves it, that is what we recommend: cheaper to run, easier to audit, and it does not drift.
Automating a process nobody agrees on multiplies the disagreement. We fix the process first.
No model answers from records that were never captured. Sometimes the first project is the capture, not the AI.
Anything with legal, financial or human consequence keeps a person in the loop, with the system doing the preparation.
Evidence we ship AI software
Raqeem is an Arabic AI learning platform we designed, built and published ourselves, and it is listed on Google Play. It is the reason we can speak about where these systems fall short as confidently as where they help: we carry a product of our own through the same problems.
How an engagement runs
Four steps, in the order that keeps the decision honest.
We map where work repeats and where decisions wait, then count what each one costs your team in time.
For every candidate we ask whether AI earns its place or a rule in the system is the better answer. You see both options.
The automation lives in Odoo, ERPNext or your own application, with a person reviewing anything consequential.
We agree the measure before we build — entries avoided, hours returned, time to approval — then train your team to run it.
Entry offer
30minutesYou leave with a short list of what is worth automating, not a demo.
Direct answers, including the ones that lose us work.
Three things dependably today: automate steps inside your ERP such as approval routing and transaction classification, read incoming documents like invoices and contracts into records, and answer questions from your own company data. Anything past that we would want to prove before selling it.
Then we say so. A large share of what companies bring us as an AI request is solved by a rule, a field or a fixed process step. We will show you that option and what it costs before we quote anything larger.
For the automation work usually yes, because it acts on records and needs a system of record to act on. Document extraction and an internal assistant can also be built against the files and applications you already have.
That is decided with you before anything is built, not after. Depending on the requirement we work with models running on infrastructure you approve, and we limit what leaves the system to what the task actually needs.
One well-defined process is normally a matter of weeks rather than months. The schedule is fixed after the diagnosis and written into the scope document, as it is on every project we run.
By scope, after the diagnosis. The first engagement is normally one narrow process, so you can judge the result on something small before committing to more.
Not in the work we do. It removes the retyping and the chasing. Judgment stays with your team, and consequential decisions keep a person in the loop by design.
Yes. BDC was founded in Saudi Arabia in 2016 and operates from Cairo, working with organisations across Egypt, the Gulf and Libya, with clear checkpoints and deliverables throughout.
Pick the step that repeats most in your week, and let us work out together whether AI is the right tool for it.
Book the free review