Wripp Freight Marketplace — Master Question List

CATEGORY 1 — VISION, BUSINESS LOGIC & SUCCESS METRICS

1. What is the exact target user persona for shippers — size of business, shipping frequency, biggest pain points today?

2. What is the exact target user persona for carriers — owner-operators vs. fleets, fleet size, typical lanes they run?

3. How do we define a "successful load" in the first 90 days?

4. What are the top 3 KPIs we must hit in the first 6 months?

5. What is our go-to-market strategy — organic, paid, partnerships, or a specific combination?

6. What competitive products do we want to explicitly beat in specific features (uShip, Uber Freight, DAT)?

7. What revenue mix do we want between transaction fees and subscriptions in Year 1?

8. What are our hard non-goals for MVP — what are we explicitly NOT building at launch?

9. How do we define "done" for the MVP launch?

10. What is our tolerance for manual operations in the first 6 months?

11. How important is liquidity in the first 30 days, and what seeding strategies should we prioritize?

12. How do we measure network effects — when do we consider the marketplace "healthy"?

13. What is our stance on white-labeling the platform for large brokers or enterprise clients?

14. What is our policy on data ownership — who owns shipper and carrier data on our platform?

15. How do we want to handle disputes where both parties claim equal fault?

16. What insurance partnerships or integrations do we want operational from day one?

17. How important is sustainability/ESG reporting for our brand and marketing?

18. How should we handle seasonal spikes (harvest season, holiday freight surges)?

19. How should we handle international expansion — timeline and which countries first (Canada, Mexico)?

20. What is our policy on canceling loads — what are the penalty fees for each party?

21. What is our target NPS score at 90 days post-launch?

22. How do we measure when the marketplace has achieved "healthy liquidity"?

23. What are the biggest unknowns we should stress-test in the first 12 months?

24. What questions should we be asking at 6 months, 12 months, and 24 months that we are not asking today?

CATEGORY 2 — MONETIZATION, FEE MODEL & SUBSCRIPTIONS

Fee Model

1. Is the 20% total fee (10% shipper + 10% carrier) fixed permanently, or will it adjust as we scale?

2. When exactly does escrow release to the carrier — immediately on POD confirmation, after a dispute window, or manually?

3. What is the dispute window after delivery before escrow auto-releases (24hr, 48hr, 72hr)?

4. Should we support instant payouts for Elite carriers (same-day, at an additional fee)?

5. What is the default carrier payout schedule — next business day, Net 2, Net 7, or carrier-configurable?

6. Should we build a wallet/balance system where carriers keep earnings inside Wripp?

7. Should we offer invoice factoring integration in the Elite tier?

8. What is our chargeback policy — who bears the loss?

9. How should we handle fee reversals on cancelled loads — full refund, partial, or tiered by cancellation timing?

10. How should we handle sales tax on platform fees across 50 states?

11. Should we show projected earnings in the Carrier Tools dashboard?

12. Should we support invoice customization with carrier or shipper logos?

13. What export formats are mandatory — CSV, Excel, PDF, QuickBooks, Xero?

14. What is the exact copy for the 20% fee disclosure checkbox at signup?

15. How should we handle currency conversion and FX risk if we go international?

Subscription Tiers

1. Are the tier prices final: FREE, STARTER $49/mo, PRO $79/mo, ELITE $129–149/mo, ENTERPRISE custom?

2. Should the FREE tier have a time limit (e.g., 30-day trial) or be unlimited time with feature limits?

3. What exactly is included in each tier for bid limits, active load limits, and seat counts?

4. Should subscription discounts apply for annual billing on all tiers?

5. What referral incentives should we offer — free month, fee credit, or cash?

6. Should a successful referral grant one free month upgrade to BOTH the referrer and the new user?

7. What is the maximum number of active loads before we encourage upgrading?

8. Should we implement performance-based pricing incentives for high-volume users?

Payment Processing & Compliance

1. Are we at risk of being classified as a Money Transmitter / Money Services Business (MSB)?

2. What steps must we take to avoid MSB registration in multiple states?

3. Should we partner with a licensed escrow provider or bank?

4. Should we use Stripe Connect for carrier payouts?

5. What are the PCI compliance implications?

6. Should we offer factoring or invoice financing through partners?

7. Should we integrate directly with QuickBooks/Xero via OAuth, or just formatted export files?

8. Should the 1099-NEC be generated and filed automatically, or just generated for manual filing?

9. Should carriers be required to have a W-9 on file before receiving their first payout?

10. Should we support partial payments or milestone-based payments for multi-stop loads?

11. How should we handle refunds and adjustments visually — a separate credit memo or an updated invoice?

12. Should we offer buyer protection or shipper guarantees?

13. Should we build a reserve fund for chargebacks and claims?

14. Should we use Avalara or TaxJar for sales tax automation?

15. When do we need to issue 1099-NEC forms to carriers and what is the annual threshold?

CATEGORY 3 — ONBOARDING, VERIFICATION & GATING

Onboarding Wizard

1. Are all 6 wizard steps mandatory with no skipping, or can users skip steps with a warning?

