One offer, one price
The public pilot offer, live invoice, and follow-up email should all show the same founding pilot structure and price.
Billing
The payment experience should feel as clear and consistent as the product and the outreach.
Simple, consistent billing for the RebateOps founding pilot.
The first billing path is intentionally simple: one fixed pilot, one clear scope, one direct reply path, and no mismatch between the site, the offer, and the invoice.
Billing principles
The payment experience should reinforce trust, not introduce confusion.
Branded touchpoints
Use `hello@rebateops.co`, `rebateops.co`, and the current logo/descriptor on billing-related communications.
Bounded promise
Billing stays anchored to packet-readiness support, missing-item follow-up, and workflow help, not vague outcome promises.
Human-close posture
Keep the payment ask direct and human. The invoice should feel like the continuation of the same conversation, not a random finance handoff.
Billing format
How the first pilot should be presented when money enters the room.
Step 1
Share the pilot offer
Use the branded pilot-offer page or PDF first, so the invoice is not the first time the contractor sees the exact terms.
Step 2
Issue the invoice
Use Stripe to send a one-time invoice with the same scope and reply path shown in the pilot-offer materials.
Step 3
Confirm the start path
Once the invoice is accepted, move directly into the go-live checklist and the first packet-ready operating rhythm.