Odoo Sales Crm Expert

Odoo Sales & CRM Expert

Overview

This skill helps you configure and optimize Odoo Sales and CRM. It covers opportunity pipeline setup, automated lead assignment, quotation templates, pricelist strategies, sales team management, and the sales-to-invoice workflow.

When to Use This Skill

• Designing CRM pipeline stages for your sales process.
• Creating a quotation template with optional products and bundles.
• Setting up pricelists with customer-tier pricing.
• Configuring automated lead assignment by territory or salesperson.

How It Works

1. Activate: Mention @odoo-sales-crm-expert and describe your sales scenario.
2. Configure: Receive step-by-step Odoo setup instructions.
3. Optimize: Get recommendations for improving pipeline velocity and deal closure rate.

Examples

Example 1: Configure CRM Pipeline Stages

Menu: CRM → Configuration → Stages → New

Typical B2B Pipeline:
  Stage 1: New Lead          (probability: 10%)
  Stage 2: Qualified         (probability: 25%)
  Stage 3: Proposal Sent     (probability: 50%)
  Stage 4: Negotiation       (probability: 75%)
  Stage 5: Won               (is_won: YES — marks opportunity as closed-won)
  Stage 6: Lost              (mark as lost via the "Mark as Lost" button)

Tips:
  - Enable "Rotting Days" in CRM Settings to flag stale deals in red
  - In Odoo 16+, Predictive Lead Scoring (AI) auto-updates probability
    based on historical data. Disable it in Settings if you prefer manual
    stage-based probability.

Example 2: Create a Quotation Template

Menu: Sales → Configuration → Quotation Templates → New
(Requires the "Sales Management" module — enabled in Sales Settings)

Template Name: SaaS Annual Subscription
Valid for: 30 days

Lines:
  1. Platform License   | Qty: 1 | Price: $1,200/yr | (required)
  2. Onboarding Package | Qty: 1 | Price: $500       | Optional
  3. Premium Support    | Qty: 1 | Price: $300/yr    | Optional
  4. Extra User License | Qty: 0 | Price: $120/user  | Optional

Signature & Payment:
  ☑ Online Signature required before order confirmation
  ☑ Online Payment (deposit) — 50% upfront

Notes section:
  "Prices valid until expiration date. Subject to Schedule A terms."

Example 3: Customer Tier Pricelist (VIP Discount)

Menu: Sales → Configuration → Settings
  ☑ Enable Pricelists

Menu: Sales → Configuration → Pricelists → New

Name: VIP Customer — 15% Off
Currency: USD
Discount Policy: Show public price & discount on quotation

Rules:
  Apply To: All Products
  Compute Price: Discount
  Discount: 15%
  Min. Quantity: 1

Assign to a customer:
  Customer record → Sales & Purchase tab → Pricelist → VIP Customer

Best Practices

• ✅ Do: Use Lost Reasons (CRM → Configuration → Lost Reasons) to build a dataset of why deals are lost — invaluable for sales coaching.
• ✅ Do: Enable Sales Teams with revenue targets so pipeline forecasting is meaningful per team.
• ✅ Do: Set Expected Revenue and Closing Date on every opportunity — these feed the revenue forecast dashboard.
• ✅ Do: Use Quotation Templates to standardize offers and reduce quoting time across the team.
• ❌ Don't: Skip the CRM opportunity when selling — going directly from lead to invoice breaks pipeline analytics.
• ❌ Don't: Manually edit prices on quotation lines as a workaround — set up proper pricelists instead.
• ❌ Don't: Ignore the Predictive Lead Scoring feature in v16+ — configure it with historical data for accurate forecasting.

Limitations

• Commission rules are not built into Odoo CRM out of the box — they require custom development or third-party modules.
• The Quotation Template optional product feature requires the Sale Management module; it is not available in the base sale module.
• Territory-based lead assignment (geographic routing) requires custom rules or the Enterprise Leads module.
• Odoo CRM does not have native email sequence / cadence automation — use the Email Marketing or Marketing Automation modules for drip campaigns.

AGI Framework Integration

Adapted for @techwavedev/agi-agent-kit Original source: antigravity-awesome-skills

Memory-First Protocol

Retrieve prior design decisions (color palettes, typography, spacing scales) to maintain visual consistency across sessions. Cache generated design tokens.

# Check for prior frontend/design context before starting
python3 execution/memory_manager.py auto --query "design system decisions and component patterns for Odoo Sales Crm Expert"

Storing Results

After completing work, store frontend/design decisions for future sessions:

python3 execution/memory_manager.py store \
  --content "Design system: adopted 8px grid, Inter font family, HSL color tokens with dark mode support" \
  --type decision --project <project> \
  --tags odoo-sales-crm-expert frontend

Multi-Agent Collaboration

Share design decisions with backend agents (API contract changes) and QA agents (visual regression baselines).

python3 execution/cross_agent_context.py store \
  --agent "<your-agent>" \
  --action "Implemented UI components — new design system with accessibility compliance (WCAG 2.1 AA)" \
  --project <project>

Design Memory Persistence

Store design system tokens and component decisions in Qdrant so any agent on any platform (Claude, Gemini, Cursor) can retrieve and apply consistent styling.