Requirement guides

Know the user work before you begin

LISTDIR classifies all 1,021 catalog records. Only 274 currently have evidence-backed requirements; every other candidate is explicitly marked research required.

These guides explain the categories of work that recur across directories. LISTDIR can prepare fields and assist locally where supported, but account access, protected checks, commercial decisions, and final submission remain with the user.

Requirement research needed

This is a candidate surface. LISTDIR has not yet verified its current submission path or user requirements.

What you do

  • Do not create an account or submit until this target is evidence-reviewed.
  • Use the verified cohort for active campaigns; candidates are research inventory only.

No form filling or submission is available.

Quality or policy review needed

The surface appears potentially useful, but LISTDIR has not yet promoted it because current source quality, policy fit, or submission rules still need review.

What you do

  • Treat this as guided research inventory, not a launch-ready target.
  • Review the provider page and quality notes before adding it to an active campaign.

LISTDIR can prepare research notes and reusable product copy, but does not fill or submit this target until evidence review is complete.

Product-specific fit required

This surface may be valuable only for a specific product type, platform, vertical, geography, integration, app store, marketplace, or technology stack.

What you do

  • Confirm the product genuinely fits the directory before spending time on signup or submission.
  • Use the assistant guidance to map required assets and skip the target when the product does not match.

LISTDIR can guide qualification and prefill reusable fields after fit is confirmed, but does not submit mismatched products.

Not applicable for product submission

This record is kept for marketing inventory transparency, but it is not currently a useful product-listing or backlink submission surface.

What you do

  • Skip this target for normal launch campaigns.
  • Only revisit it if your product, region, hiring, marketplace, or partnership strategy changes.

LISTDIR does not automate signup, form fill, or submission for surfaces marked not applicable.

Email account access

The destination uses an email-based account, sign-in, or confirmation step.

What you do

  • Use a role-based business email you control.
  • Complete provider email confirmation in your own inbox.

LISTDIR never stores directory passwords or inbox access.

OAuth or social sign-in

The destination offers or requires an OAuth/social identity flow.

What you do

  • Choose and authorize the account directly in the provider window.
  • Confirm the account belongs to the intended company or founder.

OAuth approval always stays in the provider window.

Domain or repository ownership

The provider requires proof that the submitter represents the product.

What you do

  • Use an official-domain email or authorized repository account.
  • Complete the provider verification link or permission check.

LISTDIR does not handle verification tokens, repository permissions, or credentials.

CAPTCHA or anti-bot check

The provider may require an anti-abuse challenge before accepting the form.

What you do

  • Complete the challenge yourself.
  • Stop and report a changed surface if the challenge blocks a documented workflow.

CAPTCHAs are never bypassed or solved by LISTDIR.

Payment or commercial decision

The provider may require payment, revenue-share terms, or a package selection.

What you do

  • Review price, refund terms, and expected value before approval.
  • Use the provider checkout directly.

LISTDIR never approves charges, accepts commercial terms, or stores payment data.

Identity verification

The provider requires personal or business identity checks.

What you do

  • Complete document and selfie checks only in the provider’s secure flow.
  • Confirm the company and person information are accurate.

LISTDIR never collects identity documents, biometric data, or verification results.

Terms and policy review

The destination requires agreement to provider policies or content rules.

What you do

  • Read the current provider terms and listing policy.
  • Confirm the listing claims, rights, and disclosures are accurate.

Terms acceptance remains a user action.

Editorial or eligibility review

The directory decides whether the product fits its scope and may edit, reject, or delay publication.

What you do

  • Check product fit before starting.
  • Monitor the provider inbox and respond to factual follow-up requests.

LISTDIR cannot influence provider approval or represent a listing as accepted before evidence exists.

Media and asset upload

The listing may need a logo, screenshots, video, or other visual proof.

What you do

  • Prepare real product media with rights to use it.
  • Review the provider preview before uploading.

LISTDIR can prepare approved assets; the user confirms any upload.

Product access or demo

The provider may request a working demo or temporary test access during review.

What you do

  • Create least-privilege, time-limited test access directly with the provider.
  • Remove or rotate test access after the review when appropriate.

