A private day school in Toronto already running Odoo, held up by delays with their previous implementation partner. We stepped in, built a parent-facing online registration portal, and stayed on for the reporting and automation around it.
The school runs on Odoo, and family registration was being handled by the office.
They were also waiting on their previous implementation partner, so the work that would have fixed it was not moving. We were brought in to be responsive about it.
We built a parent-facing registration portal that plugs into the school's Odoo. Families register online, the record lands in the system, and staff spend less time on admin.
Around it we built the custom reporting and the workflow automation the school needed, and we maintain it as their requirements change.
A parent-facing portal is one of the cases that genuinely needs building. It lives outside the staff-facing system, it has to be safe for a non-technical person to use, and it has to write clean records into Odoo.
Inside Odoo it is usually custom reporting, workflow automation, portals your customers or staff log into, and integrations with systems Odoo does not talk to out of the box. Everything else we configure first.
We configure what Odoo already does before we write code. Configuration carries forward when you move to the next version. Custom code gets reviewed and often rewritten, so every module is a bill you pay again at every upgrade.
The school needed the system they already had to move. Stepping into someone else's Odoo and getting it going again is how two of our Odoo clients started.
Tell us how your business runs and we'll build the workflows costing you the most time in Odoo, on sample data shaped like your business, with a written guide for each one. Then we send you the login. Try it before you commit to anything.