Whatever is bleeding, TVA helps you name it, route it, fix it, prove the fix exists, and stop it from becoming your permanent job. https://tradingvendoracademy.com/ 2026-10-08T00:00:00Z QuantKey AI Trading Vendor Solutions https://tradingvendoracademy.com/lessons/bir-1-1 2026-10-08T00:00:00Z

Every product has one of four origins, and the origin decides your obligations. Self-written: you still ship libraries you did not write, so the dependency inventory (BIR-5.5) still applies at a lighter level. Commissioned: the entire BIR-5: Code Custody course is mandatory because payment alone may not establish ownership. Tool-generated: send the tool's output-ownership terms to counsel through BIR-5.2, and arrange bought review through BIR-5.6. Inherited or acquired: run the buyer's kill-check (BIR-22.5) retroactively, then rebuild custody through BIR-5. Declare origins per product and, when necessary, per component; mixed origins are common. Record the declaration beside your licensing-path record (BIR-8.1) and test it with three questions: Can I rebuild it? (no or unknown: BIR-5.4), Do I own it? (unsure: BIR-5.2), and Do I understand what it does? (no: BIR-5.6). You remain responsible for the product in every case, but the answers change your next steps. Expected Impact: One Origin and Inheritance Record per product - origin named (mixed allowed), three honesty questions answered, every "no" or "unsure" routed to its lesson with a date, and the declaration line recorded where your ops docs live.

https://tradingvendoracademy.com/lessons/bir-1-2 2026-10-08T00:00:00Z

Code is only one part of vendor readiness. Unclear promises, fragile fulfillment, weak compliance controls, or too little support capacity can block a launch even when the product works. Use the worksheet to score product, technical, business and compliance, and personal readiness. Your result is a go / no-go decision plus the Top 3 fixes to complete before you take on more customers. Expected Impact: By the end of this lesson you have a completed 20-question Fit Score with four section totals and a grand total, a written go/no-go decision routed by your score band, and a dated Top 3 fixes list with an owner and a due date on each item.

https://tradingvendoracademy.com/lessons/bir-10-1 2026-10-08T00:00:00Z

Four layers of rules can reach a trading-software vendor, each by a different mechanism. Layer 1 - general law - binds everyone, always: honest claims are the floor, whatever you are registered as. Layer 2 - registration-based regulation - binds by status: whether your activities put status in play - personalized recommendations, account authority, tailored signals - routes to qualified counsel on any yes or near-yes before the activity continues or ships. Layer 3 - partner-carried rules - bind by relationship: your NFA-Member partners carry obligations your material can activate - your promotional audio/video with specific trading recommendations or reference to past or achievable profits, used or directly benefited from by a Member, can create their filing obligation - so partner-safe is a business requirement even where no rule names you. Layer 4 - platform contract - binds by agreement and can be stricter than law: no money claim runs until the platform's compliance department has verified it in writing - record each platform rule as verified in writing or pending verification, and chase every pending line to verified. Disclaimer text is authority-specific; BIR-11.1 carries the texts. What you sell is the gate's second axis: the category rows below - copier, signals, subscription research, automated execution, education-adjacent, cross-border - each carry their own questions and counsel triggers, and never any disclaimer language. A product in several rows answers every one of them, and a program you run that pays customers on their trading is a counsel trigger in any row. Fill the Compliance Scope Record once; every claims decision downstream reads it. Expected Impact: One filled Compliance Scope Record: your position in each layer with its mechanism, the counsel-trigger list answered honestly, the triggers of every category row your product touches answered with it, a partner census with the carried-rules flags, platform rules verified in writing (or marked pending verification), and the authority-to-surface disclaimer mapping that BIR-11.1's texts execute.

https://tradingvendoracademy.com/lessons/bir-10-2 2026-10-08T00:00:00Z

Stop selling outcomes. Sell what you control. In the next 5 minutes, you will scan your top marketing surfaces for "red flag" words (guaranteed, risk-free, best, profitable, partner, approved, and the rest) and replace them with feature- and process-based language. Then you will label and disclose anything that looks like performance (backtests, sim results, trade screenshots) and hold any testimonial carrying a money claim - a dollar amount, P&L figure, win rate, passed evaluation, or funded-account result - until your platform's compliance department has verified it; a disclosure block is not a safe harbor. The scan produces an inspectable copy record: the public claim, its supported feature or workflow replacement, and the date changed. Reuse that record and the Copy Library at later launches, while every new or revised money claim receives written platform-compliance verification before publication. Sources include platform vendor guidance and the scoped promotional standards discussed below. What success looks like: A search for red-flag words on your site returns zero matches outside the disclaimer and disclosure text you are required to carry. Your headline describes utility (what it does) instead of certainty (what you will earn). Any simulated/backtest "results" are clearly labeled and carry the disclaimer text your governing authority prescribes for that surface (BIR-10.1 records which one that is). Expected Impact: The term-by-term scan records matches on the actual public pages and their replacements or removals, with required disclosure text preserved. Save the before-and-after evidence and the version-specific money-claim verification. A clean scan confirms that inspection result; later compliance questions remain subject to their actual review. Keep two evidence entries separate: the dated pages and terms inspected, and the applicable written verification of a particular claim version. The first shows the editorial work performed; the second records the outside answer actually received. Neither entry supplies an answer about a different version, a listing decision or legal liability.

https://tradingvendoracademy.com/lessons/bir-10-3 2026-10-08T00:00:00Z

Your biggest risks are rarely technical bugs. They are business-ending events: getting removed from a platform directory after a compliance review, getting banned by a payment processor, accidentally collecting customer financial PII in logs, or getting pulled into an indemnification dispute. Use the applicable published guidance and actual notices as evidence for the next action; a risk category does not establish a platform or regulator motive or a future outcome. Your job is to stop doing panic checks and start running a short, repeatable risk scan. In 5 minutes, you will identify your top 3 risks. In 15 minutes, you will create a simple risk register and a recurring calendar cadence with dated evidence and open actions for the next review. Compliance becomes scheduled work. Expected Impact: After this lesson, your risk register names your top 3 business-ending risks - each with an assigned owner and one next action - and your calendar holds at least one recurring Risk Scan reminder, so you can answer "What could take us offline this month?" in under 60 seconds instead of launching a panic sweep.

https://tradingvendoracademy.com/lessons/bir-10-4 2026-10-08T00:00:00Z