2. Should "Save & Continue Later" save progress to the database (resumable from any device) or just localStorage?

3. Should we pre-fill any wizard fields using data from the user's phone number or email domain?

4. Should we require a "test bid" or "test load post" during onboarding before going live?

5. How should we handle users who sign up with both roles but only complete one role's profile?

6. How aggressive should upgrade prompts be during onboarding — subtle tooltips or prominent modals?

7. What is the maximum time we allow for profile completion before sending re-engagement nudge emails?

8. Should business verification have different document requirements than individual carrier verification?

Carrier Verification

1. How strict should FMCSA verification be — what is the exact threshold between auto-approve and manual review queue?

2. What is our fallback procedure if the FMCSA API is down when a carrier submits their DOT/MC?

3. Should we require insurance COI upload even if the FMCSA API confirms insurance is currently on file?

4. What verification documents need AI OCR processing vs. always going to manual human review?

5. Should we support bulk document upload for fleet carriers submitting multiple drivers at once?

6. What is our policy on temporary limited access during the document review period?

7. What is our re-verification policy after a rejection — can they retry immediately or is there a waiting period?

8. How should we handle name mismatches between uploaded documents and the signup name?

9. What is the exact FMCSA compliance checklist — which fields must be verified before a carrier can bid?

10. How should we communicate verification status in real time — live status badge, email, SMS, or all three?

11. Should we require carriers to upload proof of a drug/alcohol testing program?

12. Should we manually review every new carrier before activation, or rely on automated checks?

13. What automated red flags should trigger manual review?

14. Should we require video verification for high-risk or flagged carriers?

15. How do we handle fake document detection — AI flag only, or immediate suspension?

Gating Enforcement

1. Should the teaser marketplace show blurred load cards with "Verify to unlock" overlays, or completely hide loads until verified?

2. Should partially verified users (email done, documents pending) get read-only marketplace access?

3. Should we have a "Verification Blocked" error page with a specific illustration and recovery path?

4. Should we have a "Why am I being asked for this?" tooltip on every verification field?

CATEGORY 4 — UI/UX & DESIGN SYSTEM

Visual Design

1. Dark mode only, or do we offer a light mode toggle at any point?

2. Should glassmorphism blur intensity be adjustable based on device performance?

3. Should confetti fire on every successful action or only major milestones (first booking, first payout)?

4. What style should empty state illustrations be — minimal/geometric, playful, or realistic?

5. How should error messages balance friendliness and professionalism for truckers?

6. Should the Verified badge use a glowing green checkmark or a different visual treatment?

7. Should load cards show deadhead miles by default, or only after a tap/expand?

8. Should there be a small map thumbnail on every load card?

9. What is the maximum number of filters visible before collapsing into "More Filters"?

10. Should we have a "Favorites" heart icon on load cards for carriers to save interesting loads?

11. How should pulsing live bid counters animate — subtle pulse, number increment, or color flash?

12. Should we use skeleton loaders, standard spinners, or neon shimmer placeholders?

13. Should very long load descriptions truncate with expand, or be fully scrollable?

14. How should multi-stop routes be visualized on load cards and the map?

15. What is the "In Transit" status color — and define every status color in the system?

16. Should we support portrait and landscape orientations on mobile for the tracking map?

17. What is the exact hover and tap feedback for load cards?

18. How should loading states feel on slow 3G connections for truckers?

19. How should we design the public tracking page for receivers?

20. Should the role switcher be always visible (persistent) or only shown when the user has both roles activated?

21. What is the desired scroll behavior on the live load feed?

Typography & Motion

1. Is Space Grotesk (Bold/Medium) confirmed as the primary typeface?

2. Is the typography scale confirmed: Hero 48–72px, Headers 28–36px, Cards 22–26px, Body 16–18px?

3. Should the 300ms spring easing apply to all animations, or should some be faster/slower?

4. Should reduced motion mode disable all animations or only the non-essential ones?

5. Should haptic feedback fire on all button taps or only on significant actions?

Accessibility & Trucker UX

1. What accessibility features are non-negotiable for truck drivers specifically?

2. Should we support voice commands during active tracking for hands-free use?

3. Should the app integrate with the phone's Do Not Disturb mode to suppress non-critical notifications during rest?

4. Should we have a guided tour on first login after onboarding completion?

CATEGORY 5 — DASHBOARD, NAVIGATION & PAGES

Dashboard Structure

1. Should the dashboard remember the last visited tab and filter state per user per role?

2. What is the default sort order on the Marketplace feed for a newly verified carrier?

3. How many recent loads should appear in quick-view widgets on the dashboard home?

4. Should there be a "Today's Opportunities" section at the top of the Carrier dashboard?

5. Should Finance tab show completely different layouts for shippers vs. carriers, or the same layout with different data?

6. What quick actions should be pinned on the dashboard home for each role?

7. Should there be a "Favorite Lanes" feature where carriers save preferred origin-destination pairs?

8. Should there be a "Saved Carriers" list on the Shipper dashboard for repeat business?

9. What keyboard shortcuts should we support on desktop?

10. Should we have a command palette (Cmd/Ctrl+K) for power users?

