Construction & infrastructure · Odoo CRM
Ethereum Infracon: from first enquiry to booking, no lead slips through the cracks
Published · Updated
Ethereum Infracon delivers residential, commercial and industrial projects across India. Its leads lived in spreadsheets, scattered across channels, chased from memory. KoderXpert built a CRM around how construction sales cycles actually move, from enquiry to booking.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Ethereum Infracon
- Industry
- Construction & infrastructure, India
- Platform
- Odoo CRM, customised
- Implementation partner
- KoderXpert Technologies
- Headline result
- Lead-to-booking cycles on one pipeline
01 · Overview
The 30-second version
- Ethereum Infracon is a rapidly growing construction and infrastructure company delivering residential, commercial and industrial projects across India.
- Sales ran on manual lead sheets: enquiries scattered across channels, no shared system, no pipeline visibility, slow follow-ups and no forecasting.
- KoderXpert delivered a customized Odoo CRM: every channel synced into one system, pipelines shaped around each project type, automated reminders, a 360° customer view, website integration and executive dashboards.
02 · Leads slipping through the cracks
What was going wrong before Odoo?
Six ways the sales site had no foundations
Construction sales cycles are long, high-value and multi-stakeholder. Running them on spreadsheets and memory meant every crack below cost real bookings.
Manual lead sheets
Spreadsheet-based lead management with no shared system across the sales team.
The cost → every rep an islandScattered channels
Leads arrived from multiple channels with no centralized tracking or single starting point.
The cost → enquiries lost between inboxesNo pipeline visibility
Limited project-wise visibility into where each opportunity actually stood.
The cost → status by asking aroundMissed follow-ups
Slow, inconsistent follow-ups on active leads, each one dependent on someone remembering.
The cost → hot leads going coldNo forecasting
No analytics for conversions or demand forecasting to plan projects and capacity against.
The cost → building blindDisconnected teams
Sales, marketing and project teams coordinating by forwarding emails and repeating context.
The cost → handoffs that drop the thread03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the lead-sheet era, right is the construction-focused CRM.
- ✗ Leads managed on spreadsheets, per person
- ✗ Channels feeding separate inboxes
- ✗ Pipeline status known only by asking around
- ✗ Follow-ups dependent on memory
- ✗ No conversion or demand analytics
the lead-sheet era 😵
one connected pipeline ✨
- ✔ Every enquiry channel synced into one CRM
- ✔ Pipelines shaped per project type
- ✔ Every opportunity's stage visible at a glance
- ✔ Reminders triggered automatically
- ✔ Dashboards for conversions & forecasting
← drag toward the sheets · drag toward the system →
04 · The plan
What "fixed" had to actually mean
Six objectives agreed with Ethereum Infracon before configuration began. Hover any goal to tick it off.
Centralize records: all leads, opportunities and customer records in one place.
Automate follow-ups: reminders and task assignments handled automatically.
Track the journey: customer journeys from enquiry to booking.
Improve coordination: across sales, marketing and project teams.
Executive dashboards: business reports for leadership visibility.
Data-driven forecasting: enable sales and demand forecasting from real pipeline data.
05 · What we delivered
What did KoderXpert build?
Six capabilities, one connected CRM
A CRM built around construction sales cycles, from first enquiry through to booking, delivered on customized Odoo.
Multi-channel lead capture
Website and every other enquiry channel synced into a single, unified CRM: no more leads lost between spreadsheets and inboxes, and a consistent starting point for every sales conversation.
zero leads lost at the doorProject-specific pipelines
Stages built around residential, commercial and industrial projects, so the pipeline structure matches the real sales process and every opportunity's position is clear.
pipelines that match realityAutomated follow-ups & reminders
Reminders triggered automatically at the right moments, giving faster, more consistent engagement and fewer leads going cold from missed follow-up.
a cadence that never forgetsCustomer 360° view
Full communication and document history in one place: every interaction visible in a single customer record, enabling faster handoffs between sales, marketing and project teams.
context that travels with the dealWebsite integration
Website enquiries flow straight into the CRM with source tracking, closing the gap between marketing and sales.
the site feeds the pipelineExecutive dashboards
Conversion, pipeline and demand analytics for leadership, turning gut feel into data-driven sales and capacity forecasting.
forecasts built on real data06 · Functional deep dive
How the construction CRM actually works
The delivery summary says what was built. This is the functional detail underneath: how enquiries route, how each project type's pipeline behaves, and where the forecasts come from.
Capture & routing across channels
Every enquiry (website, phone, referral, walk-in, campaign) lands as one CRM lead with its origin stamped.
- Website integration: site forms create leads directly with source tracking, closing the marketing-to-sales gap.
- Deduplication: enquiries match against existing customers and past opportunities, so history follows the person.
- Routing rules: project type and location assign the right owner automatically, ending shared-inbox limbo.
Pipelines shaped per project type
Residential, commercial and industrial deals move at different speeds with different stakeholders, and their pipelines reflect it.
- Residential stages: enquiry, site visit, negotiation, booking, tuned for volume and speed.
- Commercial & industrial stages: requirement study, proposal, multi-stakeholder negotiation, agreement, tuned for long, high-value cycles.
- Stage discipline: each stage carries required fields and next activities, so a deal cannot drift forward half-documented.
The customer 360 in practice
One record holds every conversation, document and site detail, so handoffs carry context instead of forwarded emails.
- Full history: calls, emails, meetings and notes log to the opportunity timeline.
- Documents attached: plans, quotations and agreements live on the record, versioned, not in personal drives.
- Team handoffs: sales-to-projects transitions keep the entire trail, so the delivery team starts informed.
Forecasting from real pipeline data
Leadership planning moved from gut feel to numbers the pipeline itself produces.
- Conversion analytics: win rates by channel, project type and stage show exactly where deals leak.
- Demand forecasting: weighted pipeline value by expected close month feeds capacity and project planning.
- Follow-up hygiene: idle-opportunity alerts keep the pipeline honest, so the forecast stays believable.
Pipelines shaped per project type
Residential deals run short, high-volume stages; commercial and industrial run long, multi-stakeholder ones. Each stage carries required fields and next activities, so a deal physically cannot drift forward half-documented or unowned.
07 · How we built it
How was the Odoo project delivered?
From site survey to structure
Six stages: understanding how construction deals actually move, then building the CRM around them.
Discovery & sales mapping survey the ground
KoderXpert mapped how residential, commercial and industrial deals really progress, from enquiry to booking.
Pipeline architecture pour the foundations
Project-specific stages, fields and automation rules designed around each sales motion.
CRM configuration raise the frame
Odoo CRM configured and customized: capture, activities, 360° records and team workflows.
Website & channel integration connect the services
Website and enquiry channels wired directly into the pipeline with source tracking.
Dashboards & forecasting install the controls
Executive reporting for conversions, pipeline health and demand forecasting.
Training, go-live & support hand over the keys
Sales, marketing and project teams onboarded, with support through the first cycles.
08 · Engineering notes
The technical decisions behind the pipeline
For the technically curious: how the work was engineered so it survives upgrades, audits and time.
Custom addons, zero core edits
Everything KoderXpert built lives in namespaced custom modules (kx_lead_capture · kx_project_pipelines · kx_followups · kx_forecast) on Python and the Odoo ORM.
- Inheritance, not modification: models and views are extended through Odoo's inheritance mechanisms, never edited in core, so future Odoo upgrades do not bury the work.
- Configuration as data: pipelines, stages, required-field rules, routing logic and activity plans ship as XML data records, reproducible and reviewable.
- PostgreSQL underneath: one database as the single source of truth, so no exports or reconciliation jobs exist between the moving parts.
The data migration pipeline
The riskiest part of the project was the data: lead sheets and enquiry registers maintained per salesperson. It moved through a staged pipeline, not a bulk import.
- Extract & cleanse: legacy records exported, deduplicated and normalized in a staging environment before anything touched production.
- Ordered loading: imports run in dependency order: customers, then historical opportunities mapped to the new stages with owners assigned, via the ORM so routing and validation rules apply.
- Verified before sign-off: record counts and key balances checked against the source system, with every opening figure posted as an auditable entry.
Reports, automation & performance
Dashboards and documents are native Odoo artifacts reading live data, so they inherit access rules and never go stale.
- QWeb & OWL: printable documents render through QWeb templates; on-screen dashboards read aggregated, indexed queries that stay fast as volume grows.
- Scheduled automation: scheduled jobs flag idle opportunities, refresh conversion dashboards and recompute the weighted forecast nightly.
- Filters built in: period, location and team filters are part of the report definitions, so answering a leadership question is one click, not a new spreadsheet.
Testing, cutover & hardening
The rollout landed on a live business, so it was engineered to be boring.
- Staging mirror: every change proven on a copy of the real database before reaching production.
- Role-based UAT: sales, marketing and project teams walked scripted enquiry-to-booking journeys per project type, including handoff to delivery, before go-live.
- Access hardening: group permissions and record rules reviewed role by role, so each team sees exactly what its job requires.
- Documented handover: configuration, roles and workflows documented so the system's logic belongs to the client, not to anyone's memory.
A forecast the pipeline produces
Win rates by channel and project type combine with weighted pipeline value by expected close month, giving leadership a demand forecast generated from real deals rather than gut feel, and kept honest by idle-deal alerts.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- Every lead, opportunity and customer record in one place
- Follow-ups running on automation instead of memory
- Clear pipeline visibility for every project type
- Faster handoffs between sales, marketing and project teams
- Leadership dashboards for conversions and forecasting
- A sales foundation that scales with new projects and regions
10 · Under the hood
Technologies & core skills
"A CRM built around construction sales cycles, from first enquiry through to booking: every channel feeding one system, reminders that trigger themselves, and leadership visibility that finally supports data-driven forecasting."
11 · Quick questions, honest answers
Thinking about a similar build?
Because sales cycles differ per project type: residential deals are high-volume and fast, while commercial and industrial deals are long and multi-stakeholder. Ethereum Infracon's pipelines were built stage-by-stage around each motion instead of one generic funnel.
Website forms, phone enquiries, referrals and campaigns all create leads in one system with source stamped, deduplicated against existing history, and routed to the right owner by project type and location.
A single record holding every call, email, document and site detail for the customer, so sales, marketing and project teams hand off with full context instead of forwarded emails and repeated questions.
Each stage schedules its next activities automatically with owners and deadlines, and opportunities that sit untouched surface to managers before they go cold, so no lead depends on someone remembering.
Yes. Weighted pipeline value by expected close month, combined with win rates by project type and channel, gives leadership a forecast produced by the pipeline itself, usable for capacity and project planning.
Website enquiries flow straight into the pipeline with source tracking, so campaign performance is measured in booked deals, not just clicks, and marketing sees exactly which channels convert.
Stage discipline: each stage carries required fields and mandatory next activities, so an opportunity cannot advance without the information the next team needs.
Yes. Any business selling projects with distinct types and long cycles benefits from the same pattern: unified capture, per-type pipelines, enforced follow-ups and pipeline-driven forecasting.
Yes, by design. All of KoderXpert's work for Ethereum Infracon lives in namespaced custom addons that extend Odoo through inheritance; the core is never edited, and configuration ships as data records, making the setup reproducible and upgrade-safe.
It is the riskiest part, which is why it runs as a staged pipeline: extract and cleanse in a staging environment, load in dependency order through the Odoo ORM so business rules still apply, then verify counts and balances against the source before sign-off.
It depends on scope, which is why delivery ran in structured phases from discovery to supported go-live. Mapping the real process first fixes the scope before any build starts, and phased rollout keeps the business running throughout.
KoderXpert is an Odoo partner that maps the real process before building, engineers upgrade-safe custom modules with zero core edits, and delivers measurable outcomes: for Ethereum Infracon, every enquiry channel feeding tailored pipelines with automated follow-ups and forecast dashboards. Talk to KoderXpert about your project.
Building a sales pipeline for construction?
Tell us how your enquiries arrive and how your deals move, residential, commercial or industrial. KoderXpert will show you a CRM shaped around your real sales cycles.
Related case studies
- Pathfinder Global: Odoo CRM and accounting implementationOne pipeline for 150+ malls and 1,600+ brands
- Kamakhya Pipes: Odoo manufacturing ERP implementationShop-floor hardware wired into production and stock
- Unicorn Petro: Odoo ERP and export documentationMarketplace leads and export documents automated
Construction & infrastructure · Odoo CRM
Ethereum Infracon: from first enquiry to booking, no lead slips through the cracks
Published · Updated
Ethereum Infracon delivers residential, commercial and industrial projects across India. Its leads lived in spreadsheets, scattered across channels, chased from memory. KoderXpert built a CRM around how construction sales cycles actually move, from enquiry to booking.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Ethereum Infracon
- Industry
- Construction & infrastructure, India
- Platform
- Odoo CRM, customised
- Implementation partner
- KoderXpert Technologies
- Headline result
- Lead-to-booking cycles on one pipeline
01 · Overview
The 30-second version
- Ethereum Infracon is a rapidly growing construction and infrastructure company delivering residential, commercial and industrial projects across India.
- Sales ran on manual lead sheets: enquiries scattered across channels, no shared system, no pipeline visibility, slow follow-ups and no forecasting.
- KoderXpert delivered a customized Odoo CRM: every channel synced into one system, pipelines shaped around each project type, automated reminders, a 360° customer view, website integration and executive dashboards.
02 · Leads slipping through the cracks
What was going wrong before Odoo?
Six ways the sales site had no foundations
Construction sales cycles are long, high-value and multi-stakeholder. Running them on spreadsheets and memory meant every crack below cost real bookings.
Manual lead sheets
Spreadsheet-based lead management with no shared system across the sales team.
The cost → every rep an islandScattered channels
Leads arrived from multiple channels with no centralized tracking or single starting point.
The cost → enquiries lost between inboxesNo pipeline visibility
Limited project-wise visibility into where each opportunity actually stood.
The cost → status by asking aroundMissed follow-ups
Slow, inconsistent follow-ups on active leads, each one dependent on someone remembering.
The cost → hot leads going coldNo forecasting
No analytics for conversions or demand forecasting to plan projects and capacity against.
The cost → building blindDisconnected teams
Sales, marketing and project teams coordinating by forwarding emails and repeating context.
The cost → handoffs that drop the thread03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the lead-sheet era, right is the construction-focused CRM.
- ✗ Leads managed on spreadsheets, per person
- ✗ Channels feeding separate inboxes
- ✗ Pipeline status known only by asking around
- ✗ Follow-ups dependent on memory
- ✗ No conversion or demand analytics
the lead-sheet era 😵
one connected pipeline ✨
- ✔ Every enquiry channel synced into one CRM
- ✔ Pipelines shaped per project type
- ✔ Every opportunity's stage visible at a glance
- ✔ Reminders triggered automatically
- ✔ Dashboards for conversions & forecasting
← drag toward the sheets · drag toward the system →
04 · The plan
What "fixed" had to actually mean
Six objectives agreed with Ethereum Infracon before configuration began. Hover any goal to tick it off.
Centralize records: all leads, opportunities and customer records in one place.
Automate follow-ups: reminders and task assignments handled automatically.
Track the journey: customer journeys from enquiry to booking.
Improve coordination: across sales, marketing and project teams.
Executive dashboards: business reports for leadership visibility.
Data-driven forecasting: enable sales and demand forecasting from real pipeline data.
05 · What we delivered
What did KoderXpert build?
Six capabilities, one connected CRM
A CRM built around construction sales cycles, from first enquiry through to booking, delivered on customized Odoo.
Multi-channel lead capture
Website and every other enquiry channel synced into a single, unified CRM: no more leads lost between spreadsheets and inboxes, and a consistent starting point for every sales conversation.
zero leads lost at the doorProject-specific pipelines
Stages built around residential, commercial and industrial projects, so the pipeline structure matches the real sales process and every opportunity's position is clear.
pipelines that match realityAutomated follow-ups & reminders
Reminders triggered automatically at the right moments, giving faster, more consistent engagement and fewer leads going cold from missed follow-up.
a cadence that never forgetsCustomer 360° view
Full communication and document history in one place: every interaction visible in a single customer record, enabling faster handoffs between sales, marketing and project teams.
context that travels with the dealWebsite integration
Website enquiries flow straight into the CRM with source tracking, closing the gap between marketing and sales.
the site feeds the pipelineExecutive dashboards
Conversion, pipeline and demand analytics for leadership, turning gut feel into data-driven sales and capacity forecasting.
forecasts built on real data06 · Functional deep dive
How the construction CRM actually works
The delivery summary says what was built. This is the functional detail underneath: how enquiries route, how each project type's pipeline behaves, and where the forecasts come from.
Capture & routing across channels
Every enquiry (website, phone, referral, walk-in, campaign) lands as one CRM lead with its origin stamped.
- Website integration: site forms create leads directly with source tracking, closing the marketing-to-sales gap.
- Deduplication: enquiries match against existing customers and past opportunities, so history follows the person.
- Routing rules: project type and location assign the right owner automatically, ending shared-inbox limbo.
Pipelines shaped per project type
Residential, commercial and industrial deals move at different speeds with different stakeholders, and their pipelines reflect it.
- Residential stages: enquiry, site visit, negotiation, booking, tuned for volume and speed.
- Commercial & industrial stages: requirement study, proposal, multi-stakeholder negotiation, agreement, tuned for long, high-value cycles.
- Stage discipline: each stage carries required fields and next activities, so a deal cannot drift forward half-documented.
The customer 360 in practice
One record holds every conversation, document and site detail, so handoffs carry context instead of forwarded emails.
- Full history: calls, emails, meetings and notes log to the opportunity timeline.
- Documents attached: plans, quotations and agreements live on the record, versioned, not in personal drives.
- Team handoffs: sales-to-projects transitions keep the entire trail, so the delivery team starts informed.
Forecasting from real pipeline data
Leadership planning moved from gut feel to numbers the pipeline itself produces.
- Conversion analytics: win rates by channel, project type and stage show exactly where deals leak.
- Demand forecasting: weighted pipeline value by expected close month feeds capacity and project planning.
- Follow-up hygiene: idle-opportunity alerts keep the pipeline honest, so the forecast stays believable.
Pipelines shaped per project type
Residential deals run short, high-volume stages; commercial and industrial run long, multi-stakeholder ones. Each stage carries required fields and next activities, so a deal physically cannot drift forward half-documented or unowned.
07 · How we built it
How was the Odoo project delivered?
From site survey to structure
Six stages: understanding how construction deals actually move, then building the CRM around them.
Discovery & sales mapping survey the ground
KoderXpert mapped how residential, commercial and industrial deals really progress, from enquiry to booking.
Pipeline architecture pour the foundations
Project-specific stages, fields and automation rules designed around each sales motion.
CRM configuration raise the frame
Odoo CRM configured and customized: capture, activities, 360° records and team workflows.
Website & channel integration connect the services
Website and enquiry channels wired directly into the pipeline with source tracking.
Dashboards & forecasting install the controls
Executive reporting for conversions, pipeline health and demand forecasting.
Training, go-live & support hand over the keys
Sales, marketing and project teams onboarded, with support through the first cycles.
08 · Engineering notes
The technical decisions behind the pipeline
For the technically curious: how the work was engineered so it survives upgrades, audits and time.
Custom addons, zero core edits
Everything KoderXpert built lives in namespaced custom modules (kx_lead_capture · kx_project_pipelines · kx_followups · kx_forecast) on Python and the Odoo ORM.
- Inheritance, not modification: models and views are extended through Odoo's inheritance mechanisms, never edited in core, so future Odoo upgrades do not bury the work.
- Configuration as data: pipelines, stages, required-field rules, routing logic and activity plans ship as XML data records, reproducible and reviewable.
- PostgreSQL underneath: one database as the single source of truth, so no exports or reconciliation jobs exist between the moving parts.
The data migration pipeline
The riskiest part of the project was the data: lead sheets and enquiry registers maintained per salesperson. It moved through a staged pipeline, not a bulk import.
- Extract & cleanse: legacy records exported, deduplicated and normalized in a staging environment before anything touched production.
- Ordered loading: imports run in dependency order: customers, then historical opportunities mapped to the new stages with owners assigned, via the ORM so routing and validation rules apply.
- Verified before sign-off: record counts and key balances checked against the source system, with every opening figure posted as an auditable entry.
Reports, automation & performance
Dashboards and documents are native Odoo artifacts reading live data, so they inherit access rules and never go stale.
- QWeb & OWL: printable documents render through QWeb templates; on-screen dashboards read aggregated, indexed queries that stay fast as volume grows.
- Scheduled automation: scheduled jobs flag idle opportunities, refresh conversion dashboards and recompute the weighted forecast nightly.
- Filters built in: period, location and team filters are part of the report definitions, so answering a leadership question is one click, not a new spreadsheet.
Testing, cutover & hardening
The rollout landed on a live business, so it was engineered to be boring.
- Staging mirror: every change proven on a copy of the real database before reaching production.
- Role-based UAT: sales, marketing and project teams walked scripted enquiry-to-booking journeys per project type, including handoff to delivery, before go-live.
- Access hardening: group permissions and record rules reviewed role by role, so each team sees exactly what its job requires.
- Documented handover: configuration, roles and workflows documented so the system's logic belongs to the client, not to anyone's memory.
A forecast the pipeline produces
Win rates by channel and project type combine with weighted pipeline value by expected close month, giving leadership a demand forecast generated from real deals rather than gut feel, and kept honest by idle-deal alerts.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- Every lead, opportunity and customer record in one place
- Follow-ups running on automation instead of memory
- Clear pipeline visibility for every project type
- Faster handoffs between sales, marketing and project teams
- Leadership dashboards for conversions and forecasting
- A sales foundation that scales with new projects and regions
10 · Under the hood
Technologies & core skills
"A CRM built around construction sales cycles, from first enquiry through to booking: every channel feeding one system, reminders that trigger themselves, and leadership visibility that finally supports data-driven forecasting."
11 · Quick questions, honest answers
Thinking about a similar build?
Because sales cycles differ per project type: residential deals are high-volume and fast, while commercial and industrial deals are long and multi-stakeholder. Ethereum Infracon's pipelines were built stage-by-stage around each motion instead of one generic funnel.
Website forms, phone enquiries, referrals and campaigns all create leads in one system with source stamped, deduplicated against existing history, and routed to the right owner by project type and location.
A single record holding every call, email, document and site detail for the customer, so sales, marketing and project teams hand off with full context instead of forwarded emails and repeated questions.
Each stage schedules its next activities automatically with owners and deadlines, and opportunities that sit untouched surface to managers before they go cold, so no lead depends on someone remembering.
Yes. Weighted pipeline value by expected close month, combined with win rates by project type and channel, gives leadership a forecast produced by the pipeline itself, usable for capacity and project planning.
Website enquiries flow straight into the pipeline with source tracking, so campaign performance is measured in booked deals, not just clicks, and marketing sees exactly which channels convert.
Stage discipline: each stage carries required fields and mandatory next activities, so an opportunity cannot advance without the information the next team needs.
Yes. Any business selling projects with distinct types and long cycles benefits from the same pattern: unified capture, per-type pipelines, enforced follow-ups and pipeline-driven forecasting.
Yes, by design. All of KoderXpert's work for Ethereum Infracon lives in namespaced custom addons that extend Odoo through inheritance; the core is never edited, and configuration ships as data records, making the setup reproducible and upgrade-safe.
It is the riskiest part, which is why it runs as a staged pipeline: extract and cleanse in a staging environment, load in dependency order through the Odoo ORM so business rules still apply, then verify counts and balances against the source before sign-off.
It depends on scope, which is why delivery ran in structured phases from discovery to supported go-live. Mapping the real process first fixes the scope before any build starts, and phased rollout keeps the business running throughout.
KoderXpert is an Odoo partner that maps the real process before building, engineers upgrade-safe custom modules with zero core edits, and delivers measurable outcomes: for Ethereum Infracon, every enquiry channel feeding tailored pipelines with automated follow-ups and forecast dashboards. Talk to KoderXpert about your project.
Building a sales pipeline for construction?
Tell us how your enquiries arrive and how your deals move, residential, commercial or industrial. KoderXpert will show you a CRM shaped around your real sales cycles.
Related case studies
- Pathfinder Global: Odoo CRM and accounting implementationOne pipeline for 150+ malls and 1,600+ brands
- Kamakhya Pipes: Odoo manufacturing ERP implementationShop-floor hardware wired into production and stock
- Unicorn Petro: Odoo ERP and export documentationMarketplace leads and export documents automated
