What we've shipped, are shipping, and won't ship

PixelProof — Meta Pixel & Shopify checkout tracking

PixelProof exists because Shopify's Aug 26, 2026 checkout-extensibility upgrade removes the Additional Scripts box and checkout.liquid support that thousands of merchants rely on for Meta pixel, GA4, and GTM tracking — and because Meta's own API deprecation wave (47 Commerce endpoints blocked Jul 29 2026, Graph API v20 and Marketing API v24 sunsetting in the fall) is landing on an independent timeline.

Shipped

• M0 free scan & landing (Aug 5 2026): storefront scanner for Meta pixel, GA4, GTM tracking gaps ahead of the Aug 26 upgrade. Live at /meta-monitor.
• M1 checkout monitoring: paid tier with continuous scans, alert routing, incumbent price-watch monitor tracking Elevar / Northbeam / SegmentStream weekly.
• Rewardful affiliate program, dunning sequence, lifecycle emails, Founding Trio bundle — three-product bundle at /founding-trio.
• Free tools trio: Meta Pixel Debugger, Schema Markup Generator, Cookie Consent Checker — no signup required.
• Trust surface: public status page, changelog with RSS, cookie consent gating PostHog + Sentry, self-serve account deletion.

In progress

• M2 revenue gate: cron-tracked MRR threshold before unlocking the next pricing tier (per PICK_1_PRODUCT_BUILD_PLAN.md).
• Session Replay Verifier: weekly PostHog recording review flags UX-blocking issues found in real user sessions.
• Named credentialed reviewer: no page currently carries a byline other than the founder's — an open, tracked gap per Google Perfection Standard v2 §16.3.

Not shipping

• Chrome extension published to the Chrome Web Store — extension code exists in this repo (chrome-extensions/), but publishing a store-listed extension is deliberately deferred until a signed named reviewer is in place; a compliance-tool extension without a named human reviewer is not a trust signal we're willing to ship yet.
• LLM-generated ad copy or on-brand pixel replacement: this is not what PixelProof is. The scanner is deterministic-rules only.
• Real-time Slack integration with every ad platform: email + webhook only for now. Slack integrations for every platform is a maintenance treadmill we have not proven demand for yet.

Full detail on /meta-monitor/roadmap.

EntryProof — CPSC electronic-filing readiness

EntryProof exists because the CPSC Product Registry electronic-filing rule went mandatory Jul 8, 2026 under 16 CFR Part 1110, and a single missing or malformed data field in that filing can hold a container at the port. The scanner is currently in its v0 heuristic-only phase and we are honest about that stage on the product and here.

Shipped

• v0 readiness scanner & landing: free readiness check at /cpsc-efile, HTS-chapter-to-CPSC-applicability mapping, data-completeness heuristics against publicly inspectable product pages.
• Free CPSC Penalty Calculator: no signup, real 16 CFR Part 1110 penalty formulas at /tools/cpsc-penalty-calculator.
• CPSC rule-change calendar: iCal feed at /cpsc-efile/calendar for subscription-based deadline tracking.
• Platform PSEO + comparison pages: Shopify/BigCommerce/WooCommerce/Amazon/Etsy specific readiness pages, plus comparison against Descartes CustomsInfo, Enhesa, Assent.
• Founding-cohort waitlist, embeddable readiness badge, self-serve account deletion, JSON-LD schema, glossary.

In progress

• M1 rule engine (target Q4 2026): full rule-by-rule check against every CPSC safety standard for every product category, replacing the v0 heuristic layer. This is the honest disclosure the scanner already ships in its result UI.
• Broker + filing-agent partnership pipeline: the customs brokers who actually submit these filings are the natural referral partners; outreach is in progress via the LOI CSV pipeline already shipped.

Not shipping

• A filing-agent SaaS that actually submits your CPSC entry for you: submitting a real CPSC PGA message set is a licensed customs-broker activity under 19 CFR 111 and we are not a licensed customs broker. Any future submission product would ship as an integration with a real broker, not as us directly touching CBP's ACE.
• A guarantee that a green scan means "compliant": the scanner explicitly does not certify a filing. The disclosure is on the result UI, not just in Terms.

