M6iT — Targeted Odoo Customisations Scoped to the Real Operating Need

M6iT didn't need a full Odoo implementation. They needed two specific things — refinements to the sales workflow they already ran, and a weekly-email automation that runs on schedule and reports cleanly. The engagement is included here precisely because the discipline that mattered was not scope creep into modules that weren't needed.

The Operating Reality M6iT Needed Solved

• Sales-workflow gaps in the existing Odoo CRM. The standard Odoo sales workflow was 80% right for M6iT's motion, but the 20% gap was costing time on every deal. The fix was customisation, not replacement.
• Manual weekly reporting that ate hours. A weekly internal email needed to be assembled by hand each week — pulling data from Odoo, formatting it, sending it. Automating it was small in scope and high in compounding value.
• No appetite for a bigger engagement. M6iT didn't want a multi-module implementation. They wanted the two specific gaps closed with minimum surface area.

How Linescripts Built the Solution

Sales-workflow customisations aligned to the real motion

Targeted refinements to the standard Odoo CRM workflow — stage transitions, required fields at the right gates, automation triggers where they save time, manual control where the salesperson should stay in the driver's seat. The standard workflow stayed standard everywhere it was already working.

Scheduled weekly-email automation

A scheduled job that reads the relevant Odoo data each week, formats the weekly summary, and sends the email. Reliable, predictable, no manual assembly. The format is configurable so M6iT can refine what goes in the email without re-engineering the job.

Deployment and handoff documentation

Engagement closed with deployment, handoff, and the kind of documentation that lets M6iT maintain the customisations themselves without an open ongoing relationship if they prefer.

What Changed for M6iT

• The 20% sales-workflow gap closed. Time on every deal reduced, without forcing the team to relearn the system.
• The weekly report sends itself. Hours of manual assembly removed; consistency improved because the data source is the live system.
• Engagement stayed scoped. No module sprawl, no scope creep, no surprise Phase 2.

Closing

The engagement is small by design. Most ERP work that costs disproportionate effort relative to the value delivered is work that scoped wider than it needed to. M6iT's engagement is the counter-example: a tight scope, two specific deliverables, and a deliberate refusal to expand. Sometimes the discipline is in not selling a bigger project.