LISTDIR never stores test-account credentials.

Community participation

The destination requires founder interaction, launch participation, or ongoing replies.

What you do

  • Write authentic, product-specific replies.
  • Plan time to participate after publication.

LISTDIR never impersonates a founder or posts community content without review.

Final human confirmation

The final review and submit action stays with the user even when fields can be prepared or filled locally.

What you do

  • Review every field and destination URL.
  • Submit only when the provider page and terms are current.

The browser helper never clicks the final submit button.

Evidence-backed destination requirements

General

Uneed

The submitter must be authorized to represent the product and provide accurate, complete information. Free launches must meet Uneed's current visibility and vote rules to remain published.

  • product website
  • product details
  • tags
  • launch option
  • launch date when eligible
  • product media

Dev Tools

Edge Add-ons

For Microsoft Edge extensions submitted through Partner Center, packaged as a working extension, with availability, properties, privacy details, store listing content, and certification notes.

  • Partner Center developer account
  • working extension package ZIP
  • availability and markets
  • extension properties
  • privacy purpose and permission justifications
  • store listing assets

SaaS

Shopify App Store

For public Shopify apps that meet Shopify App Store requirements. Shopify reviews app functionality, listing content, documentation, credentials, privacy, and category compliance, and may reject apps at its discretion.

  • Shopify Partner account
  • public app
  • development store test
  • app listing content
  • demo screencast
  • app category

SaaS

Salesforce AppExchange

For Salesforce packages, API solutions, and listings that pass AppExchange Security Review. Public searchable listings require approval.

  • Salesforce Partner Community account
  • Partner Console access
  • managed package or API solution
  • listing content
  • security review information
  • free or paid application selection

Dev Tools

Atlassian Marketplace

For Atlassian cloud or Data Center apps that meet app approval guidelines, security checks, partner verification, listing requirements, and technical review where applicable.

  • Atlassian vendor account
  • Marketplace Partner Profile
  • app descriptor or app file
  • public/private visibility
  • listing description and branding
  • privacy and security information

SaaS

Slack App Directory

For fully functional, publicly available Slack apps installed on at least 10 active workspaces, tested with customers or early partners, and compliant with Slack Marketplace guidelines.

  • Slack app configuration
  • Marketplace listing information
  • OAuth scopes
  • automated test readiness
  • supplementary review information
  • test account credentials where needed

SaaS

HubSpot App Directory

For unique public HubSpot apps that use OAuth as the sole authorization method, have at least three active unique installs, meet brand/security/privacy/performance/usability requirements, and pass HubSpot Ecosystem Quality review.

  • HubSpot developer account
  • public app ID
  • OAuth client ID
  • at least three active unique installs
  • app listing content
  • public setup documentation

Dev Tools

StackShare

For developer tools and services relevant to StackShare's tool-discovery catalog. The official website URL must be correct before a tool can be claimed and verified.

  • StackShare account using the currently offered sign-in method
  • tool listing information requested by the post-login flow
  • correct official tool website URL
  • official-domain email or an eligible GitHub repository for ownership verification when claiming the listing

SaaS

Gartner Peer Insights

A vendor must select an active Gartner Peer Insights market/category that matches the product. Gartner reviews the request and determines eligibility at its discretion; a Magic Quadrant mention is not required.

  • Gartner Peer Insights Technology Provider Tool account
  • verified email address
  • existing company selection or new company details
  • new product details
  • active Gartner Peer Insights market or category
  • factual vendor and product profile information

SaaS

GetApp

The product must be a publicly available packaged B2B or B2C solution, fit an existing category, use the same product name as the vendor-controlled website, and expose a public trial, demo, purchase, or information-request call to action. GetApp excludes bespoke services, marketplaces, database websites, clones, personal apps, and waitlist-only products.

  • vendor and product name
  • product website URL
  • eligible software category
  • unique factual third-person product description
  • product logo
  • product features and pricing information

SaaS

AppSumo

The current partner page seeks operational software products with market fit, business stability, and readiness to support customers. AppSumo reports an approximately 10% acceptance rate.

  • AppSumo account
  • product and company information
  • working product access for review
  • product copy
  • cover image and product images
  • listing price and deal features