Full detail on /cpsc-efile/roadmap.

TariffWatch — Section 232 exposure

TariffWatch exists because Section 232 tariffs on steel, aluminum, and copper (currently 50% on most articles through Dec 31, 2027) plus the Aug 6, 2026 BIS-14 notice proposing 14 additional derivative-article categories put real six-figure exposure on importers who did not know what their HTS chapters mapped to. The current rules-version string is section232-v1-2026-08-08.

Shipped

• Exposure calculator at /tariffwatch/checker, real chapter/heading-level rate assignment against USITC HTS chapters 72/73/74/76.
• 14 BIS-14 comment-letter templates at /tariffwatch/comment-letter, one per proposed derivative article, ready to file into the BIS docket.
• 14 inclusion-rebuttal templates at /tariffwatch/inclusion-rebuttal, for importers who need to request a specific exemption.
• Regulatory calendar at /tariffwatch/regulatory-calendar: Section 232 modification windows, BIS comment deadlines, USTR docket dates.
• Methodology page pinning the rules-version string and citing all four primary sources (Federal Register notice, Presidential Proclamations, USITC HTS).

In progress

• M1 auto-file service for inclusion rebuttal comments: fill out the form, we submit the inclusion rebuttal comment into the BIS docket on your behalf. Requires broker-of-record verification handoff, in design.
• Section 301 (China tariffs) coverage: separate rules-version tag, USTR docket instead of BIS. Not shipped today.

Not shipping

• LMK-integration (import-license management platforms): not enough demand signal from real customer conversations to justify the integration cost yet.
• Tariff hedging / forward-contract recommendations: this is a licensed-financial-advice adjacency we are not going to touch.
• Full 10-digit HTS classification advice: this is licensed customs-broker work under 19 CFR 111, and the methodology page is explicit that the calculator's chapter/heading-level match is not a substitute for a full classification.

Full detail on /tariffwatch/roadmap.

Portfolio-level surface

Shipped

• Founding Trio bundle ($299/yr, all three products, capped at 5 founding spots) at /founding-trio.
• Data Processing Agreement (v0) at /dpa for enterprise procurement.
• Security & responsible-disclosure page at /security with PGP key, RFC 9116 security.txt, and safe-harbor language.
• Per-product terms, privacy, sub-processors, cookie policies, accessibility statements — shipped for all three picks.
• Portfolio methodology + glossary + roadmap + changelog (this page and its three siblings, Foxtrot7 Aug 20, 2026 ship).
• Portfolio identity table (empire.customers): shared cross-pick identity so a customer buying two products is not two disconnected accounts.

In progress

• SOC 2 Type II: target 2027-Q2. This is a real audit, not a self-attestation. Any listing on /security today is aspirational and marked as such.
• ISO 27001: same 2027 timeframe; deferred behind SOC 2 which the U.S.-focused enterprise buyer asks for first.

Not shipping (deliberately, at least for now)

• Native mobile app: the compliance workflows in each product are dashboard-tier work, not phone work.
• API-first tier with heavy customization: not until at least 10 paying customers ask for it. Every enterprise API tier we've built pre-demand has been a maintenance drain.
• Bolt-on products beyond the current three (PriceProof, Meta Ad Fleet Monitor are in planning; the Meta ad-monitor product previously shipped waitlist copy under the working name “AdSentry” but is being renamed pre-launch, product name pending trademark clearance): shipping is gated on PixelProof M2 revenue milestones.

How this roadmap is maintained

This page has no marketing gate. The founder edits it directly on the same commit that ships the feature. There is no product-marketing team writing a different version of the truth than what the code does. When a feature ships, its line moves from "In progress" to "Shipped" here (and gets an entry on /changelog that same week). When a planned feature is deliberately dropped, it moves to the "Not shipping" list with a stated reason, not deleted silently.

A roadmap that only ever says "everything is great, more is coming" is not a roadmap; it's marketing copy wearing a roadmap's clothes. This one is deliberately built not to be that. If a competitor or a curious prospect is reading this specifically to gauge how seriously we take our own claims, that scrutiny is the point.