# Affiliate Program

Promote Madrix with trackable links and ready-made content. You earn a commission for customers attributed to your link.

{% hint style="success" %}
**Commission:** 10% on eligible payments from the customer attributed.\
**Duration:** 12 months per attributed customer.\
**Tracking:** via Affiliate Dashboard.
{% endhint %}

### Who it's for

* Content creators (LinkedIn, YouTube, newsletter).
* Consultants and freelancers (dev, product, data, automation).
* Agencies that recommend tools in delivery.

### Quick checklist

{% stepper %}
{% step %}

### Activate your affiliate access

* [ ] Create your account and log in.
* [ ] Request access to the **Affiliate Program** (may require approval).
* [ ] Confirm that you can see the **Affiliate Dashboard**.

**Expected result:** you can see clicks and conversions in the dashboard.
{% endstep %}

{% step %}

### Generate your affiliate link (with UTM)

* [ ] Use one link per channel (LinkedIn, YouTube, newsletter).
* [ ] Standardize UTMs to compare performance.
* [ ] Test the link in an incognito tab before publishing.

Recommended standard:

* `utm_source=linkedin`
* `utm_medium=post`
* `utm_campaign=affiliates`
* `utm_content=demo-7min`

Example URL (template):

`https://YOUR-LINK-HERE?utm_source=linkedin&utm_medium=post&utm_campaign=affiliates&utm_content=demo-7min`

**Expected result:** you can separate results by channel and format.
{% endstep %}

{% step %}

### Publish 1 piece of content per day for 7 days

* [ ] Vary the format: short post, 60s video, thread, email.
* [ ] Repurpose the templates below.
* [ ] Use a single CTA per piece of content.
* [ ] Monitor clicks, sign-ups and conversions in the dashboard.

**Expected result:** you discover 1 channel with good traction.
{% endstep %}
{% endstepper %}

### How it works

#### Commission structure

* Commission per customer attributed to your link.
* Standard commission: **10%**.
* Standard duration: **12 months** per attributed customer.
* Final rules may vary by plan and campaign.

#### Tracking and attribution

Validate these points in the dashboard before promoting:

* **Attribution window (cookie):** how many days after the click count.
* **Attribution model:** usually last-click.
* **Tracked events:** click, sign-up, upgrade and payment.

#### What each metric means

Use these definitions to align expectations with your audience.

* **Click:** someone opened your trackable link.
* **Sign-up:** created an account after visiting via your link.
* **Activation:** completed a minimal action in the product.
* **Conversion:** became a paying customer.
* **Approved for payout:** passed validation and was not refunded.

#### Affiliate dashboard

The dashboard usually answers these questions:

* How many clicks did I generate per channel?
* How many sign-ups and activations came from my link?
* Which customers are pending validation?
* What amount is approved for payout?

#### Payments and reports

Confirm in the dashboard (or in the terms) before planning your schedule:

* Payout frequency (monthly / biweekly).
* Minimum amount for payment.
* Method (e.g. transfer) and required details.
* Refund/chargeback rules and validation period.

### Recommended links

Use one landing per intent. Avoid mixing CTAs.

* For “hands-on”: [Start here](/get-started-here.md)
* For “see it live”: [Demonstrations](/demonstrations.md)
* For “first deploy”: [Deploy and Cloud Environments](/hands-on-tutorials/3.-deployment-and-cloud-environments.md)

### Marketing kit

#### Ready copies (copy and paste)

{% tabs %}
{% tab title="LinkedIn (short)" %}
If you want to get software out of the idea phase faster:

I used Madrix to go from **prompt → app** in minutes. It helps create, iterate and publish with more control and governance.

Want to see a 7-min demo? Message me or click the link.
{% endtab %}

{% tab title="WhatsApp (direct)" %}
I tried Madrix: you can go from prompt → app pretty fast.

If it makes sense, I’ll send you a 3–7 min demo + link.
{% endtab %}

{% tab title="Email (B2B)" %}
Subject: Quick demo: prompt → app in minutes

Hi {Name},

If you are evaluating how to accelerate delivery with AI, it's worth checking out Madrix. In a few minutes you can create a simple app and publish an environment.

If you’re up for it, I’ll send a short demo and the link to try it.
{% endtab %}
{% endtabs %}

#### Quick hooks (to vary the start of the post)

* “If you’ve tried ‘AI that generates apps’ and got frustrated…”
* “The problem isn’t generating code. It’s governing changes.”
* “You can go from prompt to app without losing control.”
* “What changed when I tested building with agents?”
* “Quick demo: what you can do in 7 minutes.”

#### Assets and formats

* **Banners and images:** use for posts and landing pages.
* **Short videos (30–60s):** better for click volume.
* **Screen capture (2–5 min):** better for conversion.

#### Recommended landing pages

Always use one landing per intent:

* **“See quick demo”** (top of funnel)
* **“Create first project”** (hands-on)
* **“Governance and enterprise”** (decision-maker)

#### Template library

* Post templates (educational, case study, comparative).
* Library of hooks and headlines.
* Post calendar (4 weeks).

### Quick demo script

Use this script for short, repeatable demos.

#### 7-min version (recommended)

* **1 min:** what Madrix is and who it's for.
* **3 min:** create a live system (prompt → generate).
* **2 min:** make 1 quick change (Chat AI vs Editor).
* **1 min:** deploy to a cloud environment (overview).

#### Script (suggested lines)

* “I will create an app from scratch with a prompt.”
* “Now I will approve the specification and generate the software.”
* “I will request a change and show where it appears in the project.”
* “Finally, I will publish to the cloud to make it accessible.”

#### Common objections (short answers)

* **“Is this just another ‘generator’?”** No. It's a build + iteration + deploy flow.
* **“Can it be governed?”** That's a focus. Validate the control options in your case.
* **“What about maintenance?”** Treat it like a software project. Use incremental iteration.

### Light educational content

Content ideas that convert without sounding like “advertising”.

* What is an **agentic software platform** (in practical terms).
* Why **governance** matters when AI generates software.
* Main use cases (by area and by maturity).
* Benefits vs. traditional tools (where it wins and where it doesn’t).
* How to talk about ROI without making up numbers (time, risk, cost).

### Videos for affiliates (30s-5 min)

Video suggestions (titles and formats):

* **Madrix in 60 seconds** (teaser)
* **Build an app in 3 minutes** (screen capture)
* **Top 5 use cases Madrix solves** (list)
* **Why enterprises need governance with AI** (educational)
* **How to pitch Madrix (affiliate version)** (script)

#### Materials

* Links with UTMs ready per channel.
* Post calendar (4 weeks).
* Library of hooks and headlines.
* Email templates.

### Rules and policies (summary)

Use as a guardrail. The program terms are the final rule.

#### You may

* Use UTMs per channel and per format.
* Talk about qualitative and observable results.
* Indicate the full flow (prompt → generate → iterate → deploy).

#### You may not

* Spam (mass DMs, purchased lists, aggressive automation).
* Promises without basis (“guaranteed ROI”, “replaces your team”).
* Use of brand/identity outside the official kit, if any.
* Paid media with brand bidding, if the terms prohibit it.

### Next steps

* Publish 3 pieces of content and compare performance by UTM.
* Repurpose what performs: same theme, new format.
* Drive traffic to a single CTA per post.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.madrix.dev/affiliate-program.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.