Automate Odoo Prospecting with Claude

Build a Claude Skills engine that finds and scores Odoo ERP prospects.

Introduction

30 Second Summary

Finding new clients is the hardest part of sales. You could spend hours searching for companies, reading their websites, and manually deciding which ones are worth reaching out to.

In this project, you will build an automated prospecting engine inside Claude that finds companies ready for an Odoo ERP implementation. It scores prospects against your ideal customer profiles and exports a ready-to-use list you can act on immediately.

What You'll Build

You type /prospect-research manufacturing Ecuador and Claude goes to work. It researches companies in that market, scores each one against your buyer personas, and delivers a structured prospect brief ready for outreach.

By the end of this project, you'll have:

A slash command that produces a scored prospect list for any of your 6 key verticals in Ecuador or Mexico, powered by buyer personas that encode your Odoo sales expertise.
Detailed company intel for each prospect, including estimated pain points, a qualification score, and a recommended approach.
An exported Excel file of your full prospect list, sorted by tier and ready for outreach tracking.
Secret Mission: Schedule daily automated prospecting and build personalized outreach drafts that position Odoo for each prospect's specific needs.

Do I need anything before starting?

This project uses Claude on the web at claude.ai. You need an active Claude Pro subscription to access Cowork mode, Skills, and Plugins.

Before We Start

Before we dive in, let's lock in what you're about to build and why it matters to your day-to-day prospecting work.

Enable Skills and Install the Sales Plugin

You've defined your prospecting challenge and the verticals you want to target. To turn that vision into an automated system, Claude needs some infrastructure enabled first.

Skills let you package multi-step workflows as slash commands that run on demand. In this step, you'll enable Skills and install the Sales Plugin for built-in prospecting tools.

In this step, get ready to:

Enable Code execution and file creation in Claude's settings.
Switch to Cowork mode for task-oriented work.
Install the Sales Plugin for built-in prospecting capabilities.

Enable code execution and open Cowork

Skills run code behind the scenes to process data and create files. Before you can use any Skills or Plugins, you need to toggle on the Code execution capability.

In claude.ai, click the gear icon in the bottom-left corner to open Settings.
Select Capabilities.
Toggle on Code execution and file creation if it is not already enabled.
Close the settings panel to return to the home screen.

Now switch to Cowork mode so you can work with Skills and Plugins.

Find the message box at the bottom of the home screen.
In the bottom-left corner of the message box, select Cowork instead of Chat.

The message box now says Cowork. You're in task-oriented mode.

What is Cowork?

Cowork is Claude's task-oriented mode. Instead of a back-and-forth chat, Cowork lets Claude take on multi-step tasks, run Skills, and create files like spreadsheets and documents.

Cowork on the web is currently in beta for Pro, Max, and Team plans. If you run into any issues, you can also use Skills in Chat mode.

Install the Sales Plugin

Plugins extend Claude with pre-built capabilities from verified publishers. The Sales Plugin adds prospecting, outreach, and pipeline management tools that work standalone with web search and your input.

In your Cowork session, click Customize in the left sidebar.
Open the Plugins tab.
Click Browse plugins.
Find Sales (marked Anthropic Verified) and click Install.

The Sales Plugin now appears in your installed plugins list.

What does the Sales Plugin include?

The Sales Plugin provides slash-command skills for common sales workflows. It also activates automatic skills for account research, call preparation, daily briefings, outreach drafting, and competitive intelligence.

Every command works standalone with web search and your input. You do not need to connect a CRM or any external tools.

Can't find the Sales Plugin?

Make sure you are in Cowork mode, not Chat. The Customize menu with Plugins is available in Cowork.

help me find and install the Sales Plugin in Claude Cowork

Verify the Sales Plugin skills are available

Before you check, what skills do you think the Sales Plugin added to your Cowork session?

In your Cowork session, click the message box and type / to open the skills menu.
Confirm you can see the Sales Plugin skills available, including /call-summary, /forecast, and /pipeline-review.

You should see a list of skills from the Sales Plugin in the menu. These three slash commands handle call summaries, sales forecasts, and pipeline health reviews.

Don't see the Sales Plugin skills?

Make sure you are in Cowork mode, not Chat. Skills and Plugins require Cowork.
Confirm the Sales Plugin shows as installed under Customize then Plugins.
Check that Code execution and file creation is toggled on in Settings then Capabilities.

I can't see Sales Plugin skills when I type / in Cowork

