01 / Client
A furniture-making business with messy operations
The client is kept anonymous in published copy and described as a Kenyan furniture-making business.
The business was struggling with payment allocation and customer satisfaction. Operational mess was showing up in the customer experience, which is often where internal workflow problems become impossible to ignore.
02 / Problem
Payments, sales visibility, and inventory needed to connect
The implementation needed to cover Accounting, Sales/CRM, Inventory, and M-Pesa integration. That combination matters because payment allocation cannot be solved cleanly if sales records and inventory flow are disconnected.
For furniture and craft businesses, the real workflow often crosses quotations, deposits, follow-ups, production, delivery, and final payment. Odoo had to support that operating reality.
03 / SOW
The statement of work turned a vague implementation into a bounded one
The SOW clarified what was in scope, which modules mattered, how payment allocation would connect to the rest of the workflow, and what would not be treated as open-ended customization.
It also created a practical implementation boundary around Accounting, Sales/CRM, Inventory, and M-Pesa integration so the client had a delivery path instead of a vague software conversation.
04 / Outcome
A completed implementation with stronger operating clarity
The implementation was completed. The important win was not just installing Odoo; it was giving the business a clearer operating structure across customer flow, payment allocation, inventory, and reporting.
Pricing is intentionally kept private on the site because Odoo cost depends on scope, modules, integrations, data migration, and change-management needs.