Redo

1.1 Identity and platform scope

Redo presents itself as a Draper, Utah technology company serving direct-to-consumer brands. Its current platform spans returns and claims, shipping and fulfillment, order tracking, support, marketing, payments, and international returns rather than remaining a single-purpose returns portal. The product thesis is vendor consolidation: post-purchase interactions share customer and order data, allowing Redo to automate exchanges, support, recovery, and fulfillment workflows from one operating surface. Shopify's discussion of direct commerce supports the strategic value of first-party purchase and preference data, but it does not validate Redo's execution or economics. The available evidence therefore supports the product category and operating model, while founding date and a complete corporate history remain unverified.[CO001, CO006, CO016]

1.2 Capital, scale, and milestones

On June 23, 2026, Redo announced an $81 million Series B at a reported $1.25 billion valuation, led by Smash Capital with Pelion Venture Partners and Cervin Ventures also participating. The same syndicated company release said more than 4,100 brands used the platform and more than 1,750 used multiple offerings. Redo's current homepage now says it serves more than 4,500 brands, which is directionally consistent with expansion but is not an independently audited customer count. The financing release also says Redo had acquired ReturnBear to add international return and fulfillment operations across more than 100 countries. Total capital raised, revenue, ARR, margins, retention, and headcount are not disclosed in the assigned evidence and must remain gaps.[CO002, CO003, CO004, CO005, CO010, CO013]

1.3 Leadership and stakeholder concentration

The accessible leadership evidence identifies Sterling Snow as co-founder and chief executive and Aaron Evett as chief commerce officer. It does not establish the full founder group, board composition, executive tenure, ownership, voting rights, or succession planning. That limited disclosure makes key-person and governance analysis preliminary. Economically important stakeholders include the Series B lead and existing investors, the acquired ReturnBear operation, Shopify as the principal commerce ecosystem highlighted by product documentation, and merchants whose adoption sustains the usage-led model. None of the public sources specifies investor control rights or liquidation preferences, so the financing documents and capitalization table are required before drawing control conclusions.[CO003, CO009, CO010, CO011, CO012]

1.4 Business model and diligence boundaries

Redo advertises its returns portal as free and says it covers return-label costs, while an independent August 2026 comparison explains that the economics rely on shoppers opting into paid returns coverage at checkout and that several adjacent modules are usage-priced. This can accelerate adoption and cross-sell, but it shifts diligence toward checkout consent, fee disclosure, merchant concentration, and unit economics rather than a conventional seat-based SaaS model. The comparison also characterizes Redo as Shopify-shaped and notes that portal vendors emit events while warehouse and ERP systems retain physical and financial control. The cited FTC fee rule currently covers live-event tickets and short-term lodging, not general ecommerce returns; therefore it is a disclosure benchmark, not evidence that Redo violates that rule. Product-level legal review across relevant jurisdictions remains necessary.[CO007, CO008, CO009, CO014, CO015]

1.5 Exhibits

2.1 Market boundary and substitutes

Redo's addressable category is narrower than ecommerce or DTC commerce: it begins with shopper-facing returns and exchanges, then extends into order tracking, package protection, fulfillment support, customer service, marketing, and AI-assisted commerce workflows. A third-party comparison draws an important boundary between the customer-facing portal and the physical or financial back end: authorization, exchange choice, labels, and inbound tracking sit in the portal, while receiving, inspection, disposition, inventory state, and accounting remain with an ERP, WMS, warehouse, or 3PL. For apparel, the same comparison estimates online return rates at roughly 20% to 30% of orders, versus under 10% for most other retail, making returns software especially relevant in high-return categories. Status-quo substitutes include manual support workflows, native commerce-platform features, separate point solutions, and internal ERP or warehouse processes; none should be counted automatically as spend available to Redo.[CM005, CM009, CM010, CM011]

2.2 Sizing lenses and limits

The available market data establishes demand context but not a defensible TAM/SAM/SOM. Shopify's 2026 DTC guide cites a third-party projection that the global DTC ecommerce market grows from about $163 billion in 2024 to $595 billion in 2033, and separately cites an estimate that ecommerce represented about 23.5% of retail sales. Those figures are broad commerce-flow measures, not software revenue pools, and therefore cannot be applied as Redo's TAM. At the company level, a June 2026 company release syndicated by two outlets says more than 4,100 brands use Redo and more than 1,750 use multiple offerings. An archived company homepage separately states 3,000-plus ecommerce businesses, a compatible but less current floor. These adoption counts indicate installed footprint and cross-sell evidence; without merchant GMV, contract values, eligible-brand counts, or revenue, they do not isolate serviceable market value or market share.[CM001, CM002, CM003, CM004, CM008]

