Odoo for an architecture practice in Morocco
An architecture practice has no stock, no catalogue, no recurring orders. It has long-running projects, contracts split into phases, fees called as work progresses, and a volume of documents that carry professional liability.
It is one of the cases where Odoo looks least obvious at first — and serves best once adapted, because it replaces on its own a tracking spreadsheet, a contract folder and invoicing kept separately.
What a practice actually tracks
A project, in the architectural sense, does not have the shape of a standard Odoo project. It splits into mission phases, each with its own progress and its own fee call.
What has to be readable at any moment:
- Where each project stands — current phase, deadlines, next delivery
- What has been invoiced and what remains to call — per phase, not overall
- Which documents were produced and sent — with their versions
- What the project cost — time spent, subcontracting, travel
None of this is available in Odoo straight out of the box. All of it comes from assembling existing blocks and writing what is missing.
The modules we built
The Architecture module
The central object: the project, with its client, location, mission type, phases and progress. It ties everything else together.
Contracts
The mission contract sets the phases, attached fees and calling conditions. Linked to the project, it allows fee invoices to be generated at the right moment, on the right basis, without re-entry.
Receipts and office administration
The daily grind business tools always miss: receipts, running expenses, administrative follow-up. Gathered in Odoo rather than scattered between a binder and a spreadsheet.
Automated reports
The most recurring need in this profession: statements produced automatically — daily, weekly, monthly — on project progress, fees called and payments received.
What used to take half a day of compiling at month end becomes a report available at any time.
What Odoo provides without development
Part of the need is covered as standard, and rebuilding it would be absurd:
- Timesheets — time spent per project, the basis for profitability
- Invoicing and reminders — once phases are defined
- Purchasing and subcontracting — engineering firms, surveyors, specialists
- Document management — documents attached to the project
- Accounting — depending on the edition, see Community or Enterprise
Profitability per project
A practice can work a great deal and earn little, without knowing which projects consume the margin. Fees are known; time actually spent rarely is.
Attaching hours and expenses to each project allows a final comparison between what was planned and what was consumed. It is often the most useful discovery of the whole project — and it requires no development, only the discipline of logging hours.
Frequently asked questions
Does Odoo suit a practice of a few people? Yes, provided scope stays narrow: projects, contracts, fees, time. Deploying manufacturing or stock modules in a practice makes no sense and only weighs the tool down.
Can we invoice by progress phase? Yes. That is precisely what the mission contract allows once modelled: each phase carries its fee and triggers its invoice at the right time.
Can our project documents be managed in Odoo? Yes, attached to the project and its phase. For heavy design files, the common practice is to keep existing storage and reference the documents in Odoo rather than dumping everything into it.
Can several partners or teams be tracked? Yes, through project assignment and analytic accounting. Each partner or team can have its own view and statements.
How long does a deployment take for a practice? Less than in an industrial company: the scope is narrower. A few weeks for the foundation and projects, plus the time for specific modules. Detailed, free quote within 24 hours after scoping.
For the details of our offer, see our Odoo service. On what to avoid, read the mistakes that make ERP projects fail. Delivered projects are shown in the portfolio.