Authenticated seller workspace / territory + account operations
This is the Sales Partner operating dashboard. Seller attribution, your book of accounts, qualification windows, commissions, referrals, resources, agreements, and account software all live under one account.
Seller first. FrankieFam software is available inside this account as a secondary entitlement area. Customer attribution and seller-referral attribution remain separate records.
01 / Seller identity
The permanent attribution ID is the system connection point for future customer sales, seller referrals, commissions, seller links, customer-facing pages, and account records.
Use the seller ID for approved customer-sale records, seller referrals, commissions, customer-facing seller pages, seller links, and future account integrations.
SP-PHARMA-00421Demo hook only — connected attribution service pending.
02 / First 72 hours
The first qualifying customer sale made during the 72-hour launch period may earn a bounty equal to 10% of the customer's first paid month. It becomes payable only after that customer's 30-day money-back/guarantee window clears.
Starts at the application approval timestamp. Connected timer pending.
One qualifying customer sale starts the bounty lifecycle.
Current example: $300 one-time. Payable after the customer's 30-day guarantee clears.
Qualifying sale recorded inside the 72-hour window.
30-day customer window is still open.
Guarantee cleared; eligible for payout processing.
Payout recorded against the seller account.
The highlighted position is a display-state example, not a connected bounty claim.
03 / Seller status
Referral creates Tier 2 Pending. The recruited seller must make a qualifying sale within 30 days of application approval. Two qualifying sales per month retain this compensation package and Tier 2 eligibility.
Every seller begins here.
Activated when a referred seller enters the required sale path.
Continuing/lifetime commission concept; final configuration supplied by program rules.
04 / Customer sales
Seller-facing status for opportunities, accounts, and qualification windows. Fulfillment internals remain outside this dashboard. A sale is recorded separately from guarantee clearance and commission payability.
Connected sales ledger pending.
Customer account status hook.
30-day window tracking hook.
Guarantee-cleared account hook.
Account-state feed pending.
| Customer | Sale date | Current account state | Guarantee-clear date | Commission state |
|---|---|---|---|---|
Connected customer sales will appear here. No live customer records are fabricated in this prototype. | ||||
05 / Commissions & money
Sale recorded is not the same as commission payable. This dashboard separates customer activation, the 30-day guarantee, payable status, and paid history.
Recorded, not yet payable.
Guarantee window cleared.
Recorded payout history.
Seller payout account hook.
Current example: three-month service, billed quarterly, first month free — $1,200 direct recurring + $500 onboarding completion + $300 first-sale bounty, equal to 10% of the first paid month.
Display example only. Each component remains subject to the current approved plan, qualification, and guarantee-clearance rules.
No connected payout records yet. Future entries will retain sale reference, guarantee-clear date, payable date, payout date, destination, and state.
06 / Seller referrals
Seller-referral attribution is separate from customer-sale attribution. This is the operating area for downstream seller status and Tier 2 progression.
SP-PHARMA-00421Referral link will be issued by the connected partner system.
Demo hook only — tracking, cookies, IDs, and payout attribution are not implemented.
07 / Account governance
Approval, activity, leave, tax documentation, and authorization are recorded as account states rather than inferred from portal access.
Approved leave pauses the clock only for approved dates. Without leave, 90 consecutive days of inactivity is voluntary termination.
Minimum 14 consecutive days, prospective and logged. Medical leave requires verified doctor documentation.
Required documentation: identification, taxpayer information, and proof of address. Missing documentation can end unpaid program compensation.
Selling requires approval. Terminated sellers must reapply and be approved again; white-label status exists only with an active separate agreement.
Tax documentation is not collected in Frankie chat fields. The administrative destination is jamie@engineeredlaunch.com; JLS provides applicable 1099 reporting.
08 / Customer support
The seller is first-line support for originated customers. JLS retains the support history needed to confirm service is being handled and to identify any direct-client reclassification.
Every customer-facing site must expose an approved trouble-ticket method. If an issue cannot be resolved, record the issue, plan, follow-up, next steps, current status, and responsible owner within one business day when possible.
Phone, email, text, portal, and ticket contacts belong in the same client history.
09 / Seller resources
Permanent access positions for approved materials. Manual fulfillment can occupy these spaces before every resource is automated.
Current principal Partner Sales product overview.
Approved seller conversation material.
Relationship-first outreach position.
Approved cold outreach position.
Objection handling and approved answers.
Explain the customer sale and start-Dominator path.
Seller scheduling access position.
Customer-facing seller site access position.
Approved forms and other seller materials.
10 / Customer-facing site
The seller website is a separate page/product. This dashboard provides the operating links and status positions without building the site here.
Customer-facing Dominator page is represented here as a separate destination.
11 / Documents & agreements
Document positions are ready for the approved seller program files. No new substantive legal terms are created by this dashboard prototype.
Seller-specific accepted versions are retrieved here after account authorization. Draft source files remain outside public page markup.
Authenticated retrieval and electronic acceptance are future integration hooks. The seller's own accepted version remains associated with the seller/account record.
12 / Secondary account entitlement
A Sales Partner can also be a FrankieFam software user. The seller does not need a second account or portal. Only connected entitlements should appear as owned software.
Free Frankie product-family entitlement position. Form Frankie, FAQ Frankie, and Contact Frankie remain separate product capabilities and are not shown as owned here unless connected.
Activation: Not connected · Expiration: Not connected
Future licensed FrankieFam products will be inserted as self-contained entitlement records; non-entitled products do not appear.
13 / Account
Account controls stay available without competing with the seller operating areas.
Profile, employer, contact, and account identity management hook.
PayPal destination, security, authorized access, and support contact positions.
Standalone demo — account authentication, transactions, payout processing, referral tracking, and backend persistence are not connected.