Rule out the ecosystem before you blame the platform, then send one clean packet engineering can act on. Before you write a word, screen for a recent platform update, a feed incident, and rollover week. State impact using the vendor's own P0-to-P3 definitions in this template, with the known headcount recorded separately. Then build the packet: the exact build, reproduction steps written like a recipe, a clean-environment reproduction run outside session hours, the smallest relevant log and trace files after scrubbing sensitive data (vendor-side - see BIR-10.5 and the Diagnostic Ladder in TB-1), and a minimal code sample if it is an API behavior issue. If clean-environment tests place the failure inside another vendor's product the customer also uses, send that vendor's support the same packet and tell the customer, in plain facts, which product owns the fix. Expected Impact: Your next escalation is more likely to get a response that engages your reproduction steps instead of a request for basics, because your first message already carries the build numbers, the ruled-out ecosystem triggers, and the severity call support would otherwise have to ask for. (This reflects standard bug-reporting best practices and the platform support protocols referenced below.)

https://tradingvendoracademy.com/lessons/bir-10-6 2026-10-08T00:00:00Z

Compliance works best on a cadence. Platform review can reach your directory listing, website, social media, and email marketing. Do not assume it comes with a schedule. NinjaTrader's published partner guidelines say a NinjaTrader Ecosystem representative will be reviewing all partner sites "on an on-going basis to ensure quality standards are being met"; read in full on 2026-08-02, the guidelines name no review cycle, notice, appeal or consequence beyond that clause. Because the guidelines publish no cadence, set your own. The dated reading establishes the published clause, while notice practice and review consequences remain unspecified; record an actual notice when one arrives. Run a small pre-audit on a schedule and before every launch or major copy update. Check the same four things every time: 1. Claims language 2. Performance and testimonials 3. Disclosures (risk + hypothetical, when applicable) 4. Trademark and endorsement signals What success looks like: You can answer "Are we review-ready?" in under 10 minutes, and you have a dated evidence folder with screenshots and notes. Expected Impact: After this lesson, your calendar holds the three recurring compliance events (monthly hot-word scan, quarterly pre-audit, and pre-launch audit), your pre-audit checklist has been run once end-to-end with every item marked review-ready or logged as a fix, and your dated evidence folder holds the before/after screenshots - so you can answer "Are we review-ready, and what changed and when?" straight from your audit log instead of scrambling when a review notice lands. Alt text: "Running a compliance cadence: Flowchart showing monthly scan, quarterly audit, and pre-launch audit in a repeating loop."

https://tradingvendoracademy.com/lessons/bir-10-7 2026-10-08T00:00:00Z

The 2025 headlines were true but narrow: the FTC's amended Negative Option Rule - the "Click to Cancel" mandate - was vacated in full by the Eighth Circuit on July 8, 2025, on procedural grounds; the court pointedly did not bless hard-to-cancel practices, and enforcement continues under everything that survived. The FTC restarted the rulemaking with a new Federal Register notice in early 2026. What survived is plenty. The federal baseline, ROSCA (the Restore Online Shoppers' Confidence Act), requires any online negative-option seller to clearly and conspicuously disclose all material terms before obtaining billing information, to obtain the consumer's express informed consent before charging, and to provide "simple mechanisms" to stop recurring charges. The safe build puts the recurring price, billing frequency, and how to cancel at the payment button, not buried in linked terms; whether a given placement meets the statute is your counsel's call. The strictest state standard - California's Auto-Renewal Law (§ 17602) - is what a nationally selling vendor realistically engineers to: affirmative consent to the offer terms, an acknowledgment with cancellation instructions, advance notice 15 to 45 days before an annual renewal (the receipt after the charge does not count), online cancellation via a prominent link when signup was online, annual reminders, and consent records retained. A third layer is not law at all: your card network's subscription Standards arrive through your acquirer's merchant agreement, and Mastercard's add a cancellation-instructions notice 3 to 7 days before the billing date - a different notice on a different clock from California's, triggered by a condition Mastercard's own document states two contradictory ways. Both statements reach annual plans - the rule text through its condition, the FAQ through its own examples - and the semi-annual plan sits on the rule text's 180-day edge but is named outright in the FAQ, so if you bill annually or semi-annually, send the notice. Many small vendors create an asymmetry: a frictionless payment-link checkout paired with email-only cancellation. Record the medium shift, human wait and effective date in a real test. Inspect the subscription-management facilities actually available through the processor, configure the supported cancellation route and verify its result. Plan product access separately, preserving paid time. Whether a specific flow complies stays counsel's determination; a working portal is evidence of a tested billing stop, not completion of every access or legal question. Expected Impact: One filled Subscription Compliance Worksheet covering every recurring SKU: disclosure-at-the-button verified by screenshot, consent evidence produced and retained, cancellation parity fixed or scheduled, the annual advance notice automated inside the 15-45 day window, the card-network notice scheduled 3 to 7 days out on any annual or semi-annual plan, and counsel flagged where any answer is unsure.

https://tradingvendoracademy.com/lessons/bir-10-9 2026-10-08T00:00:00Z

You can do content marketing without drifting into trading advice by building hard guardrails: keep content one-to-many and impersonal, remove profit projections and "almost certain" claims, use clear disclosures when you reference hypothetical or simulated results, and treat any money claim (a P&L figure, a win rate, a passed evaluation, a funded-account result, or a result stated in points, ticks, or R multiples) as something you verify with your platform's compliance department before it appears anywhere, because the disclosure block is not a safe harbor. The points, ticks and R-multiple extension is this lesson’s own review rule, not a definition attributed to a regulator or platform. Record written compliance verification for the actual claim before publication. Then script your support team to redirect any "tell me what to trade" question into platform tutorials. This aligns with the "publisher style" posture (general, impersonal, regular circulation) and avoids the common trap of thinking "training purposes only" labels protect you. Expected Impact: After this lesson, your highest-traffic marketing asset passes the 2-minute pre-publish checklist: zero profit-projection or certainty words in the copy, a No-Advice boundary line next to the first call-to-action, and a results-context label beside every chart. And your next "what should I trade?" message gets the saved support macro reply in under 2 minutes, with no one on your team improvising trade advice.

https://tradingvendoracademy.com/lessons/bir-11-2 2026-10-08T00:00:00Z

