Phyllux Technologies · strategic transfer
Acquire the phyllux.io research surface
For labs, strategics, and funds evaluating an asset purchase or exclusive license of the Phyllux Technologies public layer: brand, documentation, evidence labeling, and GitHub org relationships mapped on this domain. Figures below are illustrative—not audited forecasts.
- Package
- phyllux.io · narrative · partner lanes · linked public repos
- Stage
- Research-grade stack; revenue requires validation & GTM
- Diligence
- Research status · Proof · Ecosystem · Docs
Confidential acquisition brief
Board-ready memorandum: IM-style layout, full sections, valuation framing. Regenerate after edits: npm run export:acquisition-pdf then npm run compress-pdfs.
Scope & exclusions
Phyllux Technologies only. This transfer covers the phyllux.io technical research brand (WAVE · MESH · VAULT/PhiKey · CORE), public site corpus, and repository relationships described here.
Outside scope. Separate businesses operating on other domains—consumer publishing lanes, unrelated franchises—remain with the seller unless expressly listed in a definitive agreement. This keeps the acquisition artifact aligned with Phyllux R&D positioning.
Executive summary
What transfers. A coherent research-facing brand with geometric spine (golden-angle / 137.5°), public documentation, blog surface, links to phyllux-technologies org repos, and partner routes for paid evaluation and licensing.
Why it can matter. Buyers in RF, security, med-device, or enterprise research can reuse pillars via consulting, licenses, evaluations, and—where measurement supports claims—component relationships. No revenue is implied by the transfer alone.
Candor. Many capabilities are labeled research or roadmap on Research status and Proof. Serious buyers budget validation (bench, third-party review), not only brand conveyance.
Public diligence anchors
Checkable without NDA:
- Live property: phyllux.io · site source phyllux-web
- Evidence posture: Research status · Proof · Docs
- Open artifacts: Ecosystem · biomimetic-inventions-public · phyllux-framework
- Commercial entry: Partners · Contact
Illustrative economics (not forecasts)
Scenario bands for internal modeling only—actuals depend on buyer motion, vertical, and claim substantiation.
| Lane | Mechanism | Illustrative range (Years 1–2) |
|---|---|---|
| Paid technical evaluation | Scoped reviews for defense, med-tech, or telecom; summary + integration sketch. | Low five figures × handful of deals (high variance). |
| License fees | Field-limited use per framework patterns. | Near-zero during pipeline build to mid–high five figures if one anchor licensee closes. |
| Training | Structured sprints on spine and safe-publish lanes. | Mid four to low five figures per sprint. |
| Components / OEM | After measurement milestones + engineering headcount. | Speculative; not assumed. |
No row is a promise. Buyer builds the model with CAC, cycle time, and compliance.
Valuation framing (illustrative)
Pre-revenue research brands are triangulated via replacement cost, strategic fit, and adjustments for evidence gaps—not simple revenue multiples. Micro-acquisitions of small-team technical surfaces vary widely.
Negotiation anchors (not appraisals). Comparable tuck-in conversations for solo-founder research brands often start in the low six figures USD range when buyers value narrative + repo bundle + exclusivity—but outcomes span high four figures (minimal asset pass-through) to mid six figures (strategic premium, retention, milestone structure). Independent advisors set price.
Full methodology and scenario detail appear in the PDF memorandum.
What a buyer needs post-close
- Legal: Domain assignment, trademark posture, contributor agreements for commercialized repos.
- Technical: Senior RF or applied-math capacity (WAVE lane); security review (VAULT/PhiKey); program management for evaluations.
- Validation budget: Bench plan aligned to Research status gaps.
- GTM: Honest shipped-vs-roadmap labeling on public pages.
90-day skeleton
- Days 1–30: Asset inventory, claims audit, legal alignment.
- Days 31–60: One vertical wedge; one evaluation template; Research status updates.
- Days 61–90: Optional transitional consulting; first pilot MOU if pipeline permits.
Risks
- Research vs. product: Revenue needs scope and often external validation.
- Regulatory / dual-use: RF and security narratives require screening—see Ethics.
- Integration cost: Engineering bandwidth often exceeds headline purchase price.
Next step
phibronotchi@gmail.com — subject Phyllux strategic acquisition inquiry. Include mandate, timeline, and structure (asset purchase, exclusive license, hybrid). Evaluation-first: Partners.