Your prospecting infrastructure is ready. Next up, you'll put the Sales Plugin to work on a real prospect search and discover exactly where it falls short for your Odoo-specific needs.

Test the Sales Plugin on a Real Prospect Search

Your Claude environment is set up and the Sales Plugin is installed. Now it is time to put it to the test on a real prospecting scenario.

The Sales Plugin was designed for general B2B sales workflows. Your prospecting needs are far more specific: you sell Odoo ERP implementations to companies in Ecuador and Mexico. Testing the plugin on your actual use case will reveal where generic tooling falls short and what your custom Skills need to fix.

In this step, get ready to:

Run a prospect search using Claude's built-in capabilities.
Identify the gaps between generic results and Odoo-specific prospecting needs.

Run a generic prospect search

The Sales Plugin gives Claude built-in prospecting tools. Your first test is simple: ask Claude to find potential ERP clients in one of your target markets and see what comes back.

Before you send the prompt below, think about what you expect Claude to return. Will the results mention Odoo by name? Will they account for the regulatory landscape in Ecuador?

In your Cowork session, paste this prompt into the message box and send it:

Research medium-sized manufacturing companies in Ecuador that might need an ERP system. Give me a list of 5 prospects with company name, estimated size, and why they might need an ERP.

Claude returns a list of 5 companies with basic information about each one. Read through the full list before moving on.

What should I see?

You should see a list of companies with names, estimated employee counts or revenue ranges, and generic reasons they might need an ERP. The results are functional but surface-level.

Notice what is missing. The list does not mention Odoo by name. It does not score or rank the prospects. It does not reference LATAM-specific business dynamics like e-invoicing mandates or fiscal localization requirements.

Not seeing any results?

Claude uses web search to find companies. If your results are sparse or empty, try sending the prompt again. Web search results can vary between attempts.

Help me troubleshoot why Claude is not returning prospect results in my Cowork session.

Identify the gaps in the generic results

Now that you have seen what Claude produces out of the box, compare it to what you actually need as an Odoo Partner Manager. The generic results highlight four key gaps.

Review your results against each of these four questions:

Does the list distinguish between companies that would benefit from Odoo specifically versus any ERP? Generic results treat all ERPs as interchangeable. There is no mention of Odoo's modular approach, competitive pricing versus SAP or Oracle, or its strengths in your verticals.
Is there a scoring framework to prioritize which prospects to contact first? Without one, you have a flat list with no clear indication of which companies are hottest.
Does the output account for LATAM market dynamics? Factors like e-invoicing compliance, fiscal localization, import/export regulations, and Spanish localization are critical buying triggers in Ecuador and Mexico.
Are there buyer persona definitions guiding which signals matter for each vertical? Manufacturing prospects have different pain points than medical or retail prospects. The generic search treats them all the same.

Why do these gaps matter?

A generic prospect list gives you names but not direction. Without Odoo-specific qualification criteria, you cannot tell which companies are a strong fit for Odoo versus a competitor like SAP or Oracle.

Without LATAM market context, you miss buying triggers that are unique to Ecuador and Mexico. These gaps are exactly what your custom Skills will close in the next steps.

You have now experienced the ceiling of generic AI-assisted prospecting firsthand. The answer to all four questions above is "no." That is the gap your custom Skills will fill.

Next up, you will build a Buyer Persona Skill that encodes your Odoo sales expertise and LATAM market knowledge directly into Claude. Every future prospecting task will use your qualification criteria instead of generic assumptions.

Build Your Buyer Persona Skill

In Step 2, you saw the gap firsthand. Claude returned generic ERP prospects with no understanding of Odoo's strengths, your LATAM markets, or the vertical-specific signals that separate a promising lead from a dead end.

This step fixes that. You will build a dedicated Buyer Persona Skill that encodes your Odoo sales expertise into a reusable reference. Once saved, this Skill teaches Claude exactly what to look for across your 6 key verticals in Ecuador and Mexico.

In this step, get ready to:

Describe your Odoo sales role, verticals, and qualification criteria to Claude in a Cowork conversation.
Define a scoring framework with three weighted categories and prospect tiers.
Save the finished Skill and confirm it appears in your sidebar.

Start creating the Skill through conversation

Claude Skills are created through natural conversation. You describe what you want, share your domain expertise, and Claude packages everything into a reusable Skill file.

In your Cowork session, start a new conversation by sending this message:

I want to create a skill for Odoo ERP buyer personas. I am a Partner Manager at Odoo covering Ecuador and Mexico. I prospect for end customers who need an ERP implementation. My 6 key verticals are: medical, retail, imports, construction, transport, and manufacturing.

What does this message do?

This tells Claude you want to build a Skill, not just have a one-off conversation. Claude will start organizing a structured reference document and ask follow-up questions about your process.

Claude will ask follow-up questions about your prospecting process. It needs specific details about each vertical so it can build useful ideal customer profiles.

When Claude asks for more detail, share these vertical-specific pain points and your qualification criteria by sending a follow-up message like this:

Here are the specific details for each vertical:

Medical: regulatory compliance and supply inventory management.
Retail: multi-location inventory and POS integration.
Imports: customs documentation and multi-currency handling.
Construction: project costing and subcontractor management.
Transport: fleet management and route optimization.
Manufacturing: production planning and quality control.

Company size sweet spot: 50-500 employees with growing revenue.

Buying triggers that signal a company is ready:
- Outgrowing spreadsheets or manual processes
- Scaling operations or opening new locations
- Regulatory pressure like e-invoicing mandates
- Merging disconnected systems across departments

Qualification criteria:
- Budget indicators: revenue range, recent funding, growth signals
- Decision-maker accessibility: can we reach the CTO, COO, or owner?
- Timeline urgency: regulatory deadlines or competitive pressure

Odoo advantages for LATAM:
- Full Spanish localization
- Fiscal compliance modules for Ecuador and Mexico
- Competitive pricing versus SAP and Oracle
- Modular approach so companies start small and expand

Why this level of detail?

The more specific you are, the sharper Claude's prospecting becomes. Generic pain points like "needs an ERP" apply to every company. Vertical-specific signals like "customs documentation friction" help Claude filter for companies that actually need Odoo.

The LATAM advantages section is especially important. It teaches Claude to position Odoo against SAP and Oracle on the criteria that matter in Ecuador and Mexico.

Review Claude's response. It should be organizing your details into structured persona profiles for each of your 6 verticals.

Claude asking too many questions?

If Claude keeps asking for more information instead of organizing what you have shared, tell it: "That is enough detail. Please organize what I have given you into buyer persona profiles for each vertical." Claude sometimes over-gathers when it should start structuring.

help me get Claude to organize my buyer persona details into a structured Skill

Define the scoring framework

Right now Claude has your vertical details, but every prospect looks equally important. A prospect scoring framework assigns a numerical score so you can prioritize who to contact first.

Ask Claude to add a scoring system to the Skill by sending this message:

Include a scoring system in this skill with three categories:

- Company Fit (industry match, company size, geography): 0-40 points
- Pain Indicators (visible signs they need an ERP): 0-30 points
- Accessibility (decision-maker identifiable, not locked into a competitor): 0-30 points

Total score 0-100 with tiers:
- Hot: 70 or above
- Warm: 40 to 69
- Cold: below 40

Why these scoring weights?

Company Fit gets the most weight (40 points) because a company in the wrong industry or geography wastes your time no matter how accessible they are. Pain Indicators and Accessibility split the remaining 60 points evenly.

The tier cutoffs (Hot at 70+, Warm at 40-69, Cold below 40) create a prioritized queue. You focus outreach on Hot prospects first and nurture Warm ones for later.

Review Claude's response. It should show your scoring framework integrated into the persona profiles, with the three categories, point ranges, and tier definitions.

Scoring framework not matching your request?

If Claude changed the point ranges or added extra categories, correct it directly: "The scoring must use exactly Company Fit 0-40, Pain Indicators 0-30, Accessibility 0-30, with tiers Hot 70+, Warm 40-69, Cold below 40." Claude sometimes improvises on numeric details.

help me fix Claude's scoring framework to match my requirements

Save the Skill

Ask Claude to save everything as a Skill by sending:

Package this into a skill called buyer-personas

What happens when Claude saves a Skill?

Claude creates a structured SKILL.md file and stores it so any future conversation can reference it. The Skill becomes part of Claude's context whenever you invoke it, without you needing to re-explain your verticals, criteria, or scoring every time.

Click Customize in the left sidebar.
Open the Skills tab.
Confirm you see buyer-personas listed as a saved Skill.

Now verify that the Skill actually contains everything you built. Before you run this check, think about what you expect Claude to describe. How many verticals should it name? What three scoring categories should it list? What LATAM-specific details should it mention?