11. Should there be a floating action button on mobile — "Post Load" for shippers and "Place Bid" for carriers?

12. How should the role switcher animate when switching context between Shipper and Carrier?

13. Should the Reports tab have a gallery of pre-built export templates?

14. What is the maximum depth of nested modals before we push to a new page?

15. Should there be a mini-map widget visible on multiple tabs, not just My Loads?

16. Should we have a global search bar that searches across loads, bookings, and conversations simultaneously?

17. Should filters persist across sessions (saved per user in the database)?

18. What is the desired pull-to-refresh behavior — instant, with animation, or with a smart cache check?

19. How should we visualize load status in list view vs. card view?

20. How should we handle very long timelines in My Loads?

21. How should empty states look when a user has no loads yet?

Mobile Navigation

1. What are the exact 5 icons on the mobile bottom navigation bar?

2. How should mobile bottom navigation behave when arriving via a deep link?

3. Should we support swipe gestures for tab switching on mobile?

4. How should we handle landscape orientation on tablet for the tracking map?

Public Marketing Pages

1. Should the homepage show a live load feed teaser with blurred cards, or a static value proposition?

2. Should the /become-carrier page include an earnings estimator calculator?

3. Should the /for-shippers page include an ROI calculator showing cost savings vs. traditional brokers?

4. Should the blog be part of the platform build or handled separately via a CMS?

5. Should we build a /help knowledge base as part of this build or use an external tool (Intercom, Zendesk)?

CATEGORY 6 — MARKETPLACE, BIDS & BOOKING

Load Posting

1. Should shippers be able to save load posting templates and duplicate previous loads with one click?

2. Should the load posting wizard include an insurance upsell modal during posting?

3. Should shippers be able to set a "Buy It Now" fixed price alongside the target price (Instant Book option)?

4. Should loads have a visibility setting — public to all verified carriers, or invite-specific carriers only?

5. Should shippers be able to add a Purchase Order (PO) number to a load for their accounting?

6. Should multi-stop loads support different pickup/delivery windows at each stop?

7. How should we handle hazmat loads — additional fields, extra verification, or restricted to certain carriers?

8. Should we require a minimum notice period before pickup (e.g., no same-day posting)?

9. Should we require shippers to certify the accuracy of load descriptions before posting?

10. What is our policy on editing load details after a shipment has started?

Bidding

1. Should the bid ladder (all bids ranked) be visible to the shipper in real time?

2. Should carriers see other carriers' bid amounts (open auction) or is it always a blind auction?

3. Should a suggested market rate be shown to the carrier before they enter their bid amount?

4. How many rounds of counter-bidding should be allowed before a decision is forced?

5. What is the bid expiry duration — 24 hours, 48 hours, or shipper-configurable?

6. Should there be a "Best Offer" button that auto-accepts the current lowest bid?

7. Should chat open as soon as a carrier places a bid, or only after booking confirmation?

8. Should there be a real-time bidding ladder animation showing new bids as they arrive?

9. Should the FREE tier bid limit reset daily or weekly?

Booking

1. After bid acceptance, does booking creation happen instantly (auto) or require a manual shipper confirmation step?

2. Should a rate confirmation document be generated and sent immediately on booking creation?

3. Should a BOL (Bill of Lading) be auto-generated on booking, or only on carrier pickup confirmation?

4. Should bookings require a digital e-signature from both parties before becoming active?

5. What happens if the shipper does not respond to a bid within the expiry window?

Map Tabs

1. For the Shipper Map tab: should it show verified carriers by their registered operating region, or by their last known GPS location?

2. For the Carrier Map tab: should load pins show the pickup location or the midpoint of the route?

3. Should the direct shipper-to-carrier offer flow on the map create a new load record, or is it a separate offer type?

4. Should map pins cluster at high zoom-out levels, and what is the clustering strategy?

5. For the Vehicle Search tab: should search results show only carriers with available equipment, or all carriers with that equipment type?

CATEGORY 7 — CHAT & COMMUNICATION

1. Should chat be available as soon as a carrier places a bid, or only after booking confirmation?

2. Should chat remain open for 7 days after delivery completion, then archive?

3. Should voice messages be available in chat for drivers who cannot type while driving?

4. Should pre-built quick replies be included in chat (e.g., "Running 2 hours late", "At the gate", "Need more straps")?

5. Should emoji reactions be supported on individual messages?

6. Should the dispute chat room be a completely separate thread, or a flagged section within the existing booking chat?

7. Should message history be searchable by keyword?

8. Should message history be exportable as PDF or CSV for dispute evidence?

9. Should Wripp support staff be able to join a chat thread when escalated (visible to both parties)?

10. Should there be read receipts and typing indicators?

11. Should file/document sharing in chat support BOL, POD, insurance certificates, and photos?

12. Should we support live chat during active GPS tracking, or keep them separate?

CATEGORY 8 — GPS TRACKING & LIVE FEATURES

Tracking Behavior

1. What geofence radius should trigger pickup and delivery confirmations — 500ft, quarter mile, or carrier-configurable?

2. How should we handle GPS permission denial — degrade to manual check-ins only, or block shipment start entirely?

