Thefword

Thefword documents read-write integration with named PLM systems and factory tools on its Enterprise tier.

Production Handoff describes "two-way sync with Centric, PTC FlexPLM, Backbone, and custom systems through REST endpoints"; pushing "the approved tech pack and bulletin straight into the factory's planning system through API" (factory ERP and MES); sending "AQL plans and measurement points to inline and final inspection tools"; and versioned, vendor-scoped links for sourcing portals.

The Enterprise page repeats "PLM and ERP sync: Centric, FlexPLM, REST", and the Pricing FAQ says Enterprise plans include PLM and ERP integrations. Standard exports (.glb,.png,.pdf) come on every plan. Named native PLM connectors plus REST for custom systems are documented, read and write.

Integrations come only with Enterprise and are scoped through a "Book an integration review" step, the FAQ still frames PLM and ERP as integration planning, and credential scoping and revocation are not documented.

Sourcethefword.ai/production-handoff, /enterprise, /pricing, /faqs; readread 2026-09-16

Generation steps, approvals and deterministic checks chain into workflows of several steps on one product record. The Pricing page itemizes each bundle as sequenced steps, for example Trend to Tech Pack = Brief Workflow + AI Fashion Designer (20) + Garment AI Analysis (22) + Tech Pack (65), with an Autonomous Trend Run at the head of Trend to Brief.

Approved outputs route forward ("send the approved brief into AI fashion design, tech pack generation, and product launch workflows"), and Production Handoff converts approved tech packs into factory operations bulletins automatically and runs factory readiness checks before release. Generation steps chained with deterministic readiness checks and approval states mix fixed and autonomous steps, and revision history sits on the record.

Workflows are defined by the vendor rather than authored by the buyer. Branching, retries, fallback paths and reuse across teams beyond shared workspaces are not documented, and the site describes steps rather than an orchestration surface.

Sourcethefword.ai/pricing, /creative-direction, /production-handoff, /product; readread 2026-09-16

A brand's own knowledge base, historical tech packs and PLM data are ingested, but no retrieval structure over them is documented.

The Enterprise page says "your workspace also ingests your knowledge base, brand DNA, and PLM data", with pilot week two covering that ingestion; the Pricing page offers "bring your own knowledge base and PLM data" and "historical tech pack onboarding"; and Production Readiness says the workflow "can use prior tech packs, fit comments, grading decisions" and supplier notes.

Thefword's proprietary garment records tied to real factory outputs are the vendor's own dataset, not grounding in the buyer's data.

Whether brand data is retrieved at run time or trained in is not stated, though an article on brand DNA refers to custom models, and whether retrieved passages are visible or outputs cite sources is not documented.

Sourcethefword.ai/enterprise, /pricing, /production-readiness; readread 2026-09-16

Approvals gate downstream work and missing ones get flagged, but review of drafts is described as practice rather than a configurable gate. The Production Readiness page says "your technical team reviews every production field before supplier handoff", and the FAQ says a tech pack draft "should be reviewed by your team before manufacturing". Downstream workflows take an approved brief or approved tech pack as input, and Production Handoff's "factory readiness checks flag missing trims, lab dips, or approvals before the order is released to cutting".

The buyer cannot set which actions need sign off, who signs off or what happens when nobody does, and neither where approvals sit in a workflow nor autonomy modes by risk are documented.

Sourcethefword.ai/production-readiness, /production-handoff, /faqs; read; thefword.ai/production-handoffread 2026-09-16

Single sign on, role based access and isolated enterprise workspaces are documented, but no independent attestation is. The Enterprise page lists "SSO: Okta, Azure AD, Google", and the Pricing page's Enterprise card lists SSO, role-based access and data isolation. Data use: "paid customer content is not used to train shared models unless you expressly opt in in writing", and enterprise workspaces are isolated by default.

No SOC 2, ISO 27001 or equivalent attestation is published or pending. "GDPR and CCPA compliant data handling" is a regulatory posture rather than an independent audit, no trust portal is published, and the Enterprise page's "Download security overview" button leads to the pricing page rather than a document.

Sourcethefword.ai/enterprise, /pricing, /faqs; probe trust.thefword.ai; readread 2026-09-16

Every approval and revision is logged with who made it and when, but no record of what each AI step did is documented. Production Handoff's approval and revision history says "every change is logged with who approved it and when", an approval and revision log is among the handoff outputs, and revision history is carried on the tech pack record. That is an audit record of approvals at record level.

Nothing shows which inputs an AI step used or what it generated before a person edited it, and the log is not described as separating AI steps from human edits. Export and retention are not documented.