For an ordinary "scam / I paid and got nothing" complaint, reply publicly fast, move the conversation into a ticket, verify fulfillment (payment, provisioning, entitlement, activation), and either fix it or refund it. Use the same triage regardless of prose or tone. Active threats, doxxing, legal demands, regulatory threats, and filed chargebacks escalate instead. Then install a small permanent system: an immediate acknowledgment, a stated sub-24-hour deadline for the substantive response, an "activation gap" message, and a trigger log. These address silence and uncertainty; measure whether complaints recur rather than promising they will stop. Success looks like: the next ordinary "where is my access" complaint has an acknowledgment requesting the relevant fields, a substantive response within your stated deadline, and a recorded fulfillment result or next check. The customer may still need to supply information; one-reply resolution and a changed review are not guaranteed. Expected Impact: A tested auto-responder immediately acknowledges new messages and states the promised sub-24-hour substantive-response deadline. For ordinary review triage, measure the public reply against a 2-hour target and the fulfillment check against a 10-minute target. Record what the check established and any unresolved next step; missing evidence can require follow-up. Use the trigger log to evaluate whether operational fixes reduce repeat complaints. Alt text: "Review triage flow: A simple flowchart showing public reply, ticket resolution, and root cause logging."

https://tradingvendoracademy.com/lessons/bir-11-3 2026-10-08T00:00:00Z

Documentation is not a "nice to have." In trading software, it's a credibility test. Clear setup steps, prerequisites (data feed, platform version), troubleshooting, and "what to do when things break" let the customer compare the expected running result with what actually happened. A completed setup demonstrates that observed result; an incomplete setup identifies the next check or support request. In 15 minutes, you can add three trust signals: (1) a single Start Here page with screenshots, (2) a Connectivity + Requirements page, and (3) a Troubleshooting + Logs page, each with a "Last updated" date and a small changelog link. Models like Bookmap's segmented knowledge base (Getting Started, Connectivity, Troubleshooting, Learning Center) show how clear, maintained documentation can build trust without hype and reduce onboarding friction. Expected Impact: After this lesson your docs carry three visible trust signals a buyer can see on the page - a Start Here page with the 4-step checklist (Install - Activate - Connect data - Verify) and a "Last updated" date, a Connectivity + Requirements page naming your supported feeds/brokers, and a Troubleshooting page built from your real top ticket phrases - each linked to a small changelog. Check the next ticket for whether the customer found the instructions and whether the expected running result was confirmed; record any unresolved step separately.

https://tradingvendoracademy.com/lessons/bir-11-4 2026-10-08T00:00:00Z

When support is slow or unclear, customers assume the worst. That turns normal friction into refund requests, chargebacks, and "scam" posts. Then those posts create more tickets from new buyers asking if you are legit. More marketing will not repair that loop; a fast, predictable support and refund flow will. Acknowledge every request quickly, verify purchase and environment in one pass, choose a clear path (fix or refund), and respond publicly to reviews with a calm "take it offline" script. Vendors who tighten first reply time and standardize refund handling typically see fewer duplicate follow-ups, fewer chargeback threats, and fewer "ghosting" accusations that damage reputation. Expected Impact: After this lesson your support runs on four saved artifacts a customer or auditor can see: a two-tier SLA firing inside your auto-reply, three saved macros (acknowledge / fix-steps / refund-decision) ready to insert, a Refund Decision Snapshot attached to your next refund ticket, and a written first-reply-time baseline you can compare against next week. You can confirm it worked on your next high-risk thread: the acknowledgement goes out from the auto-reply and the refund reply comes from a saved macro instead of a from-scratch email. Alt text: "Understanding the reputation loop: arrows linking slow support replies to refunds, negative reviews, and increased ticket volume."

https://tradingvendoracademy.com/lessons/bir-11-5 2026-10-08T00:00:00Z

Partner trust is fragile. When a platform flags you, you do two things fast: (1) remove the trigger from public view, and (2) respond with a clean, documented plan. Then organize the evidence and recurring checks in a small "Partner Health Binder": a single folder containing your risk disclosures, proof for hypotheticals, testimonial disclosures, marketing approvals, corporate verification documents, and a one-page note on who holds licensing authority and what they can still do for a customer if the listing gets paused. Keep the response fast, transparent, and consistent. Expected Impact: After this lesson you have a Partner Health Binder holding your disclosures, a dated promotional-material archive, your marketing approvals, and your corporate verification documents in one searchable place, plus a licensing-continuity note naming the two people who can restore a customer's access (issue a key, reset an entitlement, or re-bind a Machine ID - whichever your recorded licensing path uses) and recording which of those your licensing setup still allows while the partner account is paused, a Marketing Approval Log with at least one entry, and a monthly Partner Health Check on your calendar. You can confirm it worked on the next partner request: you answer it straight from the binder's saved files instead of hunting across email threads.

https://tradingvendoracademy.com/lessons/bir-12-1 2026-10-08T00:00:00Z

Your "First Win" is the first value moment a buyer can see on-screen, fast, without guessing. In trading software, that is usually: license validates, tool loads, and the customer sees it working on a chart (not a profit claim). You build a First Win System by choosing one "golden path," removing choices, and measuring whether people reach it quickly. Use under 30 minutes and 85% or higher activation as aspirational general-software benchmarks, then measure your actual product and refine its targets. These are not trading-vendor guarantees. Trading-vendor data is scarce, so both figures come from general software-onboarding research; FinTech and desktop-trading baselines actually run far lower, so treat these as aspirational goals. They still matter here because the customer base churns hard and early. If many traders quit within the first month, you do not have weeks to "educate them later." You have days. Expected Impact: After this lesson, your Day 0 welcome email opens with a one-sentence First Win (customer action + on-screen proof + license state) followed by a 3-step Golden Path, and a Day-3 "Trouble installing?" safety-net message is drafted for buyers who never activate. You can verify it: open your welcome email and confirm the First Win sentence sits in the first three lines, followed by exactly three steps with no branching options.

https://tradingvendoracademy.com/lessons/bir-12-2 2026-10-08T00:00:00Z