3. What is the exact behavior when a carrier turns off location services mid-shipment?

4. Should we show speed and heading on the live tracking map visible to shippers?

5. How long should raw GPS point data be retained — 30 days, 90 days, or 1 year?

6. What is the maximum time between manual check-ins before an escalating alert fires?

7. Should carriers be able to mark "Running Late" and self-report an adjusted ETA?

8. Should there be a rest stop logging modal with a reason selector (HOS, fuel, meal, mechanical)?

9. Should we integrate with the phone's Do Not Disturb mode during driver rest periods?

10. How should offline sync conflicts be resolved — last-write-wins or flag for admin review?

11. Should we have a driver fatigue warning system based on time since last movement or last check-in?

12. Should we support voice commands during active tracking (e.g., "I've arrived", "I'm delayed by 2 hours")?

13. How should we handle multiple carriers on multi-stop loads?

14. How should we calculate and display carbon emissions — per load, per mile, or both?

15. Should we cache routes for common lanes to reduce map API costs?

16. Should we show traffic overlays on the route map?

17. How should jurisdiction crossing alerts work — just for hazmat or for all loads?

18. What analytics should we track on tracking engagement?

19. What fallback map should we use if Mapbox fails?

20. What is the exact GPS timeline data model we need?

Photo Verification

1. Should the mandatory pickup photo have an AI check for cargo securement and visible damage?

2. What happens if the AI flags a photo as potentially showing damage — hold shipment start or just flag for review?

3. Should the delivery photo require a consignee signature (captured on screen) as well as a photo?

4. How should shipper rejection of a delivery photo be handled — dispute auto-filed or notification sent?

5. Should a damage report photo be a mandatory fifth checkpoint, or optional and carrier-initiated?

Public Tracking & Privacy

1. Should receivers get a different tracking link than shippers (ETA + status only vs. full route)?

2. Should the public tracking link have optional password protection?

3. Should the public tracking link have an expiration date?

4. Should carriers be able to pause location sharing with a 30-minute grace period notification to shippers?

5. Should we show carbon emissions on the public tracking page?

6. How should we design the public tracking page branding?

CATEGORY 9 — MOBILE APP

1. Should the mobile app be required for tracking, or is phone browser GPS fallback sufficient for MVP?

2. What is the background location update frequency — every 30 seconds, 60 seconds, or smart sampling based on speed?

3. What battery optimization thresholds should trigger reduced GPS frequency?

4. Should we support iOS and Android simultaneously at launch, or iOS first?

5. Should deep links use the wripp:// scheme, or universal links (HTTPS) for better app store compatibility?

6. Should the mobile app be on the App Store before the web platform launches, or after?

7. Should we use RevenueCat for in-app subscription management on mobile?

8. How do we handle mobile app updates and versioning?

9. Should we have an App Store and Google Play Console set up before development begins?

CATEGORY 10 — CARRIER PROFILES, FLEET & REVIEWS

1. Should carrier profiles be publicly visible without login for SEO and organic discovery?

2. Should the "Available Now" toggle on vehicle cards be visible to shippers browsing carrier profiles?

3. Should carrier profiles show total miles driven as a statistic — and is that data we actually track?

4. Should reviews include a photo from the delivery as contextual evidence?

5. Should both parties be forced to leave a review before the final payout/transaction closes, or is it optional?

6. After how many days should the review window close if a party has not submitted?

7. Should carriers be able to publicly reply to reviews, and is there a character limit on replies?

8. Should there be a "Saved Carriers" feature for shippers — and should carriers see who has saved them?

9. Should shipper profiles also be publicly visible, or private (visible only to carriers they have booked)?

10. Should the carrier profile show a "Response Rate" metric (% of bids responded to within X hours)?

11. Should we show a "Load Acceptance Rate" — bids won vs. bids placed?

12. How do we handle negative reviews and defamation risks?

13. Should we use AI moderation for inappropriate review content?

CATEGORY 11 — INVOICES, PAYMENTS & ACCOUNTING

1. Should both parties be able to edit invoice line items before finalization, with mutual approval required?

2. Should the invoice show state-specific taxes auto-calculated, or just the Wripp fee?

3. Should the invoice include a carbon estimate for the load?

4. Should the invoice number format be WF-XXXXXX?

5. Should fuel surcharge be a line item carriers can add, or is it always included in the base bid?

6. Should the Finance tab reconciliation engine flag discrepancies automatically with AI detection?

7. Should there be a predictive payout calendar showing expected earnings from active loads?

8. How should we visualize profitability per lane?

9. What reconciliation reports should be available?

10. How should we handle partial payments or payment adjustments?

CATEGORY 12 — DISPUTES & ADMIN

Disputes

1. Should the "Open Dispute" button be available on any active or recently completed load, or only on the booking detail page?

2. Should the dispute form include a requested resolution amount field?

3. Should the proposal system allow unlimited counter-proposals, or a maximum number of rounds?

4. Should the 48-hour self-resolution timer pause if both parties are actively chatting?

5. Should post-resolution ratings of the dispute handling process be mandatory or optional?

