Zero-Friction Mill Pattern

Overview

The Zero-Friction Mill Pattern is a core design philosophy of wiki/entities/b2bpaper. It recognizes a fundamental truth about the paper surplus market: mills will not adopt new technology unless it requires no change to their existing workflow. The pattern dictates that the platform must meet mills where they are, not where the platform wishes they were.

The Pattern

What Mills Do Today

Paper mill sales managers have surplus inventory to sell. Their current workflow:

1. Open Excel
2. List surplus items (paper type, GSM, width, quantity, grade, price)
3. Email the spreadsheet to brokers and trading contacts
4. Wait for responses via email or phone

This workflow has been the same for decades. Mills see no reason to change it.

What the Platform Does

Instead of asking mills to log into a dashboard, fill out web forms, or learn new software:

1. Mill emails their Excel file to the platform (same action they already perform)
2. AI parses the Excel spreadsheet -- handling varying formats, column names, units, and languages
3. Structured surplus data is extracted and stored
4. Geographic visibility rules determine which regions see the surplus
5. Matched buyers are notified automatically

The mill's workflow is identical. The platform is invisible to them.

Why This Matters

• Adoption barrier is zero -- no training, no onboarding, no software to install
• Trust is preserved -- mills are doing what they already trust (emailing Excel to a known contact)
• Data quality improves -- AI standardizes messy spreadsheet data into structured records
• Scale becomes possible -- what previously required manual broker processing is now automated

Relationship to Three Pillars

The Zero-Friction Mill Pattern is directly connected to the Trust pillar of the wiki/concepts/three-pillars framework. Mills share their surplus data because they trust wiki/entities/thierry and wiki/entities/morichal-trading. Forcing them onto a new platform would introduce friction that erodes that trust.

Technical Implementation

The pattern requires several technical capabilities:

• AI-powered Excel parsing -- one of the wiki/concepts/eight-core-actions (Excel Ingestion)
• Email ingestion pipeline -- Celery task + email client library (planned)
• Flexible data extraction -- must handle different column names, units, formats, and languages per mill
• Data validation -- AI-extracted data must be verified before entering the matching pipeline
• Fallback to manual -- when AI parsing confidence is low, admin review is required

Anti-Pattern: Dashboard-First

The explicit anti-pattern is building a mill-facing dashboard and expecting mills to use it. The project brief is clear: a mill dashboard is a "nice-to-have, not required." Mills should never need to log in to anything. If a dashboard is built, it is for admin monitoring, not mill data entry.

Sources

• raw/notes/productContext -- UX goals and mill user journey
• raw/notes/systemPatterns -- Zero-Friction Mill Pattern definition

Related

• wiki/concepts/three-pillars -- the trust pillar that this pattern preserves
• wiki/concepts/eight-core-actions -- Excel Ingestion action implements this pattern
• wiki/concepts/four-layer-architecture -- Data Bootstrap Layer handles ingestion
• wiki/entities/morichal-trading -- operational knowledge that informed the pattern
• wiki/entities/thierry -- domain expertise behind the pattern
• wiki/summaries/productcontext-summary -- full product context with mill user journey