How it works From joining to your first payout

How it works.
From a brief to a customer's own system.

You learn AI on paid client work. Proto builds each system from a plain-language brief, and you decide how the client's business should run, deliver it and support it.

Apply to join See the tiers
The path Six steps, in order

Six steps to
your first payout.

Each step below happens once per partner or once per customer, in this order.

  1. Apply

    Apply to join

    Anyone can apply, and joining is free. Any workspace can claim a namespace and publish the systems you build.

  2. Certify

    Build one system from a brief

    Build a working system with Proto from a written brief. ERP•AI reviews it. Certification is optional: it is $99 a year, waived during the launch period, and you can receive keys and payouts without it.

  3. Bring

    Give your customer a key

    A key gives a business that has never bought ERP•AI credits $100 of credit and makes you its partner of record. A start from your catalog listing also makes you partner of record, without using a key.

  4. Build

    Build the customer's own system

    Every customer gets its own copy, started from a catalog system or from your private library of starter systems, which you adapt to how its business works. The customer owns the copy and its data. You keep admin access until the customer revokes it.

  5. Bill

    Charge your client as you do today

    You set your price and bill the client directly. ERP•AI takes nothing from it.

  6. Paid

    Receive what the customer pays ERP•AI

    When the customer buys ERP•AI credits with its own money, you receive the same amount for its first 12 months. Each payment is held 60 days, then paid in cash in the next weekly payout.

A client engagement From the partner delivery guide

Deliver one process
at a time.

Every engagement names four roles and moves through the same six stages. The delivery guide, discovery worksheet and handover checklist below follow the same order.

Client sponsor
Owns the business outcome, the priorities and the acceptance decision.
Partner implementer
You. Defines the scope, builds the system with Proto, validates changes and prepares the handover.
Client administrator
Owns day-to-day access, configuration and operating guidance after delivery.
Employees
Explain the real work, try representative tasks and report obstacles.
  1. Discover

    Start with one complete process

    Describe the trigger, records, decisions, handoffs and expected result, for example a purchase request that becomes an approved order. Agree what belongs in the first release and what waits.

  2. Brief

    Write the brief Proto builds from

    Inspect the starting system with the client and separate what exists from what still needs to change. For a new build, agree the records, relationships, roles and first workflow before expanding.

  3. Build

    Build against the brief

    Give Proto the brief and the relevant builder skills, and ask it to propose a plan before it changes anything. Review records, permissions, workflows and integrations with the client administrator, in a test workspace with sample data.

  4. Prove

    Demonstrate the result

    Test the normal path and an exception with real employees, check permitted and restricted actions, and compare imported totals and record counts with the source. Write acceptance criteria as observable results.

  5. Hand over

    Hand over an operating system

    Deliver the accepted scope, configuration notes, data mapping, employee instructions and known limitations. Confirm the client controls its workspace, data and access.

  6. Support

    Agree what happens next

    Agree your continuing responsibilities, the support route and how future changes are reviewed. Support and changes are work you bill for.

Partner of record Who the customer belongs to

How you become
the partner of record.

A business that has never bought ERP•AI credits becomes your customer, with you as its partner of record, when it activates your key, starts from your catalog listing, or creates its workspace within 120 days of confirming a deal you registered. While the registration is confirmed, no other partner's key or listing can claim that business.

Switching
A customer can change partners at any time.
Earned money
Payouts already earned stay with the partner who earned them.
First 12 months
A change of partner does not restart them.
Access
The customer can revoke a partner's admin access at any time.
Resources For every client delivery

Bring a plan to the
first conversation.

The same delivery documents work for every system: understand the client, agree the scope, prove the first workflow and hand over.

Partner delivery guide
Choose a starting point, prepare the first workflow and help the client team start.
Client discovery worksheet
The questions to ask before you scope a system.
Delivery and handover checklist
What the client receives and who is responsible afterward.
Builder skills guide
Skills Proto uses to build records, pages, workflows and access.