Partner Docs
Partner PortalGet started
ProgramRevenue Share

Revenue Share

How much Softr partners earn on referred customers' subscriptions, for how long, and how to check eligibility on a submitted project.

Softr partners earn a percentage of a customer’s subscription revenue when working with new Softr customers.

A customer is considered “new” when:

  • their initial subscription payment is made after a partner begins working on the project, or
  • their initial subscription payment is made up to 45 days before the partner starts working on the project.
Revenue share at a glance: 20% for a customer connected through Softr Partners, 30% for a customer connected outside Softr Partners; a 12 month period for Certified Partners and 24 months for Premium Partners

The revenue share period is based on your partner tier (Certified vs Premium) and your connection to the customer (connected through Softr Partners vs connected outside Softr Partners).

Partner tierCustomer connectionRatePeriod
Certified PartnerConnected through Softr Partners20%12 months
Certified PartnerConnected outside Softr Partners30%12 months
Premium PartnerConnected through Softr Partners20%24 months
Premium PartnerConnected outside Softr Partners30%24 months

Customer connection

A customer is classified as “Connected through Softr Partners” when the customer is connected to a partner via:

  • the softr.io partner directory “Get matched with a partner” form
  • the softr.io partner directory “Contact partner” form
  • a direct internal referral from the Softr team

A customer is classified as “Connected outside Softr Partners” when a partner registers a project in the partner portal with a customer who was not originally connected to that partner via one of the methods above.

Period

The revenue share period begins when the project is registered by the partner in the partner portal.

The period is a fixed length from the project registration date. If a customer pauses their Softr subscription during this period and reactivates later, the end date of the revenue share period does not change. The partner is entitled to a percentage of a customer’s subscription revenue for a given 12/24 month period.

Tier changes

If a partner moves up or down in tier, their existing revenue shares inherit the new tier’s settings.

  • If a Certified partner has existing 12-month revenue shares and then earns Premium status, those revenue share end dates are extended by 12 months to be 24 months in total.
  • If a Premium partner has existing revenue shares and is downgraded to Certified, their existing 24-month revenue share end dates are reduced by 12 months to be 12 months in total.

PartnerStack vs Partner Portal

All revenue share payouts are administered via PartnerStack, but all project/deal registration happens in the partner portal. You only need to register and manage your projects in the portal; all activity syncs through to PartnerStack via API.

Checking eligibility on a submitted project

Every project submitted in the Partner Portal shows a Revenue Share Eligibility Reasoning indicator on its Project Details page, next to an eligibility toggle. It shows at a glance whether the customer linked to that project qualifies for revenue share, and why.

Project lifecycle

Draft

A new project starts in Draft status when first created in the Partner Portal.

24-hour wait

A 24-hour wait is required before a draft can be submitted for review. This window allows backend data (BigQuery, Stripe, PartnerStack) to sync so the eligibility check has accurate information.

Submit for review

Once the project is submitted for review, the eligibility check runs.

Pending, then verdict

While the check is in progress, the indicator shows ⚠️ Pending: Stripe and PartnerStack data haven’t been checked yet. When it completes, the indicator updates to one of the verdicts below.

Possible verdicts

  • ✅ Eligible: no existing PartnerStack customer was found. A new PartnerStack customer record was created and attributed to the submitting partner. Commission applies to all future subscription payments.
  • ✅ Eligible: this customer hasn’t subscribed in Stripe yet. Commission starts with the customer’s first payment.
  • ✅ Eligible: customer’s first payment was X days before this project was submitted (within the 45-day window). The customer’s first Stripe payment is within the 45-day eligibility window, so the project qualifies.
  • ❌ Not eligible: customer’s first payment was X days before this project was submitted, which exceeds the 45-day window. The customer paid more than 45 days before the project was registered, so this project does not qualify.
  • ❌ Not eligible: this customer is already associated with a different Partner in PartnerStack. Under the first-touch attribution model (see PartnerStack), revenue share goes to the originally attributed partner.

If a verdict appears incorrect, contact partners@softr.io.

Scope

These verdicts apply to non-Enterprise plans. Enterprise deals (above $3,228.00) follow the sliding-scale process described above and are processed manually by the Partnerships Manager.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Partner Docs documentation and read it in full, instead of answering from memory.

https://partner-docs.iamno.pro/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://partner-docs.iamno.pro/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.