2.3 Buyers, users, payers, and adoption path

The economic buyer varies by module. Ecommerce and customer-experience leaders own the returns and shopper journey, operations teams care about label expense, routing, fraud, and warehouse handoffs, support leaders evaluate ticket automation, and finance tests whether retained revenue and labor savings exceed usage charges. Redo's published pricing lowers software-entry friction by listing the returns portal as free and saying Redo covers return-label costs, while charging by usage for modules such as tracking, checkout optimization, and support. The shopper may nevertheless become an indirect payer when a merchant adopts opt-in return coverage at checkout, so consent, presentation, and brand impact belong in procurement. Company-reported outcomes such as a 17% average exchange-rate increase and up to 60% automated ticket resolution are adoption hypotheses to test in a merchant cohort, not independent market benchmarks. Shipping economics remain material: Shopify cites an average 8.7% of annual business expenses spent on shipping before storage, packing, returns, or special requirements.[CM006, CM007, CM012, CM013, CM014]

2.4 Drivers, constraints, and valuation relevance

Demand is driven by high return intensity in apparel, merchant interest in converting refunds into exchanges, pressure to consolidate fragmented apps, and the use of shared order and customer data across support and marketing. Adoption is constrained by Shopify concentration, integration with the systems that own inventory and money, uncertain shopper acceptance of checkout coverage, and the need to validate vendor-reported ROI. A Shopify process-management guide identifies compatibility, workflow complexity, coding requirements, and user access as core software-selection criteria; these translate directly into implementation burden for a multi-module post-purchase platform. Fee presentation is another diligence issue. Current FTC staff guidance for unfair or deceptive fees is expressly scoped to live-event tickets and short-term lodging, so it is not evidence that Redo's retail model is covered by that rule. It nevertheless states that optional ancillary charges must be clearly disclosed and included in the final amount before payment, a useful control principle for shopper-funded coverage. Valuation should therefore rely on verified merchant economics, retention, module attach, and regulatory review rather than a top-down share of broad DTC GMV.[CM005, CM009, CM011, CM015, CM016]

2.5 Exhibits

3.1 Landscape and buyer alternatives

The competitive set spans direct returns portals, enterprise post-purchase suites, Shopify-native components, internal workflows, and the status quo of multiple point solutions. A 2026 vendor comparison places Redo, Loop, and Narvar at the shopper-facing layer that authorizes returns, offers exchanges, creates labels, and tracks inbound parcels; it explicitly separates those functions from warehouse inspection, disposition, inventory accounting, and wholesale credit workflows. Redo's own materials broaden the contest further by positioning one platform across returns, tracking, fulfillment, support, and marketing. Shopify can also supply native customer-account, automation, and support components, giving merchants a credible build-or-compose alternative even when they do not select another dedicated portal.[CP001, CP007, CP011, CP013, CP014]

3.2 Capability, distribution, and operating fit

Redo's published edge is breadth plus a Shopify-centered distribution surface rather than a uniquely proven returns algorithm. The company describes AI exchange recommendations, image and policy review, support automation, and a unified data layer; Shopify's merchant-review summary also says users replace multiple applications and value complex custom flows. Loop is presented by the comparison publisher as the exchange and policy specialist, while Narvar is positioned for multi-brand, multi-region, fraud-intensive enterprise deployments. Those are directional vendor descriptions, not an independent benchmark. Buyers should therefore test policy configurability, inventory-location logic, fraud overrides, event write-back, implementation burden, and support quality against their own order and return history.[CP005, CP006, CP007, CP010, CP011, CP012]

3.3 Pricing and packaging

Redo's pricing page lists its returns portal as free and says Redo covers return-label costs, with paid modules layered around that core: order tracking is listed at $0.08 per tracked order, checkout optimization at $0.40 per order, and support at $0.20 per resolution. The reviewed comparison says the model is funded by optional shopper-paid return coverage at checkout. It describes Loop Core as another shopper-funded free tier, with paid plans starting at $155 and $340 per month, while Narvar does not publish pricing. These are list prices and packaging descriptions, not realized contract economics; discounts, attach rates, coverage losses, and implementation costs remain unavailable.[CP002, CP003, CP008, CP009, CP010]

