Paid Listing

Listing Details page

The following table describes the fields of the Listing Details page for a Paid Listing.

Field	Content and examples	Best practices
Monetization Type	Paid Listing: for advanced lead-generation features	Spell out exactly what’s included in the paid tier later in the submission form. Suggest “free” features have hidden charges.
Listing Language	Select the language in which you’ll author the content of the listing (available only English or Japanese). Example: English Or Japanese	Localize every field and image caption to your chosen language. Mix languages or use machine-translated placeholders.
Category	Pick one: Partner Solution (quote form feature to be enabled). Check out Monetize Business Solutions for more information.
Subcategory	Automatically filled: Partner Solutions
Listing Type	Automatically filled: Partner Solutions
Fulfillment Message	Provide next-step instructions that customers receive post-purchase. Example: “After purchase, download the Business Solution package at <website link>.	Be crystal-clear on where, how, and when the customer gets the solution. Provide unclear guidelines.

Description page

The following table describes the fields of the Description page for a Paid Listing.

Field	Content and examples	Best practices
Listing Title	Keep under 50 characters. Check out Submit a listing for more information. Example: Invoice Bottleneck Analysis with Process Mining	Lead with the outcome (“Analyze invoices…”). Include internal codes or overly technical jargon.
Icon/Logo	Upload 100 × 100 px image.	Keep it simple and legible. Use screenshots or busy compositions.
Tags	Up to 5 single-word tags to indicate Process · Source System · Industry. Example: Procure-to-Pay, SAP, Manufacturing	Choose words users actually search for. Use sentences or generic terms like “App".
Card Summary	Follow {Action} {System} {Purpose} pattern. Check out Submit a listing for more information. Example: "Automate invoice analysis in SAP to improve payment speed."	Be concise and outcome-focused. Reinvent your overview here—keep it punchy.
Application	Select from dropdown (e.g., “SAP”) or type to add new.	List only applications your template directly integrates with. Pad with irrelevant apps.
Overview	Cover the following: What: What does your app do? Why: What problem does it solve? How: How does it work? Who: Who is it for? Check out Submit a listing for more information.	Use clear, customer- centric language. Overload with technical details.
Features	Define Problem Solved · User Benefits · Estimated Time Savings. Problem Solved: What inefficiency is addressed? User Benefits: How does it help users? Estimated Time Savings: Realistic time or effort saved. Example: "Real-time bottleneck identification (save up to 20 hours/week)." Check out Submit a listing for more information.	Quantify impact where possible. Promise “infinite” or unmeasurable savings
Upload image	Mandatory screenshots: Overview dashboards with KPIs; Variant Explorer / process graph. Check out Submit a listing for more information.	Use clear, annotated images. Upload low-quality visuals.
Paste Video URL	Mandatory 2–3 min YouTube/Vimeo showing: Data Ingestion: Showcase how the Upload of the CSV/system data is done. The expectation is to show the data import completing successfully. App Execution: Show specific process app dashboards and KPIs The expectation is that dashboards are loading based on the data ingested, filters are responding and specific process KPIs are visible. Use Case: Narrated a use case scenario delivered part of the process mining project. The expectation is to narrate a real project use case proving the template value.

Files and Terms page

The following table describes the fields of the Files and Terms page for a Paid Listing.

Field	Details
Dependencies	List required technologies (e.g., Salesforce, SAP ECC 6.0, Oracle Fusion).
License	Select Custom License (commercial terms). Check out Files and Terms for more information.
Privacy Terms	State if personal data is processed; link policy if yes.
Documentation	Attach/link Data Structure & sample requirements (mandatory) and User Guide / Setup Instructions (recommended). Tip: You can download the following sample template file and use it as a starting point for your documentation package: Documentation Framework Sample.docx.
Documentation URL	Public link to your documents (if applicable)
Support	Provide contact + SLA (e.g., “Email [e-mail])

Pricing page

The following table describes the fields of the Pricing page for a Paid Listing.

Field	Details
Listing Price	Enter a minimum amount. Once the quote is requested, you can contact the user for further commercial discussion.
Quote Request	Select NO to enable users to only "Request a quote".
Subscription
Service Support
Documentation URL
Taxes