Dashboard
/ Exiid Labs · Growth architecture studio · 01
We build ventures. We partner with a few.
Build is abundant. Decisions, distribution, and compounding loops are not.
Ventures: Owned and co-owned ventures built on model transfer. MedLibrary is live at medlibrary.net.
Joint Ventures: Joint ventures, not clients. Bring a market or a proven model, we bring the build and the growth machine, and we co-own what we make. A paid Decision Diagnostic tells us both whether the fit is real before anyone commits.
For operators who own a market and want to co-build, teams with a proven model to transfer into a new market, founders transferring a proven model, and partners bringing distribution or capital.
/ Two lanes, one standard · 02
Two lanes
Ventures
We study models that already work, transfer them into markets that lack them, and scale only when proof holds. Our own capital and operating stack behind every one: product, growth, instrumentation. Every venture starts with one question: can this model win where it has not arrived yet? We call that a Model Transfer Evaluation. When a thesis fails its gate, we kill it and publish the memo.
Propose a venture thesis →Joint Ventures
We are not for hire by the hour. We take a few joint-venture partners a year: you bring a market, distribution, or a proven model, we bring the build, the growth machine, and the kill discipline we run on our own ventures. RECON before RAID: a paid Decision Diagnostic qualifies the fit, then we co-own what we build. We say no by default.
See the stack we run →Propose a JV thesis →/ Proof · 03
Proof and trust
Yassine ELFADILI
Founder & Operator
Software engineer turned growth-systems operator. Shipped MedLibrary, dentistry EdTech LMS from spec to production, with instrumented activation and lifecycle automation.
Previously CPO at Scale (Casablanca). IIT CS.
Briefs go directly to the operator inbox.
No handoff queue, no generic intake, no nurture sequence.
Reply within 2–3 business days, next steps or a direct no-go with the reason.
One inbox, not a nurture sequence.
Verifiable
Profiles
Model transfer, validation gates, owned ventures, and scoped systems work where operating outcomes are measurable.
Open the Brief Desk →Live venture · visitable
Live product with instrumentation from day one, visitable proof, not a pitch deck.
Open live venture ↗
Creator CRM
GATE FAILED · Willingness-to-pay gate, fewer than 5 of 20 discovery calls would prepay a pilot.
GCC Returns OS
GATE FAILED · Market-access gate, no verifiable partner with merchant relationships materialized inside the six-week window.
MedTranscribe
GATE FAILED · Risk gate, health-data residency requirements pushed compliant infrastructure cost past the entire validation budget.
First paid step
Decision Diagnostic from $1,500
Known number before open scope. Pre-revenue on Joint Ventures, bands confirmed in written scope after brief review.
Open the Brief Desk →/ The Method · 04
Decode, transfer, prove, or kill in public.
Decode → Adapt → Validate (RECON) → Build / Launch / Scale (RAID), or kill The same gates that run on our ventures run on every joint venture. 3 killed on written gates, memos public, not hidden.
- Will the gap survive the first competitor launch?
- What can you do in week one that a funded cold entrant cannot?
- Why is this possible now and not three years ago?
/ How we work · 05
Five stops before you send a brief.
- 00
Operating stack
Frameworks, tools, models, and harnesses with attribution and receipts.
- 01
Market transfer framework
How we decode proven models and choose underserved markets.
- 02
Model Transfer Evaluation
What happens in the first paid gate, artifacts, timeline, stop criteria.
- 03
Transfer readiness checklist
Five-minute fit score before you send a brief.
- 04
Public kill archive
When gates fail, the memos stay public, same discipline in a joint venture.
/ Portfolio snapshot · 06
Monitor.app →Derived from the content layer, not live telemetry. Same counts as the public archive and operating board.
Portfolio snapshot
/ Six Engines · 07
Six capabilities, from opportunity to operating company.
Opportunity Engine
ENG-01Finds proven business models paired with markets that lack them. Scans corridors, names reference models, and maps where the same mechanics could win again before anyone builds.
Validation Engine
ENG-02Tests demand before major investment. Smoke offers, concierge runs, and paid signal tests against named thresholds, weak evidence is a decision, not a delay.
Product Engine
ENG-03Ships the smallest product that proves transferred behavior · SaaS, AI products, EdTech, marketplaces. Instrumentation from day one; activation before expansion.
AI Engine
ENG-04Deploys agents, workflows, and automation on explicit autonomy boundaries. One operator runs systems that used to need teams, judgment on fit, ethics, and kill calls stays human.
Growth Engine
ENG-05Designs acquisition, retention, and lifecycle as loops, not campaign bursts. Instrumentation before spend; compounding only where payback is visible by cohort.
Scale Engine
ENG-06Turns validated products into operating businesses. Channel expansion where unit economics hold; operational architecture that survives growth; discipline to kill what stalls.
/ Activity · 08
Live operational timeline
EXIID OS v1.0 · Exit the obvious · exceed the standard