3.4 Moat durability and displacement risk

Redo has credible distribution signals: the Shopify App Store showed 814 reviews, a 4.9 rating, and 96% five-star ratings when fetched, while a June 2026 company release reported 4,100 brands and 1,750 multi-product merchants. The same release tied its $81 million Series B to AI, international expansion, and the ReturnBear acquisition. Yet this evidence is company-issued or platform-hosted rather than an independent retention benchmark. Shopify can expand native post-purchase functions, direct rivals can copy shopper-funded packaging, and internal builds can keep workflow control. The FTC fee rule reviewed here applies to live events and short-term lodging, so it does not establish compliance for ecommerce return coverage; jurisdiction-specific legal analysis remains necessary rather than assuming either safety or prohibition.[CP004, CP005, CP006, CP013, CP014, CP015, CP016]

3.5 Exhibits

4.1 Revenue model and pricing

Redo uses a land-and-expand monetization design rather than a single disclosed subscription. Its official pricing surface lists the returns portal as free and says Redo covers return-label costs; an adjacent-industry comparison describes the economic mechanism as an optional shopper-paid returns-coverage fee at checkout. Around that anchor, Redo publishes usage prices for checkout optimization, order tracking, support resolutions, email and SMS, and recovered carts, while returns AI remains custom-priced. These are list prices, not realized revenue, discounts, contract values, or gross margin. The model may lower initial merchant adoption friction, but underwriting requires the revenue mix and unit contribution of each stream, especially the shopper-funded coverage pool and label-cost exposure.[CI001, CI002, CI003, CI010]

4.2 Commercial traction and expansion signals

Public evidence offers scale and cross-sell proxies but no audited financial traction. Redo's current homepage says it serves more than 4,500 brands, and the June financing release says more than 1,750 merchants use multiple offerings. Those figures support a plausible expansion motion from free returns into paid adjacent modules, but they do not reveal paying-customer count, average revenue per merchant, cohort retention, sales cycle, CAC, or payback. Redo also publishes merchant-reported outcomes such as higher exchange rates and retained revenue, with an explicit warning that individual results vary. These outcomes are product-value signals, not evidence of Redo's own revenue, margin, or merchant-level profitability.[CI004, CI005, CI011]

4.3 Cost structure and unit-economics constraints

Redo's cost base cannot be reconstructed from public disclosures. The operating model likely combines software delivery with return-label funding, customer support, AI inference, payments, carrier connectivity, and increasingly physical international returns operations. Redo says ReturnBear added local inspection, refurbishment, re-fulfillment, and reshipment capabilities across more than 100 countries; those activities can introduce service-delivery and working-capital complexity beyond a pure software model. Shopify's merchant guidance identifies acquisition, pick-and-pack, packaging, parcel shipping, 3PL services, discounts, spoilage, and returns as order-level profitability inputs, while an industry comparison notes that portals still depend on ERP and warehouse systems for inspection, disposition, inventory, and accounting. None of these benchmarks discloses Redo's actual costs.[CI008, CI009, CI012, CI013, CI014]

4.4 Capital adequacy and financial verdict

The $81 million Series B is verified financing, not evidence of cash available today or a measured runway. The company said proceeds would support product development, AI initiatives, and international expansion, and it had already deployed an unspecified portion to acquire ReturnBear. No reviewed source reports cash on hand, monthly burn, debt, project-finance obligations, acquisition consideration, preferred terms, liquidation preferences, or a next-round trigger. The FTC fee-rule source retained for refresh evidence applies specifically to live-event tickets and short-term lodging, so it does not establish that Redo's checkout coverage is governed by that rule; product-level and jurisdiction-specific legal analysis is still required. The financial verdict is therefore evidence of a credible multi-stream model and ample recent financing, but insufficient evidence of revenue quality, margin durability, or capital adequacy.[CI006, CI007, CI008, CI009, CI015, CI016]

4.5 Exhibits

5.1 Product surface and customer workflow

