Paid pilot - approved commercial terms

A defined 90-day operating period at $99 per month.

The USA Paid Pilot is commercially released for approved merchants after operating-fit review. Systems Integral is identified separately as the public-website operator. The executed merchant agreement or order form identifies the contracting and billing entity for SaaSMX merchant services before activation.

Verified commercial facts

Ten commercial terms have an approved source.

Price, duration, setup fees, provider-cost treatment, cancellation, continuation, support, eligibility, and geography now have an approved commercial source.

Verified

Monthly price

$99 per month

The Paid Pilot permits no more than three $99 monthly SaaSMX subscription charges, for a maximum SaaSMX subscription total of $297 during the defined 90-day period. Separate provider, delivery, and payment-processing costs are not included.

Verified

Pilot duration

90 days

The approved duration is a fixed evaluation period. Continuation after the pilot requires separate terms.

Verified

Setup fees

$0 SaaSMX setup fee; $0 onboarding operator fee

No SaaSMX setup fee and no onboarding operator fee are charged during the 90-day Paid Pilot. Any separately required third-party hardware or services must be identified and approved before purchase.

Verified

Stripe fees

Separate - merchant responsibility

Stripe payment-processing fees, settlement, disputes, chargebacks, and Stripe account requirements are separate from the $99 SaaSMX fee and remain the merchant's responsibility.

Verified

Delivery costs

Separate - merchant responsibility

Delivery-provider charges are separate from the SaaSMX subscription. The provider controls pricing, availability, and service area. SaaSMX does not add an undisclosed delivery markup.

Verified

Cancellation

End of current paid monthly period

The merchant may cancel during the pilot. Cancellation takes effect at the end of the current paid monthly period. Amounts already billed for that period are not prorated or refunded.

Verified

Renewal or continuation

No automatic renewal

The paid pilot does not automatically convert or renew after 90 days. Continuation requires explicit acceptance of an available SaaSMX production plan and its then-approved pricing and terms.

Verified

Included support

Best-effort pilot support included

The pilot includes onboarding and configuration assistance plus support for SaaSMX operational issues through the approved support channel. No 24/7 SLA or response-time commitment is included unless separately agreed.

Verified

Merchant eligibility

USA hospitality merchants after operational-fit review

Eligibility requires a merchant workflow that fits the supported SaaSMX scope, completion of the operational-fit review, required external accounts or services, and merchant approval of the configured workflow before buyer use.

Verified

Pilot geography

United States

The paid pilot is offered for approved United States merchants. Delivery and other third-party capabilities remain subject to availability at the merchant's location.

What paid pilot means

A paid operating period, not unpaid product testing.

The merchant pays for a defined SaaSMX scope during an agreed period. This is not a free trial. The purpose is to evaluate operational fit before any separate continuation decision.

The pilot is intended to validate

  • Confirm that the approved order path matches the merchant’s actual operating process
  • Confirm that merchant, kitchen, pickup, delivery, and review responsibilities are understandable
  • Identify unsupported requirements before they are treated as part of the product scope
  • Evaluate the agreed operating period before any continuation decision

Explicit responsibility

SaaSMX and the merchant do different work.

The final agreement must assign each responsibility directly rather than imply that the software or merchant handles everything automatically.

SaaSMX responsibility

Define the approved scope

SaaSMX must state the product surfaces, configuration, external dependencies, and exclusions accepted for the pilot.

Keep boundaries explicit

SaaSMX must not represent an unapproved capability, provider arrangement, or existing-system connection as included.

Review the operating path

SaaSMX must evaluate the agreed buyer, merchant, kitchen, pickup, delivery, and completion sequence with the merchant.

Merchant responsibility

Provide accurate operating information

The merchant must provide the menu, hours, pickup or delivery rules, responsible roles, and external-account details required by the approved setup.

Assign responsible people

The merchant must identify who reviews orders, who releases preparation, who handles the kitchen, and who completes pickup or delivery.

Review before buyer use

The merchant must test and approve the configured workflow and report requirements that fall outside the agreed scope.

System boundary

The SaaSMX price does not absorb every surrounding cost or responsibility

Stripe, delivery providers, external systems, merchant operations, and legal terms retain their own boundaries.

Inside the boundary

Defined in the final SaaSMX pilot scope

  • The approved SaaSMX product surfaces
  • SaaSMX-owned configuration and review responsibilities
  • The exact operating period and SaaSMX price

Connected or separate

Separate or still requiring qualification

  • Stripe processing, settlement, disputes, and account requirements
  • Delivery-provider pricing, availability, service area, and contracts
  • POS, accounting, tax, and existing-order-source responsibilities
  • Merchant staffing, decisions, and operating execution

Readiness sequence

Application and review come before provisioning.

Commercial terms and the application path are approved. The public-website operator is stated separately in the Website Terms. The merchant must still complete operating-fit review and receive approval before the merchant agreement or order form, provisioning, configuration, and launch review proceed.

  1. Step 1

    Apply for Paid Pilot review

    Provide the business, operating location, current order sources, fulfillment requirements, and responsibility context needed for review.

  2. Step 2

    Confirm operational fit

    Review merchant type, order sources, responsibilities, pickup or delivery needs, and conditions requiring merchant review.

  3. Step 3

    Confirm scope and commercial terms

    Confirm the supported SaaSMX scope, external dependencies, pilot price, fees, cancellation, continuation, support, eligibility, and geography.

  4. Step 4

    Approve and provision the merchant

    After qualification and agreement, the first successful SaaSMX subscription payment is required before ACTIVE service entitlement. SaaSMX then provisions the merchant, completes configuration, and performs the required launch review.

Application

Paid Pilot applications are available for operating-fit review.

Applying begins the controlled qualification process. It does not create a merchant account or bypass agreement, provisioning, configuration, or launch review.

Demo access opens the certified Luna Bakery merchant environment. It is a nonproduction demonstration, not a Paid Pilot merchant account or production merchant sign-in.

Paid Pilot navigation is available. Application remains operator-assisted and does not create a merchant account or automatically approve participation.