6. Should the Dispute Center be a standalone page AND a sub-tab under My Loads?

7. Should Elite users get a dedicated dispute SLA (e.g., resolved within 24 hours)?

8. What is our internal claims handling process?

9. Who owns the claims process — platform or carrier?

10. Should we have a dedicated claims reserve fund?

11. Should we self-insure any portion of risk at scale?

12. What is our process for rejected loads — carrier refuses to accept freight as described?

13. How do we handle concealed damage discovered after delivery?

14. What is our policy for weather-related delays and force majeure?

Admin Console

1. Should the admin console have a real-time revenue dashboard (daily/MTD/YTD)?

2. Should admins be able to impersonate users for support purposes — and should this be logged with full audit trail?

3. Should Super Admin actions require a second admin to confirm (4-eyes principle)?

4. Should admin session recording be implemented for destructive actions?

5. Should there be a "break-glass" emergency admin account locked in a vault?

6. What is the exact escalation path: Support Tier 1 → Tier 2 → Operations → Legal?

7. Should support be 24/7 from day one, or phased in as load volume grows?

8. Should the admin have a compliance monitoring dashboard showing FMCSA status across all active carriers in real time?

9. Should the admin audit log be exportable in a format suitable for legal/regulatory review?

10. What are all the distinct admin/permission roles we need at launch and at scale?

11. Should there be a Super Admin (God Mode) role, and what are the exact permissions?

12. Should there be multiple Super Admins or just one?

13. Should Super Admin access require VPN + hardware key (YubiKey)?

14. Who can manually override verification status?

15. Who can issue refunds or goodwill payments?

16. Who can access raw GPS tracking data?

17. Should we implement time-based access expiration for elevated admin roles?

18. How do we handle impersonation of users by admins — should impersonation require dual approval and logging?

19. What is our escalation path from support to operations to founders?

CATEGORY 13 — SECURITY

1. What is our data breach notification policy — who gets notified, in what timeframe, and via what channel?

2. Should we target SOC 2 Type II compliance, and what is the realistic timeline?

3. Should we require hardware security keys (YubiKey) for Super Admin accounts?

4. Should we implement a formal bug bounty program at launch or post-launch?

5. Should we conduct penetration testing before MVP launch or wait for a beta milestone?

6. What is our vulnerability scanning and dependency audit cadence?

7. Should we implement a Web Application Firewall (WAF) from day one?

8. What is our password policy for admin accounts — minimum length, rotation schedule, breach database checks?

9. Should we use zero-trust architecture for all internal tool access from day one?

10. Should admin access require VPN + MFA + time-limited credentials for production database?

11. Should we use end-to-end encryption for chat messages?

12. How do we secure GPS data specifically at rest and in transit?

13. How do we handle secrets management (API keys, credentials)?

14. How do we protect against account takeover attacks?

15. How do we protect against GPS spoofing or tampering?

16. What secure coding practices are mandatory?

17. How do we protect against supply chain attacks (compromised npm packages, etc.)?

18. Should we use a SIEM system for admin activity monitoring?

19. How do we detect insider threats?

20. How do we handle former employee access revocation?

CATEGORY 14 — LEGAL & REGULATORY COMPLIANCE

FMCSA & DOT

1. Are we legally classified as a freight broker, marketplace, or technology platform under FMCSA rules?

2. Do we need to obtain our own FMCSA broker authority (MC number)?

3. What are the exact requirements to maintain "marketplace" status and avoid full broker liability?

4. What ongoing monitoring obligations do we have for carriers' authority status?

5. How frequently must we re-verify carrier DOT/MC numbers and insurance?

6. What is our liability if we allow an out-of-service or revoked carrier to book loads?

7. Do we need to file Form BOC-3 (Designation of Process Agent) in every state?

8. How should we handle hazmat loads from a regulatory perspective?

9. What compliance is needed for oversize/overweight loads?

10. How do we address Hours of Service (HOS) compliance when using our tracking data?

11. Can we be held liable for constructive knowledge of HOS violations?

12. What record-keeping requirements apply to us as a marketplace?

13. Are we subject to FMCSA audits or investigations, and do we need a compliance calendar?

14. What are the rules around advertising loads and "best rate" claims?

Digital Marketplace & Privacy Laws

1. To what extent does Section 230 of the Communications Decency Act protect us?

2. Are we required to comply with ADA website and mobile app accessibility standards?

3. How do CCPA, CPRA, Virginia CDPA, and other state privacy laws apply?

4. Do we need a formal Data Protection Officer or privacy program?

5. What consent mechanisms are required specifically for GPS tracking before it activates?

6. Are we subject to TCPA rules for SMS notifications, and how do we ensure compliance?

7. What CAN-SPAM compliance is needed for email marketing?

8. Could we face anti-trust scrutiny for facilitating rate discussions or suggesting prices?

9. What disclaimers should appear on all load boards and tracking pages?

Contracts & User Agreements

1. Should we mandate binding arbitration for all user disputes in the Terms of Service?

2. Should we use a "clickwrap" or "browsewrap" approach for user agreements?

3. Should we have separate Terms of Service for shippers vs. carriers?

