How is this different from data mapping between systems?

Mapping preserves what it claims to cure: both identifiers survive plus a third artifact to maintain, it scales pairwise, and it decays when either model changes. Coalesce does not map — two parties specifying the same thing produce one identity.

Who is Coalesce Workstream for?

Structural and graphic designers, project coordinators, and estimators in the paperboard and corrugated packaging value chain — mills, converters, brand owners, and 3PL/warehousing.

Identity, computed from content

Q: What does Coalesce Workstream do?

Coalesce computes a work product's identity from its content, so the same packaging specification created twice — by anyone, anywhere in the supply chain — is recognized as one thing rather than as two unrelated part numbers.

The same specification created twice is recognized as one thing.

Coming soon to a supply chain near you

Structural or graphic designers, project coordinators, and estimators in paperboard and corrugated packaging: send your name and company to reserve a free trial at launch.

free-trial@edgewoodsoftwarecorp.com

Company Purpose

Coalesce is a platform for manufacturing that computes a work product's identity from its content, so that the same specification created twice — by anyone, anywhere in the supply chain — is recognized as one thing.

The name is the thesis: identical work products coalesce onto a single canonical identity.

The Problem

Identity in manufacturing is assigned, not derived

A part number is issued by one company's ERP and encodes nothing about the thing itself.

Two firms holding physically identical product have no way to discover that fact.

Duplication is not an accident to be cleaned up afterward. It is the default output.

One specification, four records

Converter re-draws it Broker re-specs it Three suppliers re-quote it Brand owner re-keys it

Every tool in use today — CAD by email, ERP part numbers, spreadsheets, recognition by eye — stops at the company boundary, which is exactly where duplication happens.

The Cost of Duplication

$226 billion a year is spent searching for and validating specifications

6.0M US knowledge workers who create and consume specifications

17 hrs Per week spent searching and validating information (IDC)

$34B Annual waste removed at 30% adoption and half the search time

At every plausible knowledge-worker share — 10% to 25% — the answer is tens of billions of dollars a year, against an entry-segment revenue ceiling of $1.19 billion.

The Solution

Coalesce derives identity from the work product itself

Identity is computed

A specification's identity comes from its properties plus the identities of what it is composed from, cascading up the bill of materials.

Approval is permanent

Freely editable in progress, frozen on approval. No versions, no revision chain — derived identity is stable only if content is.

The model composes

Each entity carries only what belongs to it, and assembles lower-order entities by reference. Clean boundaries make the cascade possible.

De-duplication stops being a maintenance activity and becomes a property of the system. The first customer gets a well-modeled specification system; the thousandth arrives to find their work product already has an identity.

Why Now

Three preconditions are satisfiable at once for the first time

Design geometry normalizes reproducibly

Drawings that mean the same thing reduce to one canonical form, produced identically every run. Built and verified here.

Databases treat permanence as native

Immutable, append-only storage makes freeze-on-approval the natural shape rather than a discipline imposed on top.

Professional design runs in a browser

Nothing installed, nothing licensed per desktop, nothing emailed — removing the company boundary duplication lives on.

The market did not have to change. The technology did.

Market Entry

US corrugated and folding carton

The ceiling is the whole value chain, because a specification passes through every link of it — from the mill's furnish to the warehouse that stores the finished case.

Mills — material specifications Converters — structure/graphic specifications Brand owners — read-only 3PL and warehousing — read-only

Subscriber ceiling 1,144,560

Average annual subscription $1,036

Revenue ceiling $1.19B

The Plan Against That Ceiling

of one segment, in five years: 23,119 subscribers and $22.4M ending ARR.

No incumbent has to be displaced and no industry converted. Two subscribers in every hundred.

US packaging value chain $1.19B

US manufacturing value chain $41.4B

Global manufacturing value chain Headroom

One method at every tier: employment served × $1,036. Post-MVP domains are reserved namespaces, not roadmap promises.

Competition

The industry has converged on one approach: mapping

Where mapping stops

