Yorbis
Cash flow orchestration for US SMBs. Six live customers in the LA food import market. DILA evaluated Yorbis with access to the full FounderOS behavioral record — constraint sequence, experiment log, decision history.
What Yorbis is building
Yorbis is building cash flow infrastructure for small and mid-sized businesses in the US — starting with the food import sector in Los Angeles. The product sits between suppliers and buyers, orchestrating payment timing to reduce the cash flow gaps that consistently constrain growth for businesses operating on thin margins and long payment cycles.
The founder, Sun Migliacci, was showcased at Signal LA. She came through FounderOS — which means DILA had access to something most evaluations don't: a timestamped record of how she thinks under pressure, how her constraint framing evolved, and where her logic tightened or drifted over time.
The real constraint
The constraint DILA identified is not what most evaluators would surface. It is not distribution — Yorbis has six live customers, which is real signal in a market that is notoriously hard to penetrate cold. It is not regulatory — cash flow orchestration, structured correctly, operates within existing payment infrastructure. It is not technology — the mechanism is well-understood.
The constraint is value perception at activation. The food import businesses Yorbis serves are operationally sophisticated but organizationally lean. A new financial product has to demonstrate value before the second invoice cycle — not after. If the founder cannot compress time-to-value to a single cycle, the behavioral change required to sustain adoption does not happen. The product works. The question is whether the customer knows it worked fast enough to keep using it.
Mechanism credibility
The causal chain is real. Cash flow gaps in the food import sector are structural — driven by net-30 to net-60 payment terms from buyers combined with immediate payment obligations to suppliers. A product that inserts itself into this gap and shifts the timing genuinely solves a recurring, painful problem. The mechanism is not aspirational.
What DILA pressed on: does Yorbis control enough of the transaction to make the timing shift visible to the customer? Early behavioral data from FounderOS suggests the founder understands this question and is building toward it deliberately — not deferring it.
Wedge strength
The wedge is the specific vertical focus. Food import in LA is not a random choice — it is a defensible beachhead with network density, referral dynamics, and a shared operational pain that makes word-of-mouth credible. A founder who lands six customers in this market before raising has demonstrated something important: the product earns trust inside a skeptical operator community.
The wedge weakens if Yorbis tries to generalize too early. The constraint is vertical-specific. The referral network is vertical-specific. Moving horizontally before the LA food import segment is fully defended would dilute the wedge without adding a stronger one.
What must be true next
Two conditions. First: at least two of the six current customers must expand usage beyond the initial transaction — demonstrating that the value perception problem at activation is solvable, not just solved once. Second: the founder must articulate a clear mechanism for how a seventh customer is acquired differently from the first six. Founder-sold, referral-driven growth is proof of product-market fit. It is not proof of a repeatable acquisition motion.