4. What governing law and venue should we choose for all disputes?

5. What force majeure language is appropriate for freight-specific scenarios?

6. What cargo claims and liability allocation language should be in our agreements?

7. How strong should our limitation of liability clause be?

8. What indemnity provisions should we require from users?

9. How do we handle class action waivers?

10. What notice period is required for material changes to Terms of Service?

11. How do we structure load confirmation contracts?

12. What payment terms and escrow language should be used in agreements?

13. What insurance verification warranties should users provide in the agreement?

State-by-State & International

1. Which states have the strictest marketplace facilitator tax laws, and what is our exposure?

2. How do we track economic nexus in all 50 states?

3. What are the varying broker licensing requirements by state?

4. How do we handle cross-border loads (U.S.–Canada–Mexico)?

5. What customs brokerage compliance is needed for cross-border?

6. Do we need local legal entities for international expansion?

7. What are the insurance minimums that vary by state?

Ongoing Compliance

1. What compliance monitoring system should we build internally?

2. Should we retain outside compliance counsel on retainer?

3. How often should we conduct internal compliance audits?

4. What training should operations and support staff receive on trucking regulations?

5. Should we implement a whistleblower hotline?

6. How do we handle government investigations or subpoenas?

7. How do we handle carrier deactivations and appeals?

8. What is our policy on banned users?

9. What are the biggest regulatory risks we are currently underestimating?

10. How do we prepare for potential class action lawsuits?

CATEGORY 15 — CARRIER INSURANCE REQUIREMENTS

1. What minimum cargo insurance limits must carriers carry to use the platform?

2. Should we require carriers to carry liability insurance above the FMCSA minimum?

3. Should we integrate with RMIS or Truckstop for real-time insurance verification?

4. What automated alerts fire when a carrier's insurance is within 30 days of expiration?

5. What happens if a carrier's insurance lapses mid-shipment — automatic suspension or grace period?

6. Should we require higher insurance limits for hazmat or high-value loads?

7. Should we offer optional cargo insurance products to shippers through an insurance partner?

8. Should we require on-hook cargo coverage from carriers?

9. What happens if we fail to verify a carrier's insurance and they cause damage — what is our platform exposure?

10. Should we require carriers to name Wripp as Additional Insured on their policies?

11. How do we verify insurance for owner-operators vs. fleets differently?

12. Do we need contingent cargo insurance as a backstop if carrier insurance fails?

CATEGORY 16 — PLATFORM INSURANCE & RISK MANAGEMENT

1. What General Liability (GL) coverage limits should Wripp carry as a digital freight marketplace?

2. Do we need Professional Liability / E&O insurance from day one?

3. What Cyber Liability / Data Breach insurance do we need, and what should it cover?

4. Should we purchase D&O insurance from day one?

5. Should we purchase crime/fidelity insurance for employee theft?

6. What is the potential vicarious liability exposure if a carrier causes an accident?

7. Should we have a "no liability for carrier actions" clause in our Terms of Service?

8. Should we cap our total liability in the Terms of Service?

9. What disclaimers should appear on all load boards and tracking pages?

10. Should we create a formal Risk Management Committee?

11. What is our crisis response plan for a major accident involving a carrier on our platform?

12. What is our crisis communication plan for public incidents?

13. What is our potential liability for GPS tracking data used in litigation?

14. How do we protect against negligent verification claims?

15. Should we have a rapid response team for incidents?

16. How do we model total cost of risk (TCOR)?

CATEGORY 17 — DATA PRIVACY

1. Who owns GPS/location data generated during shipments — the platform, the carrier, or jointly?

2. Should GPS data be retained for 30 days post-delivery and then anonymized/archived?

3. Should carriers be able to turn off location tracking during rest stops, or is tracking continuous?

4. Should we implement a formal "Right to be Forgotten" process for GDPR/CCPA compliance?

5. Should we have a Privacy Dashboard where users can see and control all their data?

6. Should we allow carriers to export all their data (loads, earnings, GPS history)?

7. Should we conduct Data Protection Impact Assessments (DPIAs) before launch?

8. What is our data retention policy per data type: GPS, messages, financial records, documents, audit logs?

9. What third parties do we share data with (analytics, maps, payments)?

10. Do we have Data Processing Agreements (DPAs) with all vendors?

11. What is our policy on selling or licensing anonymized data?

12. Should we have separate privacy policies for shippers vs. carriers?

13. What privacy notices should appear during signup and onboarding?

14. Can law enforcement request GPS data, and what is our response process?

15. Should we appoint a Data Protection Officer (DPO)?

CATEGORY 18 — TECHNOLOGY & ARCHITECTURE

1. Should we use tRPC for all internal API calls, or mix tRPC with REST for certain endpoints?

2. What is our branching and deployment strategy — GitFlow, trunk-based, or feature branches with short-lived PRs?

3. Should we implement feature flags using a managed service (LaunchDarkly) or an in-house system?

4. Should we implement CQRS for high-read domains like the marketplace feed?

5. What is our database indexing strategy for GPS time-series data in TimescaleDB?

6. What is our disaster recovery RTO (recovery time objective) and RPO (recovery point objective) target?