Sourcethefword.ai/production-handoff, /production-readiness; readread 2026-09-16

What the product calls memory is prior work reused as reference, not agent memory. The Production Readiness page's "pattern intelligence and technical memory" says "the workflow can use prior tech packs, fit comments, grading decisions, measurement logic, base blocks, and supplier notes to make the next style stronger", and a single product record carries revision history.

Learning across sessions is not a memory layer, and neither is the application's own database: the brand's prior tech packs reused as reference are a knowledge store, and the product record and revision history are the application's own data. No session, conversation or agent memory is documented, so there is nothing to review or delete.

Sourcethefword.ai/production-readiness, /product, /enterprise; readread 2026-09-16

Thefword's Enterprise tier names US and EU data residency, with a private, isolated tenant. Under "Security and integration", the Enterprise page lists "Data residency: US and EU regions" beside a private workspace, and the Pricing page's Enterprise card lists a private tenant and data isolation, noting that "enterprise workspaces are isolated by default".

Residency is an Enterprise feature. No selection surface, self-hosted, VPC or on-premises mode is documented, and whether model traffic, not only storage, stays in region is not stated.

Sourcethefword.ai/enterprise, /pricing; readread 2026-09-16

Four named workflow bundles run on any plan, but there is no browsable catalog. The bundles are Trend to Brief (30 credits), Trend to Tech Pack (115), Full Product Workflow (162) and a Launch Content Add-on (30), each a complete chained workflow that stands on its own.

Only the outputs, editable drafts, are documented as editable, not the workflows themselves. The blog's Fashion Design Brief Template is an article.

Sourcethefword.ai/pricing, /enterprise, /product; readread 2026-09-16

A person launches every workflow in the web app; nothing documented starts one on its own. Workflows start from the app ("Start free", "Generate a tech pack"); the Creative Direction page's first step is "Collect: bring in signals from market, culture, references"; and the Autonomous Trend Run is an 8-credit step inside a bundle the user launches. Market and trend signals are inputs a person brings, not events that start a workflow. The one automatic seam, Production Handoff converting "approved tech packs... into factory-ready bulletins automatically", starts from a person's approval.

No schedule, webhook, inbox or PLM event that starts a workflow is documented.

Sourcethefword.ai/creative-direction, /pricing, /production-handoff; readread 2026-09-16

No underlying model or provider is named, and buyers get no choice; the vendor controls the model.

No page names a model or provider, offers a provider list or mentions bring-your-own keys, and the Pricing page describes the platform as "not a generic image model dressed up for fashion" and prices each generation step in credits with no model option.

Working across models, routing tasks between them, or letting buyers bring their own providers and keys is not documented. The Pro plan's "bring your own fashion models" refers to on-figure model likenesses for AI photoshoots, not machine-learning models.

Sourcethefword.ai/pricing, /enterprise, /product; readread 2026-09-16

Thefword says enterprise customers get API access, but publishes no reference or SDK. The pricing FAQ says "Enterprise plans include PLM and ERP integrations, SSO, API access", the FAQ page lists API access for enterprise teams, and Production Handoff says the platform "receives approved tech packs through an API" and returns "a structured payload".

The API is named but not documented: no reference, endpoint list, authentication method, SDK or developer documentation is published, and no MCP support is mentioned.

Sourcethefword.ai/pricing, /faqs, /production-handoff, /llms.txt; probe docs.thefword.ai; readread 2026-09-16

Quality checks here test the buyer's product specification; no way to evaluate a change to the AI workflows is documented. Production Readiness lists POM validation and supplier readiness checks, and Production Handoff's factory readiness checks flag missing trims, lab dips or approvals; all of these test the garment specification, not the AI workflow.

The pilot's week-five KPI report, comparing outcomes with the agreed baseline, is delivered by the vendor's rollout team inside an engagement, and cost simulation reads on the garment. No evaluation harness, scored test cases, quality gates in a release path or optimization loop is documented, and testing with fixtures or scoring output quality over time is not described. The Pricing page's ROI calculator and 4.8/5 satisfaction figure are marketing.

Sourcethefword.ai/production-readiness, /production-handoff, /enterprise, /pricing; readread 2026-09-16

Outputs are made inside the web app and outside systems are reached through APIs, so there is no browser or computer control. The product generates moodboards, briefs, designs, tech pack drafts, 3D visualizations and on-model images in the app, and connects to PLM, ERP and factory systems through APIs; nothing operates a browser or desktop interface. AI photoshoots and virtual try-on render garments on figures, which is image generation, not computer use.

Sourcethefword.ai/product, /production-handoff, /pricing; readread 2026-09-16