It preserves what it claims to cure — both identifiers survive, plus a third artifact to maintain.

It scales pairwise, and the escape hatch turns a technical problem into a governance one.

It is probabilistic, and it decays the moment either model changes.

Coalesce does not map

Two parties specifying the same thing produce one identity, not two records in need of correspondence.

Incumbents cannot follow incrementally: deriving identity invalidates the mapping layer they already sold.

The model's distinctions took a domain expert to see. A flattened model cannot produce stable identities.

Seats today belong to Esko, Adobe Illustrator, Amtech, and general-purpose SaaS. On the axis that matters — where identity comes from — the field is unoccupied.

Product

Five domains, each composing the ones beneath it

Materials Paperboard and corrugated recipes

Designs Structure/Graphic constituents

Processes Action distinguished from method

Components Assembled by reference, not absorption

Quotes The top of the identity cascade

It answers "does this already exist?" without searching — the answer arrives as a property of saving the work.

It carries identity across company boundaries intact, with no integration between systems.

The Hard Part

A single object can be drawn in unlimited ways

Split a line in half and rejoin it. Nothing about the object changed and nothing looks different — but the two files no longer match, and no amount of care makes them match.

Node counts, segment ordering, how a transform is expressed: all authoring accidents. Two drawings of the same design are essentially never the same file.

So Coalesce normalizes a drawing to a canonical form that reflects what the designer meant, and hashes that — never the original file.

Protected by three US patents

US 11,308,113 B1 US 11,847,129 B2 US 12,158,891 B2

Alongside them: a professional design pipeline modified to produce reproducible output. Core platform built and determinism verified.

Business Model

Creator seats land the account; read-only seats expand it

Creator Permission to build specifications. Typically the vendor — a converter such as WestRock.

Read-only Access without creation. Typically the vendor's customer — a brand owner such as P&G.

Administrator Permission and account management, roughly two per customer.

593 Subscribers per customer, observed

$1,036 Blended annual subscription

Thirty-nine customers carry 23,119 subscribers. Coalesce sells to a company and is adopted by a supply chain.

Team

Domain architecture, then implementation

Dave Co-founder, domain expert

Author of the architecture and the domain model, and principal author of the three issued patents — he wrote most of the specification and claims himself, with a top-tier firm editing.

Chris Implementation

Clojure/ClojureScript, Fulcro, Pathom, Datomic.

Jarrett Implementation

Clojure/ClojureScript, Fulcro, Pathom, Datomic.

Board: Dave is currently sole member; the company expects to expand to a conventional three- to five-member structure in connection with an outside investment.

De-duplication is not an operation the system performs. It is a property the system has.

The schema, the identity cascade, and the pipeline internals are available on demand — and best seen in a working demonstration.

See it working →

Videos & Downloads

See it, then read the whole argument

Derived identity, in the product

Files, folders, and revisions stop being your problem

Design is where a product comes into existence, and its spatial attributes are what make it that product and not another one. Watch a design get saved and receive its identity in the same motion — no file name to invent, no folder to choose, no revision to email, and no way to create a duplicate of something that already exists.

The normalization and identity work behind it is covered by three issued US patents, linked above.

One wrong part number

What an assigned identity costs in the real world

Everyone has ordered the wrong part at some point. Often it isn't carelessness — it's a specification problem, and the identifier was never able to tell you what the thing actually was. Dave walks through a recent example of exactly that, the kind of thing supply chains absorb every day without ever pricing it.

The search-and-validate cost behind it is the 17 hours a week in the IDC study — the input to the $226 billion figure above.

Download the IDC brief

Why we're building it this way

An entrenched problem needs an unconventional approach

Deriving identity instead of assigning it is not an incremental improvement to how the industry works — it invalidates the mapping layer the industry has already bought. That takes patience, a well-modeled domain, and investors who are comfortable being early rather than fashionable.

Dave lays out the roadmap and where the company is today: core platform built, determinism verified, three patents issued.

Download the business plan A personal note from the founder

Questions after reading it: investors@edgewoodsoftwarecorp.com