Redo's current public surface is broader than a returns portal. Its homepage groups the proposition around marketing, payments, shipping, and returns, while the pricing page itemizes returns, claims, shipping and fulfillment, warranties, checkout optimization, upsell, email and SMS, order tracking, recovery, identity resolution, support, AI agents, and chargeback representment. Returns is listed as free and includes a portal, analytics, return-label coverage, and return-specific AI agents; several adjacent products use transaction or resolution pricing. That structure supports a land-and-expand product strategy rather than a single-SKU application. A 2026 third-party article reported that more than 1,750 customers used multiple Redo offerings, but the claim is not independently audited and should not be treated as retention evidence. For merchants, the practical workflow is shopper self-service first, with exchanges, claims, support, and tracking sharing order and interaction context.[CE001, CE002, CE003, CE005, CE006]

5.2 Operating architecture and dependencies

The observable architecture is an operating workflow, not a disclosed software stack. Shopper portals and agents initiate requests; policy, recommendation, and fraud logic determine the proposed outcome; commerce-system events then pass work to fulfillment, warehouses, and finance. An ERP-focused comparison describes portals such as Redo as the customer-facing authorization and decision layer, while inspection, disposition, returns-in-process inventory, reconciliation, and accounting remain warehouse and ERP responsibilities. This boundary makes implementation quality dependent on clean events, inventory-location accuracy, and integrations rather than the portal alone. Public material is strongly Shopify-shaped, although the comparison reports support for BigCommerce and Salesforce Commerce Cloud. Redo also claims international labels in more than 100 countries, five in-country hubs, and three-to-four-day refunds; these are company-issued operating claims, not verified performance benchmarks.[CE007, CE008, CE009, CE011, CE012]

5.3 Maturity, differentiation, and control gaps

Product maturity is clearest in packaging and operating breadth: Redo offers white-glove onboarding, publishes granular usage prices, and describes a consolidated data surface for order, return, claim, support, and marketing workflows. Its own 2025 article claimed that AI agents could resolve up to 60% of support tickets, but no cohort, denominator, evaluation method, or independent benchmark was disclosed. A direct competitor's 2026 comparison adds a useful caution: Redo's published help materials list order-tracking actions for the agent, while the AI product page reportedly names order, return, and claim inputs without naming tracking data. That inconsistency requires implementation-level verification, not a conclusion that tracking data is absent. Trust diligence remains incomplete: the assigned evidence contains no SOC 2 or ISO 27001 report, penetration-test summary, public status history, SLA, data-flow map, API documentation, or public repository activity. Shopify's own guidance underscores that first-party customer data creates governance and security obligations. The FTC fee rule reviewed here directly covers live-event tickets and short-term lodging rather than general ecommerce, so it is not proof that Redo's optional shopper-paid coverage is compliant; it is a control-design reference for affirmative selection, fee purpose, and clear disclosure.[CE004, CE010, CE013, CE014, CE015, CE016]

5.4 Exhibits

6.1 Customer segments, users, and payers

Redo's commercial base is best understood as direct-to-consumer ecommerce merchants rather than shoppers, even though shoppers are the end users of return, claim, tracking, and support flows. Ecommerce, operations, customer-experience, and finance teams can each own part of the buying decision: the free returns portal addresses operating cost, while usage-priced tracking, support, checkout, and marketing products create additional merchant-paid expansion paths. A third-party comparison says the core returns model can instead be funded by an optional shopper-paid coverage charge at checkout, creating a second payer and making disclosure and brand trust part of the product decision. Shopify's broader DTC analysis also explains the strategic buyer appeal: direct transactions expose purchase-frequency and product-preference signals that can support retention workflows. The retained evidence does not segment Redo's 4,500+ brands by revenue, order volume, vertical, geography, or plan, so the mix of small Shopify stores versus larger enterprise deployments remains unknown.[CU006, CU007, CU009, CU013, CU016]

6.2 Adoption trajectory and multi-product expansion

The available snapshots indicate expanding reach, but they are not a cohort series. An archived company page said 3,000+ ecommerce businesses trusted Redo; TechBuzz reported more than 4,300 brands in June 2025; and the current company page says 4,500+ brands. Differences in page date, counting methodology, and the meaning of "brand" versus "business" prevent a defensible growth rate. The strongest expansion signal is TechBuzz's report that more than 1,750 merchants, roughly 40% of the base at that time, used multiple Redo products. That supports land-and-expand behavior, but it is a company-supplied figure carried by media reporting and lacks product-level attach rates, revenue contribution, cohort age, or renewal evidence. Investor diligence should therefore treat cross-product adoption as promising commercial proof rather than as a substitute for NRR, GRR, or churn.[CU001, CU002, CU003, CU004, CU015]

