What this recipe does
Start from a company URL or uploaded deck, research the company, search available Axomap landscapes, and identify where the company clearly fits.
When to use it
Use this when you want to know whether a company belongs in one of your private Axomap landscapes or an existing public landscape.
Prompt
Use Axomap's recipe for finding relevant landscapes for a company. Company URL: https://example.com
Expected result
- A concise summary of what the company does and the market it appears to compete in.
- A short list of private/shared or public Axomap landscapes that are clear or possible fits.
- A brief reason for each landscape match, including why the company fits the landscape scope.
- A clear answer when no existing landscape appears to be a good fit.
Requirements
- The user has a company URL, startup deck, PDF, or presentation they want to place in an existing Axomap landscape.
- The user has a ChatGPT Pro or equivalent MCP client account with web research enabled.
- The user connected Axomap MCP with read access.
Agent workflow
-
Understand the company
If the user uploaded a deck, inspect it enough to identify the company, product, buyer, use case, and positioning. If the user provided a URL, use web research with the URL as the identity anchor. Keep this research quick and factual.
-
Infer search terms
Create a concise set of market, buyer, workflow, product category, and competitor keywords that describe where the company might fit. Avoid overly broad industry terms unless the company is broad.
-
Search available landscapes
Use search_available_landscapes with the strongest inferred keywords to search both the user's private/shared landscapes and public Axomap landscapes. If the first search is too narrow, run one or two broader or alternative keyword searches. Do not fetch every landscape one by one.
-
Shortlist likely matches
Compare the company against each returned landscape's name, description, thesis, company_count, access, and public/private status. Shortlist only clear or plausible fits. If there are no good matches, say so plainly.
-
Confirm with deeper landscape context
For the strongest shortlisted landscapes, use get_landscape_overview to inspect categories and company previews. Use list_landscape_companies or search_companies only when the fit is still uncertain or when checking for similar companies already present.
-
Report the fit
Give the user a concise company summary, the inferred market, and the matching landscapes. Separate clear fits from possible fits. For each landscape, include the landscape name, whether it is private/shared or public, and a short fit reason.