In a Cowork session, test your Skill by sending this message:

What verticals and qualification criteria does my buyer-personas skill cover?

Claude loads the Skill and describes your 6 verticals (medical, retail, imports, construction, transport, manufacturing), the scoring framework with its three categories (Company Fit, Pain Indicators, Accessibility), and your LATAM-specific qualification criteria including fiscal compliance and Spanish localization.

Skill not appearing in the sidebar?

Make sure Claude confirmed it saved the Skill. Look for a message like "Skill created" or "Skill saved" in your conversation. If Claude only described the Skill without saving it, send the packaging message again: "Package this into a skill called buyer-personas."

If buyer-personas still does not appear under Customize > Skills, try refreshing the page and checking again.

help me save my buyer-personas Skill in Claude

Your Odoo sales expertise is now encoded as a reusable Skill. Next up, you will build a /prospect-research Skill that puts these personas to work, automatically researching and scoring companies when you type a single command.

Build the /prospect-research Skill

Your buyer personas are locked in. Claude now understands your 6 verticals, your scoring framework, and what makes an Odoo prospect worth pursuing in Ecuador and Mexico.

Personas alone do not find prospects. You need a Skill that puts them to work by searching for real companies and scoring each one. In this step, you will build a /prospect-research Skill that takes an industry and country, researches companies via web search, and delivers a prioritized prospect table ready for action.

In this step, get ready to:

Create a /prospect-research Skill that loads your buyer personas and scores companies it finds online.
Add LATAM-specific research signals so Claude knows which buying triggers to look for in Ecuador and Mexico.
Test the Skill on a real market segment and review the scored output.

Create the prospect-research Skill

The /prospect-research Skill is the core engine of your prospecting system. You will describe what you want the Skill to do in plain language, and Claude will create it for you.

In your Cowork session, describe the Skill you want by sending this message to Claude:

I want to create a skill called prospect-research. When I type /prospect-research followed by an industry and country, Claude should:

- Load my buyer-personas skill for context
- Research companies in that industry and country using web search
- Extract company name, estimated employee count, industry sub-segment, website, and any visible pain points for each company found
- Score each company against my buyer persona criteria
- Output a structured table sorted by score with columns for Company Name, Score, Tier, Industry, Estimated Size, Key Pain Points, and Recommended Approach

Include a summary with total prospects found, how many are in each tier, and recommended next steps.

What does this message do?

You are describing a full Skill specification in natural language. Claude uses this to create a SKILL.md file that defines the slash command trigger, the data extraction steps, and the output format.

Referencing buyer-personas tells Claude to load your existing scoring criteria automatically whenever this Skill runs. Every prospect gets scored against the framework you built in the previous step.

Claude will ask follow-up questions about your format preferences and how deep you want the research to go.

Answer Claude's questions based on your actual workflow. For example, you might specify how many prospects you want per search, whether you prefer a brief or detailed recommended approach, or how many web sources Claude should check per company.

Share what you actually know

The more specific you are with your answers, the sharper the Skill becomes. If you know that companies with 50 to 500 employees are your sweet spot, say so. If you have preferred data sources for a particular market, mention them.

Add LATAM-specific research guidance

A generic web search might miss buying signals that matter in Ecuador and Mexico. Adding explicit research guidance ensures Claude prioritizes the triggers that actually indicate ERP readiness in these markets.

Tell Claude the specific signals the Skill should look for by sending this message:

The skill should also look for these LATAM-specific signals when researching companies:

- Companies still running manual processes or spreadsheets
- Businesses expanding operations or opening new locations
- Companies facing regulatory changes such as e-invoicing mandates
- Businesses with visible technology debt
- Companies recently receiving investment or growing headcount

Why do these signals matter?

Companies running manual processes or spreadsheets are prime ERP candidates because the pain is immediate and visible. E-invoicing mandates in Ecuador and Mexico create regulatory urgency that makes the buying timeline shorter.

Recent investment or headcount growth indicates budget availability and scaling needs. These are the companies most likely to score as Hot-tier prospects.

Claude will incorporate these signals into the Skill definition. You should see it confirm that the LATAM-specific guidance has been added to the research criteria.

Save and test the Skill

Ask Claude to package and save the Skill by sending this message:

Package this into a skill called prospect-research

Confirm the Skill is saved by clicking Customize in the left sidebar, then selecting Skills.
You should see prospect-research listed alongside your buyer-personas Skill.

