Odoo sales crm expert
Skill srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/odoo-sales-crm-expert
Native macOS skill-catalog studio for Claude Code — browse 1,492 Markdown skills, customize with variables or AI (hosted or local), export to .claude/skills. SwiftUI + Liquid Glass.
npx -y skills add srg-sphynx/MDForge --skill odoo-sales-crm-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Expert guide for Odoo Sales and CRM: pipeline stages, quotation templates, pricelists, sales teams, lead scoring, and forecasting.
SKILL.md
4.3 KB, 991 tokens by cl100k_base, as published. Nobody here has run it
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
- Activate: Mention
@odoo-sales-crm-expertand describe your sales scenario. - Configure: Receive step-by-step Odoo setup instructions.
- 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
salemodule. - 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most sales audience skills give in 991 tokens
Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07
- Read product marketing context before asking questionsin 21 of 401, across 11 files
- Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
- Start every page with a summaryin 15 of 401, across 4 files
- Use a single, low-friction call to actionin 15 of 401, across 7 files
- Create a single source of truth for each competitorin 14 of 401, across 3 files
- Make each follow-up email add new valuein 11 of 401, across 5 files
- Cut any sentence that does not drive a replyin 10 of 401, across 4 files
- Tie personalization directly to the problemin 10 of 401, across 4 files
- Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
- Link between related competitor pagesin 9 of 401, across 3 files
- Keep subject lines short and lowercasein 9 of 401, across 3 files
- Define ideal customer profile from top customersin 9 of 401, across 3 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.