Your onboarding sequence is not "marketing." It is your Time-to-Value (TTV) infrastructure. In desktop trading platforms, the first mile is high-friction and users churn fast, often within the first month if they do not reach value quickly. General-software onboarding benchmarks (activation around 85%, time-to-activation under 30 minutes) sit far above FinTech and desktop-trading baselines; steer toward them, do not expect them. Build a 72-hour sequence with one job: get them to first successful load on a chart, fast. Use four branches: Activated, Not Activated, Trial / Re-Bind Needed, and Needs Human Help. Your first email delivers the asset (download, license, exact next step) and fires immediately. Your Reminder and Safety Net emails are install work, so they land outside regular trading hours: a buyer mid-session will not import an add-on into a platform that is running a position, let alone restart it when asked, and a mid-session send burns the safety net's only good shot. Expected Impact: After this lesson, every new purchase auto-sends Email 0 (download, license, and one exact next step) within minutes, the Reminder and Safety Net follow-ups are scheduled to land outside the regular session, and each new buyer sits in exactly one named branch (Activated, Not Activated, Trial / Re-Bind Needed, or Needs Human Help) that you can point to in your CRM.

https://tradingvendoracademy.com/lessons/bir-12-3 2026-10-08T00:00:00Z

You cannot fix what you cannot verify. This checklist gives you a fast pass/fail way to confirm setup is actually complete: entitlement and identity match, the correct package was installed the correct way, the tool appears in the platform list, it loads on a chart without errors, and (if applicable) the license validates and stays validated. A clean validation loop shortens time-to-value because delays strongly increase abandonment and churn risk. Activation rate and time-to-activation are among the most widely tracked onboarding KPIs in software, and this loop is what moves them. Success looks like: You collect one "green check" screenshot (tool loaded on a chart) plus one "proof pack" (email + version + error text if any), and you can record the pass, the missing evidence, or the complete packet for escalation from that loop. Expected Impact: After this lesson, your support tool holds a saved Setup Validation - Proof Pack macro and a one-screen "Setup Complete" pass/fail checklist, so the first request for your next ordinary "installed but not working" ticket asks together for the three screenshots plus the copy/paste error text (if any) and login email - and the Machine ID too, if your recorded licensing path is machine-bound. Record any missing evidence for follow-up. You can verify it: open the saved macro and confirm it requests all three screenshots, the exact error text, the copy/paste identifier fields your path needs, and the line telling the customer to run the steps out of session.

https://tradingvendoracademy.com/lessons/bir-13-1 2026-10-08T00:00:00Z

A launch combines licensing, packaging, compliance surfaces, payment readiness, and support readiness. For the flight check, pick one release candidate build, run one entitled activation test, run one failure test with neither entitlement nor a remaining product trial (so you know the block path works), run one clean import test, and scan your disclaimers and support contact surfaces. If any must-pass gate fails, it is a no-go. Fix it before you flip the switch. Before the first paid sale, also tick the scorecard's PAYMENT READINESS rows. What success looks like: You can prove, with screenshots and logs, that (1) a paid user activates in under 2 minutes, (2) an unpaid user with no free trial left is blocked gracefully with correct support info, (3) a clean machine imports without errors, and (4) your required risk and independence disclaimers are visible where customers will actually see them. Expected Impact: A completed go/no-go scorecard for your frozen release candidate, backed by screenshots that prove three things: an entitled user activates, a test user with neither entitlement nor a remaining product trial is blocked cleanly with your correct support contact visible, and a clean machine imports without errors. Any must-pass gate that fails is a documented NO-GO you can act on before you flip the listing live.

https://tradingvendoracademy.com/lessons/bir-14-1 2026-10-08T00:00:00Z

Your warm positioning sentence usually fails as a cold-audience hook because it assumes context, category awareness, and intent the stranger does not have. First impressions form almost instantly, and the highest probability of a cold reader abandoning you is in the very first seconds - research on web dwell time shows attention follows a "negative aging" pattern where most visitors who bail do so early, before they've read anything carefully. So the hook has one job: let a stranger decode what it is, who it's for, and why they'd care in a single read. You pick one job-to-be-done (not a feature list), phrase your difference as a tradeoff you chose rather than a competitor you beat, and frame the value around an operational pain the reader wants to avoid - not a profit they'll gain, which is exactly where hooks drift into performance-claim territory. Then you gate it: every hook and variant runs through the BIR-10.9 kill-words / No-Advice boundary, BIR-10.2 partner-safe check, and the BIR-10.6 publish gate before it appears anywhere. Expected Impact: You finish with one primary discovery hook plus two to three variants on the Discovery Hook Canvas, a thin message-test winner between two wordings, Cleared statuses for every shipping line, one Primary on the Channel Priority Scorecard, and a one-page MVAP Sketch naming entry surface and CTA. Those are outcomes you can verify yourself in an afternoon - not a conversion percentage. (Any attention or conversion figure you see quoted for this niche is a general SaaS or web-usability analogy, not a trading-vendor-specific benchmark; treat it as directional only.)

https://tradingvendoracademy.com/lessons/bir-14-10 2026-10-08T00:00:00Z

Partnerships can be a high-leverage top-of-funnel channel when trust, audience fit, and claim control are strong, because you borrow attention you did not have to buy. But every partner you recruit becomes a new publisher of your claims, and the vendor must review the partner’s claims and disclosure before release and keep the actual publication evidence. Questions about the applicable legal responsibility go to qualified counsel. So the play is: pick ONE channel this quarter, qualify the target before you attach your brand, and put a prohibited-claims list into the recruiting conversation itself. For seeding, give the tool "no strings" and make disclosure a condition of the seed. For prop-firm distribution, score the firm's durability before you co-market, because the sector is volatile and reputational spillover is real. For affiliates and JV partners, vet the partner's existing content posture before you generate a tracking link - if they already make claims you cannot own, they are disqualified. Then route every partner-facing asset through the compliance gate and hand the running program off to operations. The FTC's revised endorsement guides (16 CFR Part 255) make product seeding itself a disclosure obligation for the brand, and the cited FTC 2025 inflation-adjustment notice records a $53,088 maximum for the covered violations; this is a dated figure, not the current amount or a determination that a particular endorsement incurs it. Verify the applicable current authority and amount with qualified counsel. A 2025 industry analysis of the prop-trading sector describes heavy attrition - a meaningful share of operators shut down or froze payouts in recent years. Those are reasons to qualify before you attach, not after. Expected Impact: A written go/no-go on ONE partnership channel within 48 hours, and a prohibited-claims list embedded in every partner-facing asset before any seed license, listing request, or tracking link leaves your hands - verifiable by opening the asset and finding the list present. (No conversion or revenue promise: partnership outcomes depend on the partner's audience, which you do not control.)

https://tradingvendoracademy.com/lessons/bir-14-12 2026-10-08T00:00:00Z