Productivity

Monday App Marketplace

For valid monday apps that meet marketplace requirements. New apps primarily built using no-code platforms or AI-generated vibe code are not eligible for marketplace approval.

  • monday Developer Center account
  • published shareable auth.monday.com app link
  • marketplace submission form
  • listing requirements
  • review checklist
  • technical, security, privacy, content, asset, support, documentation, and legal readiness

Dev Tools

Heroku Elements Marketplace

For Heroku Ecosystem Partners delivering code, tools, or services as Heroku Add-ons or related Elements. Buildpacks require GitHub access to the source repository and open source licensing for contributed buildpack/button content.

  • Heroku Ecosystem Partner application
  • Partner Portal access
  • service or add-on details
  • provider price where applicable
  • technical integration
  • GitHub source access for buildpacks

Dev Tools

AWS Marketplace

For publicly available, full-featured production-ready software from eligible sellers. Seller registration is a prerequisite, and paid-product sellers must be in an eligible jurisdiction. EU member states are listed as eligible for paid products.

  • AWS account
  • AWS Marketplace seller registration
  • seller business, tax, VAT, and bank details when applicable
  • product title
  • product logo URL
  • short and long product descriptions

Dev Tools

Azure Marketplace

For Microsoft Marketplace offers that can pass publisher business eligibility, content validation, technical validation, and marketplace certification. Some offer types require testing instructions and technical integration.

  • Microsoft Partner Center account
  • verified email in Action Center
  • publisher role with offer permissions
  • offer setup
  • marketplace listing title
  • descriptions

Dev Tools

Google Cloud Marketplace

The organization must join Google Cloud Partner Network, be incorporated in a supported region, and maintain a Cloud Marketplace vendor account and payment profile. Products must be production-ready, enterprise-ready, secure, and commonly hosted on or integrated with Google Cloud under approved patterns.

  • Google Cloud Partner Network membership
  • Cloud Marketplace vendor account
  • payment profile
  • organization region and partner details
  • production-ready product details
  • enterprise readiness and support details

Dev Tools

Netlify App Directory

For Netlify extensions and integrations published by Netlify, official partners, and community members. Netlify reviews and approves all extensions before listing them in the directory.

  • Netlify account
  • extension or integration details
  • documentation
  • support information
  • extension type
  • listing metadata

AI

Microsoft Copilot Extensions

For Microsoft 365 Copilot agents, custom engine agents, and packaged connectors that meet Microsoft Commercial Marketplace certification policies, Microsoft 365 store validation guidelines, Responsible AI validation checks, and any applicable compliance program requirements.

  • Microsoft Partner Center account
  • Microsoft 365 and Copilot program enrollment where applicable
  • Microsoft 365 app package
  • manifest
  • large and small icons
  • agent or connector package

SaaS

Zendesk Marketplace

For Zendesk apps or integration apps that meet Zendesk Marketplace requirements, content checks, branding checks, and review. Zendesk documents a typical 1 to 3 week turnaround for new app submissions.

  • Marketplace developer portal organization
  • app ZIP or integration marketing package
  • GitHub repository URL optional
  • up to two categories
  • pricing or additional-fee details where applicable
  • terms agreement

SaaS

Freshdesk Marketplace

For Freshworks apps built with the Freshworks CLI and submitted through the Developer portal as public Marketplace apps. Apps must pass content and code review guidelines.

  • Freshworks developer account
  • supported product
  • app name
  • code upload
  • app information
  • media and installation details

Productivity

Notion Integration Partner

Only public Notion connections with installation scope set to Any workspace can be listed. Internal connections and public connections limited to selected workspaces are not eligible.

  • Notion developer account
  • public connection
  • Any workspace installation scope
  • Marketplace listing content
  • integration permissions
  • terms and policy review

Dev Tools

Stripe Apps Marketplace

For Stripe Apps that meet Stripe app standards, use English listing copy, avoid prohibited/restricted business purposes, and pass app review. Stripe states one public app per account.

  • activated Stripe account
  • public distribution manifest
  • required permissions with justifications
  • app upload
  • listing copy
  • app logo and images