6.3 Customer proof, deployment quality, and durability

Public proof is much stronger at aggregate scale than at the named-account level. Redo's archived page identifies Primo Golf in a testimonial about consolidating point solutions, but it gives no deployment date, contract scope, baseline, or quantified retention outcome. The current page adds testimonials describing a ShipHero integration and a 78% increase in exchanges, yet the merchants are not identified in the fetched text. A company blog separately claims a 17% average increase in exchanges after merchants moved from legacy return platforms. These claims show the intended value mechanism, but they are company-issued and have unspecified samples and denominators. No retained source reports NRR, GRR, churn, renewals, average contract length, referenceable customer cohorts, or production-versus-pilot status. Customer calls and cohort exports are therefore necessary before assigning durable revenue quality to the adoption figures.[CU005, CU008, CU010, CU015]

6.4 Customer journey, value loop, and friction

The customer loop starts with a merchant facing high returns volume and shopper expectations for a low-friction experience. Redo lowers the entry barrier with a free portal and company-funded labels, while the shopper-coverage mechanism can shift part of the economics to the checkout. Once installed, exchange recommendations and self-service workflows aim to convert refunds into retained revenue; successful merchants can then add tracking, support, fulfillment, and marketing modules. Industry evidence makes the stakes clear: NRF estimated that 15.8% of annual retail sales would be returned in 2025, and 71% of consumers said a poor returns experience would make them less likely to shop with a retailer again. The principal friction is trust. A comparison source warns that shopper-funded coverage is a brand decision, while the cited FTC fee rule applies only to live-event tickets and short-term lodging and therefore does not resolve the legal treatment of Redo's general ecommerce checkout model.[CU005, CU006, CU009, CU011, CU012, CU014]

6.5 Exhibits

7.1 Ranked risk view

The central diligence risk is not a documented enforcement action against Redo; none is established by the assigned evidence. It is the combination of shopper-facing protection products, fee-sensitive checkout design, free merchant entry points, and limited public proof about legal classification or unit economics. The FTC fee rule reviewed here directly covers live-event tickets and short-term lodging, not Redo's disclosed ecommerce categories, so it is a disclosure-principles signal rather than proof of applicability. A proposed case concerning competitor Route likewise illustrates a possible fee-presentation theory but is neither a Redo incident nor an independent benchmark of Redo's compliance. The heatmap therefore ranks residual exposure, not proven violations, and assigns lower mitigation maturity where public controls are absent.[CR001, CR002, CR003, CR006, CR009, CR015]

7.2 Legal and regulatory exposure

Redo's public pages describe claims, warranties, payments, checkout optimization, cross-border operations, and package protection, but the assigned evidence does not identify the legal entities, licenses, insurance counterparties, policy wording, jurisdictional exclusions, or consumer-consent controls supporting those products. FTC staff guidance says covered businesses may not misrepresent fee purpose or amount and treats default billing, pre-checked boxes, and opt-out provisions as potentially making a fee mandatory. That rule has a narrow stated sector scope, yet the control lesson is relevant: diligence should reconstruct Redo's checkout flows by jurisdiction and product, test affirmative consent and refund disclosures, and obtain counsel's classification memo. The competitor case heightens the diligence priority without establishing misconduct by Redo.[CR001, CR002, CR003, CR007, CR008]

7.3 Operational, quality, AI, and financial-model exposure

Redo reports labels in more than 100 countries, five in-country return hubs, licensed customs brokers, and three-to-four-day refunds, creating execution dependencies across carriers, brokers, hubs, data flows, and merchant systems. Its pricing page also shows free returns and claims products, return-label funding, revenue-share choices, transaction pricing, per-resolution pricing, and performance fees. That breadth may diversify monetization, but public evidence does not disclose gross margin, fraud losses, subsidy incidence, service-level performance, or working-capital requirements. Company-authored AI results and merchant outcomes are not independent validation; the company's own interview stresses human oversight. Investment approval should require cohort economics, error and fraud rates, incident logs, and product-level profitability.[CR005, CR006, CR007, CR008, CR013, CR014]

