Scope sold
APW sold design translation, sourcing support, managed development, and handoff — not just advisory discussion.
Password-protected evidentiary record
Private matter summary/Service dispute / partial performance
Midstream erosion
By March, the record showed paused tech-pack updates, rough BOM language, narrowed sourcing support, and continued founder-side translation.
Final non-closure
APW declared completion while refusing updated pricing and declining to confirm the factory could execute the packet without interpretation.
01 / Case overview
Matter Overview
The issue wasn’t aesthetic development. The issue was translation into a contradiction-free, factory-usable handoff.
Spoils had already substantially defined the product vision, silhouette, and direction.
APW was hired to operationalize that direction into manufacturable documentation, sourcing support, and managed handoff.
Months later, the record still showed paused tech-pack updates, rough BOM language, missing supporting notes, and a final refusal to confirm factory executability without interpretation.
This page is structured as a review record built from primary-source exhibits, chronology, admissions, and the final disputed handoff.
02 / Chronology
Chronology Matrix
Read this as a sequence of commitments, pauses, narrowed scope, and final completion language.
| Date | Event | Actor | Request / Promise | What happened | Why it matters | Exhibit |
|---|---|---|---|---|---|---|
| Aug. 20, 2025 | Scope confirmation email | Trevor / APW | One production tech pack, size variants, sourcing support, comparable quotes, managed development through T1/T2, and handoff closeout are confirmed in writing. | The promised deliverables are fixed before payment. | This is the operative source for what APW sold. | Exhibit B |
| Sep. 2025 | Onboarding and activation | Rabia / APW | APW positions itself as the operating lead for technical development and supplier coordination. | Client references are delivered into APW’s process and the project begins. | Shows APW taking responsibility for translation and coordination. | Exhibit B |
| Jan. 2026 | First sample fails | Factory / Spoils | Sampling should convert APW’s direction into a usable corrective loop. | Sample 1 arrives with zipper and construction problems. | This is when APW’s technical ownership should have tightened. | Exhibit C / Appendix 1 |
| Mar. 5, 2026 | Reset / recovery request | Michael | Michael requests a recovery plan, build recommendation, milestones, and a factory-usable source of truth. | He states the packet still is not contradiction-free or factory-ready. | Shows the core handoff problem remained open. | Exhibit E |
| Mar. 12, 2026 | T2 work acknowledged as paused | Rabia / Trevor | Clarify status and explain how handoff will actually be completed. | APW says T2 updates were paused and the sampling document was originally drafted by Spoils. | Founder-side translation was still doing active work. | Exhibit G |
| Mar. 13, 2026 | BOM limitation admitted | Rabia / APW | Provide a comparative BOM suitable for review and decision-making. | APW says the BOM will be basic and will not include pricing or suppliers. | A core handoff document is admitted incomplete on its face. | Exhibit G |
| Mar. 17, 2026 | Working BOM sent | Rabia / APW | Show revised BOM progress and move the packet toward T2 closure. | APW describes the BOM as still rough because exact weights remain pending. | The file is still a working draft, not a clean handoff. | Exhibit G |
| Mar. 17, 2026 | Tech-pack updates deferred | Rabia / APW | Advance the revised packet toward final alignment. | APW says it prefers to hold off on updating the tech packs until later discussion. | The packet is still open and unresolved in mid-March. | Exhibit G |
| Mar. 18, 2026 | Sourcing role narrowed | Rabia / APW | Clarify component sourcing and cost support tied to the recommended build. | APW says it does not do component sourcing or detailed cost breakdowns. | The sold sourcing / COGS value is materially narrowed. | Exhibit G |
| Mar. 31, 2026 | Current packet rejected as complete | Michael | Refund or deliver a true handoff-ready package. | Michael says the file is, at most, a revised packet for Sample 2, not final completion. | States the completion dispute in direct procedural terms. | Exhibit H |
| Apr. 3, 2026 | One last adjustment promised | Trevor / APW | Provide supporting notes and close the handoff cleanly. | Trevor says APW is making one last adjustment and will include supporting notes. | Confirms those notes still were not in the earlier handoff. | Exhibit H |
| Apr. 7, 2026 | Final completion-or-refund demand | Michael | Michael requests either a completed packet or a refund by a fixed deadline. | He again lists the missing construction recommendation, notes, pricing, and executable packet. | The open items are still the same at closeout. | Exhibit H |
| Apr. 7, 2026 | Completion declared / exit taken | Trevor / APW | Respond to the final request for handoff completion or refund. | APW refuses updated pricing, disclaims factory executability, and says the engagement is over. | Completion language and execution disclaimer land in the same email. | Exhibit H |
02A / Missed dates
Missed Dates / Missing Deliverables
Only the slippages, reversals, and unresolved handoff elements are highlighted.
| Item | Date requested | Date promised | What arrived | What was missing |
|---|---|---|---|---|
| Recovery plan with dates and ownership lanes | Mar. 5, 2026 | By Mar. 13 EOD | Follow-up discussion only | No concise written recovery plan with milestones and owners. |
| Comparative BOM suitable for review | Mar. 12–13, 2026 | For the next review call | A basic / rough BOM | No suppliers, no final pricing, and no locked component weights. |
| TP2 revision progress sufficient to instruct Sample 2 | Mar. 17, 2026 | Before next alignment | APW deferred the update | No consolidated revised packet at that point. |
| Supporting notes for handoff rationale | Before final closeout | Apr. 3, 2026 | Later notes, still detached from executability | No stand-behind packet APW would affirm as executable. |
| Updated pricing tied to recommended construction | Repeatedly through Mar. 31 and Apr. 7 | Needed for clean closeout | Refused on Apr. 7 | No final pricing tied to the final build path. |
| Factory-executable handoff | At final closure | APW said TP2 was finished | TP2 PDF plus notes only | APW would not confirm the factory could execute without interpretation. |
03 / Scope versus delivery
Scope vs Delivery
This matrix compares what APW sold with what the closeout record actually supports.
The product vision and silhouette were already substantially defined before APW’s paid translation work. The question is not whether APW contributed ideas. The question is whether APW converted that direction into a usable manufacturing handoff.
| Scope sold / promised | What was delivered | Status |
|---|---|---|
| Design translation into manufacturing specs | That was the core paid value, but the record never reaches a contradiction-free packet APW would own as executable. | admitted missing |
| Construction recommendation | APW discussed options and adjustments, but no final build path was carried through closeout with execution confidence. | partial |
| Sourcing / COGS / supplier work | APW sold quote and sourcing support, then later said it does not do component sourcing or detailed cost breakdowns. | admitted missing |
| Factory communication ownership | Factory contact existed, but March emails still show reliance on a Spoils-drafted source document and client-side translation. | partial |
| Tech pack completion | TP2 was delivered, but the final packet remained generic at core manufacturing and sourcing fields. | partial |
| Post-sample revision support | Some revisions occurred after Sample 1, but the corrective loop never closed into a final aligned packet. | partial |
| Supporting notes / rationale | Notes were promised and later attached, but not as part of a packet APW would stand behind as executable. | partial |
| Updated pricing tied to recommended construction | Updated pricing was expressly refused at closeout. | not delivered |
| Final factory-ready handoff | APW expressly declined to commit that the factory could execute the packet without interpretation. | admitted missing |
| Termination / closeout compliance | APW ended the engagement, rejected refund, and exited while the same open handoff items remained in dispute. | partial |
04 / Key admissions
Highlighted Admissions
These are APW’s own words.
Source excerpt
Exhibit G
“We are currently in the T2 stage of Tech Pack development, but we paused further updates...”
Source
Rabia Dastgir email
Date
Mar. 12, 2026
Why it matters
APW’s own status update says the handoff was still in revision.
Source excerpt
Exhibit G
“The document sent to the factory to initiate sampling was the one originally drafted by Spoils...”
Source
Rabia Dastgir email
Date
Mar. 12, 2026
Why it matters
Shows founder-authored translation still carried live factory work.
Source excerpt
Exhibit G
“We will have a basic Bill of Materials (BOM) ready for review, but it won’t include all the details like pricing and suppliers.”
Source
Rabia Dastgir email
Date
Mar. 13, 2026
Why it matters
A core handoff document is admitted incomplete.
Source excerpt
Exhibit G
“This is still rough because I’m waiting for the factory to provide exact weights for bolsters and base foam.”
Source
Rabia Dastgir email
Date
Mar. 17, 2026
Why it matters
The BOM is described as a working draft in APW’s own words.
Source excerpt
Exhibit H
“We are not providing updated pricing...”
Source
Trevor Crotts email
Date
Apr. 7, 2026
Why it matters
Updated pricing was withheld at the closeout moment.
Source excerpt
Exhibit H
“We are not able to commit the factory can execute it without interpretation.”
Source
Trevor Crotts email
Date
Apr. 7, 2026
Why it matters
APW disclaims the exact executable handoff standard in dispute.
05 / Working-file evidence
Working File vs Final Delivery
The issue is not whether APW produced files. The issue is whether the final packet actually closed the technical loop.
Exhibit G / Working-file page 1
This page captures three provisional admissions in one place: the BOM will be basic, it will omit pricing and suppliers, and it is still rough because exact weights remain pending.
Exhibit G / Working-file page 2
This page adds the other key admission: APW paused further updates while the document sent to the factory had originally been drafted by Spoils.
Right / supposed final-delivery evidence
Exhibit H / Final closeout page
The contradiction is visible on the page itself: APW closes the engagement, withholds updated pricing, and refuses to commit that the factory can execute without interpretation.
Appendix 2 / TP2 page 3
The construction page is diagrammatic and high-level. It does not close the loop on a full production-ready method.
Appendix 2 / TP2 page 6
The delivered BOM is visually tidy but generic at the exact fields where a factory-ready handoff should become specific.
Read together, the March email pages and the final TP2 pages show a packet that moved forward cosmetically but never crossed into an APW-backed executable handoff.
06 / Final email analysis
Final Email Analysis
This is the clearest contradiction in the record: completion language paired with execution disclaimers.
Source / date
Exhibit H, culminating in Trevor Crotts’ Apr. 7, 2026 message, read alongside Michael’s Mar. 31 and Apr. 7 replies.
Finding 01
Exhibit G
Rabia Dastgir emailsMar. 12–17, 2026
Earlier APW emails already described the packet as unfinished.
The March chain uses APW’s own words: paused, basic, and still rough.
Finding 02
Exhibit H
Trevor Crotts emailApr. 7, 2026
Updated pricing and closeout support were refused.
The final exchange rejects updated pricing while the same closeout items remain open in the record.
Finding 03
Exhibit H
Trevor Crotts emailApr. 7, 2026
APW would not stand behind factory executability.
APW declined to confirm that the factory could execute the packet without interpretation.
Finding 04
Exhibit H
Trevor Crotts emailApr. 7, 2026
APW still declared the engagement complete.
Completion language appears in the same exchange as the pricing refusal and execution disclaimer.
07 / Damages
Damages Schedule
This schedule is intentionally narrow and limited to current documented out-of-pocket costs.
Exhibit D / Raythy transaction proof
The transaction view shows three Raythy payments—$360 on Dec. 8, 2025, $360 on Dec. 16, 2025, and $400 on Mar. 30, 2026—for a documented sample-cost total of $1,120.
| Amount | Description | Basis | Evidence source |
|---|---|---|---|
| $5,000 | APW engagement fee | Core contract amount in dispute for the paid APW package. | Exhibit A (reserved) / Exhibit B |
| $1,120 | Documented Raythy sample payments | Filtered Raythy transaction record showing three outgoing sample-related payments of $360, $360, and $400. | Exhibit D |
| $6,120 | Current direct documented subtotal | APW fee plus the currently documented Raythy sample payments shown in the curated exhibit record. | Calculated from Exhibits A / B / D |
This schedule excludes founder time, delay cost, and future remediation cost.
08 / Exhibits
Curated Exhibit Register
Only the curated exhibit pack appears here.
Core exhibits appear first. Supporting appendices remain secondary.
Exhibit A
APW Payment Proof
Reserved slot for the card or statement proof of the $5,000 APW fee so the register starts with payment evidence rather than summary description.
PendingFile pending
Exhibit B
Scope / Engagement Sold
Aug. 20 scope email confirming deliverables, revisions, sampling management through T1/T2, and handoff expectations.
PDFOpen
Exhibit C
Founder Technical Directions Sent to Factory
Jan. 26 founder-authored technical direction showing the client was still supplying executable factory instructions inside APW’s paid process.
PDFOpen
Exhibit D
Raythy Transaction Proof
Filtered transaction record showing three Raythy payments of $360, $360, and $400, totaling $1,120 in sample-related out-of-pocket cost.
WEBPOpen
Exhibit E
Reset / Recovery-Plan Request
March recovery-plan chain where Michael asks for a corrected technical path, clear milestones, and a factory-ready source of truth.
PDFOpen
Exhibit F
Supposed T2 Handoff Without Notes
The March 17 handoff packet preceding the later notes and final closeout language, useful for showing what APW was calling progress before the record was actually closed.
PDFOpen
Exhibit G
Incomplete TP2 Handoff / Working-File Admissions
March chain capturing the “basic BOM,” “still rough” BOM, paused TP updates, and the admission that the factory had been sent the Spoils-drafted document.
PDFOpen
Exhibit H
Final Handoff Chain
Final email chain where APW declares the engagement complete, refuses updated pricing, and declines to commit that the factory can execute without interpretation.
PDFOpen
Appendix 1
Project Overview / Timeline Support
APW project overview sheet showing GTM structure, timing framework, and sample-charge references useful for context but secondary to the core dispute emails.
XLSXOpen
Appendix 2
TP2 PDF Packet
The delivered TP2 packet, used here to show the gap between polished presentation and factory-usable technical detail.
PDFOpen
Appendix 3
APW Client Engagement Agreement
The formal engagement agreement with the blank services field, included as appendix support rather than as the primary scope source.
DOCXOpen