Paid accelerates a cleared hook and honest landing: it does not replace them. Pass four gates (claims, hook, capacity, kill-budget), then pick one channel, before spend. Prefer marketplace promo or native sponsorship before cold search. Plan for missing campaign parameters after redirects or off-site checkout: test the relevant path, capture campaign ids before the buyer leaves, and keep a dual ledger (paid last-click + buyer-stated source). Frame ads as charting / risk / workflow capability; Google’s documented examples include bans on trading signals, tips, or speculative trading information. Kill creatives that drift into performance promises. Prefer no ROAS number over a borrowed SaaS claim. Expected Impact: You finish with a one-page Paid Experiment Sheet: go/no-go status, channel choice, budget cap, three creative variants cleared against BIR-10.9 / BIR-10.2 / BIR-10.6, UTM convention + pre-checkout capture note, and a weekly log of spend → clicks → trials/starts you can verify yourself, not a promised ROAS.

https://tradingvendoracademy.com/lessons/bir-14-14 2026-10-08T00:00:00Z

Your delivery model is somebody's published breach. The normal way to ship an automated tool in this category - code that runs unattended, hosted where it stays up while the trader sleeps - is addressed by name in firms' rule pages, and the answers differ per firm and per program. Topstep's TopstepX API Access article, updated 17 September 2026, states: "All trading activity must originate from your personal device. The use of VPS, VPNs, and remote servers is prohibited by Topstep's Terms of Use"; on the same page, it says, "Running automation on a VPS can result in account suspension or removal from the program". Yet the same firm sells API access at $29 a month through ProjectX. FTMO publishes a hard numeric ceiling instead of a ban, and reaches conduct done "knowingly or unknowingly". Apex Trader Funding publishes a flat prohibition on automation across all account types and the sentence "We strongly encourage the submission of your software for approval before use" - an open door most vendors never knock on. Three named firms, three different answers, and inside one of them the answer changes by account stage. Two things follow that no rate card or partnership conversation will tell you. First, the passive breach - this academy's own term, used by no firm - is the case where your tool executes exactly as coded and a rule breaks anyway, by volume, by silence, by deployment, or by a limit that moved. What your other customers do is an exposure beside it, and whether that breaches anything is a question to put to the firm in writing. Second, a vendor's unit economics and their compliance exposure are the same variable: selling one tool to many traders inside one firm's ecosystem is precisely what you are trying to do, and it is precisely the shape that a per-strategy capital cap and a copier-responsibility clause describe. Where a firm has not said how such a clause applies to your customers, that is a question to put to it in writing, not one to answer with a guess. So the work is: read the rule pages of the firms your customers actually use, before you design; ask the firms that publish an approval path; disclose the constraint to buyers rather than letting them find it in a support ticket; and re-check, on a date, because these pages change without notice. Expected Impact: One dated Rule Surface Read per firm covering a meaningful share of your customers, a named verdict on your deployment model for each, one buyer-facing disclosure sentence live on your sales page and in your setup guide, and a re-check date on the calendar - all verifiable by opening the worksheet and finding a date, a scope, and a source URL on every line.

https://tradingvendoracademy.com/lessons/bir-14-3 2026-10-08T00:00:00Z

Price a listing surface on six dimensions, not one. (1) Take rate and fixed costs: published shapes differ radically - one major closed marketplace takes a flat 20% with USD-only pricing; TradingView announced on September 30, 2026 that from November 1, 2026 it no longer permits selling invite-only script access, or including it in another paid product or service, and that script sales move to its Marketplace - read its take from its current terms on the day you price the channel; and the NinjaTrader ecosystem's direct-sale terms are negotiated per vendor agreement rather than published platform-wide - the honest finding, verify yours with the platform. (2) Payout friction: published holds and cycles (a seven-day dispute-monitoring hold on one surface; monthly payout cycles with processor minimums and validation holds on the documented affiliate stream) belong in your cash-flow plan, not your surprise file. (3) Tax posture: who is merchant of record differs by surface and by buyer jurisdiction - one platform remits EU VAT for you and leaves the rest to you; record every other surface's answer in its own current, dated words. (4) The language and review process: record the applicable listing requirements and written answers for each surface. Every money claim is verified in writing with the platform's compliance department before use, and a disclosure is not a safe harbor. Carry any unanswered claim or professional scope question as OPEN; use the BIR-10.1 scope record and BIR-10.2 copy library. (5) The licensing mandate: some surfaces dictate the licensing path you may use there - the closed marketplace prohibits external license systems entirely (no external calls, hardware-locked native activation only), which overrides the path your BIR-8.1 record names for that platform - TB-2 is where the per-surface reality gets mapped. (6) Reach and exit terms: the same closed marketplace bars using it as a funnel to off-platform sales; TradingView asserts jurisdiction over your conduct "on TradingView or elsewhere" - your external funnels can cost you the channel; and exit portability (what customer relationships, licenses, and reviews leave with you) is decided by these terms long before you think about leaving. The worksheet prices all six, then asks the two veto questions - licensing survival and claims survival - because a channel that fails either is not cheap at any commission rate. Expected Impact: One filled Channel Economics Worksheet per surface you are on or considering: six dimensions priced from current official documents, an effective-take estimate that includes payment-ops burden and friction, both veto questions answered against your BIR-8.1 and BIR-10.1 records, and the exit-portability line written.

https://tradingvendoracademy.com/lessons/bir-14-4 2026-10-08T00:00:00Z

Treat a marketplace listing as an acquisition channel first, whether or not the surface also runs the checkout. Pick an anchor surface where your audience already browses and installs (for most futures vendors, the NinjaTrader Ecosystem is the mature, vendor-friendly anchor, with its User App Share for free-tool discovery), let it work beside your own site and channels, and measure what share of your buyers it brings by asking each new buyer where they found you (buyer-stated source, BIR-14.12). Score two or three cross-platform candidates instead of listing everywhere, and lead with a free or low-friction entry offer (a lite tool or a native free trial) to build install velocity rather than dropping your flagship on a public shelf. Prefer the Free-Tool Flywheel when you can: one honest lite utility that simultaneously serves as marketplace entry offer, User App Share presence, and (with consent) the lead magnet in BIR-14.7: one build, three surfaces. Every surface has hard acceptance rules (TradingView, for example, moderates its Public Library aggressively and rejects listings for things like misleading claims, and it does not want "Free" advertised in the description of scripts that are already free), so match your copy to the surface, and gate every word through BIR-10.2, BIR-10.9, and BIR-10.6 before you submit. Reviews can improve buyer trust and may influence visibility on some surfaces; verify each marketplace's current ranking and solicitation rules. Solicited reviews are governed by the FTC endorsement guides and the Consumer Reviews and Testimonials Rule, so route review requests through BIR-4.3: Ethical Value Proof Pack, with claim guardrails in BIR-10.9 and BIR-10.2. Use operational wins by default. Before using any money claim in a listing, screenshot, or testimonial, such as a P&L figure, a passed evaluation, or a funded-account result, obtain written confirmation from your platform's compliance department that it is permitted before use; a disclosure does not replace that verification. Expected Impact: One anchor-surface submission has a dated pre-submit checklist showing cleared copy and publish-gate checks, the selected entry offer, and a tracked platform response. Record a live listing URL only if accepted and published; submission does not guarantee acceptance or conversion lift.