7. Should we implement event sourcing for the full tracking history, or just store final timeline snapshots?

8. How should we version public APIs for Enterprise and TMS integrations?

9. What is our performance budget per key page — target LCP, FID, CLS values?

10. Should we use AI-assisted code review in the CI pipeline?

11. Should we use edge functions (Cloudflare Workers, Vercel Edge) for any specific API endpoints?

12. Should we implement optimistic UI updates everywhere, or only on critical user-facing actions?

13. How should we handle data synchronization conflicts between offline mobile and live server state?

14. What is our approach to logging sensitive actions — structured logs, immutable append-only table, or a SIEM?

15. What is our caching strategy per layer — Redis TTLs for marketplace feed, route cache, session?

16. What is our rollback plan for failed production deployments?

17. Should we implement real-time cost monitoring for cloud spend from day one?

18. Should we support multiple languages (Spanish first) at launch or post-launch?

19. What is our approach to technical debt tracking — formal backlog, quarterly review, or continuous?

20. How should we structure the monorepo folders exactly?

21. What is our approach to rate limiting and abuse prevention per endpoint?

22. How should we handle background job priority queuing?

23. What is our approach to schema migrations in production?

24. How should we handle real-time vs. polling tradeoffs for specific features?

25. How should we structure domain events for the event-driven architecture?

26. How do we handle third-party API failures gracefully (FMCSA down, Stripe down, Mapbox down)?

27. Should we have a style guide enforcement in CI?

28. What is our approach to A/B testing infrastructure?

29. What is our testing strategy per layer (unit, integration, E2E, load testing)?

CATEGORY 19 — OPERATIONS, GROWTH & COLD START

1. How do we solve the cold-start chicken-and-egg problem — attract carriers before shippers or vice versa?

2. Should we pay carriers to list capacity early before there are enough shippers on the platform?

3. Should we offer guaranteed minimum load volume commitments to early carrier partners?

4. What seeding strategies are legally and ethically acceptable — real loads from partners, sponsored loads, or manual matching?

5. What carrier acquisition channels work best for cold start (trucking Facebook groups, DAT migration offers)?

6. Should we manually approve all loads during the early days to ensure quality?

7. Should we create a "Launch Partner" program with large shippers for guaranteed early load volume?

8. What is our minimum viable carrier density target per region before going live in that region?

9. What referral incentives should we offer — free month, fee credit, or cash per referred user?

10. Should we have a carrier-of-the-month or leaderboard program to drive engagement?

11. Should we build in-app community forums at launch, or keep the platform purely transactional?

12. What is our post-launch user feedback collection system?

13. What metrics dashboard should leadership review weekly?

14. Should we attend trucking trade shows and industry events for carrier acquisition?

15. What is our content marketing strategy — blogs, YouTube, social?

16. Should we create separate acquisition funnels for shippers and carriers?

17. What is our win-back campaign strategy for users who sign up but never complete verification?

18. Should we gamify the platform with badges, leaderboards, or streaks?

19. What is our churn prevention strategy?

20. How do we handle low-volume rural routes during early launch?

21. Should we create "hot lane" or high-demand alerts for carriers?

22. How do we forecast staffing needs for support and operations at different load volumes?

23. What is our plan for system outages during high-volume periods?

24. Should we outsource certain functions (verification processing, claims handling)?

25. Should we publish marketplace transparency or impact reports?

26. How do we maintain marketplace quality as volume increases?

CATEGORY 20 — BUSINESS STRUCTURE, LEGAL ENTITY & FUNDRAISING

Entity Formation

1. What is the optimal legal entity type — Delaware C-Corp, Delaware LLC, or other?

2. Should we form multiple entities (operating company + IP holding company)?

3. What are the annual compliance costs for our chosen entity structure?

4. Should we elect S-Corp status at any point?

5. How do marketplace facilitator tax laws affect our entity choice across all 50 states?

6. Should we register to do business as a foreign entity in every state where we have users?

7. Should we use a formation service (Stripe Atlas, Clerky) or a specialized startup attorney?

Founder Agreements & Equity

1. What vesting schedule should we use for founders — 4-year with 1-year cliff?

2. Should vesting accelerate upon change of control or termination?

3. What IP assignment agreements are required from all founders?

4. Should we use restricted stock or stock options for founders?

5. Should founders file an 83(b) election, and what is the timing?

Fundraising & Cap Table

1. Should we use a cap table management tool like Carta or Pulley from day one?

2. Should we use SAFEs or priced rounds for initial outside capital?

3. What are the tax implications of different fundraising instruments (SAFE vs. convertible note vs. priced round)?

4. Should we apply for Qualified Small Business Stock (QSBS) benefits?

5. Should we create an Advisor Equity Pool at formation?

6. What key metrics will investors expect for a freight marketplace?

Tax & Accounting

1. What are the 1099 reporting obligations for carriers, and how do we automate this?

2. How should we handle multi-state tax nexus as we scale?

3. Should we use Avalara or TaxJar for sales tax automation?

4. How do we handle R&D tax credit opportunities?

5. How do we classify independent contractors (carriers) vs. employees properly?

