Odoo Multi-Company Operations Platform Buildout

We are seeking an experienced Odoo developer or Odoo implementation team to configure and build out a multi-company Odoo platform for a growing group of related companies and programs. This project is an advanced Odoo setup, but not to the capacity of needing to develop outside of their modules. We need a developer who can help us design, configure, customize, automate, and document a scalable Odoo environment that will support operations, financial tracking, project management, time tracking, vendor management, document management, dashboards, and eventually a specialized Pre-Employment Transition Services management engine. We currently need Odoo to replace and improve several operational systems, including project management, time tracking, rate-based billing summaries, vendor purchasing, document management, reporting, and program service tracking. The platform must be structured so that each company can operate separately while leadership can still view consolidated financial and operational reporting across the full organization. The developer must configure a stable enterprise data model using shared objects across companies, including: * Contacts * Clients * Students * Vendors * Partners * Employers * Parents / Guardians * Projects * Tasks * Timesheets * Employees * Contracts * Documents The following Odoo modules must be installed, configured, and integrated into a unified relational structure: * Contacts * Project * Timesheets * Employees * Documents * CRM * Accounting * Website * Sales * Dashboards * Inventory * Barcode * Surveys * Sign * Studio * Expenses * Purchase * Approvals * Activities * Budget Management, if available or recommended through the appropriate Odoo-compatible method Multi-Company Financial Requirements The system must support multiple companies operating independently while allowing consolidated leadership reporting. The developer must configure: * Multi-company structure * Company hierarchy * Standardized chart of accounts * General ledger configuration * Budget tracking * Cost centers * Vendor payments * Vendor invoices * Purchase orders * Revenue tracking * Financial consolidation reporting * Role-based access to financial data Revenue may come from client services, program funding, grants, workforce contracts, or other funding sources. Cost centers may include programs, departments, schools, companies, or client projects. Core Workflow Automation Requirements The platform must include reusable workflow automation that can be used across all companies. The developer must configure automation using Odoo Studio, Odoo Automation, Approvals, Activities, or other appropriate Odoo-native tools whenever possible. The next major scope is a PerXuade operations platform to replace and improve Workamajig-style functionality. This portion must support: * Client project management * Project hierarchy * Task management * Staff assignments * Vendor assignments * Deliverable tracking * Project budgets * Rate sheets * Role-based billing calculations * Timesheet-based billing summaries * Internal vs. billable hours * Vendor expense allocation * Project profitability reporting * Revenue projections * Financial dashboards Each project must be able to show: * Revenue * Labor cost * Vendor cost * Profit * Profit margin * Billable hours * Non-billable hours * Outstanding invoices * Paid invoices * Revenue by client * Revenue by project * Revenue by company Rate Sheet and Billing Summary Requirements PerXuade bills clients using role-based hourly rates. Example roles and rates may include: * Project Manager — $50/hour * Designer — $125/hour * Developer — $150/hour The system must support: * Multiple rate sheets * Client-specific pricing * Role-based billing * Project-specific rate assignments * Automatic billing summary calculations from approved timesheets Example billing summary: Client: ABC Organization Project Manager: 1.5 hours @ $50/hour = $75 Designer: 3 hours @ $125/hour = $375 Total billable amount = $450 The system does not necessarily need to send invoices in the first version, but it must calculate billing summaries accurately and support future invoicing. Pre-ETS Service Engine After the core platform and operations platform are built, we need a reusable Pre-Employment Transition Services management engine inside Odoo. Student Intake Workflow The developer must build or configure an intake workflow that allows students to be registered through program coordinators, application forms, or bulk import. The intake workflow should follow this general process: Application Submitted → Intake Review → Counselor Approval Pending → Approved → Case Created Documents must be stored in Odoo Documents and linked to the student record. Authorization Management Requirements The system must track service authorizations issued by vocational rehabilitation counselors. The system must automatically alert staff when: * Authorization hours reach 80% usage * Authorization expires within 30 days * Authorization has expired The system must prevent or flag service sessions that exceed remaining authorized hours. Instructor Service Logging Requirements Instructors must be able to log service delivery sessions. Delivery methods should include: * In person * Virtual * Hybrid The system must generate progress reports for each student. Reports should include: * Student name * Instructor * Services delivered * Hours delivered * Attendance * Skill performance * Attendance tracking * Punctuality * Task completion * Teamwork * Communication * Responsiveness to feedback Reports must support PDF export and, if feasible, e-signature capture. Dashboards Required The developer must configure dashboards for leadership, administrators, coordinators, and program staff. Dashboards should include: * Active students * Services delivered * Remaining authorized hours * Instructor activity * Missing reports * Program utilization * Projects in progress * Billable hours * Revenue projections * Profitability * Vendor costs * Revenue by client * Revenue by company * Outstanding invoices * Paid invoices Dashboards must be filterable by: * Company * Program * School * Instructor * Service type * Client * Project Security and User Roles The developer must configure role-based permissions. Initial roles may include: * System Administrator * Leadership / Executive * Finance * Project Manager * Program Administrator * Coordinator * Instructor * Employee / Staff * Vendor, if portal access is needed * Student / Parent, if portal access is needed The system must ensure users only see the companies, projects, students, financial records, or program data they are authorized to access. Expected Deliverables The selected developer must deliver: 1. Fully configured Odoo environment 2. Installed and integrated Odoo modules 3. Multi-company structure 4. Shared contact and vendor system 5. Unified chart of accounts 6. General ledger configuration 7. Budget and cost center structure 8. Project management configuration 9. Timesheet configuration 10. Rate sheet and billing summary system 11. Vendor expense tracking 12. Document storage linked to records 13. Workflow automation framework 14. Approval workflows 15. Role-based security configuration 16. Dashboards and reports 17. Pre-ETS student intake workflow 18. Authorization tracking system 19. Instructor service logging interface 20. Progress report generation 21. PDF export functionality where applicable 22. Basic user documentation 23. Admin handoff/training session 24. Testing and bug-fix period before final acceptance Acceptance Criteria Project will be considered complete when: * Multiple companies can be created and managed in Odoo * Shared contacts and vendors are accessible across companies where appropriate * Operational data can remain separated by company * Financial reporting can consolidate across companies * Financial transactions post correctly to the general ledger * Documents are stored and linked to the correct records * Employees can log time to projects * Approval workflows operate correctly * Automated activities and reminders work correctly * Role-based permissions function properly * Client projects can be created and managed * Staff can log time to projects and tasks * Rate sheets calculate billing summaries correctly * Billable and non-billable hours are tracked * Vendor expenses can be assigned to projects * Project profitability can be viewed * Leadership dashboards display project and revenue data * Students can be enrolled through the intake workflow * Authorizations can be recorded and tracked * Remaining authorized hours calculate automatically * Instructors can log service sessions * Sessions reduce available authorized hours * Progress reports can be submitted, reviewed, approved, exported, and stored * Dashboards display accurate program metrics * Role-based access works for administrators, coordinators, and instructors Developer Qualifications Required. Please only apply if you have direct experience with: * Odoo implementation * Odoo multi-company configuration * Odoo Accounting * Odoo Project and Timesheets * Odoo Studio or custom Odoo module development * Workflow automation * Role-based permissions * Dashboards and reporting * Data model planning * Document management * Python / XML / QWeb, if customization is required * [login to view URL], self-hosted Odoo, or Odoo Online, depending on recommended deployment Experience with service-based businesses, agencies, workforce programs, grant-funded programs, education programs, or compliance-heavy reporting is strongly preferred. In your proposal, please include: Your recommended Odoo deployment approach Whether you recommend Odoo Online, [login to view URL], or self-hosted Odoo Which requirements can be handled through native Odoo configuration Which requirements require Studio customization Examples of similar Odoo projects completed Any risks, assumptions, or dependencies you see in this scope

Project ID: 40510159