Product architecture

How MySignSells actually works.

From the moment a business subscribes to the moment their illuminated insert lands on the doorstep, every step is orchestrated by a single flow, backed by a small set of rules.

End-to-end flow

Step 1

Signup

Plan selection, ABN check, identity verification, agreement signature.

Step 2

Payment

Stripe subscription created. Customer entitlement provisioned.

Step 3

Portal

Customer lands on portal, sign hardware order pushed to fulfilment.

Step 4

Request

Standard, Multiple, or Canvas artwork request submitted.

Step 5

Design

AI-assisted proof generated. Designer refines. Customer approves.

Step 6

Production

Approved artwork queued to printer. QC checkpoint before packaging.

Step 7

Shipping

Label generated, courier assigned, tracking pushed to customer.

Step 8

Aftercare

Delivery confirmed. Claims and revision flow available.

Artwork engine

Requests are typed as Standard, Multiple, or Canvas. Each type has its own SLA, quota impact, and designer routing.

Rules engine

Six deterministic rules gate quota, billing, shipping and claim escalation — no ML in the critical path.

Trust boundary

Customer portal, designer console and admin CRM are separate surfaces with role-based access. All writes are audit-logged.

Artwork state machine

Draft

Pending review

Revision

Approved

In production

Printed

Shipped

Delivered

Backwards transition allowed only from Pending review → Revision. All other steps move forward.

Rules engine

ID	When	Then	Severity
R-01	Plan quota reached this billing cycle	Block new standard requests. Suggest upgrade.	Hard block
R-02	ABN not verifiable	Hold onboarding, prompt manual review.	Hard block
R-03	Artwork idle in `pending_review` > 5 days	Auto-nudge customer. Escalate to designer.	Soft nudge
R-04	Delivery > 10 days without scan	Open claim, notify support.	Soft nudge
R-05	Payment failed 2x	Pause portal access. Retain artwork history.	Hard block
R-06	Referral code redeemed at checkout	Attach dealer commission on first paid cycle.	Soft nudge

Data model (core)

Customer  ── has-many ─→ Subscription
Customer  ── has-many ─→ Artwork
Artwork   ── has-one  ─→ Shipment
Artwork   ── has-many ─→ Proof
Dealer    ── has-many ─→ Referral ─→ Customer
Claim     ── belongs-to ─→ Customer

Integrations map

Stripe
Subscriptions
ABR (ABN Lookup)
Verification
Sumsub
Identity
DocuSign
Contracts
Mapbox
Shipping map
Postmark + Twilio
Alerts