Skip to Content
ThinkDevs
  • Home
  • Services
  • Work
  • Approach
  • About
  • Journal
  • Careers
  • Contact
  • +92 00 0000000
  • Sign in
  • Talk to us
ThinkDevs
    • Home
    • Services
    • Work
    • Approach
    • About
    • Journal
    • Careers
    • Contact
  • +92 00 0000000
  • Sign in
  • Talk to us
Home / Work / Aviation & Charter ERP
Aviation ERP · Odoo 18

A sales pipeline reps can't skip steps in

Mandatory checklists gate every stage change, and an AI assistant drafts checklists and whole pipelines from a plain description.

Led by Haseeb · ~4,300 LOC
Odoo 18 LLM API

The problem a client brought us

“Sales reps skip steps in the pipeline when they're busy, and every new deal type means writing the same follow-up checklist from scratch again.”

Before and after

Where steps used to get skipped

  • A busy week
  • A new deal type
  • A stage change

What every stage change now passes

A checklist gate

What we found and built

Mandatory-completion checklists that gate every pipeline stage advance, backed by an AI assistant that generates stage checklists, activities, and full pipeline structures from a plain description — configurable to any OpenAI-compatible provider, with no credentials ever hardcoded.

Result

Reps stop skipping steps because the system won't let a deal advance without them — and setting up a new pipeline takes minutes, not a meeting.

Under the hood

  • The assistant runs only when a user asks for it — there is no background job calling a model.
  • Responses follow a strict JSON contract and map back onto Odoo activity types.
  • Endpoint, model and API key are set from the CRM settings.
  • A review workspace and dashboard sit over the checklist review activities.

Built with

Odoo 18 LLM API

The pattern behind it

Enforce the rule where it can't be walked around

A rule that only lives on a screen can be bypassed by an import, a script or a busy person. We put it in the model: constraints, gates on stage changes, access checks on every data path.

How we think about problems

Next case study

Aviation ERP · Odoo 18

Books that looked slightly wrong, repaired without SQL

Currency revaluation plus explicit tools that find and fix stale fields on posted journal lines.

Built by Yaseen Read the case study

Or go back to the full list and start from the symptom closest to yours.

All case studies

Recognise any of this?

Most of our work starts with a message that sounds a lot like this one did.

Tell us what's broken See the problems we've solved

ThinkDevs

A small, senior engineering team that builds and rescues production Odoo ERP systems.

Remote team · Pakistan / Saudi Arabia

Work

  • Problems we've solved
  • MAFA Group
  • Aviation & Charter ERP
  • Journal

Company

  • Approach
  • Services
  • About
  • Careers
  • Contact

Talk to us

  • info@thinkdevs.com
Tell us what's broken
© 2026 ThinkDevs. All rights reserved. Built on Odoo 18