DockFrame is a modular USB-C hub from HW Media Lab that accepts Framework-style Expansion Cards and a set of small bench-tool cards. Its useful idea is not that every buyer needs five swappable slots. It is that the buyer can postpone deciding which ports and instruments belong on the desk. That option has value only after the base hub, cards, chargers and unvalidated combinations are counted together.
A slot postpones a decision; it does not erase it
The project began with a familiar frustration: fixed docks make one permanent selection of ports. DockFrame instead gives a computer five card positions, while its own cards can also work directly from a suitable USB-C device. That makes the card, rather than the enclosure, the unit of change.
The first-party site says the prototype has seven USB-C connectors in total, including five card positions, a host connection and a second power input. It also says the main data path is shared, host charging tops out at 60 W, and simultaneous video and data performance remains under validation. Those qualifications matter more than the largest number printed on a specification sheet.
The product page reports more than 1,400 submissions on its pre-order list. That is a useful design signal, not 1,400 completed sales. Community requests helped surface the Mini Hub, multimeter, power-supply and breadboard cards, but each extra card also expands the support and purchasing surface.
These records mix company statements, founder recollections and independent reporting. Company numbers are attributed rather than presented as audited results. The mechanism is useful because it identifies a decision to test, not because one visible company guarantees another's outcome.
Price the working desk, not the purple enclosure
Use illustrative arithmetic for a maker who expects to need three functions over two years. Assume a fixed dock costs US$180 today and a second replacement dock costs US$140 next year when requirements change. The two-purchase path costs US$320. Assume instead that a modular base costs US$139, three initial cards average US$35, and one later card costs US$45. That path costs US$289, before chargers and cables. It saves US$31 under these invented inputs. Add a US$60 charger that the fixed dock included, and the modular path costs US$349. The apparent saving reverses.
This arithmetic is illustrative. Its invented inputs are not the subject company's costs, margins or forecast. Replace every input with a dated quote, invoice or observed time before using the result for a commitment.
A decision rule worth carrying forward
Write every required function in one column and the exact supporting port, card, cable, charger and host capability in the next. Leave an item unpriced if it is still unvalidated. Do not convert an unknown into zero.
The rule forces attention onto the denominator behind the attractive headline. Orders are not accepted deliveries. A technical specification is not a validated workflow. Enterprise value is not founder proceeds. Traffic is not contribution. Naming the conversion between those states is the beginning of useful operating evidence.
Build an evidence ladder before scaling
Start with the weakest evidence and refuse to give it a stronger name. A comment, waiting-list entry or sample request shows attention. A deposit or paid order shows willingness to buy under stated terms. An accepted delivery shows that the operation fulfilled the promise. A reorder, referral or renewed contract shows that value lasted beyond novelty. For DockFrame and how buyers should price a modular hardware system rather than its base unit, those stages should be recorded separately because each one authorizes a different size of commitment.
Next, attach time to every observation. A strong launch week can hide a slow replenishment cycle, seasonal use or a queue created by publicity. Record the date of purchase, date cash becomes available, date production begins, date the customer accepts the result and date any return or support cost appears. A contribution estimate assembled from events in different months can look healthy while the bank balance is under strain.
Then give variance the same attention as the average. One fast machine, cooperative bakery, cheap parcel or enthusiastic interview does not describe a repeatable system. Keep the best, median and worst observed case. Investigate the worst before buying capacity for the average. If the downside is a safety failure, unusable batch or loss of an essential customer, an average result is the wrong decision tool.
Finally, write who owns every handoff. The supplier may finish a component while the founder still owns inspection. A carrier may deliver the box while the business still owns setup. A retailer may place an order while the manufacturer still owns sell-through risk through markdowns or returns. A buyer may acquire the company while the founder remains exposed through deferred consideration. Ownership of the next action is part of the cost.
This ladder prevents a common analytical shortcut: using one vivid public milestone to fill several private cells. It is acceptable for cells to remain blank. In fact, a blank can be the most decision-useful result because it identifies the next small test. The goal is not to make the story look complete. It is to stop the next commitment from depending on an unsupported conversion.
Keep the first version deliberately small. One batch, one customer segment, one configuration or one channel makes a failure interpretable. Changing product, price, audience and fulfillment at the same time may produce a better headline, but it destroys the comparison. Record the baseline before intervention, change one important variable, and choose the review date in advance. If the result misses the threshold, shrink or stop the commitment without rewriting the threshold afterward. A disciplined no is useful evidence and preserves cash for a better test.
Run the one-hour version
In one hour, photograph the ports and power supplies already on the desk. Mark which Framework cards or full-featured USB-C hosts are genuinely owned, then price only the missing pieces. Run a second column for a conventional dock that performs the same accepted tasks.
- Write the next irreversible commitment.
- Choose one observed denominator connected to cash or accepted output.
- Separate company claims, independent evidence and your assumptions.
- Set the result that would shrink or stop the commitment.
- Keep the record and compare the forecast with the eventual outcome.
Two adjacent Builtplain cases offer useful contrast: PocketBeagle configuration record and Keyboardio quality gate. They use different products but apply the same discipline of counting the work around the visible milestone.
What the public record cannot answer
Public sources do not reveal complete private margins, cohort retention, contracts, ownership waterfalls or defect ledgers. No inference here fills those gaps. Survivorship bias also applies: visible companies leave better records than similar attempts that failed. Use the case to design a smaller test, not to claim a guaranteed result.
Sources checked on November 17, 2026
- Current first-party specifications, prototype status, card functions and explicit independence from Framework
- Planned kit contents, charger requirements, browser limits and validation caveats
- Independent coverage of the prototype and its reuse of the Framework card format
Modularity is most valuable when it prevents a credible second purchase. The empty slot is not the saving. The avoided replacement is.
Discussion
Sign in with Google or just a name. No email link, no password to remember.