https://tradingvendoracademy.com/lessons/bir-14-5 2026-10-08T00:00:00Z

Stop trying to originate a fresh video every day. Run an engine: record one 8-15 minute screen-shared tutorial per week - the anchor - built entirely around demonstrating utility ("how to configure a trailing-stop automation in NinjaTrader using our tool"), never around market calls or profit. In the same sitting, slice 3-5 self-contained moments out of that anchor into 9:16 vertical short-form clips for YouTube Shorts, TikTok, and Reels. Record after the cash close or on the weekend, and never publish into the Sunday Globex reopen or a rollover morning. Publish windows are named slots: post-close, weekend, or pre-open. Batch a few anchors ahead to provide a recorded reserve for a busy week, and fill those slots from the ecosystem calendar - the release-wave reconfigure, the rollover workflow, the reinstall-after-Windows-update walkthrough - so the engine's output doubles as ticket deflection. Before anything publishes, run a thin video-specific pre-publish gate that terminates in the compliance gate (partner-safe wording, the No-Advice/Content Risk Ladder gate, and the publish gate). Treat cadence and format numbers as operator heuristics, not guarantees - and verify every platform spec against that platform's own current documentation, because they change. Expected Impact: One recorded anchor session yields a full week of published assets - one long-form video plus 3-5 shorts - and every single one carries a checkmark in a dated content log showing it passed the video pre-publish gate before going live. You can verify it in one glance: no un-gated asset ever ships, and you have a runway of at least one anchor recorded ahead.

https://tradingvendoracademy.com/lessons/bir-14-6 2026-10-08T00:00:00Z

Spend your search effort where the buyer is closest to deciding, not where the volume is biggest. That means three bottom-of-funnel intent buckets: branded (your product name and its variations), comparison ("best order flow indicator for NinjaTrader," "[Product] vs [Competitor]," "[Competitor] alternative"), and problem-to-tool ("how to see volume delta in NinjaTrader"). Own your own name first - it is the lowest-risk, highest-leverage SEO a vendor can do, and it is your defense against clones and reputation searches. Build comparison pages on operational facts a vendor can honestly attest to (features, requirements, support, licensing, price transparency) - not on profitability rows or "we win every row": a profitability figure about your own tool is a money claim, which means written platform-compliance verification before it appears anywhere, while a competitor's profitability is something you cannot verify at all. Let the docs you already maintain (BIR-11.3) do double duty as findable pages. Treat AI Overview / AI-answer citation as an outcome of the same pages, not a separate project: same SEO rigor; no GEO hacks. Then route every page through the BIR-10.9 pre-publish checklist and the BIR-10.6 cadence before it ships. The mechanism, not a magic metric: a person searching your product name or "[X] vs [Y] for NinjaTrader" is far further down the buying path than someone searching a broad strategy term - so a small, winnable set of these pages tends to convert better per visit than chasing head terms you cannot win. (This is the intent logic behind the classic Broder search-intent taxonomy, not a trading-vendor conversion statistic - we do not have a reliable public benchmark for this niche.) Expected Impact: A verifiable end state you can check yourself within a week: (1) a dated record of the actual results for your exact product name and your canonical page’s position; (2) a completed Query Triage worksheet with each candidate query tagged by intent and mapped to exactly one target asset; and (3) a dated pass on the BIR-10.9 pre-publish checklist for every comparison or "best" page before publication. Pages, factual evidence and gate decisions are the deliverables; ranking changes are observations to record.

https://tradingvendoracademy.com/lessons/bir-14-9 2026-10-08T00:00:00Z

You earn discovery in rooms you do not own by leading with value and using each venue's current written rules as the permission record you look up before posting. Every venue is different: futures.io has an explicit tiered vendor/Elite structure; Reddit is decentralized (the widely cited 90/10 self-promo guideline is rooted in Reddiquette, but each subreddit sets its own rules, and some - like r/algotrading - ban all promotion); third-party Discord servers may confine promotion to a designated channel or forbid unsolicited DMs; record the target server's actual rule; fintwit has no gatekeeper but sits inside FTC disclosure enforcement. Across all of them, you contribute far more than you promote, you disclose that you are the vendor whenever you name your product, you never sock-puppet or buy engagement, and you never speak for NinjaTrader or drift into "what should I trade." Then you route each promotional post through your existing compliance gates before it ships. Expected Impact: A written per-venue rule log for every community you post in, and a vendor-disclosure line on every product mention - verifiable by re-reading your last ten posts and finding (1) zero undisclosed product mentions and (2) zero venues you posted in without a saved rule entry. No conversion or ROI number is claimed here; attribution in community channels is fuzzy, so you measure with directional signals only (see Root Fix Step 6).

https://tradingvendoracademy.com/lessons/bir-15-2 2026-10-08T00:00:00Z

Retention has two immediate levers: (1) reduce involuntary churn from failed payments with dunning and retries, and (2) address the Day 30 drop-off with a short onboarding sequence that gets customers to "first value" quickly. In many subscription businesses, failed payments drive a meaningful share of churn, and strong dunning programs recover a real portion of what would otherwise be lost - the published medians all come from dunning vendors measuring their own customers, so measure your own rate rather than borrowing theirs. Together, these measures reduce avoidable churn while you improve the product and documentation. Expected Impact: By the end of this lesson you can point to four live artifacts and verify each exists: a one-page Retention Scoreboard with all five numbers filled in for this week, a dunning sequence applied to every account currently marked "past due" with its suspension step scheduled after the cash close, a 5-touch onboarding sequence scheduled for every new buyer, and a cancel-reason question every canceling customer sees, answered or skipped, that never blocks the cancellation.

