Scoped before configured
Most failed ERP rollouts were configured before anyone mapped the process. We produce the process flow diagram first and implement against it.
Odoo and ERP implementation
ERP scoped, configured, and migrated against a documented process map, with the customisations your operation needs and none that it does not.
Why this, and why now
What changes when it is done properly.
Module-to-requirement mapping
Every requirement is mapped to a specific module before build, so you know exactly what is standard configuration and what needs development.
Migration planned, not improvised
Data migration gets its own plan, import templates and reconciliation step. Your historical records arrive intact and verifiable.
Adoption is part of delivery
Structured UAT and user training are built into the engagement. An ERP nobody uses is a more expensive spreadsheet.
Customisation with a boundary
We customise where your process is genuinely differentiated and configure where it is not, which keeps you upgradeable.
What the service covers
Scoped, built and documented.
- Requirements and fit-gap analysisWhat the platform does natively, what needs configuration, and what needs development, documented before commitment.
- Module configurationSales, purchasing, inventory, accounting, manufacturing and HR configured to your mapped process.
- Data migrationExtraction, cleaning templates, staged import and reconciliation against your source system.
- Custom module developmentPurpose-built modules where standard functionality genuinely does not reach.
- Training and handoverRole-based training, admin manual, and a documented configuration baseline.
Technologies
What we work in
Chosen per engagement against your constraints, not a fixed stack we apply to every client.
Pricing
The price is here, before you talk to anyone.
The same four tiers apply across every service.
One clearly-bounded problem you need designed and started.
A process you have already outgrown and need rebuilt properly.
Multiple connected processes, or a migration off a system you no longer trust.
Multi-stakeholder programmes that need architecture agreed before budget is committed.
FAQ
Questions about working with us.
What does Sanghaya Labs do?
Sanghaya Labs is a Philippine software consultancy. We design and build custom software, implement Odoo and other ERP platforms, architect AWS cloud infrastructure, and integrate or migrate data between the systems a business already runs.
We already use Odoo or another ERP. Can you work with it?
Yes. We build custom modules, integrations and reports on top of the system you already run, so you keep your existing setup and data. If a rollout stalled partway, we can review where it stands and finish the parts that were left. Where you are not on an ERP yet, we implement Odoo or build a system around your process.
How much does an engagement cost?
Engagements start at ₱50,000 for Foundation, ₱100,000 for Framework, and ₱150,000 for Infrastructure. Enterprise engagements are quoted after a scoping workshop. Every tier states exactly how many consultation sessions and implementation hours it includes, so you can compare them directly.
Why do you publish your prices when most consultancies do not?
Because the most common reason a good engagement never starts is that the buyer cannot tell whether they can afford the conversation. Published tiers let you rule us in or out before you spend a meeting finding out.
What is a consultation session?
A consultation session runs up to 30 minutes and is attended by a Delivery Manager and, from the second meeting onward, a Solutions Architect. Sessions are working meetings, and each one produces a named artifact such as a requirements questionnaire, a module-to-requirement mapping, or a process flow diagram.
What does an implementation hour cover?
An implementation hour is costed to include development, quality assurance, and delivery management, so the number you see is the number of hours of real progress you receive rather than developer time with overheads billed separately.
How does an engagement start?
It begins with a discovery session covering your current state, target state, and pain points, which concludes with a mutual NDA. A fit-gap review follows to map your requirements against systems you already own. You then receive an engagement proposal before any implementation is scheduled.
Why are there so many meetings and so much documentation?
Because each meeting produces a document you keep, and those documents are what protect your budget. The requirements analysis defines what is in scope, the acceptance criteria define what finished means, and the risk register records what could change the estimate. Without them, scope disputes are settled by whoever has the better memory.
Book a walkthrough
See what your system could look like.
Thirty minutes, online. We will cover:
- How your process runs today, and where time is lost
- Example builds close to what you need
- Which tier fits, and what it would cost