Don't see prospect-research in your Skills list?

Scroll through Claude's conversation to see if it confirmed the Skill was saved. If it did not confirm, send "Save the prospect-research skill" again.
Make sure Code execution and file creation is still toggled on in Settings > Capabilities. Skills require code execution to be enabled.
Try refreshing the page and checking Customize > Skills again.

Still stuck? Ask for help.

Now it is time to test the Skill on a real market segment. Before you run it, think about what you expect the output to look like. Will every manufacturing company in Ecuador score as Hot? Or will the scores vary based on the pain indicators and accessibility signals Claude can find online?

Test the Skill by typing this into your Cowork session:

/prospect-research manufacturing Ecuador

Review the output. You should see a scored prospect table with columns for Company Name, Score, Tier, Industry, Estimated Size, Key Pain Points, and Recommended Approach, sorted by score from highest to lowest.
Below the table, look for a summary showing total prospects found, how many fall into each tier (Hot, Warm, Cold), and recommended next steps.

What should I see?

Claude will research manufacturing companies in Ecuador using web search, then score each one against your buyer persona criteria. Expect a mix of tiers. Companies with visible pain points and accessible decision-makers will score higher. Companies where Claude could not find much public information will score lower.

The Recommended Approach column should reflect Odoo-specific positioning, not generic ERP advice. If you see generic recommendations, refine the Skill by telling Claude to emphasize Odoo advantages like Spanish localization and fiscal compliance modules.

Output missing scores or columns?

If the table is missing the Score or Tier columns, tell Claude: "Update the prospect-research skill to always include the Score and Tier columns in the output table."
If the scoring does not match your buyer persona framework (Company Fit 0-40, Pain Indicators 0-30, Accessibility 0-30), tell Claude: "Make sure the scoring uses the framework from my buyer-personas skill."
If the results feel too generic and do not mention Odoo, tell Claude: "The Recommended Approach column should position Odoo specifically, referencing advantages like Spanish localization and fiscal compliance modules."

Need more help refining the output?

Your prospecting engine is ready. Next up, you will run it across multiple verticals, compare which markets produce the strongest prospects, and export everything as a downloadable Excel file for real outreach tracking.

Run the Full Pipeline and Export Your Prospect List

In the last step, you built a /prospect-research skill that finds and scores potential Odoo clients in any vertical and country you specify. One test run proved it works. Now it is time to run it across your real market.

A single search only shows one slice of your opportunity. Running your skill across multiple verticals and countries reveals where your pitch resonates strongest. In this step, you will research three market segments, consolidate the best prospects into a master list, and export it as an Excel file ready for outreach.

In this step, get ready to:

Run /prospect-research across three verticals and two countries.
Consolidate your Hot and Warm prospects into a single master list.
Export the master list as a downloadable Excel file.

Run prospecting across multiple verticals

You already tested your skill with manufacturing in Ecuador. Now you will run it on three more combinations to build a complete picture of your market.

In your Cowork session, prospect the medical vertical in Ecuador by typing:

/prospect-research medical Ecuador

Claude loads your buyer-personas skill, researches companies in this segment, and returns a scored table. Review the results and note which companies scored as Hot (70+) and what pain points were identified.

What should I see?

Claude returns a structured table with columns for Company Name, Score, Tier, Industry, Estimated Size, Key Pain Points, and Recommended Approach. Below the table, you will see a summary with the total number of prospects found and a breakdown by tier (Hot, Warm, Cold).

Not seeing a scored table?

If Claude returns a generic response instead of a scored table, it may not have loaded your prospect-research skill. Type / to open the skills menu and confirm prospect-research appears in the list. If it does, try running the command again in a fresh Cowork session.

help me troubleshoot why my /prospect-research skill is not returning a scored table

Now run a second search for the retail vertical in Mexico by typing:

/prospect-research retail Mexico

Compare the retail Mexico results with your medical Ecuador search. Notice the differences in pain points and score distribution across tiers.

Run a third search for the imports vertical in Ecuador by typing:

/prospect-research imports Ecuador

Review the imports Ecuador results. You now have three sets of scored prospects across two countries.
Compare which vertical produced the most Hot-tier prospects. This tells you where your Odoo pitch resonates strongest in the market.

Why run multiple verticals?