https://tradingvendoracademy.com/lessons/bir-15-3 2026-10-08T00:00:00Z

Run a listing iteration every 90 days, and sooner, within two weeks of a platform release wave or a contract rollover, because that is when screenshots go stale and version questions arrive. Score the listing for clarity and compliance, and name your tested platform version, verified data feeds, prop-firm eval status, and licensing model. Then call each channel Green (keep or scale), Pause (fix listing), or Kill (stop spend). If you test paid traffic, define an activated customer as one whose entitlement is bound and whose first chart has loaded, not as someone who merely completed checkout. Stop when the cost per activated customer exceeds what BIR-18.4 says you can afford. Scale a Green paid channel one budget step at a time: a fresh guardrails worksheet, re-cleared creative, and a support-capacity check before each step. Log results on the BIR-19.5 scorecard. Expected Impact: By the end of this lesson you can point to a completed Listing Iteration Scorecard: every row marked Pass/Fail, including the named platform version, data feeds, prop-firm eval status, and licensing model, plus one single-variable change for this sprint, and a Green / Pause / Kill status for each active channel. If you test paid traffic, you also have a Paid Test Spend Guardrails worksheet whose CAC stop is computed per activated customer against your BIR-18.4 ceiling. Your next review date sits on the calendar: 90 days out, or two weeks into the next release wave or rollover, whichever comes first.

https://tradingvendoracademy.com/lessons/bir-15-4 2026-10-08T00:00:00Z

Affiliate growth without ops becomes compliance roulette. Stand up three pieces: a partner onboarding packet (disclosures, prohibited claims, support boundaries), a creative review log with weekly cadence for top-revenue partners, and support macros that reset expectations without debating in public. Set the payout rule from the sale type (recurring pays on schedule, a lifetime license is held until the refund window closes because there is no future stream to claw back from) and keep the clawback window at least as long as your refund window. Attribution has to land on the order that provisions the entitlement, and a clawback is not finished until that entitlement is off. Sunsetting is a documented three-strike process, and strikes come from creative, not from a refund cluster you have not yet tagged drawdown / failed eval versus creative overpromise. Expected Impact: By the end of this lesson you can point to three standing artifacts and verify each exists: an Affiliate Partner Ops checklist acknowledged (name + date) by every active partner, a Creative Review log with at least your top-revenue partner's live creative logged Pass/Fail with a fix deadline, and the three support macros saved in your helpdesk. Every active partner record names its type, its sale type (lifetime or recurring), and the matching payout and clawback window. You can open one affiliate-sourced order and see the partner code on the record that granted access, and one refunded affiliate order whose entitlement was deactivated before the commission reversed. Then your next "your affiliate promised" ticket gets the Expectation Reset macro reply, and any failing creative gets its tracking link paused with the Link Paused macro instead of an ad-hoc argument.

https://tradingvendoracademy.com/lessons/bir-16-1 2026-10-08T00:00:00Z

Build a simple 3-level ticket taxonomy (Category, Subcategory, Detail) and enforce one clear owner per ticket. Then add routing rules so tickets auto-assign based on category (Licensing, Billing, Connectivity, Bugs, How-to, Install). Give every ticket an owner and a bucket in the first reply so tickets stop bouncing and you can see patterns worth fixing. A good taxonomy is rooted in issue type (where the fix lives), not product line, because it maps directly to resolution workflows. What success looks like: New tickets stop landing in "Other," and you can filter your inbox by category in seconds. Expected Impact: A completed Support Routing One-Page with six Tier 1 categories, a named owner per category, and routing rules that auto-assign and promote session-critical tickets ahead of the queue. Your last 10 new tickets will each carry a Category, a Session Impact value, and an owner set in the first reply, with none parked in Other/General.

https://tradingvendoracademy.com/lessons/bir-16-2 2026-10-08T00:00:00Z

Build one place where every support macro lives, give every macro an ID and version, and stop editing inside random tickets. Start with your top repeated issues (licensing, connectivity, refunds). Create a Macro Index, paste your macros into a single canonical doc, add a version header and change log, then publish those macros into your helpdesk from the canonical source. Expected Impact: A canonical macro doc where every macro carries an MF-ID and version, a Macro Index covering your top 5 repeat reasons, and a Change Log with at least one dated entry, so your next repeat ticket is answered by pasting one versioned macro instead of rewriting it, with the same refund and licensing wording every time.

https://tradingvendoracademy.com/lessons/bir-17-3 2026-10-08T00:00:00Z

Build three Minimum Viable Runbooks today: Licensing, Release, and Support Triage. Put them in one place your team can find (your Single Source of Truth) and include copy-paste replies. Then assign an owner and a 15-minute monthly review to prevent documentation rot. Urgent operations will follow a checklist instead of relying on memory. Expected Impact: The next routine licensing or install ticket has a findable route through prerequisites, ordered actions, observed validation and escalation. Have the assigned person follow that route, record the actual outcome and repair any missing step. A completed runbook supports delegation; it does not guarantee resolution of every ticket.

https://tradingvendoracademy.com/lessons/bir-17-4 2026-10-08T00:00:00Z

Continuity planning should produce one outcome: someone else can keep your promises when you're unavailable. In 15 minutes, you can (1) name a Deputy, (2) write a one-page Continuity Card, and (3) start a Digital Asset Inventory so your Deputy knows what accounts exist and how to access them. The card starts the handover; another person becomes effective coverage only after the required access is available and they demonstrate the critical task. Expected Impact: Demonstrate that your Deputy can (a) reach the required systems with authorized access and (b) post an accurate customer status update before the next session open. Record any remaining access or task gaps rather than assume the card alone supplies complete coverage - the bar that matters when a licensing hiccup surfaces at the Sunday evening reopen. Increasing "bus factor" from 1 to 2+ is the measurable win.

https://tradingvendoracademy.com/lessons/bir-18-3 2026-10-08T00:00:00Z

Build a "margin reality snapshot" for the last full month using collected revenue, refunds, disputes, payment fees, and every recurring tool cost. Then calculate True Margin (%) and Spendable Cash (today). Exclude reserves and held receipts from spendable cash because they are unavailable this month. (BIR-18.2: Refund Reserve Planning covers how reserves work; this lesson counts what is currently spendable.) Expected Impact: You calculate two written numbers for your last full month - True Margin (%) and Spendable Cash (today), with pending/held funds excluded - and complete a Stack Ledger, a Margin Reality Snapshot, and a documented tooling decision: a justified cut or the specific prerequisite still unresolved. Verify it by confirming all four artifacts exist and your reserve/hold terms are recorded as a line rather than counted as spendable.

