How We Work
/ How We Work · 03
Two lanes. One evidence bar. No capability catalog.
Exiid is a growth architecture studio with two operating lanes. Client Systems install a fixed-scope system for an existing business (e.g. Odoo, internal apps, dashboards, growth loops). Ventures are owned or co-owned companies. Model Transfer Evaluation is for Venture Partnership only, not Client Systems. Briefs get a written reply within 2–3 business days: next steps or a direct no-go with the reason. Client Systems paid work is scoped per project and paid before it starts.
Scope is confirmed after brief review. No external Client Systems price has been validated by a closed engagement yet.
Client Systems Fit Reads are open. Paid Client Systems work is scoped per project in writing and paid before it starts. Venture Partnership paid evaluation is not open currently. Advisory is scoped after brief review.
Method terms (Ventures vocabulary)
- Model transfer
- The method behind Ventures: adapt a model that already works into a corridor it has not reached, and let evidence decide whether build continues. Mechanics are adapted and IP respected, so it is not cloning. Model Transfer Evaluation is the scoped engagement that tests one thesis.
- RECON
- Discover + Validate: decode the reference model, test the gap, decide with evidence before build.
- RAID
- Build + Launch + Scale: execution only after gates clear; weak evidence stops the work.
- Model Transfer Evaluation
- Venture Partnership only: a scoped 2–4 week engagement that turns a co-owned transfer thesis into a go/no-go memo with a locked proof metric. Not used for Client Systems installs.
- corridor
- A proven model paired with an underserved market it has not reached yet.
- Autonomy Ladder
- Assist, draft, execute-with-review, execute: autonomy expands one rung at a time when eval evidence supports it.
- five-point loop test
- Reach, conversion, payback, repeatability, and decay: five criteria before a loop earns budget.
- Decision Diagnostic
- Client Systems paid entry (when open): map the bottleneck, architecture, and go/no-go criteria before open install scope. Separate from Model Transfer Evaluation.
/ Positioning boundary
Outcome systems, not disconnected capacity.
Same kinds of work you already know. Different deal: one bottleneck, fixed scope, written stop. Not hours and not a retainer. Offers: Software and internal apps · business systems · growth and marketing · data and dashboards. Fit read first, then diagnose, then install.
- An agency on a retainer or a dev shop billing hours
- Staff augmentation or disconnected production capacity
- A consultancy selling slide decks
- A clone farm. We adapt mechanics and respect IP
- A fund writing checks without operating the build
/ Primary · Client Systems journey
Fit Read → Decision Diagnostic → Install
For existing businesses: we install the system around a bottleneck. Fixed scope. Clear outcome. Examples include Odoo or ERP workflows, internal apps, dashboards, and growth loops. Not a task list or retainer.
We check fit → we scope the decision → we install the system.
Fit Read is open and keepable: A short written read: fit, not fit with reason, or what to clarify, plus a prioritized list of what is broken first. You keep that list either way. The next paid step is scoped per project in writing and paid before work starts.
01
Fit Read
You tell us what you want installed (software, business systems, growth, or dashboards). We reply in writing: yes this fits, no with a reason, or what to clarify, plus a prioritized list of what to fix first. You keep that list either way. Free. No commitment.
02
Decision Diagnostic
If it fits, we scope the next paid step in writing for that project: what is broken, what to build, what done means, and when we would stop. Fee is per project. Paid before work starts. Ends with a clear go or no-go before bigger work.
03
Install
If we go, we build and connect the system to a defined outcome, then run it for a period or hand it to your team. Fixed scope confirmed in writing, paid before work starts, no retainer tail.
Availability: Fit Read free · paid next step scoped per project and paid before work starts.
Full path detail · Proof Sprint and operate or transfer
- 01
Fit Read
FreeYou tell us what you want installed (software, business systems, growth, or dashboards). We reply in writing: yes this fits, no with a reason, or what to clarify, plus a prioritized list of what to fix first. You keep that list either way. Free. No commitment.
- 02
Decision Diagnostic
Not open currentlyIf it fits, we scope the next paid step in writing for that project: what is broken, what to build, what done means, and when we would stop. Fee is per project. Paid before work starts. Ends with a clear go or no-go before bigger work. Not open currently; send a Client Systems brief for a fit read.
- 03
Proof Sprint
Gated while the Decision Diagnostic is closedSometimes we prove the riskiest piece first before full install: a time-boxed test with written stop criteria and a go/no-go memo.
- 04
System Install
Gated while the Decision Diagnostic is closedIf we go, we build and connect the system to a defined outcome, then run it for a period or hand it to your team. Fixed scope confirmed in writing, paid before work starts, no retainer tail.
- 05
Operate or Transfer
Gated while the Decision Diagnostic is closedAfter install: Exiid runs the system for a defined period, or transfers it to your team with ownership, instrumentation, and runbooks.
/ Client Systems offers
Four familiar offers. Fit read, then install.
Four offers buyers already recognize. Scope follows the fit read. Fixed scope, not a retainer.
Software and internal apps
Custom tools your team can run every week.
- Internal ops apps
- Client or partner portals
- Workflow tools between teams
Business systems
ERP and ops workflows that match how you actually work.
- Inventory and sales workflows
- Invoicing and payments workflows
- Warehouse and order ops
Growth and marketing systems
Demand loops you can measure and repeat.
- CRM and lifecycle loops
- Channel playbook
- Campaign instrumentation
Data and dashboards
Numbers you can decide on.
- Decision dashboards
- Attribution cleanup
- Weekly operator scorecard
Illustrative Client Systems result
Harbor Trade Co.
IllustrativeWholesale distribution
Sales, stock, and invoicing ran on three tools that never agreed. Month-end closed late every cycle.
12 → 3 days
invoice cycle time
/ Secondary · Inside Ventures
Partner-originated ventures
This path uses Model Transfer Evaluation when open. It is not Client Systems.
Bring a proven model, market access, domain advantage, or distribution. Exiid brings evaluation, product, growth machinery, and operating discipline. If the evidence clears, we co-own the venture.
Availability: Not merchandised while the paid gate is closed.
- Partners with a proven model and a credible underserved market
- Operators with market access or domain advantage
- Owners with distribution that can accelerate a co-owned venture
/ Secondary · Advisory
Advisory, when the product is a decision
Bring a consequential go or no-go decision. Exiid evaluates the evidence and returns a written recommendation with the reasoning attached.
Pricing: Scoped after brief review.
Open an Advisory brief/ Receipts
Patterns we scope before scale.
Venture gates stay public when they fail. Client Systems proof lives on Client Systems results. For venture kill memos, see the kill archive.
MedLibrary, live EdTech LMS
Structured learning library shipped from spec to production with activation and completion instrumentation from day one.
medlibrary.net ↗Client Systems track, first external install pending
The reference implementation is the venture portfolio. External case studies publish only after a real Client Systems engagement clears its delivery and proof gates.
See owned ventures →/ Before you send a brief
Most conversations should not become work.
- Ideas with no reference model stay ideas, name what already works.
- Partners must show speed to act in weeks, not exploratory quarters.
- Unethical cloning is refused outright; transfer adapts mechanics and respects IP.
- If demand proof cannot be named before build, the work stays in validation.
- Website, campaign, or integration requests without a systems outcome are a no.
/ Operator
One inbox. Named prior. Live proof.
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.
Live proof: MedLibrary ↗
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.
Profiles
Model transfer, validation gates, owned ventures, and scoped systems work where operating outcomes are measurable.
Send a fit-read brief →