Each vertical has different pain points and buying triggers. Manufacturing companies struggle with production planning, while import companies face customs documentation challenges. Running multiple verticals reveals where your Odoo pitch resonates strongest, so you can prioritize your outreach time on the highest-opportunity segments.

Consolidate and refine your results

Three separate prospect tables are useful, but scattered. Merging them into one master list lets you prioritize across all verticals at once.

If the scoring feels off for any vertical (for example, medical prospects scoring lower than expected despite strong pain indicators), tell Claude to adjust it by typing:

Update the buyer-personas skill to weight Pain Indicators higher for the medical vertical

What does this do?

Claude updates the scoring weights inside your buyer-personas skill. The Pain Indicators category (0-30 points) gets more influence for medical prospects, meaning companies with strong regulatory compliance or supply chain issues score higher. This step is optional. Skip it if your scoring already looks right.

If you updated the scoring, re-run /prospect-research medical Ecuador to see the adjusted scores.

Ask Claude to merge all your results into a single list by typing:

Consolidate all Hot and Warm prospects from my prospect research runs into a single master list. Remove any duplicates and sort by tier then score.

Claude combines the Hot and Warm prospects from all your runs, removes duplicates, and presents a single sorted list.

Why leave out Cold prospects?

Cold prospects (below 40 points) have weak industry fit, few visible pain indicators, or low accessibility. Including them would dilute your outreach list with companies unlikely to convert. Focusing on Hot and Warm tiers keeps your outreach targeted and your time well spent.

Review the consolidated list. If you spot any false positives (companies that look irrelevant or already use a competing ERP), tell Claude which entries to remove.

Seeing duplicates or missing prospects?

If Claude missed some prospects during consolidation, it may have lost context from earlier in the conversation. Tell Claude to scroll back through the conversation and include all Hot and Warm results from each of your /prospect-research runs.

help me fix my consolidated prospect list

Export as Excel

Your master list lives inside the conversation right now. Exporting it as an Excel file gives you a standalone document you can track outreach in, share with colleagues, or import into a CRM.

Ask Claude to generate the export by typing:

Create an Excel file with my consolidated prospect list. Include all columns plus a Notes column for tracking outreach status.

What happens when Claude creates a file?

Claude runs code to generate a formatted .xlsx file. The file appears as a downloadable attachment directly in your conversation. You can save it locally and open it in Excel, Google Sheets, or any spreadsheet tool.

Before you download the file, think about what you expect to see inside it. How many columns should there be? What order should the rows be in?

Click the download button on the file Claude created to save it to your computer.
Open the downloaded file in a spreadsheet application.

You should see your scored prospects sorted by tier with columns for Company Name, Score, Tier, Industry, Estimated Size, Key Pain Points, Recommended Approach, and Notes. The Notes column is empty, ready for you to track your outreach as you contact each prospect.

File not appearing or not downloading?

Make sure code execution is enabled. Return to Settings, then Capabilities, and confirm Code execution and file creation is toggled on. Without it, Claude cannot generate files.

If the toggle is on but the file still does not appear, ask Claude to try generating the file again. Occasionally the code execution environment needs a moment to initialize.

help me download my prospect Excel file from Claude

Secret mission

Schedule Daily Prospecting and Build Outreach Drafts

Your prospect list is built, but prospecting should not be a one-time effort. In this mission, you will automate daily prospecting runs and build a Skill that drafts personalized outreach for your hottest leads.

Clean Up Your Resources

If you completed the Secret Mission, your scheduled prospecting task runs in the cloud every weekday morning. It will continue running even when your computer is off. If you want to stop it, pause or delete it from the Scheduled page in the left sidebar.

Nice Work!

Nice work! You built a personal prospecting engine inside Claude that systematically finds, qualifies, and scores potential Odoo clients across Ecuador and Mexico.

You've learned how to:

Built 6 buyer personas with Odoo-specific qualification criteria and a scoring framework for Ecuador and Mexico, designed after testing the Sales Plugin and identifying its limitations for specialized prospecting.
Created a /prospect-research Skill that researches companies by industry and country, scores each one against your buyer persona criteria, and delivers a prioritized prospect table.
Ran the full prospecting pipeline across multiple verticals and countries, then exported a consolidated Excel prospect list ready for outreach tracking.
Secret Mission: Scheduled daily automated prospecting with /schedule and built a /outreach-draft Skill that generates personalized cold emails and LinkedIn messages positioning Odoo for each prospect's specific pain points.

Ready to quiz yourself?