https://tradingvendoracademy.com/lessons/bir-18-5 2026-10-08T00:00:00Z

A risk register review is a short, recurring check that keeps your biggest risks visible, owned, and moving. Update your top 5 risks today by assigning each one an owner, score, and next review date. Then schedule a monthly review so changes in cash flow, compliance, or support load are recorded before they become urgent. Expected Impact: You complete a scored risk register containing your top 5 risks, each with one named owner, a likelihood-times-impact score, a leading indicator, and a next review date within 30 days. You also assign one dated mitigation task to the highest-scoring risk and schedule a recurring monthly Risk Register Review. Verify it by opening the register and confirming every top-5 risk shows an owner and a date and the review event exists. (The controls those risks point to live in BIR-18.1 and BIR-18.2; the network thresholds live in FIN-2.9: Dispute Ratio Health.)

https://tradingvendoracademy.com/lessons/bir-19-3 2026-10-08T00:00:00Z

Support collapse has measurable leading indicators. Pull four numbers from the last 7 days: tickets created, tickets solved, current backlog, and tickets older than 7 days. Calculate Kill Rate (solved divided by created) and the Old Ticket Tail (older-than-7-days tickets divided by backlog). A Kill Rate below 100% means fewer tickets were solved than created in that measured flow; check the current backlog and capacity rather than infer a fixed time to collapse. A growing old tail shows aging work is being deferred. Record the figures in a weekly scorecard with Yellow and Red triggers. Also flag observed NinjaTrader release updates, Windows patch dates, reported Machine-ID changes, data-feed incidents and reported account or VPS reimages. Record what the tickets show and when it happened; a nearby event does not establish an identifier mechanism or the cause of every ticket. Compare similar observed waves with structural trends. Expected Impact: By the end of this lesson you have a filled Support Collapse Scorecard for this week that covers Tickets Created, Tickets Solved, Kill Rate (Solved/Created), current backlog, and Old Tail % (Open >7d divided by backlog). Each Kill Rate and Old Tail value is mapped to a written Green/Yellow/Red threshold, so you can state this week's risk color in one sentence backed by those numbers.

https://tradingvendoracademy.com/lessons/bir-19-4 2026-10-08T00:00:00Z

Refund patterns can warn of reputation and dispute risk before either becomes severe. Calculate three trailing-30 figures: refund rate, fast refund percentage, and dispute ratio. Then tag the last 20 refunds with one reason code each to identify the first problem to address. Keep the figures and top reason on a one-page scorecard reviewed weekly. Expected Impact: By the end of this lesson you have a filled one-page Refund Risk Scorecard that lists your three trailing-30 numbers - refund rate, fast refund percentage, and dispute ratio - your last 20 refunds each tagged with a single reason code, a written refund-rate threshold, and a standing weekly 15-minute review with one owner-assigned fix. (The dispute-ratio thresholds and card-network monitoring programs themselves are covered in FIN-2.9: Dispute Ratio Health.)

https://tradingvendoracademy.com/lessons/bir-19-5 2026-10-08T00:00:00Z

Use a regular review rhythm to turn available signals into decisions. A 30-minute Weekly Ops Review covers support queue health, product stability, and payment risk. A quarterly QBR handles longer-term decisions such as entitlement modernization and onboarding fixes. Written thresholds tell the team when to pause normal work and protect the business. Success looks like: On any day, you can answer (in under 2 minutes): backlog trend, whether you are winning (Kill Rate >100%), whether stability is getting worse (crash spike), and whether payment risk is rising (dispute ratio trend). Expected Impact: By the end of this lesson you have a recurring Weekly Ops Review on your calendar with the agenda and red-line thresholds pasted into the invite, a "Metric Definitions - Single Source of Truth" doc, three one-click saved views (support, stability, payments), and a Weekly Growth Scorecard. On any day, you can then pull backlog trend, Kill Rate, crash spike, and dispute-ratio trend in under two minutes. (The specific dispute-ratio monitoring thresholds and card-network programs are covered in FIN-2.9: Dispute Ratio Health; the agenda below carries the action triggers.)

https://tradingvendoracademy.com/lessons/bir-2-1 2026-10-08T00:00:00Z

Without a one-page ecosystem map, each ticket requires you to trace the customer path from scratch. Map your distribution model (directory, marketplace, or invite-only), draw the happy path from purchase to working product, and mark every handoff where data moves between systems. Those handoffs are your ticket-magnet zones, especially licensing fulfillment through a manual allowlist, portal grant, invite, per-customer build, or payment-triggered provisioning. Multi-platform vendors should record a separate identifier for each platform; use TB-2: Platform Licensing Landscape Worksheet. With the map in front of you, route the ticket to a specific handoff and verify current platform licensing details in official documentation. Expected Impact: Once your map is drawn and your "Start here" routing note is saved, you can route the next "it does not work" ticket to the correct system in under 60 seconds by identifying the Zone, then the System, then what to search by. You no longer have to bounce between payment, licensing, and platform screens.

https://tradingvendoracademy.com/lessons/bir-2-2 2026-10-08T00:00:00Z

Platforms change, and customers may update before you do. Manage that change surface with a lightweight system: capture versions on every ticket, maintain a five-part map covering licensing, rendering, order handling, data-feed behavior, and platform lifecycle, and run a 10-minute smoke test after every platform update and product release. Expected Impact: Once your Platform Requirements Checklist and mandatory version triangle are in place, your next platform update triggers the 10-minute smoke test you run before you ship. The next update-week ticket arrives with the platform version, product version, and data feed provider, so you can reproduce the failure on a clean install instead of guessing. What changes often (keep this in your head): Platform lifecycle and breaking changes (method signatures, rendering APIs, order objects) Licensing models and entitlement checks (user-based licensing migrations, API behavior) Data feed edge cases (volume anomalies, missing ticks, session templates) Connectivity routes, including both their current behavior and whether they remain available. A route your customers use to reach the platform can be retired on a date somebody else chooses Platform distribution, vendor program and selling terms (submission expectations, packaging, behavior) Compliance expectations for marketing materials (if you sell trading tools, assume scrutiny is increasing)