6. What are the risks of misclassification?

Governance

1. What should our initial board composition look like?

2. How many board seats for founders vs. investors?

3. How do we handle conflict-of-interest policies at the board level?

4. Should we implement a code of conduct for the company?

5. Should we have an Internal Audit function?

6. Should we implement OKRs for support and ops teams?

CATEGORY 21 — EXIT STRATEGY & LONG-TERM

1. What exit scenarios are most likely — acquisition by a logistics company, IPO, or secondary sale?

2. Which companies are the most likely acquirers of Wripp (XPO, Convoy successors, Uber Freight)?

3. Should we build with an acquisition in mind from day one?

4. What IP strategy maximizes exit value — patents on core matching or tracking technology?

5. Should we pursue patents on any core technology?

6. How do we build a data moat that creates defensible exit value?

7. What valuation multiples are realistic for freight tech exits?

8. How do we prepare the company for due diligence in an exit?

9. Should we implement a management carve-out plan?

10. Should we build in change-of-control acceleration for equity?

11. How do we protect minority shareholder rights in an exit?

12. What is our wind-down plan if the company fails?

13. How do we protect founder personal credit and assets?

14. How do we build a company that can last 10–20+ years?

15. What is our plan if we cannot raise capital?

16. Should we build toward industry consolidation or remain independent?

CATEGORY 22 — ADVANCED FEATURES & EDGE CASES

Cargo & Load Types

1. Should we support LTL (Less Than Truckload) loads at launch, or FTL only?

2. Should we support hotshot (expedited smaller loads) as a separate equipment category?

3. Should we support intermodal or container drayage loads?

4. Should we allow livestock, perishable, or specialty cargo types?

5. Should we support oversize/overweight loads with special permitting workflows?

6. How do we handle high-value or secure loads (requiring armed escort)?

7. Should we support temperature-controlled loads with temperature log requirements?

8. Should we support a "Carrier Requested" load type where carriers post available capacity?

9. Should we have a "Backhaul Board" specifically for return route loads?

Operational Edge Cases

1. How do we handle multi-carrier loads where one carrier handles the first leg and another the second?

2. How do we handle drop-trailer loads where the carrier drops the trailer and the shipper loads independently?

3. How do we handle no-shows by carriers — automatic ban, strike system, or case-by-case?

4. How should we handle load abandonment where a carrier disappears with cargo mid-transit?

5. Should we have a "Carrier Watch List" shared with other platforms for fraud prevention?

6. Should we have a "Preferred Carrier" network where shippers can invite trusted carriers to private loads?

7. Should we support white-glove or expedited "urgent" load posting with a priority fee?

8. Should we have surge pricing or priority matching during peak freight seasons?

9. Should the platform support Canada-USA cross-border loads at launch?

10. How do we handle time zone differences in load windows across US regions?

11. Should we support the ability for multiple shippers to split an LTL load on one truck?

12. What is our process for when a carrier refuses to accept freight as described (rejected loads)?

13. How do we handle concealed damage discovered after delivery?

Future Integrations

1. Should we have a carbon credit integration for carriers with green routing achievements?

2. Should we have an ELD (Electronic Logging Device) integration for HOS data?

3. Should we have a fuel card integration for carriers (e.g., OPIS, Comdata)?

4. Should we have a "Load Insurance" product shippers can purchase during posting?

CATEGORY 23 — LABOR, COMMUNITY & CULTURE

1. What labor law implications exist if drivers use our platform as their primary work source?

2. Could we be viewed as a joint employer with carriers?

3. Should we have policies around driver fatigue detected via GPS tracking?

4. What wellness or hours-of-service support features should we consider offering?

5. Should we implement anti-harassment or code of conduct rules between users?

6. How do we handle discrimination complaints between users?

7. What background check depth is appropriate for carriers and drivers?

8. Should we build in-app forums or community features — what moderation standards apply?

9. Should we use influencer or trucker ambassador programs?

10. Should we sponsor trucking events or charities?

11. How do we address potential overwork or burnout enabled by the platform?

12. Should we implement a carrier advisory board?

13. How do we handle office vs. fully remote team structure?

14. What is our employee handbook and policy framework?

15. Should we offer benefits like health insurance from day one?

16. What is our approach to mental health support for employees?

17. What is our diversity and inclusion hiring plan?

18. How do we maintain company culture as we scale?

19. How do we measure and improve employee engagement?

CATEGORY 24 — ETHICAL AI & FAIRNESS

1. What ethical guidelines govern our AI matching and verification systems?

2. How do we audit algorithms for bias (by carrier size, region, race, etc.)?

3. Should we publish transparency reports on AI decisions?

4. How do we handle appeals for AI-driven deactivations or rejections?

5. What is our policy on using user data to train models?

6. Should carriers opt-in to contributing their data for AI improvement?

7. How do we prevent discriminatory outcomes in load matching?

8. Should we have an independent ethics advisory board?

9. How do we balance profit with fair treatment of small carriers?

10. What are our environmental claims (carbon tracking) — what greenwashing risks exist?

11. What scenario planning exercises should we run quarterly?