7.4 Partner dependencies, monitoring, and thesis-break triggers

The product narrative is explicitly Shopify-centered, while Redo is simultaneously expanding across commerce software, customer support, payments, shipping, and international returns. Company disclosures of 4,100 brands and 1,750 multi-offering merchants in June 2026, alongside current marketing to 4,500+ brands, indicate reach but do not reveal revenue concentration, retention, or Shopify-channel dependence. The June financing supplies expansion capital, not proof of runway or sustainable economics. Monitor platform-policy changes, merchant churn, broker or carrier service failures, claim-loss ratios, AI escalation rates, regulatory inquiries, and product-level gross profit. Break the thesis if counsel identifies unlicensed regulated activity, audited cohorts show structurally negative contribution margins, a critical platform dependency lacks transition rights, or material security findings remain unremediated.[CR004, CR005, CR009, CR010, CR011, CR012, CR016]

7.5 Exhibits

8.1 Decision and price discipline

The recommendation is research-more, with medium confidence, high risk, and a stretched valuation stance. Two third-party reports describe an $81 million Series B at a $1.25 billion valuation, while Redo's current homepage claims more than 4,500 brands and the June financing coverage attributes more than 1,750 multi-product merchants to the company. Those adoption signals are useful but cannot replace audited revenue quality: the retained financing accounts provide no ARR or revenue, gross margin, retention, cash burn, net cash or debt, dilution, or liquidation preference data. A target return, hold period, and supported exit value therefore cannot be calculated from public evidence. Entry discipline should begin with normalized enterprise value and audited forward revenue, then test whether Redo earns a premium through growth, retention, and margins rather than assuming the reported round price is intrinsically fair.[CV001, CV002, CV005, CV006, CV007, CV016]

8.2 Financing and benchmark context

The closest retained public-market reference is not a direct comparable: Multiples.vc reports a 1.7x next-twelve-month EV/revenue multiple for public e-commerce software as of October 21, 2026, while SaaSrise cites a 3.8x revenue multiple for private SaaS M&A. The first uses enterprise value and forward revenue; the second is a broad private transaction reference; Redo's $1.25 billion figure is a reported financing valuation with undisclosed net debt, cash, and preference terms. Dividing the reported mark by 1.7x produces an illustrative revenue hurdle of about $735 million, not an estimate of Redo revenue and not a valid equity valuation without capitalization adjustments. The exercise shows how demanding the public mark could be, while the absence of audited inputs prevents a defensible valuation range.[CV001, CV002, CV003, CV004, CV005, CV012]

8.3 Thesis, anti-thesis, and scenarios

The thesis is that returns are a large, persistent commerce problem and Redo can use free entry products, usage-priced modules, and AI-assisted exchanges to consolidate post-purchase workflows. Retail TouchPoints, citing an NRF and Happy Returns study, reports a 19.3% online return rate for 2025, while Redo claims a 17% average exchange increase after merchants move from legacy platforms. The anti-thesis is that these company-reported outcomes may not translate into durable recurring economics, and an independent comparison says the free returns model is funded through shopper opt-in coverage. Legal commentary warns that separately paid package protection can resemble insurance under broad state definitions. Bull, base, and bear cases are therefore framed as diligence conditions rather than false valuation precision.[CV008, CV009, CV010, CV011, CV013, CV014, CV015, CV016]

8.4 Exit readiness, diligence asks, and thesis-break triggers

Exit readiness is unproven because the public record does not reveal the financial durability or preference stack an acquirer or public investor would underwrite. Before investment, obtain audited revenue by module, geography, and payer; ARR reconciliation; cohort gross and net revenue retention; gross margin by software, fulfillment, and protection products; customer concentration; CAC payback; burn and runway; net cash and debt; and the fully diluted cap table with liquidation preferences. Also require state-by-state legal analysis and licensing evidence for shopper-paid protection. Thesis-break triggers include audited NRR below the cited 101% private-SaaS median, gross margin below the cited 75% median without a credible improvement plan, an enterprise-value multiple above the public e-commerce reference without superior growth, or a material regulatory restriction on a core monetization stream. Evidence clearing those tests, paired with an entry price that supports the investor's required return, could move the recommendation.[CV003, CV005, CV010, CV011, CV013, CV014, CV016]

8.5 Exhibits