Source: https://commish.sh/for-businesses

For software businesses

# A creator program. Built around your business.

Commish connects your offers, creator referrals, and Stripe-backed earnings—so your partnerships have a place to work.

[Get started](https://app.commish.sh/sign-up?role=business) [See how it works](https://commish.sh/for-businesses#how-it-works)

For software businesses that use Stripe.

**Northstar** Creator program

Illustrative example

An offer everyone can understand

## 20% commission

For the first 12 months of each eligible subscription.

**Eligible products**: Pro & Team

**Attribution window**: 30 days

**Applications**: Reviewed by Northstar

One link. A clear connection.

## Maya Chen × Northstar

A referral link connects a creator’s recommendation to an eligible purchase.

Example referral link: `https://commish.sh/p/northstar/maya`

Each creator gets their own link after joining the program.

Know where earnings stand

## From purchase to payout

- **Purchase attributed** The customer subscribed through Maya’s link.

- **Earnings recorded** Eligible earnings follow the program’s offer.

- **Waiting for payout** Payout eligibility and funding are separate steps.

Example terms and fictional names. Each business sets its own offer.

From an offer to a shared outcome

## A program that makes sense on both sides.

- 01 **Define the offer** Set the commission, eligible products, and terms for your creator program.

- 02 **Give creators a link** Creators share a referral link with an audience that trusts them.

- 03 **Follow the earnings** Connect eligible purchases to creator earnings and see their payout status.

Built for the partnership

## Less back-and-forth. More shared context.

The business sets the offer. The creator brings the recommendation. Both can follow the relationship from referral to recorded earnings.

One shared source of truth

### The partnership at a glance

- The offer and its terms

- The creator’s referral link

- Attributed purchases and earnings

- Payout status and next steps

Fits your software business

## Built around Stripe. Connected to your product.

Bring eligible purchases into your creator program with the Commish integration. Keep the customer experience in your own product.

[Explore the integration](https://commish.sh/docs)

- Your product

- Stripe

- Commish

Purchase → attribution → creator earnings

Make the next connection

## Give your creator program a home.

[Get started](https://app.commish.sh/sign-up?role=business) [See pricing](https://commish.sh/pricing)

## Branded creator pages · preview

Commish Pages is an unreleased, optional Next.js SDK module—not part of the published 0.2.3 packages. Participating brands can give consenting creators managed pages at brand.com/c/creator, with optional verified short redirects after existing merchant routes. Content and eligible new creators update without a merchant deployment. Pages does not create discounts, change commissions, or replace checkout. Layout testing requires brand opt-in and visitor measurement permission.

For businesses: install once and manage approved on-brand offers. For creators: choose whether a brand may publish your identity with its approved offer. This choice is separate from directory visibility and does not end a partnership if declined. Production rollout and package publication remain separately authorized.

### Preview integration

After obtaining a reviewed Pages-capable candidate pair, run `pnpm exec commish-next pages init --dry-run --json`, then use `--apply` to add missing routes. Read the shipped `@commish/next/guides/pages.md` and `guides/agents.md` for consent, checkout, safe routing, verification, upgrades, and removal.

```
import { createCreatorPage } from '@commish/next/pages';
import { pagesOptions } from '../../commish-pages';
export const dynamic = 'force-dynamic';
export default createCreatorPage(pagesOptions);
```

Keep `pagesOptions` server-only. Connect your consent manager and existing checkout in the generated same-origin handlers. `commish-next pages doctor --creator maya --json` checks prerequisites; it does not certify a checkout or conversion. Every new eligible, consenting creator uses the same dynamic route, without another deployment.