Startup Diligence
Diligence report Healthcare / Medical Devices Late-stage private / special situation 2026-08-03

OrCam Technologies

Healthcare / Medical Devices Diligence Report

OrCam is a real assistive-tech company with real mission value, but public evidence does not support paying a legacy unicorn price without direct diligence on current terms, revenue, and recap mechanics.

Cover facts

Current-looking Estimate 02
1.03 USD B [CV001]
Adverse 2025 Fair-Value Signal 03
~150 USD M [CV006]
Recommendation 04
research-more [CV028]

Company profile

OrCam Technologies is a private Israeli assistive-technology company founded in 2010 by Amnon Shashua and Ziv Aviram. It built its reputation on wearable and handheld AI devices such as OrCam MyEye and OrCam Read that help blind or visually impaired users read text, recognize faces, and navigate visual information, and it later added OrCam Hear for hearing support. Public evidence shows a company with genuine productization, meaningful customer stories, and historic unicorn status, but also with intense substitution pressure from smartphone and platform AI, revenue contraction, layoffs, and recapitalization uncertainty.

Website
www.orcam.com
Founded
2010-01-01
Founders
Amnon Shashua, Ziv Aviram
Founding location
Jerusalem, Israel
Headquarters
Jerusalem, Israel
Product
AI-powered assistive devices including OrCam MyEye wearable vision aids, OrCam Read handheld reading aids, and OrCam Hear hearing-support hardware with companion app surfaces.
Customers
Blind and visually impaired individuals, funded veteran-access channels, schools and learning-support environments, and adjacent accessibility buyers.
Business model
Primarily hardware sales with high-touch support, channel/funded-access reliance, and some app or service layers rather than a clearly disclosed recurring-software model.
Stage
Late-stage private / special situation
Funding status
Historic priced rounds culminated in a 2018 unicorn milestone, but current public sources conflict between a current-looking ~$1.03B estimate and a severe 2025 valuation-reset narrative.
[CV001, CV002, CV006, CV010, CV011]

Executive summary

Top strengths

  • Real assistive products with clear user value across reading, low-vision, and hearing workflows.
  • Historic founder pedigree and proven ability to attract institutional capital and strategic attention.
  • Visible customer/channel proof through veterans, accessibility users, and education-facing deployment paths.
  • Still-meaningful strategic optionality if product assets or funded channels remain durable.

Top risks

  • Current price discovery is conflicted, with public evidence spanning a current-looking unicorn estimate and a severe distress-reset narrative.
  • Platform AI and smartphone substitutes are compressing the core vision-use-case moat.
  • Reported revenue decline, layoffs, and rescue-financing friction raise high dilution and execution risk.
  • Channel dependence and support-heavy hardware economics can erode quickly if growth or funding weakens further.

Open gaps

  • Current cap table, liquidation preferences, anti-dilution protections, and convertible mechanics.
  • Audited current revenue base, gross margin by product line, and forward product-mix assumptions.
  • Commercial traction and unit economics for Hear as a second growth leg.
  • Evidence of live strategic interest or a clean path to a priced financing round.

Contents

Chapter 01

01Company Overview

1.1 Identity, headquarters, and product scope

Official OrCam materials consistently describe the company as an assistive-technology specialist built around AI-enabled wearable and handheld products, not as a generic consumer-electronics brand. The about-us page frames OrCam as a global leader focused on low vision and learning challenges, while the home page and product pages show a current lineup that includes MyEye 3 Pro, MyEye 2 Pro, Read 5, Read 3, Read, Learn, and Hear. The strongest product facts cluster around the current flagship devices. MyEye 3 Pro remains the wearable personal assistant that reads text, recognizes faces, identifies products and money notes, and adds environment descriptions and a Smart Magnifier workflow. Read 3 is more clearly a reading platform than a general wearable, functioning as a handheld OCR reader, a screen-connected Smart Magnifier, and a stand-based stationary reader. FDA-report indexing also shows a U.S. ORCAM INC registration at a New York address, while Tracxn and Caplight both place the corporate center in Jerusalem. The most defensible operating picture is therefore a Jerusalem-rooted company with a meaningful U.S. commercial or regulatory footprint.[CO002, CO003, CO004, CO005, CO006, CO021]

FO002: Company snapshot logic

The current company logic still starts from assistive vision hardware, but channel, software, and hearing pivots now matter as much as the original device story.

Flow abstracts the operating model from public materials and distress reporting; it is a logic map, not a disclosed org chart.

[CO003, CO006, CO007, CO022, CO025, CO026]

1.2 Founders, leadership, and governance visibility

The founder story is unusually easy to verify because both OrCam and independent reporting tie the company directly to Amnon Shashua and Ziv Aviram, the same duo behind Mobileye. The leadership page still presents Shashua as co-founder and chairman and Aviram as co-founder and director, while listing Elad Serfaty as chief executive officer, Shmuel Turgeman as chief financial officer, and Tzahi Israel as senior vice president of sales. Caplight adds extra operating roles around the newer Hear business, including Tal Rosenwein as CEO-Hear and Inbal Levy-March in operations. That combination suggests a company still anchored by its famous founders but no longer run only through them on a day-to-day basis. At the same time, public governance visibility remains thin. OrCam’s current website surfaces founders and core management, but not a robust board roster, committee structure, or a clean explanation of how authority is split across the vision, education, and hearing product lines. For diligence, the issue is not whether leadership exists; it is whether control and succession below the founders are sufficiently transparent.[CO001, CO010, CO011, CO012, CO040]

Leadership and founder table
PersonRoleBackgroundFounder-market fit / functional coverageKey-person dependency
Amnon ShashuaCo-founder and ChairmanMobileye co-founder; still the best-known technical brand attached to OrCamAnchors AI and computer-vision credibilityHigh — public identity and strategic influence remain closely tied to him
Ziv AviramCo-founder and DirectorMobileye co-founder and long-time company builderAnchors capital-markets and commercialization storyHigh — founder continuity remains central to investor narrative
Elad SerfatyChief Executive OfficerCurrent operating CEO listed by OrCamSignals day-to-day leadership beyond foundersMedium-high — public operating voice but less externally documented than founders
Shmuel TurgemanChief Financial OfficerFinance lead listed by OrCam and CaplightOwns treasury, fundraising interface, and restructuring executionMedium-high — especially important during financing uncertainty
Tzahi IsraelSenior Vice President, SalesCommercial leader listed on the official leadership pageConnects product portfolio to distribution and revenue executionMedium
Tal RosenweinCEO - HearCaplight-listed executive for the hearing divisionIndicates product-line specialization and pivot executionMedium
Inbal Levy-MarchChief Operating Officer / VP Sales, Marketing and OperationsCaplight-listed operating executiveSuggests broader operating bench behind go-to-market and fulfillmentMedium

Roster combines official website roles with recent market-data listings. It is intentionally not treated as a full board or full executive directory.

[CO010, CO011, CO012, CO040]

1.3 Funding history and valuation visibility

OrCam’s historical capitalization is well supported up to the unicorn moment, but the current mark is not cleanly settled. Tracxn reconstructs a $15 million Series A in 2014, a $41 million 2017 round, and a $30.4 million February 2018 round led by Clal Insurance and Meitav, bringing disclosed funding to $86.4 million. Globes and The Times of Israel independently corroborate the 2018 round and the $1 billion pre-money valuation. More recent database views diverge. Seedtable speaks of four funding rounds, while Caplight reports total funding raised of $98.9 million, labels the most recent event as July 2024 convertible debt, and estimates valuation at $1.03 billion. That picture is directly challenged by Globes’ March 2025 reporting on a distressed recovery plan, which said internal estimates had pushed value down to roughly $150 million. The right takeaway is not that one number is certainly correct, but that OrCam’s 2018 unicorn status is historically verified whereas its current valuation and financing status are contested and should not be treated as settled without primary round documents.[CO014, CO015, CO016, CO017, CO018, CO019]

Stakeholder or investor map
StakeholderRoleControl or economic importanceEvidence statusDiligence ask
Intel CapitalSeries A investorEarly strategic investor that helped validate the assistive-computer-vision thesisTracxn reportedConfirm ownership and any remaining rights
BRMEarly investor / recovery-plan participantNamed in Tracxn and later distress reportingMixed-source corroborationConfirm current ownership and any 2024-2025 bridge role
Aviv Venture CapitalSeries A investorNamed by Tracxn in the 2014 roundSingle database sourceConfirm whether still on cap table
Clal InsuranceLead investor in 2018 round; later institutional investor in dispute reportingImportant to the 2018 unicorn round and later governance conflictNews plus database corroborationRequest current stake, preferences, and voting rights
MeitavLead investor in 2018 round; later institutional investor in dispute reportingSame importance as Clal inside the unicorn round and recovery conflictNews plus database corroborationRequest current stake and anti-dilution protections
Leumi Partners and HarelInstitutional investors in 2025 dispute reportingPotential blockers to recapitalization and recovery plan approvalGlobes reportedConfirm exact holdings and consent rights
Founders (Shashua / Aviram)Strategic sponsors and 2024-2025 bridge backersStill central to rescue financing and strategic directionGlobes and official sourcesClarify current control, bridge instruments, and related-party terms

Investor map emphasizes control questions rather than a complete cap table because no primary shareholder register surfaced in this run.

[CO014, CO016, CO018, CO030]
FO001: Company milestone timeline

OrCam moved from a Jerusalem assistive-vision startup to a 2018 unicorn, then into a 2024-2025 stress period marked by layoffs and recapitalization questions.

Timeline uses public milestone dates only; it does not assume undisclosed internal product or financing events.

[CO001, CO014, CO016, CO027, CO030, CO041]

1.4 Scale signals, channel structure, and operating footprint

The public evidence on present-day scale is directionally useful but internally inconsistent. Official pages say OrCam serves users across 50 countries and 25 languages and improves life for tens of thousands of people worldwide. The Google Play and App Store listings confirm an active companion app used to control settings, connect devices to Wi-Fi, and reach support, which suggests ongoing product maintenance rather than a fully abandoned installed base. Channel evidence also matters: GetOrCam markets itself as an authorized worldwide distributor, and both the Blinded Veterans Association page and OrCam’s own veterans-benefits content suggest VA-funded procurement pathways for qualifying users. Education is a second channel, not a side note: OrCam Learn for Schools explicitly targets educators, tracking student progress and citing school and therapist testimonials. But public scale numbers conflict badly on headcount. Tracxn and Caplight list 171-172 employees in 2026, while Israeli reporting after multiple 2024 layoffs suggested only several dozen to fewer than 100 employees remained. That gap is too large to ignore, so headcount should be treated as disputed rather than precise.[CO007, CO008, CO022, CO024, CO025, CO033]

Snapshot KPI table
MetricValue / statusDate / vintageConfidenceGap / note
Founded2010HistoricalmediumCorroborated by official leadership and 2018 news coverage
FoundersAmnon Shashua and Ziv AviramCurrent historical factmediumBoth official and independent sources identify the Mobileye founders
HeadquartersJerusalem, Israel2026 aggregator viewmediumCaplight and Tracxn align; U.S. importer entity also exists
U.S. operating footprintORCAM INC listed at 1115 Broadway, New York2026 regulatory indexmediumSupports importer or commercial presence rather than global HQ
Latest clean priced unicorn round$30.4M at $1B pre-money2018-02mediumCorroborated by Globes, Tracxn, and Times of Israel
Disclosed lifetime funding$86.4M to $98.9M depending database2026lowTracxn and Caplight disagree on total and on later convertible debt
Current private valuationNot cleanly confirmed2026lowCaplight shows $1.03B estimate; Globes distress reporting cited roughly $150M
Current employee countDisputed2025-2026lowCaplight and Tracxn show ~171-172; Israeli reporting implied <100 after layoffs
Installed footprint50 countries, 25 languages, tens of thousands of usersCurrent official claimmediumOfficial company claim; no independent user ledger surfaced
Retail pricing proxy$4,250 for MyEye 3 Pro; Read 3 starts at $2,7902026mediumObserved on distributor and official product pages
Revenue disclosureNot disclosed in official materials2026highOnly adverse reporting provides directional revenue figures
Current product postureVision devices still sold; Hear positioned as new focus area2024-2026mediumOfficial site breadth conflicts with 2024-2025 pivot reporting

Table separates historically corroborated facts from contested current-state metrics. Headcount, current valuation, and post-2018 financing are not treated as settled.

[CO001, CO002, CO016, CO017, CO018, CO020]
FO003: Snapshot KPIs

The cleanest current metrics are channel footprint and pricing proxies; valuation, funding, and employee scale remain contested.

KPI figure intentionally displays conflicting current-state metrics side by side instead of forcing one canonical number.

[CO008, CO017, CO023, CO032, CO033, CO034]

1.5 Adverse signals, pivot risk, and unresolved questions

The strongest negative evidence in this run comes from Israeli business reporting rather than regulator actions. Calcalist reported in July 2024 that OrCam shut its glasses-development activity for the visually impaired, executed its third layoff round of the year, and shifted focus toward Hear because rapid progress in generative AI and smartphone-based image processing had eroded the need for further low vision-product development. Globes’ March 2025 reporting went further, describing an investor dispute that stalled a recovery financing, a revenue drop from roughly $45-50 million in 2023 to $16 million in 2024, and a plan to split the business and raise emergency capital. Those reports do not prove the consumer vision business disappeared; official pages still market MyEye and Read aggressively. But they do prove that later chapters must treat smartphone substitution, capital-structure stress, and strategy instability as core diligence issues rather than hypothetical risks. The main unresolved questions are current headcount, the real status of the 2024 convertible event, precise current revenue, and whether the company is again stabilizing around a narrower product set.[CO027, CO028, CO029, CO030, CO031, CO032]

Milestone table
DateEventTypeAmount / valuation / statusParticipantsImplication
2010-01-01OrCam foundedfoundingFoundedAmnon Shashua; Ziv AviramEstablishes the Jerusalem-born assistive-AI origin story
2014-03-27Series A financingfinancing$15MIntel Capital; BRM; Aviv Venture CapitalFirst major external capital for commercialization
2015-01-01Original MyEye device commercial era beginsproductOriginal MyEye in marketOrCam; blind and low-vision usersConfirms multi-generation product history
2017-04-02Follow-on financing roundfinancing$41MTracxn-reported investors not fully disclosedShows scaling capital before unicorn round
2018-02-20Series B / unicorn roundfinancing$30.4M at $1B pre-moneyClal Insurance; Meitav; existing investorsHistorically verified unicorn status
2024-05-12Companion app version 1.1 visible on App StoreproductSoftware update cadence visibleOrCam Technologies LTD.Evidence that installed products still receive software support
2024-07-28Glasses-development shutdown and third layoff round reportedadverseDozens laid off; focus shifted to HearCalcalist; OrCam managementSignals generative-AI pressure on the vision business
2025-03-13Investor dispute stalls recovery plangovernance$12.5M bridge plan reported; more capital neededFounders; institutional investorsShows recapitalization and control stress
2026-01-01ORCAM INC FDA registration visibleregulatoryInitial importer listing active in indexORCAM INCSupports U.S. operating footprint
2026-08-03Official site still markets MyEye, Read, Learn, and HearscalePortfolio remains publicly soldOrCamShows website breadth despite crisis reporting

Milestones mix official and independent reporting. Distress and shutdown items are preserved because they materially affect how the historical growth story should be read today.

[CO001, CO014, CO015, CO016, CO027, CO030]

1.6 Exhibits

Chapter 02

02Market Analysis

2.1 Market boundary, adjacencies, and status-quo substitutes

The cleanest way to define OrCam’s market is to start narrow and then expand outward. At the core sits the low-vision assistive-device category: reading devices, magnifiers, wearables, screen readers, and other tools that help users extract visual information they cannot reliably access unaided. The Business Research Company and Research and Markets both frame the category this way and explicitly include reading devices, wearable devices, and electronic magnifiers. Around that core is a broader assistive-technology envelope, where WHO includes products such as white canes, hearing aids, speech recognition, and captioning. OrCam clearly touches that broader space because it sells vision devices, education tools, and a hearing product, but it does not compete for the full assistive-technology TAM. It also does not cleanly belong inside the entire AI-medical-device market, which includes hospital software, imaging, and clinical monitoring systems far from OrCam’s consumer or rehab workflow. Finally, status-quo alternatives matter. White canes, orientation-and-mobility training, volunteers, and mobile apps solve many of the same daily jobs without requiring a $3,000-$4,000 dedicated device purchase.[CM004, CM005, CM008, CM009, CM010, CM011]

Market definition table
Segment / categoryIncluded spendExcluded spendBuyer / payerRelevance
Low-vision assistive devicesReading devices, electronic magnifiers, wearables, screen readers, OCR-oriented aidsGeneral ophthalmology procedures, glasses-only correction, generic consumer electronicsIndividuals, families, schools, rehab channels, some benefits programsCore market for OrCam MyEye and Read products
Broader assistive technologyVision, hearing, mobility, communication and software aidsGeneral acute care, unrelated consumer devicesGovernments, NGOs, institutions, individualsImportant adjacency because OrCam now spans vision and hearing
AI-enabled medical devicesClinical imaging, monitoring, diagnostic and hospital AI devicesNon-medical accessibility apps and many consumer aidsHospitals, clinics, payers, medtech buyersUseful technology backdrop but too broad for direct OrCam revenue sizing
Status-quo low-vision supportWhite canes, O&M services, volunteers, smartphone accessibility appsDedicated premium hardwareUsers themselves, nonprofits, public support programsPrimary substitute or complement set that caps willingness to pay

Boundary starts with what OrCam directly monetizes, then expands to adjacencies and substitutes to avoid using an inflated denominator.

[CM005, CM010, CM012, CM017, CM018, CM034]

2.2 Sizing lenses and why multiple denominators matter

Public market sizing works only if the denominators are separated. WHO’s vision-impairment fact sheet shows the top-of-funnel need base is enormous: at least 2.2 billion people have near or distance vision impairment, with at least 1 billion cases preventable or unaddressed. WHO’s assistive-technology fact sheet broadens the problem further, saying more than 2.5 billion people need one or more assistive products today, rising to 3.5 billion by 2050. Those figures describe need, not OrCam’s practical SAM. The commercial category lens is much smaller. TBRC says the low-vision assistive-devices market reached $1.23 billion in 2025 and $1.34 billion in 2026 and may grow to $1.89 billion by 2030 at about 9% CAGR; Research and Markets presents the same 2026 and 2030 values. A much wider adjacent lens comes from AI-enabled medical devices, where TBRC and Grand View Research point to multi-billion-dollar markets growing far faster. That lens is strategically relevant for component and technology tailwinds, but it is too broad to underwrite OrCam’s current revenue opportunity on its own.[CM001, CM002, CM004, CM006, CM008, CM009]

TAM/SAM/SOM or sizing lens table
PublisherYearGeographyValueCAGR / growthMethodologyConfidenceLimitation
WHO vision impairment fact sheet2026Global2.2B people with near or distance vision impairmentNeed base, not revenue marketPopulation prevalence and burden estimatesmediumNot a commercial device TAM
WHO assistive technology fact sheet2026Global2.5B people need one or more assistive products; 3.5B by 2050Long-term demand expansionPopulation need across all assistive productsmediumCovers much more than vision devices
The Business Research Company2026Global low-vision assistive devices$1.34B in 2026$1.89B by 2030 at 8.9% CAGRCommercial category market estimatelowPublisher methodology is summarized, not fully open
Research and Markets2026Global low-vision assistive devices$1.34B in 2026$1.89B by 2030 at 9.0% CAGRCommercial category market estimatelowClosely tracks a syndicated report framework
The Business Research Company2026Global AI in medical devices$16.16B in 2026$42.43B by 2030 at 27.3% CAGRAdjacency market sizinglowFar broader than OrCam’s addressable market
Grand View Research2024/2025 reportGlobal AI-enabled medical devices$13.67B in 2024$255.76B by 2033 at 38.5% CAGRAdjacency market sizinglowVery broad category with hospital-heavy mix

Table intentionally separates need-base counts from revenue-market estimates and from broader AI-device adjacency to avoid denominator inflation.

[CM001, CM004, CM008, CM009, CM012, CM013]
FM001: Market sizing lens

Need-base prevalence is massive, but OrCam’s directly monetizable market is much smaller than the broader vision-impairment or assistive-tech population.

Bottom layer is conceptual because no public source isolates OrCam’s true SAM; the figure intentionally distinguishes population need from commercial market size.

[CM001, CM004, CM008, CM034]
FM002: Market estimate range

The narrow commercial low-vision-device market is orders of magnitude smaller than the broad assistive or AI-device need pools, which is why denominator discipline matters.

Figure compares different market definitions only to show scale separation; it should not be read as interchangeable TAM measures for OrCam.

[CM008, CM009, CM012, CM013, CM036]

2.3 Buyer, user, and payer segmentation

The user is usually the blind or low-vision individual, but the buyer is often someone else. OrCam’s own channels suggest at least four recurring buying paths. First is direct consumer purchase, supported by reseller and online-store behavior. Second is institutionally influenced personal purchase, where families, rehab specialists, or teachers help justify a device for daily reading or school use. Third is school procurement, where the user is a student but the economic buyer may be a school, district, or special-needs program; OrCam Learn for Schools makes this explicit by emphasizing teacher analytics and progress monitoring. Fourth is benefit-funded or public-pathway acquisition, especially veterans with VA coverage. In those cases, the user remains the visually impaired individual but the payer may be a public program. The broader market therefore spans personal-use, healthcare-adjacent, and educational budgets. That is attractive because it creates multiple routes to adoption, but it also lengthens sales cycles, increases the importance of training and proof-of-outcome, and means OrCam is not selling into a single homogeneous checkout moment.[CM011, CM015, CM025, CM026, CM027, CM028]

Segment / buyer map
SegmentBuyerUserPayer / budget ownerWorkflowAdoption trigger
Direct low-vision consumerIndividual or familyBlind or low-vision adultPersonal budget, family support, nonprofit grantsDaily reading, recognition, navigation supportNeed for independence that smartphone tools do not fully solve
School-age student with learning or reading difficultySchool, family, or special-needs coordinatorStudentSchool budget, family budget, possibly local support programReading support, comprehension feedback, classroom participationEvidence of academic independence or lower aide burden
Veteran / rehab beneficiaryVA pathway, rehab specialist, or benefits coordinatorBlind or low-vision veteranVA or benefits fundingDaily living support, reading, rehabilitationEligibility for funded assistive device and training
Older adult with progressive vision lossFamily caregiver, individual, low-vision clinic influenceOlder adult userHousehold budget, insurer or public support when availableMail, medication, bills, menus, reading fatigue supportLoss of function that is immediate and practical
Institutional accessibility / service ecosystemAccess partner, advocacy organization, support programEnd beneficiaryProgram budget or partnership budgetDistribution, training, referral, demo accessNeed to broaden accessible-service offering

Buyer and payer are often different from the end user, which is why adoption paths are longer than a simple consumer-device checkout flow.

[CM011, CM025, CM026, CM027, CM028, CM037]
FM003: Budget ownership and onboarding intensity matrix

Budget ownership and training intensity vary materially by cohort even when the end user is always the visually impaired individual.

Matrix uses ordinal strength labels based on channel evidence from schools, veterans pathways, and direct-device marketing rather than disclosed revenue mix.

[CM025, CM026, CM027, CM028, CM037, CM032]
FM004: Adoption funnel or value-chain map

Adoption usually moves from need recognition to proof, funding, purchase, onboarding, and sustained daily use rather than from awareness straight to checkout.

Flow represents the generalized adoption path implied by OrCam’s school, VA, distributor, and direct-consumer evidence.

[CM025, CM027, CM028, CM032, CM037, CM038]

2.4 Growth drivers supporting adoption

The growth case rests on a combination of demographic need, technological improvement, and expanding institutional willingness to treat accessibility as an outcome worth funding. WHO and NEI data show the demand pool is supported by ageing populations, persistent refractive and cataract-related impairment, and significant unmet care needs. TBRC explicitly ties low-vision-device market growth to rising visual impairment prevalence and diabetes-related vision loss, while also highlighting demand for portable wearables, electronic magnifiers, and AI-powered assistive tools. OrCam’s own recent product messaging fits these trends well: Read 3 and MyEye 3 Pro now position AI assistant features, translation, and magnification as incremental value layers rather than just OCR. WHO’s global assistive-technology work adds a policy argument: devices that preserve independence can improve inclusion in education, employment, and civic life, creating a return-on-investment case for public or institutional buyers. For OrCam, that matters because the market grows not only when more people need help, but when schools, veterans systems, and families conclude that device-enabled independence is worth paying for.[CM001, CM004, CM008, CM010, CM016, CM029]

Growth drivers and constraints table
Driver / constraintDirectionTimingImplicationDiligence ask
Ageing and persistent vision-impairment burdenDriverStructural / long-termExpands need base for reading and daily-living assistanceQuantify targetable cohorts by geography and channel, not only global prevalence
AI-powered portable and wearable assistive devicesDriverCurrent / medium-termImproves feature set and perceived device usefulnessShow where dedicated hardware beats free mobile apps on task success and speed
School analytics and independence narrativeDriverCurrentCreates institutional budget case beyond consumer purchaseProvide procurement cycle length and renewal data for Learn-like offerings
VA or public-benefit pathwaysDriverCurrentCan unlock otherwise unaffordable purchases for qualified usersShow conversion rates, authorization timing, and funded volumes
High upfront device priceConstraintImmediateShrinks practical SAM even when need is obviousProvide subsidy, financing, and payback data by channel
Smartphone and volunteer substitutesConstraintImmediateFree or low-cost alternatives reduce willingness to buy dedicated hardwareProve dedicated-device superiority on high-frequency workflows
Training and onboarding requirementsConstraintNear-termRaises support cost and slows adoption for seniors or new usersShare training hours, retention by trained cohort, and support burden
Fragmented policy and limited accessConstraintStructuralNeed does not automatically convert into paid procurementMap reimbursement and institutional access by country and buyer class

Market growth is real, but adoption economics depend on whether dedicated hardware clears the substitute bar and finds a payer path.

[CM006, CM016, CM024, CM027, CM030, CM031]

2.5 Adoption constraints, substitute pressure, and sizing gaps

The hardest market question is not whether accessibility need exists; it is whether dedicated hardware captures enough value before software substitutes absorb the job. Free or low-cost smartphone tools now cover many individual tasks that once justified a dedicated reader or wearable. Microsoft’s Seeing AI reads documents, products, scenes, people, currency, colors, and handwriting for free on mobile. Be My Eyes offers free volunteer help, AI image descriptions, and major-brand service access at global scale. Aira layers in paid human interpreting plus AI. Apple is making Magnifier and Accessibility Reader more powerful inside its own ecosystem, while Envision Glasses show that dedicated AI wearables are no longer a category of one. WHO also underscores structural frictions: low awareness, high costs, limited access, procurement challenges, and workforce gaps. Those frictions shrink practical SAM relative to headline need. The implication is that OrCam’s market is attractive when a dedicated device materially outperforms free apps, secures reimbursement, or delivers independence in settings where training and support are available. Without that, adoption can stall even as the underlying need keeps rising.[CM006, CM019, CM020, CM021, CM022, CM023]

2.6 Exhibits

Chapter 03

03Competitors

3.1 Landscape by competitor class

The competitive landscape is best understood by class rather than by a flat vendor list. First are direct dedicated-device peers: Envision Glasses, eSight Go, IrisVision Vista, and HumanWare’s smart reader family all sell hardware explicitly for blind or low-vision users. Second are human-assistance or service substitutes such as Aira and Be My Eyes, which solve many of the same daily jobs without selling the user a premium reading device. Third are platform-level substitutes led by Apple and Microsoft, where accessibility features ride on top of already-owned smartphones or computers. Fourth are status-quo supports such as white canes and orientation-and-mobility instruction, which do not try to replace vision with AI but remain essential independence tools and therefore compete for time, attention, and some budget. OrCam still belongs in the direct-device class because MyEye and Read remain specialized hardware. But market evidence from the last two chapters makes clear that the strategic battle is increasingly against the substitute classes, not just against one more smart-glasses startup.[CP001, CP002, CP003, CP004, CP005, CP006]

Competitor profile table
CompetitorCategoryScale / fundingTarget segmentDifferentiationLimitation
OrCamDedicated device familyPrivate; disputed valuation; premium device pricing visibleBlind, low-vision, reading-fatigue, school, veterans channelsBroad mix of OCR, recognition, wearable and handheld optionsPremium hardware price and substitute pressure from apps
Envision GlassesDedicated smart glassesPrivate scale not disclosed in retained sourcesBlind and low-vision users wanting hands-free smart glassesRich hands-free feature stack on Google Glass hardwarePricing and broad commercial scale not visible in retained evidence
eSight GoDedicated low-vision headsetLow-vision specialist; TBRC notes Gentex acquired certain eSight assets in 2024Users with significant central vision lossStrong magnification and residual-vision enhancement orientationLess clearly a general AI narrator or document assistant
IrisVision VistaDedicated low-vision headsetCompany claims 3,000+ people helpedUsers with low vision who benefit from magnified wearable enhancementAugmented-reality style vision enhancement plus coachingLess evidence of broad non-visual task coverage than OrCam or Envision
HumanWare Smart ReaderReading-device incumbentEstablished blindness and low-vision vendor; specific financial scale not disclosed hereUsers focused on reading printed material and image descriptionDocument-first reading utility from a known assistive-tech brandLess evidence of broad scene or people-recognition coverage
AiraHuman interpreting service substituteSubscription-based service with access-location networkBlind or low-vision users who need human-guided visual interpreting24/7 trained interpreters plus AI image descriptionsOngoing minute-based cost and dependence on live service
Be My EyesVolunteer + AI substitute750k+ users and 8M+ volunteersBlind or low-vision users needing free on-demand helpFree, global, AI + volunteer blend, broad service directoryNo dedicated hardware and variable experience by use case
Seeing AI / ApplePlatform substituteDistributed through mobile ecosystems users may already ownMainstream-device owners needing reading and scene-description toolsFree or bundled accessibility integrated into existing devicesNot purpose-built dedicated hardware; safety disclaimers limit some uses

Profile table mixes dedicated peers and substitutes because buyers compare jobs-to-be-done, not only corporate form factors.

[CP001, CP010, CP012, CP015, CP019, CP020]
FP001: Competitive positioning map

Dedicated devices skew toward higher hardware specialization, while app and service substitutes skew toward lower entry cost and broader installed-base reach.

Axes are ordinal: x = hardware specialization, y = distribution reach / ease of access. Values are evidence-backed scoring, not measured market-share data.

[CP001, CP010, CP015, CP019, CP020, CP021]

3.2 Direct device peers and feature overlap

OrCam’s dedicated-device competitors overlap heavily on reading, visual description, and low-vision augmentation, but they do so through different architectures. Envision Glasses run on Google Glass Enterprise Edition 2 and emphasize hands-free text capture, scene description, object and people recognition, and live companion calling. eSight Go is less an AI narrator and more a digital vision-enhancement headset for central-vision loss, leaning on magnification, image stabilization, and a 45-degree field of view. IrisVision similarly targets low-vision enhancement through wearable magnified vision rather than text-first narration, while HumanWare’s smart-reader category stays closer to the document and image-description job. OrCam’s advantage versus these peers is breadth: MyEye and Read collect OCR, recognition, and AI assistant functions into one family. The tradeoff is focus. eSight and IrisVision appear more specialized for residual-vision enhancement, while Envision’s Google Glass base gives it a recognizable hands-free smart-glasses form factor. OrCam therefore wins when buyers want one device family for multiple blind and low-vision tasks, not when they want the most specialized tool for one narrow visual use case.[CP009, CP010, CP011, CP012, CP013, CP014]

Feature / capability matrix
Buying criterionOrCamEnvisioneSightIrisVisionHumanWareSeeing AI / Be My Eyes / Aira
Hands-free wearable useStrong on MyEyeStrongStrongStrongWeakVariable / phone-led
Dedicated document reading OCRStrongStrongModerateModerateStrongStrong
Residual-vision enhancement and magnificationModerateModerateStrongStrongModerateWeak-moderate
Scene / object / people descriptionStrongStrongWeak-moderateModerateWeakStrong
Human assistance optionWeakCompanion call onlyCoaching, not live interpretingCoaching, not live interpretingUnknownStrong
Free or bundled entry pointWeakUnknownWeakWeakUnknownStrong
Specialist training / coachingModerateUnknownStrongStrongUnknownVariable
Platform dependencyLow-moderateHigh (Google Glass base)LowLow-moderateLowHigh

Cells are directional and evidence-backed. Unknown is used where retained sources did not provide strong support for a positive or negative rating.

[CP009, CP010, CP012, CP013, CP016, CP017]
FP002: Feature breadth / capability map

OrCam’s broadest edge is combining multiple assistive jobs in one family; the strongest substitutes win on price or installed base rather than on single-device breadth.

Capability strengths are ordinal and sourced from retained product descriptions, manuals, and service pages; they are not benchmark scores.

[CP010, CP011, CP012, CP013, CP016, CP017]

3.3 Software and service substitutes are the biggest displacement threat

The most dangerous competitors are not always the best dedicated devices; they are often the cheapest good-enough alternatives. Seeing AI is free, mobile, and increasingly comprehensive, covering documents, products, scenes, currency, colors, handwriting, and AI chat around scanned text. Be My Eyes adds scale that few private hardware companies can match: a free app, 150 countries, 180 languages, hundreds of thousands of users, millions of volunteers, and AI image description through Be My AI. Aira is more expensive than these app layers but offers a very different promise: professional visual interpreters, access locations, and subscription-based assistance anywhere. Apple pushes still deeper into the base operating system with Magnifier, Accessibility Reader, and Apple Intelligence-linked exploration features, which means many mainstream-device owners receive low-vision help without buying another hardware platform at all. These tools do not always replace OrCam, especially for users wanting hands-free or dedicated-device reliability. But they unquestionably compress the price umbrella for the daily reading and scene-description tasks that once made OrCam’s hardware more singular.[CP019, CP020, CP021, CP022, CP023, CP024]

Pricing / packaging comparison
CompetitorPrice / unit / contract modelIncluded capabilitiesDiscount / unknownsImplication
OrCam MyEye 3 Pro$4,250 listed device priceWearable reading, recognition, Smart Magnifier, AI assistant, accessoriesRealized pricing and channel discounts unknownPremium dedicated-device positioning requires funded access or clear superiority
OrCam Read 3Starts at $2,790Handheld reading, Smart Magnifier, stationary reader modeActual regional pricing and financing unknownStill materially above zero-cost app substitutes
AiraSubscription from $26/month to $1,160/month depending minutesLive interpreters, access anywhere, AI descriptions, minute bundlesMany public spaces offer free access; usage is time-boundConverts capex problem into service opex and is easier to trial
Be My EyesFreeVolunteer assistance, Be My AI, service directory, desktop and mobile accessNo paid user pricing shown in retained source setSets a powerful zero-price anchor for many casual tasks
Seeing AI / AppleFree app or bundled OS featureReading, scene description, document chat, Magnifier, Accessibility ReaderRequires compatible mainstream deviceShrinks willingness to buy hardware for users with adequate phone access
Envision / eSight / IrisVision / HumanWarePricing not cleanly surfaced in retained sourcesDedicated hardware value propositions vary by feature and vision conditionRequires direct vendor or demo follow-upPrice opacity itself can slow comparison shopping but keeps dedicated-device class premium

Only prices explicitly surfaced in retained sources are treated as factual; all other dedicated-device pricing remains unknown here.

[CP011, CP019, CP020, CP021, CP022, CP024]
FP003: Moat / readiness KPIs

OrCam remains differentiated on dedicated-device integration, but substitute pressure is already too strong for a complacent premium-pricing strategy.

KPI panel mixes price and scale proxies because direct competitor revenue or market-share disclosure is sparse in public sources.

[CP011, CP019, CP020, CP021, CP024, CP026]

3.4 Switching costs, lock-in, and distribution power

Switching costs are meaningful but not absolute. OrCam users who have learned its gestures, device workflows, and accessories face real habit and training costs. Dedicated devices also create attachment when they are funded through a school, a veterans program, or a specialist distributor rather than bought casually online. But much of the market still appears multi-homing-friendly: a user can own an OrCam device and still rely on Seeing AI, Be My Eyes, a white cane, or Aira for different tasks. In that sense, the battle is less about hard lock-in and more about share of daily-use moments. Distribution power also differs sharply by class. Aira and Be My Eyes benefit from app-store scale and institutional access partnerships; Apple and Microsoft ride default platform distribution; Envision, eSight, IrisVision, HumanWare, and OrCam rely more on specialist sales, demos, referrals, and training channels. OrCam’s U.S. distributor and veterans evidence is therefore strategically important: it helps the company fight a distribution war it cannot win through consumer-platform reach alone.[CP024, CP028, CP029, CP030, CP031, CP032]

3.5 Moat durability and displacement risk

OrCam’s moat is real but fragile. The durable part is the integration of purpose-built assistive hardware, low-vision user experience, training channels, and daily-living features such as recognition, reading, and magnification. The fragile part is that many of these features are being unbundled into free or subsidized software layers. The Apple and Seeing AI materials are especially notable because they bring high-quality accessibility into devices users may already own. Be My Eyes and Aira show that human or AI support can be layered into the user’s existing camera phone, and eSight or IrisVision show that low-vision enhancement specialists can attack residual-vision cohorts directly. Even dedicated device peers now offer coaches, VA pathways, and companion-calling features that reduce OrCam’s channel and support differentiation. The result is not commodity status yet. OrCam can still win where a self-contained device outperforms apps on speed, privacy, ergonomics, and funded access. But the moat will not hold on brand alone; it depends on proving that this integration genuinely produces better outcomes than the increasingly crowded substitute stack.[CP015, CP020, CP021, CP022, CP023, CP024]

Moat durability / competitive risk register
Moat claimThreatSeverityMitigation / diligence ask
Purpose-built assistive hardwareFree smartphone accessibility apps replicate core reading and description tasksHighProve materially better speed, ergonomics, and outcome quality on daily workflows
Broad feature family across wearable and handheld form factorsSpecialists like eSight or IrisVision can win narrow visual-use cases with deeper optimizationMediumShow conversion by user condition and task, not just by feature count
Channel access via veterans, schools, and distributorsPlatform players and app stores own far larger distribution reachHighQuantify funded-channel conversion and retention where platforms cannot easily sell
User familiarity and trainingMulti-homing is easy; users can keep OrCam and still default to free apps for many tasksMedium-highShow frequency-of-use and task share after onboarding
Brand and long product historyCompetitor AI and platform features are improving quickly, compressing differentiationHighMaintain rapid software cadence and disclose benchmark wins against substitutes
Integrated support ecosystemPeers also offer coaching, calls to trusted contacts, or human assistance networksMediumClarify what support elements are unique, scalable, and margin-accretive

The key competitive question is not whether OrCam has a moat at all, but whether that moat still justifies premium hardware pricing as substitutes improve.

[CP020, CP021, CP022, CP024, CP029, CP031]

3.6 Exhibits

Chapter 04

04Financials

4.1 Revenue model, pricing, and monetization mix

The visible revenue model is still predominantly hardware-led. OrCam publicly sells MyEye and Read devices, distributes them through partner channels, and supports them with a companion app rather than a standalone paid software layer. MyEye 3 Pro is listed at $4,250 and Read 3 starts at $2,790, which means the company is not trying to win with low-ticket volume. Instead it appears to depend on premium-device economics supported by buyer segments that can tolerate training and procurement friction. Public pages also show at least two adjacent monetization paths. First, OrCam Learn for schools is framed as a solution for students and educators with analytics, suggesting an institutional budget line rather than a pure consumer sale. Second, OrCam Hear is described in adverse reporting as entering marketing and sales, which suggests future diversification but not a mature current revenue base. Caplight classifies the business as a mix of hardware sales, subscription SaaS, and services and consulting, but public official evidence strongly supports hardware first and only partially supports recurring or service-heavy revenue.[CI001, CI002, CI003, CI004, CI005, CI006]

Revenue streams table
StreamMechanismUnitCurrent value / statusQualityDiligence ask
MyEye hardwareDirect or channel device salePer deviceActive; flagship wearable still publicly soldHigh confidence on existence, low confidence on realized volumeUnits sold, realized ASP, gross margin, returns
Read / Read 3 hardwareDirect or channel device salePer deviceActive; handheld reading line publicly soldHigh confidence on existence, low confidence on realized volumeUnits sold, list-to-net discounting, attach rates
OrCam Learn for schoolsInstitutional school solution with analytics and workflow supportPer school / student deployment (exact contract unit unknown)Active public product surface for schoolsMedium confidence on offering, low confidence on booked revenueContract structure, ACV, renewal rate, implementation cost
OrCam HearEmerging hearing productUnknownAdverse sources describe marketing and sales phaseLow-medium confidence on current revenue contributionBookings, channel pipeline, commercialization stage
Companion software / supportFree app and support layer supporting installed baseNot directly priced in public sourcesSupports all devices and post-sale serviceHigh confidence on existence, low confidence on monetizationSupport cost per device, service revenue if any

Public evidence supports product existence more strongly than revenue mix or recognition policy.

[CI001, CI002, CI003, CI005, CI006, CI007]
Pricing / monetization table
OfferPrice / unit / contractList vs realized pricingDiscounts / unknownsSource-backed implication
MyEye 3 Pro$4,250 device list priceList pricing onlyChannel discounts, financed sales, and payer offsets unknownPremium-price hardware likely depends on funded or high-value cohorts
Read 3Starts at $2,790List pricing onlyRegional pricing and deal structure unknownLower than MyEye but still above mainstream-app substitutes
OrCam AppFree companion appNo visible direct monetizationMay support retention, service, and onboarding rather than direct revenueSoftware appears to support hardware economics rather than replace them
VA-funded veteran accessPotentially fully covered device for qualifying veteransPayer-funded route rather than retail realized priceActual reimbursement process and volume unknownThird-party funding may materially expand affordability
School / educator deploymentInstitutional solution with analytics and workflow benefitsContract value not disclosedACV, license structure, and implementation cost unknownEducation channel could shift the sale from consumer purchase to budgeted program

Public sources provide list pricing and payer-path hints, not clean realized pricing.

[CI002, CI008, CI010, CI011, CI012, CI013]
FI001: Revenue model bridge

Public evidence points to a hardware-first revenue loop with training, support, and payer pathways sitting around the core device sale.

This is a qualitative revenue bridge because public sources do not disclose conversion or margin data.

[CI001, CI003, CI009, CI010, CI011, CI014]

4.2 GTM motion and channel economics proxies

OrCam’s go-to-market motion is more complex than a simple direct-to-consumer device sale. Public pages show authorized distribution, a direct buy-now surface, school-oriented selling for OrCam Learn, and VA coverage pathways for legally blind veterans. That mix matters because it implies long conversion cycles for at least part of the business, together with real onboarding and support obligations after the sale. The app-store listings reinforce this view: the companion app is free and includes Wi-Fi setup, device finding, settings control, and support contact flows, indicating that service and retention work continue after hardware shipment. These are financially relevant signals even though they are not full unit economics. They imply nontrivial post-sale support cost and some dependence on channel partners or payer qualification. At the same time, funded routes like VA coverage or school budgets can raise willingness to pay and reduce the personal out-of-pocket burden that otherwise makes the list price difficult for many users.[CI009, CI010, CI011, CI012, CI013, CI014]

FI002: Unit economics bridge

The public unit-economics story is dominated by premium list prices upstream and unknown discounting, support, and hardware costs downstream.

Bridge intentionally highlights the unknowns between public list price and true gross profit.

[CI002, CI010, CI013, CI016, CI017, CI018]

4.3 Cost structure, capital intensity, and unit economics visibility

Because OrCam sells purpose-built assistive hardware rather than pure software, its cost structure almost certainly includes BOM, assembly, quality control, distribution margin, returns, training, and customer support. The public record proves some of these elements indirectly. Device support is active on mobile apps and release-note surfaces; training and orientation show up in veteran and school narratives; and the company’s products span wearable, handheld, and educational form factors, which likely increases inventory and support complexity. What the public record does not reveal is just as important: realized ASP, distributor discounting, gross margin, CAC, payback, warranty cost, return rate, and inventory obsolescence are all unavailable. That means hardware price should not be mistaken for hardware margin. In fact, adverse reporting suggests margin pressure may be severe because free or cheap AI substitutes have damaged the economic case for continued investment in low-vision product development. The result is a financial profile that looks inherently more capital intensive and less observable than a software accessibility product, with public evidence insufficient to underwrite efficient growth.[CI016, CI017, CI018, CI019, CI020, CI021]

Unit economics table
MetricValue / nullConfidenceWhy it mattersDiligence ask
List ASP (MyEye)~$4,250MediumSets ceiling for consumer willingness to pay, not marginProvide realized ASP by channel and geography
List ASP (Read 3)~$2,790MediumIndicates portfolio price ladderProvide realized ASP, promotions, and attach rates
Gross marginNullLowCritical for a hardware business under substitute pressureProvide gross margin by product family and recent trend
CAC / paybackNullLowNeeded to evaluate direct-to-consumer and institutional efficiencyProvide acquisition cost by channel and payback period
Distributor take rate / discountNullLowDetermines how much list price converts into revenueProvide partner economics and revenue share structure
Support burden per active deviceNullLowApps, onboarding, and help-center usage imply meaningful service costProvide tickets, training hours, and warranty cost per device
Inventory / obsolescence riskNullLowHardware transitions and low-vision shutdown raise risk of write-downsProvide inventory aging and reserve policy

Most unit-economics fields remain publicly unavailable, which is itself a negative underwriting signal.

[CI002, CI014, CI016, CI017, CI018, CI019]
FI004: Capital intensity / cash-flow map

Cash demand likely flows through hardware production, channel support, and product-transition spending before any recovery from new hearing revenue can appear.

Qualitative map based on the hardware business model and public distress reporting; no audited cash-flow statement is available.

[CI016, CI017, CI022, CI026, CI027, CI028]

4.4 Capital adequacy and distress signals

The strongest public signals concern capital stress rather than operating leverage. Tracxn reports $86.4 million of total funding across three rounds, while Caplight shows $98.9 million and a July 2024 convertible-debt event, and Seedtable models four funding rounds but only exposes limited detail. Those differences already tell a diligence story: even basic funding history is not perfectly settled in public sources. The more consequential evidence comes from adverse reporting. Calcalist wrote that layoffs in 2024 followed a decision to stop further development of low-vision products because smartphone-based AI alternatives had made them economically redundant. Globes later reported that 2024 revenue fell to about $16 million from $45-50 million in 2023, that the founders and allies had initiated a $12.5 million financing round with roughly $7 million from Shashua, and that the company still needed another $12-15 million. Just as important, Globes said a proposed $2 million loan would keep the company afloat only for a month or two. Taken together, the public picture is of a company with meaningful historical funding but very thin recent runway, contested rescue financing, and a business model under pressure from substitute technology.[CI023, CI024, CI025, CI026, CI027, CI028]

Capital adequacy table
ItemPublic value / statusConfidenceWhy it mattersDiligence ask
Historical funding totalConflicting: $86.4M (Tracxn) vs $98.9M (Caplight)Low-mediumEven basic financing chronology is not fully reconciled in public dataReconcile total raised by round, instrument, and close date
Latest financing statusConflicting: Caplight shows Jul 2024 convertible debt; Seedtable shows last funding date Feb 2018; Globes describes 2024-2025 rescue financing effortsLow-mediumDetermines seniority, dilution, and whether the company already bridged its runwayProvide cap table, note documents, and post-2024 financing ledger
2024 revenue~$16M per GlobesMediumShows post-crisis scale of the operating businessProvide audited or board-approved 2024 revenue by product
2023 revenue~$45-50M per GlobesMediumUseful baseline for contraction analysisProvide 2023 monthly revenue and mix by product/channel
Immediate bridge capital$2M loan would fund only one to two months per GlobesMediumImplies thin runway and urgent cash needProvide cash-on-hand and weekly cash forecast
Additional capital need$12-15M beyond founder-led round per GlobesMediumQuantifies rescue financing dependencyProvide operating plan showing exact cash requirement and milestones
Valuation conditionGlobes estimates >90% decline to ~ $150M; Caplight still shows est. valuation $1.03BLowSignals severe uncertainty around solvency and dilution economicsProvide latest 409A / board valuation and any recap terms

Capital adequacy is where the public evidence is strongest and most adverse.

[CI023, CI024, CI025, CI026, CI027, CI028]
FI003: Financial estimate range

The limited public numbers that do exist point to a severe contraction in revenue and a material rescue-financing requirement.

Figure mixes reported revenue and financing figures only because public disclosure is sparse; all values are USD millions and sourced from adverse reporting.

[CI026, CI027, CI028, CI029]

4.5 Financial verdict and diligence blockers

OrCam’s public financial profile is not investment-grade on disclosure. There is enough evidence to conclude that the company once supported premium hardware pricing, built credible institutional channels, and may still retain profitable vision products in some contexts. There is also enough evidence to conclude that the business absorbed a severe revenue shock, made repeated layoffs, and depends on rescue financing or restructuring to bridge toward any future hearing-led recovery. The core diligence blocker is not merely missing detail but asymmetry: the most concrete numbers in the public record are adverse numbers. For underwriting, management would need to produce cohort-level unit sales, realized ASP by channel, gross margin by product line, current monthly burn, cash on hand, inventory exposure, and a reconciled funding history. Without those, the correct stance is that OrCam may still have valuable products and channels, but its margin path and standalone capital adequacy remain unproven.[CI018, CI024, CI028, CI030, CI032, CI033]

Public financial gaps table
Missing metricImpactExact diligence path
Cash on handImpossible to assess runway directlyRequest latest balance sheet, bank cash, and restricted cash
Monthly burnCannot size rescue financing need independentlyRequest trailing 12-month monthly P&L and cash-flow bridge
Gross margin by productCannot determine whether premium pricing produces attractive economicsRequest product-level COGS and support allocation
Realized ASP by channelList prices may materially overstate actual revenue captureRequest invoiced ASP for direct, distributor, VA, and school sales
Units sold and installed baseCannot translate revenue into product traction or support burdenRequest shipments, active devices, and churn / replacement data
Inventory and reservesHardware transition risk may hide write-downsRequest inventory aging, obsolete stock reserve, and warranty reserve
Hear commercialization metricsCannot tell whether the new focus can finance the companyRequest pilots, orders, revenue, and gross margin for Hear

The missing metrics align closely with the company’s highest-risk underwriting questions.

[CI018, CI019, CI020, CI021, CI034, CI035]

4.6 Exhibits

Chapter 05

05Product & Technology

5.1 Product lines defined by user workflow

OrCam’s product map is best described by user job rather than by SKU list alone. MyEye is the wearable job engine for blind or visually impaired users who need real-time reading, recognition, and scene description while moving through daily life. Read and Read 3 serve the document-access workflow for people with vision loss, reading fatigue, or learning difficulty who want text read aloud, summarized, magnified, or navigated by command. Learn extends that workflow into school settings with reading practice, comprehension prompts, and teacher-facing analytics. Hear is a separate audio-attention product for noisy conversational environments rather than a vision device. That matters strategically because OrCam is not merely shipping one gadget; it is trying to turn a family of assistive workflows into specialized hardware and app experiences. The technical strength of that approach is packaging. The technical weakness is that every product family now competes against increasingly capable general-purpose AI systems.[CE001, CE002, CE003, CE004, CE005, CE006]

Product module / asset matrix
Product linePrimary userStatus / maturityDifferentiationDiligence gap
MyEyeBlind or visually impaired users needing wearable daily assistanceMature public flagshipWearable reading, recognition, scene description, voice/gesture/touch controlNeed clearer public detail on compute architecture and certifications
Read / Read 3Users needing document access, magnification, or reading supportMature public handheld lineOffline reading, full-page capture, stationary mode, Smart Magnifier, AI assistantNeed actual adoption, failure-rate, and cloud dependency detail
LearnStudents and educators in reading-support workflowsEstablished but niche workflow productReading fluency, comprehension feedback, teacher analyticsNeed public contract structure, deployment scale, and data-governance detail
HearUsers with hearing difficulty in noisy environmentsNewer preview-to-early commercial productSelective speaker isolation through earbuds, dongle, and appNeed shipping status, Android support, and real-world performance data
Companion apps and support surfacesInstalled-base usersActive support layerSettings, Wi-Fi setup, device finding, diagnostics, controlNeed release cadence, stability metrics, and support SLAs

Product maturity is based on public workflow evidence, not on audited shipment history.

[CE001, CE003, CE004, CE005, CE006, CE016]
Workflow / use-case table
User jobCurrent workflowOrCam solutionMeasurable benefitLimitation
Read printed or digital textAim camera or pointer at text, capture, listen or navigateMyEye / Read / Read 3Independent text access without screen-heavy interfaceAccuracy and speed by edge case not publicly benchmarked
Identify faces, products, colors, and banknotesCapture environment, receive audio interpretationMyEyeReduces dependence on sighted assistance for everyday tasksPublic materials do not quantify recognition error rates
Study and improve comprehensionStudent reads, receives feedback, teacher reviews analyticsLearnSupports fluency and teacher insightNo public evidence of deployment scale or measured outcomes beyond testimonials
Hear chosen speakers in noisy settingsSelect speakers in app, use dongle and earbudsHearTargets the cocktail-party problem for hearing loss usersCurrently iPhone-dependent in public app evidence
Adjust settings and get helpOpen app, manage volume, speed, Wi-Fi, and supportCompanion appsSimplifies setup and retentionApp quality becomes part of product reliability

Benefits are workflow-level, not clinical endpoints.

[CE002, CE007, CE010, CE011, CE017, CE018]
FE002: Customer workflow / operating flow

OrCam’s products are designed to turn capture, interpretation, and audio guidance into simple assistive loops for different user jobs.

Generalized operating flow across MyEye, Read, Learn, and Hear.

[CE001, CE002, CE003, CE004, CE010, CE017]

5.2 Architecture and operating model

The public architecture is concrete enough to see the system pattern even if it is not disclosed at engineering-diagram level. MyEye and Read products combine sensing hardware, edge interaction, and audio output around assistive reading and recognition. Read 3 exposes some of this most clearly: a 13MP camera, 700 mAh battery, BLE and Wi-Fi connectivity, handheld and stand-based modes, smart magnifier controls, and AI-assisted interaction. MyEye’s manual and product surfaces show a gesture, touch-bar, and voice-command interaction model for reading, face recognition, product identification, banknotes, colors, and personalization. Hear uses a different stack built from TWS earbuds, a smartphone dongle, low-latency Bluetooth, and an iPhone app that runs speaker-separation controls. Across these products, the unifying operating model is assistive AI delivered through highly constrained interfaces that reduce screen dependence. The missing layer is how much inference runs on device versus phone or cloud in each mode; public materials reveal enough for workflow understanding, but not enough for a full technical audit.[CE008, CE009, CE010, CE011, CE012, CE013]

Technology / operating architecture table
Layer / componentRoleDependencyRisk
Camera sensorsCapture text, scenes, handwriting, productsHardware optics and image-processing stackSensor quality and lighting conditions can bound utility
Assistive AI / computer visionTurn captured inputs into reading, description, or recognition outputsModel quality, device compute, and possibly connected featuresCommoditization risk as mainstream models improve
Voice, gesture, and touch controlsReduce need for screen-heavy UIReliable interaction design and onboardingAccessibility gains disappear if controls are inconsistent
Smart Magnifier / station modeExpand reading and magnification workflowsRead 3 hardware plus stand or smart screen contextFeature complexity may increase support burden
Hear dongle + earbuds + appIsolate chosen voices and deliver low-latency outputiPhone app, dongle, Bluetooth, and mic array workflowPhone dependency and latency can impair experience
Connectivity / apps / updatesConfigure devices, support Wi-Fi, personalization, and updatesApp-store distribution and support operationsSparse public release history limits auditability

Table reflects publicly visible operating components, not proprietary internal code structure.

[CE008, CE009, CE010, CE011, CE012, CE013]
FE001: Product architecture map

Across product lines, OrCam repeatedly stacks sensing, assistive AI, constrained interaction, and audio output into purpose-built workflows.

Architecture map abstracts across product families; public sources do not expose full per-device compute diagrams.

[CE008, CE009, CE010, CE011, CE012, CE015]
FE003: Critical dependency map

Product reliability depends on hardware sensing, mobile apps, support operations, and continued AI quality more than on one single component.

Dependency map uses public product and app evidence; supply-chain and cloud-service dependencies remain under-disclosed.

[CE011, CE014, CE018, CE019, CE031, CE036]

5.3 Deployment, support, and roadmap signals

Deployment appears deliberately simplified. The mobile apps are free, the manual emphasizes charging, gestures, and getting started, and the devices are designed to work through audio feedback rather than through visual UI complexity. Read 3 explicitly supports handheld and stationary-reader operation, while Hear depends on an iPhone app and phone-connected dongle, creating a tighter smartphone dependency. Support surfaces include FAQ, release notes, app-store diagnostics fields, and direct support contact from the app itself. Roadmap visibility, however, is uneven. The release-notes page confirms ongoing updates but publishes little structured change history in the readable extract. Hear’s CES-era coverage shows the product in preview or early shipping mode, and external reviews emphasized promise more than mature commercial scale. That leaves product maturity uneven across the stack: MyEye and Read look like mature assistive devices, Learn looks workflow-specific but established, and Hear still looks like a newer bet that depends materially on app quality and continued tuning.[CE016, CE017, CE018, CE019, CE020, CE021]

Roadmap / release / development-stage table
Date / stageFeature / milestoneStatusImplicationSource
Software version 9.4 guideMyEye user guide publishedLive public docSuggests maintained installed base and training surfaceMyEye manual page
Current public release-notes pageUpdates and enhancements acknowledgedLive but sparse in readable extractConfirms ongoing iteration but limits outside audit of paceRelease notes page
CES 2024 previewHear shown in hands-on and media coveragePreview / early commercial signalUseful validation, but not proof of broad deploymentEngadget / Forbes / Reviewed
Current app-store listingHear iPhone app availableLive public software surfaceShows product has consumer-facing software artifactApp Store
Current product pagesRead 3 and Learn continue to be marketedLive public product surfacesSuggests continued support for reading and education linesOfficial product pages

Roadmap evidence is inferred from public surfaces rather than from a formal roadmap disclosure.

[CE016, CE019, CE020, CE021, CE022, CE023]
FE004: Product maturity / capability map

MyEye and Read appear most mature; Hear is promising but still shows the greatest dependency on continued app and product tuning.

Capability strengths are ordinal, reflecting public workflow and support evidence rather than benchmark testing.

[CE003, CE004, CE005, CE016, CE021, CE023]

5.4 Differentiation, know-how, and technical moat

OrCam’s technical differentiation is not best understood as secret model architecture; it is best understood as assistive productization. The company has repeatedly taken computer-vision or speech separation capabilities and embedded them in constrained hardware, intuitive controls, and targeted assistive workflows. That includes laser-guided capture and offline reading on Read, multi-modal control on MyEye, teacher-analytics framing for Learn, and speaker-selection UI for Hear. External coverage from CES 2024 also suggests that OrCam can still generate genuine product interest when it packages a hard problem, such as selective hearing in noise, into a clear demonstration. The moat risk is that many underlying enabling technologies—OCR, summarization, scene description, language interaction, even some voice isolation—are becoming more widely available on general-purpose platforms. OrCam’s defense is therefore workflow-specific packaging, ergonomics, and domain focus rather than obvious public proof of a closed technical platform or uniquely disclosed IP moat.[CE024, CE025, CE026, CE027, CE028, CE029]

5.5 Trust, safety, quality, and compliance posture

OrCam’s public trust posture is mixed. The positive side is clear evidence of manuals, onboarding content, device apps, support surfaces, and an FDA-report commercial registration footprint. Those are not proof of superior safety, but they do show a structured effort to support users of assistive hardware. The weaker side is the relative thinness of public compliance detail. Compared with Microsoft’s Seeing AI manual—which explicitly states intended purpose, contraindications, and MDR classification—OrCam’s readable public materials reveal much less structured safety and regulatory disclosure. App-store data disclosures are basic, and public extracts do not expose security architecture, formal quality-system claims, incident handling, or certification scope for each device family. This does not prove a quality failure. It does mean diligence should treat trust and compliance as under-disclosed technical domains rather than as resolved strengths.[CE030, CE031, CE032, CE033, CE034, CE035]

Trust / quality / compliance table
Control / signalStatusScopeGap
MyEye user guidePublicly visibleSetup, gestures, reading, recognition, settingsNo full public safety/compliance structure in readable extract
FAQ / release notes / support contactPublicly visibleGeneral support and update signalingReadable extracts do not show robust quality metrics or incident processes
App-store privacy disclosuresPublicly visibleBasic app data handling and diagnostics fieldsNot equivalent to device-wide privacy/security architecture
FDA.report registration footprintPublicly visibleCommercial registration signal for ORCAM INCDoes not explain quality system or device-specific regulatory status
Comparative structured safety disclosureWeak versus Seeing AI manualOrCam public materials are less explicit on intended purpose and contraindicationsNeed formal safety, risk, and classification documents by product

Trust posture is supported by support surfaces, but formal compliance disclosure remains thin.

[CE030, CE031, CE032, CE033, CE034, CE035]

5.6 Exhibits

Chapter 06

06Customers

6.1 Customer segmentation by user, buyer, and payer

OrCam’s customer map is multi-sided. The end user is often a blind, low-vision, or reading-challenged individual, but the buyer and payer vary by segment. Retail-style commerce pages suggest direct or family-supported purchases for MyEye and Read devices, especially where installment plans and 30-day guarantees are emphasized. Veterans surfaces point to a distinct payer structure in which VA-linked funding or blinded-veteran associations can offset or fully cover device cost. Learn pages reveal a third structure in which teachers, schools, occupational therapists, and families participate in the purchase or deployment decision. These school-facing materials also suggest that the person benefiting from the product is rarely the sole decision-maker. The result is not one uniform customer base but a portfolio of segments with very different procurement friction, affordability, and proof requirements. That customer diversity is strategically positive, but it also makes OrCam more dependent on channel execution and advocacy than a purely self-serve accessibility app would be.[CU001, CU002, CU003, CU004, CU005, CU006]

Customer segmentation table
SegmentBuyer / user / payerUse caseScaleRevenue / strategic valueGap
Blind / low-vision individualsUser = individual; buyer = self/family/distributor; payer = self or familyReading, recognition, independenceReal but undisclosedCore device revenue baseNeed active-device counts and self-pay mix
Legally blind veteransUser = veteran; buyer / payer may involve VA pathway or BVA-linked supportRehabilitation, independent living, reading, recognitionNamed proof but no aggregate countHigh-value funded channel and credibility signalNeed actual VA unit volume and reimbursement mechanics
Students with reading differences or low visionUser = student; buyer = family or school; payer variesReading fluency, comprehension, classroom supportNamed proof across multiple schools and familiesExpands beyond low-vision niche into learning supportNeed contract structure, ACV, and retention by school cohort
Educators / therapists / schoolsBuyer or influencer rather than end userAssessment support, reading analytics, classroom independenceVisible consultative funnelInstitutional deployment path for LearnNeed number of schools, demos, and renewals
Hearing-loss usersUser = hearing-impaired adult; buyer/payer not yet clearly disclosedSelective listening in noise via HearPublic preview proof onlyPossible adjacent customer baseNeed commercial shipments and repeat-usage data

Segment table distinguishes user need from who actually pays, because OrCam’s funded and school channels matter materially.

[CU001, CU002, CU003, CU004, CU005, CU006]
FU001: Customer journey map

Different customer segments arrive through different buyers and payers even when the end user shares similar accessibility needs.

Journey map is qualitative because public sources do not disclose conversion rates.

[CU001, CU002, CU003, CU004, CU017, CU018]

6.2 Named customer proof is stronger than aggregate customer counting

Public customer evidence is much more tangible at the named-deployment level than at the portfolio level. OrCam’s veteran materials and blog stories identify real users such as Scotty Smiley and describe device usage in rehabilitative daily living. Read 3 testimonials name Ashley Mizell and make the device’s role in reading to children and navigating blindness concrete. Learn materials surface named adults and organizations, including Michelle Catterson at Moon Hall School, Charisa Cheek at Cooperative Educational Services Agency #5 in Wisconsin, and Dr. Helen Ross as an independent researcher and British Dyslexia Association leader. These references matter because they show use in schools, home learning, and rehabilitation settings rather than only in generic marketing copy. The weakness is that these stories mostly prove relevance, not scaled commercial penetration. We know more about how several users benefited than about how many customers remain active today, what portion came through funded programs, or how many upgraded beyond the first device.[CU004, CU009, CU010, CU011, CU012, CU013]

Named customer proof table
CustomerSegmentDeployment / use caseProduction vs pilotOutcomeLimitation
Scotty SmileyBlind veteranUses MyEye for reading to children, identifying clothes and kitchen itemsProduction user storyImproved independence and family participationSingle anecdotal story; no duration or cohort data
Ashley MizellBlind community advocateUses Read 3 for reading, magnification, and parenting tasksProduction user storyStates device restored confidence and ability to read to childrenCommercial relationship with OrCam reduces independence
Moon Hall School / Michelle CattersonSchool / educatorLearn used to support independent learningProduction-style testimonialHeadteacher explicitly recommends solutionNo contract size, seat count, or renewal data
Cooperative Educational Services Agency #5 / Charisa CheekSchool / therapistAssistive-technology coordinator uses Learn to support student independenceProduction-style testimonialImproved integration with less adult supportNo district-wide deployment count
Aidan Lane / Thomas Hardye SchoolStudentUses Learn for schoolwork and reading independenceProduction-style student testimonialClaims grade improved from C to ASingle-user anecdote; no controlled baseline
Wendy with dyslexiaStudent / familyUses Learn for reading and comprehension supportProduction-style testimonialDescribes homework speed and comprehension supportNo evidence of long-term retention
Ela Mae with Batten’s diseaseChild low-vision userReceived Read 3 through Ashley Mizell / OrCam connectionProduction user storyReduced painful close-up reading strainPhilanthropic story, not direct sales proof

Named proof is substantial for a hardware accessibility company, but outcomes remain anecdotal and non-portfolio-wide.

[CU004, CU009, CU010, CU011, CU012, CU013]
FU003: Customer proof matrix

Customer proof is strongest on named use-case specificity and weakest on retention visibility and portfolio-level scale.

Matrix uses ordinal evidence scoring based on how concrete each testimonial or deployment reference is.

[CU009, CU010, CU011, CU012, CU013, CU014]

6.3 Adoption trajectory and deployment signals

The public adoption trail is mostly composed of soft operational signals rather than hard customer counts. OrCam keeps multiple live product, testimonial, demo, support, and store surfaces up, which suggests an active installed base worth serving. Financing plans, free shipping, a one-year warranty, and a 30-day guarantee indicate that the company still expects individual purchasing friction and seeks to reduce it. School-contact pages explicitly ask prospects to leave information for a personal demo, which is consistent with a consultative sales motion rather than a pure click-to-buy education funnel. The apps also reveal ongoing support surfaces and mobile control layers for devices already in the field. What is absent is denominator math: no public active-device count, shipped-unit number, demo-to-close rate, or renewal rate is visible. Therefore, adoption can be described as evidenced but not quantified at scale.[CU017, CU018, CU019, CU020, CU021, CU022]

Customer growth / adoption trajectory table
MetricValueDateSourceConfidenceImplicationMissing denominator
Live testimonials surface for LearnPresent2026 accessOfficial testimonials pageMediumSuggests active customer-marketing motion and referenced user baseNo number of users represented
Live testimonials surface for Read 3Present2026 accessOfficial testimonials pageMediumSuggests active advocacy and post-sale storytellingNo number of total customers
School personal-demo CTAPresent2026 accessContact page for schoolsMediumIndicates consultative lead-generation funnelNo demo-to-close rate
Payment-plan options for Read / Read 312/18/24 installment options with 0% APR visible on store pages2026 accessOfficial store pagesMediumShows effort to lower purchase frictionNo share of financed purchases
Support apps live in app storesPresent2026 accessApple / Google app listingsHighImplies active installed base and device support needNo active monthly users or support volumes
VA / veterans funding routePresent2026 accessVeterans pages / BVA pageMediumSupports funded-channel adoption pathNo count of funded veterans

Trajectory evidence is operational rather than numerical because public denominator data is absent.

[CU017, CU018, CU019, CU020, CU021, CU022]
FU002: Adoption / deployment funnel

Public customer acquisition appears to move through awareness, proof, funding, purchase, and support rather than a simple one-click accessibility download.

Funnel is inferred from testimonials, store pages, demo CTAs, and support surfaces.

[CU017, CU018, CU019, CU020, CU021, CU022]

6.4 Retention, expansion, and concentration risks

Retention and concentration are the least transparent parts of the customer story. Public testimonials strongly imply satisfaction and repeat use, but they do not reveal renewal rates, repeat purchase, device upgrade cycles, or cohort churn. Product family breadth does create plausible expansion loops: a veteran or visually impaired user might start with MyEye or Read and later use app-connected features; a school might move from an individual assistive purchase to a broader Learn deployment; and families may purchase add-on or replacement devices as needs evolve. But the public record also suggests concentration risk. VA coverage, blinded-veteran partnerships, specialist distributors, and school demos all point to channel dependence. Adverse reporting that Arab-country purchases were frozen during wartime further shows that important demand pockets can be disrupted by geopolitical or channel-specific events. The proper conclusion is not that the customer base is concentrated beyond repair, but that its durability cannot be underwritten without segment-level revenue and retention data.[CU024, CU025, CU026, CU027, CU028, CU029]

Retention / repeat usage / satisfaction table
MetricValue / nullSegmentConfidenceDiligence ask
NRR / revenue retentionNullAll segmentsLowProvide renewal and upgrade revenue by cohort
GRR / logo retentionNullAll segmentsLowProvide active customer cohort survival by segment
Repeat purchase / upgrade rateNullDirect and family buyersLowProvide replacement, add-on, and upgrade rates
Satisfaction signalPositive testimonial evidenceVeterans, students, individual usersMediumProvide structured NPS / CSAT by product
Duration of useNullNamed customer storiesLowProvide average device life and time-to-churn
App engagementNullInstalled-base device usersLowProvide MAU, DAU, and support-contact rates

Retention proof is mostly anecdotal today; the nulls are material, not cosmetic.

[CU024, CU025, CU026, CU031, CU032]
Expansion and concentration risk table
Expansion driverConcentration riskImpactDiligence path
Cross-sell across MyEye, Read, Learn, apps, and HearPublic evidence does not show actual cross-sell ratesMedium opportunity, unknown realizationRequest product overlap and upgrade ladder by account
VA-funded veteran pathwayDependence on one payer/channel type could create concentrationHigh for U.S. funded usersRequest VA unit volume and payer concentration
School and therapist-led deploymentsInstitutional procurement can be slow and lumpyMediumRequest pipeline conversion and annual contract renewals
Distributor and financing-assisted consumer salesPartner or financing dependence can mask direct demand elasticityMedium-highRequest partner concentration and financed-sales share
Regional growth in geopolitically exposed marketsAdverse reporting says war froze purchases from Arab countriesHigh in affected geographiesRequest revenue by region and channel resilience plan

Concentration risk likely sits in channels and geographies, not just in named end users.

[CU027, CU028, CU029, CU030, CU033, CU035]
FU004: Retention / repeat cohort

Public signals support high mission fit across several segments, but give far weaker evidence on measured repeat economics or renewal durability.

Scores are 0-100 qualitative retention-signal assessments based on public evidence; they are not reported retention percentages.

[CU024, CU025, CU026, CU027, CU030, CU032]

6.5 Customer verdict and diligence blockers

The customer evidence clears the threshold of reality but not of transparency. OrCam clearly serves real blind, low-vision, and reading-support users; it has proof in veterans channels and schools; and it shows enough post-sale and testimonial activity to reject the idea that the company is purely conceptual. At the same time, almost every scaling question remains open: how many active users, what share self-pay versus funded, which segments expand, how concentrated channel revenue is, and how many customers upgrade or churn. For a diligence process, management would need to provide segment-by-segment unit shipments, active devices, funded-versus-self-pay mix, top-partner concentration, upgrade rates, and customer-support intensity. Until then, the best-supported position is that OrCam has authentic customer proof and several viable niches, but no public evidence yet robust enough to prove durable, diversified customer economics.[CU009, CU017, CU024, CU028, CU031, CU032]

6.6 Exhibits

Chapter 07

07Risks

7.1 Regulatory and legal risks

Public legal and regulatory signals are mixed rather than binary. On the positive side, OrCam exposes formal terms of use, product terms and conditions, a privacy statement hub, a cookies policy, an accessibility statement, and an FDA-report registration footprint. That suggests a company that has at least built a legal shell around its commerce and public support surfaces. On the negative side, these public materials do not clearly resolve product-specific classification, device-family regulatory status, or incident governance in the same way some adjacent accessibility tools do. OrCam’s terms explicitly state that the company is not a medical organization and that the website is not designed to provide diagnosis or medical advice, which helps define scope but also highlights legal sensitivity around how users interpret the product. The accessibility statement further shows intent to meet WCAG/Section 508 standards, but an intent statement is not a full product-compliance audit. The legal verdict is thus manageable but under-disclosed: there is enough structure to reduce obvious negligence risk, but not enough product-level detail to dismiss regulatory or privacy diligence.[CR001, CR002, CR003, CR004, CR005, CR006]

Regulatory / legal risk register
Rule / case / controlJurisdictionStatusLikelihoodSeverityMitigationResidual exposureDiligence path
Product classification and intended-use ambiguityUS / EU / UKPublic legal shell exists, but device-family classification detail is sparseMediumHighTerms and support materials narrow medical-advice scopeMaterial until device-by-device regulatory status is verifiedRequest regulatory inventory, intended-use statements, and product registrations by family
Privacy and data-handling obligationsMulti-jurisdictionPrivacy statement hub, cookies policy, and app disclosures existMediumMedium-highPolicies and app disclosures are visible publiclyPublic materials do not show device-level data-flow governanceRequest DPA, retention schedule, telemetry map, and privacy-by-product review
Accessibility and web-compliance commitmentsUS-focused with global usersAccessibility statement references WCAG/Section 508/ADALow-mediumMediumPublished accessibility statement and support contactNo independent audit or product accessibility verification in retained setRequest last accessibility audit and remediation log
Product terms, refunds, and force-majeure limitsCommerce geographies served by OrCamTerms of use and sale are public and returns are definedLow-mediumMediumContractual disclosures reduce surprise around purchase processLegal terms do not eliminate reputational or consumer-dispute riskReview complaint trends, refund rates, and territory-specific exceptions

Rows are ordered by practical investment severity rather than by formal legal taxonomy.

[CR001, CR002, CR003, CR004, CR005, CR006]
FR001: Risk heatmap

The most severe residual risks cluster around technology substitution, capital adequacy, partner dependence, and under-disclosed compliance depth.

Scores are ordinal 1-5 assessments derived from retained public evidence, not management disclosures.

[CR005, CR010, CR016, CR024, CR031]

7.2 Technology substitution and model-displacement risks

Technology substitution is the clearest thesis risk. Calcalist reported directly that language-model advances made further low-vision development unnecessary, while Globes reported that competition from AI companies was one of the two blows driving the recovery plan. The substitute set is no longer abstract: OpenAI’s work with Be My Eyes, Apple’s accessibility stack, Microsoft Seeing AI, and Google’s announced intelligent eyewear all point toward mainstream actors embedding vision and hearing assistance into general platforms. That does not prove those products beat OrCam in every workflow. It does prove that assistive perception is no longer a protected feature set. OrCam’s defense is packaging, ergonomics, funded channels, and mission fit. If those do not outweigh generic model progress, the company faces margin compression, demand erosion, and reduced justification for dedicated-device R&D.[CR009, CR010, CR011, CR012, CR013, CR014]

7.3 Capital, operational, and people risks

Operational and financial risks are tightly coupled. A hardware accessibility business already carries inventory, support, warranty, and channel complexity. When revenue contracts sharply, those burdens become harder to fund. Public reporting indicates three rounds of layoffs in 2024, a freeze in some Arab-country demand, and a rescue-financing process that was still contested in 2025. Those facts raise people and execution risk immediately: a smaller workforce may struggle to support multiple product lines, maintain quality, and continue innovation fast enough to match platform competitors. Hardware and app combinations also create reliability risk across manufacturing, distribution, onboarding, and software updates, yet the public record does not expose incident rates or failure metrics. The operating question is therefore not whether OrCam can ship products at all; it is whether it can sustain product quality, channel responsiveness, and capital discipline under visible stress.[CR016, CR017, CR018, CR019, CR020, CR021]

Operational / quality / security risk register
Failure modeLikelihoodSeverityMitigation maturityResidual exposureUnresolved gap
Product reliability or support degradation after layoffsMedium-highHighLow-mediumHighNo public QA, failure-rate, or support-SLA data
Inventory / hardware obsolescence as AI substitutes improveHighHighLowHighNo inventory-aging or write-down disclosure
App + device integration failures across updates and setupMediumMedium-highMediumMedium-highRelease notes are sparse in readable extract and incident data unavailable
Privacy or data-flow control weaknesses across devices and appsMediumMedium-highLow-mediumMedium-highPublic policy shell exists but technical controls remain under-disclosed
Security / misuse of assistive outputs in safety-sensitive contextsMediumMediumLowMediumNo structured public risk-management disclosure by device family

Operational risk rises materially if staffing and capital continue shrinking while product breadth remains wide.

[CR016, CR017, CR018, CR019, CR020, CR021]
People / execution risk register
Role / functionDependency or gapLikelihoodSeverityMitigationDiligence path
Engineering and product maintenanceMultiple product lines after repeated layoffsHighHighNarrow roadmap and prioritize core productsRequest org chart, attrition, and headcount by function
Support and training teamsAssistive products require onboarding and customer helpMedium-highHighInvest in support tooling and focused segmentsRequest ticket backlog and support staffing trend
Management executionRecovery plan and financing have been publicly contestedHighHighBoard alignment and milestone-based recapitalizationRequest current operating plan and board-approved milestones
Regulatory / compliance ownershipPublic materials do not show device-family compliance leadership clearlyMediumMedium-highCentralize compliance ownership by productRequest named compliance leaders and audit cadence
Commercial executionConsultative demos and funded channels create longer cyclesMedium-highMedium-highTighten segment focus and channel accountabilityRequest pipeline conversion and partner performance dashboards

People risk is amplified because mission-critical assistive products need both empathy-rich support and fast technical iteration.

[CR017, CR018, CR022, CR023, CR027, CR031]
FR002: Risk transmission map

Substitution and capital shocks flow quickly into margins, support quality, customer durability, and valuation.

Transmission path synthesizes adverse reporting and hardware-business economics.

[CR009, CR016, CR017, CR018, CR032, CR038]

7.4 Partner and dependency risks

OrCam depends on several external systems it does not fully control. Veterans pathways, blinded-veteran associations, school demos, distributors, app stores, smartphone platforms, and possibly broader capital providers all appear in the public operating picture. Hear is visibly iPhone-dependent in its current public app form, while Google and Apple are simultaneously moving eyewear and accessibility further into their own platforms. That creates a partner paradox: the very platforms that help distribute some of OrCam’s software surfaces are also building substitute capabilities. Distributor and funded-channel reliance adds another layer of fragility because those routes can slow, narrow, or reprioritize demand. Where partner leverage is strongest, OrCam must either own the workflow so deeply that substitution is hard, or diversify channels faster than platform competition intensifies.[CR024, CR025, CR026, CR027, CR028, CR029]

Partner / dependency risk register
DependencyCounterparty / classRoleConcentrationFailure scenarioSeverityMitigationResidual exposure
Veterans funding pathVA / BVA-linked ecosystemPayer and credibility channelPotentially meaningfulCoverage slows or policy shifts reduce funded demandHighDiversify channels and prove self-pay valueHigh until concentration is quantified
School and therapist channelsSchools / educators / demo funnelInstitutional Learn deploymentModerateLong cycles or budget freezes delay adoptionMedium-highBroaden buyer set and reduce implementation burdenMedium-high
Smartphone and app-store platformsApple / GoogleSupport apps, Hear app, phone integrationHigh for Hear and support layerPlatform rules or native substitute features reduce relevanceHighCross-platform support and stronger differentiated workflow ownershipHigh
Capital providersFounders / investors / institutional holdersBridge and rescue financingHigh in distress contextFinancing stalls or comes with punitive dilution termsHighClose committed capital and simplify cap structureHigh
Distributors and financed-sales partnersAuthorized distributors / payment-plan providersSales reach and affordability supportUnknownPartner friction or economics reduce realized demandMedium-highExpand direct evidence of demand and partner diversityMedium-high

Risk stems both from reliance on partners and from those partners simultaneously enabling substitutes.

[CR010, CR024, CR025, CR026, CR027, CR028]
FR003: Dependency map

OrCam depends simultaneously on funded channels, mobile platforms, legal/compliance infrastructure, and rescue capital while facing substitute threats from some of those same ecosystems.

Dependency map highlights that distribution and substitution can come from adjacent platform ecosystems at the same time.

[CR011, CR024, CR025, CR026, CR027, CR028]

7.5 Mitigations, monitoring, and thesis-break triggers

The main risk mitigants are conceptually visible even if not yet fully proven. OrCam can still lean on funded access routes, workflow-specific ergonomics, premium support, and segmentation where dedicated hardware outperforms smartphone substitutes. But those mitigants need evidence. If management cannot prove sufficient runway, stable gross margin on core devices, durable funded-channel demand, and a credible product roadmap against Apple/Google/OpenAI-type entrants, the thesis weakens quickly. Clear kill criteria would include another sharp drop in reported revenue, failure to close rescue capital, loss of veteran or school channels, meaningful product-support deterioration, or further evidence that low-vision functions are being replaced by mainstream AI at much lower cost. Because public disclosure is partial, diligence should focus on monitorable thresholds rather than on broad optimism about assistive-technology growth.[CR031, CR032, CR033, CR034, CR035, CR036]

Mitigation and kill criteria table
RiskMonitorable triggerThreshold / eventAction implication
Capital adequacyCash runway and financing closeNo credible bridge or rescue capital securedPause investment or require recap terms first
Technology substitutionCore workflow parity from mainstream platformsUser tasks reproducible on Apple/Google/OpenAI-led tools at much lower costRe-cut moat assumptions and margin forecast
Channel concentrationVeterans / school / distributor dependencyOne route-to-market dominates revenue without backup channelsDemand customer concentration discount
Operational qualitySupport or product-failure deteriorationRising complaints, return rates, or onboarding failuresHaircut growth and margin assumptions
Regulatory / trust disclosureCompliance diligence cannot resolve scopeNo product-level regulatory or privacy evidence on requestTreat as unresolved thesis blocker

Kill criteria are written as diligence gates rather than as abstract red flags.

[CR031, CR032, CR033, CR034, CR035, CR036]

7.6 Exhibits

Chapter 08

08Valuation

8.1 Recommendation and valuation stance

OrCam deserves a diligence discussion, but not a blind premium entry. The company still has real assistive products, real customer stories, and a founder lineage that once supported serious public-market ambition. That keeps it out of the “broken concept” bucket. The problem is that public evidence on price has diverged violently from public evidence on operating stress. Caplight still shows an estimated valuation of about $1.03 billion and a July 2024 convertible-debt round, but the strongest adverse reporting says revenue fell to roughly $16 million in 2024, additional rescue money was still needed, and institutional investors were effectively negotiating around a fair-value reset. In that context, the right investment stance is not “yes” or “no” in the abstract; it is “only if the price resets or the evidence improves.” I would not underwrite new money at a legacy unicorn narrative today. I would track the company, demand direct cap-table and revenue proof, and only engage if current terms create enough upside to compensate for the high residual risk.[CV001, CV006, CV007, CV008, CV010, CV011]

Recommendation summary table
DimensionAssessmentConfidenceValuation stanceDecision implication
Overall recommendationResearch-more / TrackMediumAvoid legacy unicorn markOnly proceed after current terms and revenue quality are diligenced
Risk ratingHighHighRequires discountUnderwrite as a special situation, not a clean growth round
Current public price visibilityConflictedHighUnknown-to-stretchedDo not treat vendor marks as a substitute for signed term sheets
Operating proofReal but impairedMediumSupportive but discountedProduct and customer proof support non-zero value, not premium certainty
Exit readinessStrategic more plausible than IPOMediumConditionalPrioritize asset-level or strategic pathways over IPO narratives

The recommendation is explicitly price-sensitive because public price discovery is conflicted.

[CV007, CV010, CV011, CV024, CV028, CV029]
Thesis / anti-thesis table
DimensionThesis argumentAnti-thesis argumentWhat would change the view
Product realityRead, MyEye, and Hear show real productization and user valueReal products can still be overvalued if substitutes commoditize the workflowShow current product mix, gross margin, and retention by device line
Funding historyOrCam achieved real institutional support and historic unicorn statusMost transparent priced-round evidence is old, while recent evidence is conflicted or distressedProvide current signed cap-table and latest financing memo
Founder / strategic haloShashua/Aviram lineage and Mobileye adjacency can attract strategic interestFounder halo does not erase declining revenue or weak current price evidenceShow live strategic interest or bids tied to current product assets
Comparable supportPremium eye-tech comps prove specialized device businesses can hold valueMainstream public medtech and vision-AI multiples are far below a 2024-distress unicorn multipleShow why OrCam deserves premium multiple persistence despite revenue stress
Exit pathStrategic sale could still unlock value from niche assetsIPO path looks weak until price, growth, and cap structure are stabilizedShow audited forward plan and bankable exit pathway
Current markCaplight suggests a unicorn-scale estimate still existsGlobes implies a drastic reset may already be the truer economic signalResolve the gap with a fresh priced round or audited secondary transaction

The debate is not whether OrCam built meaningful technology, but whether today’s price is justified by today’s evidence.

[CV001, CV006, CV008, CV011, CV019, CV021]
FV001: Recommendation logic
[CV007, CV010, CV028, CV029, CV030, CV032]

8.2 What current public marks actually confirm

The public valuation trail is less coherent than it first appears. Tracxn and the 2018 Times of Israel coverage both support the existence of a $1 billion milestone around the Series B era, while Seedtable reinforces that the last clearly priced round in its retained profile dates back to February 2018. Caplight is different: it presents a much later estimated valuation of $1.03 billion, a July 2024 convertible-debt round, and total funding raised of $98.9 million. Those data points are useful, but they do not by themselves prove a clean late-stage priced equity round at that valuation. Against them sits the most damaging independent evidence in the set: Globes reported a 2025 dispute over the recovery plan, a fall in revenue from roughly $45-50 million in 2023 to $16 million in 2024, and an estimate that fair value had fallen by more than 90% to about $150 million. The conclusion is not that one source must be perfectly right and the others wrong. It is that public investors are looking at two incompatible stories: a vendor-estimated unicorn and a distressed recap candidate. Until management resolves that gap with current signed terms and current revenue quality, price remains the core diligence problem.[CV001, CV002, CV003, CV004, CV005, CV006]

Comparable valuation table
ComparableMetricMultiple / valuation / statusRelevanceLimitation
OrCam (Caplight)Estimated private valuation~$1.03B estimate; last round shown as Jul 2024 convertible debtBest retained current-looking market-data anchorEstimate rather than clean priced-round disclosure
OrCam (Globes adverse estimate)Distress/fair-value signal~$150M after >90% fall from 2021 valueBest retained adverse price-reset signalMedia estimate, not signed transaction
MobileyePublic market cap and 2024 revenue~$6.77B market cap on ~$1.7B revenue (~4.0x)Israeli computer-vision founder adjacency and strategic-acquirer precedentFar larger platform and different end market
GlaukosPublic market cap and 2024 net sales~$9.83B market cap on ~$383.5M net sales (~25.6x)Premium public ophthalmic growth compRegulated ophthalmic platform, not distressed assistive hardware
Sight SciencesPublic market cap and 2025 revenue~$0.28B market cap on ~$77.4M revenue (~3.6x)Useful small-cap eye-tech downside / reality anchorDifferent procedure economics and reimbursement model
SonovaPublic market cap and 2025/26 sales~$16.54B market cap with CHF 3.606B salesScaled assistive-device incumbent showing what maturity can look likeMuch larger, diversified global platform
Intel / Mobileye 2017Strategic M&A precedent~$15.3B equity value acquisitionShows strategic buyers will pay for mission-critical vision AINot a like-for-like current valuation anchor for OrCam

This is a partial comparison set chosen to bracket OrCam’s conflicting public marks against relevant private, public, and strategic anchors.

[CV001, CV006, CV013, CV014, CV015, CV016]
FV004: Investment KPIs
[CV001, CV002, CV006, CV007, CV028, CV030]

8.3 Scenario ranges and entry discipline

Because the public record does not reveal a clean present-day priced round, the right framework is scenario valuation rather than faux precision. In the bull case, OrCam closes its recapitalization, preserves the profitable reading-glasses economics described by Globes, proves that Hear can become a second leg of growth, and restores revenue into a range that can justify a premium niche-device multiple. That is the only path that cleanly supports staying near the unicorn line. In the base case, OrCam remains a real but narrower assistive-device company with funded channels, a support-heavy go-to-market model, and enough product relevance to stabilize but not enough proof to command elite multiples. In the bear case, platform substitutes keep compressing the vision use case, funding terms turn punitive, and the outcome looks more like a structured recap, spinout, or strategic asset sale. Entry discipline should follow those scenarios directly: a buyer paying today’s public unicorn mark is implicitly underwriting the bull case before management has proven it.[CV013, CV014, CV015, CV017, CV018, CV019]

Bull / base / bear scenario table
ScenarioOperating assumptionsImplied valuation rangeValuation logicKey risksProbability signal
BullRecap closes, Hear gains traction, vision products stay profitable, revenue recovers toward $60M-$70MUSD 0.85B-1.30BRoughly 12x-18x on restored niche-device revenue and strategic scarcityExecution, funding, platform substitutionRequires proof strong enough to defend or re-earn the Caplight-like mark
BaseBusiness stabilizes as a narrower assistive-device company with funded channels and partial recovery to $35M-$50M revenueUSD 0.35B-0.70BRoughly 7x-12x on stabilized revenue with heavy risk discountCustomer concentration, slower growth, support burdenMost consistent with a real but smaller company than the legacy unicorn story
BearFurther substitution, punitive recap, or asset-level restructuring leaves revenue flat or lower around $15M-$30MUSD 0.15B-0.35BRoughly 5x-10x on stressed revenue or strategic asset-value framingDown-round, channel loss, product obsolescenceConsistent with the adverse 2025 recovery narrative and fair-value reset risk

Scenarios express plausible valuation bands in USD billions based on public operating anchors, comparable corridors, and recap uncertainty.

[CV006, CV017, CV018, CV019, CV020, CV025]
FV002: Valuation sensitivity
[CV006, CV017, CV018, CV019, CV025, CV026]
FV003: Valuation / return range
[CV033, CV034, CV035]

8.4 Comparable anchors and exit options

The comparable set argues for discipline. Mobileye, a founder-adjacent Israeli computer-vision success story, had roughly $1.7 billion of 2024 revenue and an August 2026 market cap around $6.77 billion, which is a far larger platform than OrCam today. Sight Sciences, a much smaller public eye-care technology company, sits closer to the scale question that matters for OrCam and is valued at only about $0.28 billion against $77.4 million of 2025 revenue. Glaukos is the premium public ophthalmic growth comp, but its nearly $9.83 billion market cap is attached to a regulated ophthalmic platform with approximately $383.5 million of net sales, not to a distressed niche hardware company. Sonova provides the opposite reminder: scaled assistive-device incumbents can be worth a great deal, but only after they have achieved global distribution, strong financials, and billions of sales. Exit logic therefore tilts strategic before IPO. Intel’s $15.3 billion 2017 agreement to acquire Mobileye shows that strategic buyers will pay for category-leading computer-vision assets, but OrCam’s present public scale does not justify treating that precedent as a base case. If OrCam exits well from here, the more credible path is a strategic transaction or structured financing linked to specific product assets, not a near-term standalone IPO.[CV013, CV014, CV015, CV016, CV021, CV022]

Thesis-break and kill triggers table
TriggerThresholdTransmission to thesisAction implication
New financing validates deep resetFresh priced round or structured rescue far below unicorn markConfirms legacy price story is brokenRebuild valuation from reset terms, not historic labels
Revenue does not stabilizeNo evidence of recovery from ~$16M 2024 level or further declineBull and base cases lose supportShift weighting toward bear / asset-sale outcomes
Mainstream AI replaces core workflowUser tasks become credibly replicable on cheaper platform toolsDedicated-device moat compressesCut revenue multiple and strategic-premium assumptions
Funded channel erosionVeterans or similar funded-access routes weakenCustomer-acquisition economics worsenRaise discount and lower base-case probabilities
Further workforce shrink or support degradationAnother major reduction or visible service declineInstalled-base trust and product upkeep weakenTreat as product-quality and commercialization warning
Transparent round near or above $1BIndependent demand supports premium price with clean termsPublic mark conflict narrows materiallyRe-open premium-case underwriting only with revenue proof

Triggers are designed to be monitorable and valuation-relevant.

[CV017, CV018, CV020, CV036, CV037, CV038]

8.5 Final diligence asks and thesis-break triggers

The missing evidence is unusually specific. First, what is the current price? Not a vendor estimate, not a stale 2018 round, and not a press estimate of distress—actual signed current terms. Second, what revenue should investors underwrite: the 2024 trough, a stabilized 2025 run-rate, or a split-company forward plan that changes the revenue base entirely? Third, what sits above common equity in a rescue scenario: anti-dilution demands, loans, convertible instruments, liquidation preferences, or product-level sale rights? These are not cleanup questions. They determine whether a seemingly attractive reset is actually investable. The cleanest thesis-break triggers are equally concrete: a financing that validates a deep value reset, another sharp workforce reduction, further evidence that mainstream AI fully replaces core low-vision workflows, or loss of funded access channels that currently support demand. The positive triggers are just as clear: a transparently priced new round, evidence that revenue has stabilized, proof that Hear can scale without burning excessive capital, and a cleaner cap structure. Until then, OrCam belongs in the watchlist / special-situations bucket, not in the standard growth-equity bucket.[CV024, CV028, CV029, CV030, CV032, CV036]

Final diligence asks table
TopicMissing evidenceWhy it mattersOwner / diligence path
Current cap tableLatest priced round, conversion terms, liquidation stack, anti-dilution rightsValuation cannot be trusted without understanding who sits ahead of common equityManagement + counsel data room
Current revenue bridge2024 actuals, 2025 run-rate, split-company pro forma, product mixScenario weighting changes dramatically depending on which revenue base is realCFO package + board materials
Gross margin and support burdenMargin by device line, warranty costs, training/support expenseDedicated hardware can look attractive on revenue but weak on contribution marginFinance + operations review
Hear tractionPipeline, paid conversions, retention, and sales efficiency for hearing productBull case depends on Hear becoming more than a concept offset to vision declineProduct + sales diligence
Strategic interestAny live buyer, partner, or structured-financing process by asset lineStrategic optionality could justify value above pure public-comp mathBoard / banker discussions
Governance and recovery planBoard-approved operating plan and investor alignment after 2025 disputeExecution risk remains high if governance is still misalignedBoard minutes + financing documents

These asks are ordered by value to the investment decision, not by ease of collection.

[CV024, CV029, CV030, CV032, CV039, CV040]

Disclaimer

This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.

Evidence index

Claims
IDStatementConfidenceSources
CO001 OrCam was founded in 2010 by Amnon Shashua and Ziv Aviram. Medium SO002, SO016, SO017
CO002 Current market-data sources place OrCam Technologies in Jerusalem, Israel, while official pages position it as a global assistive-technology company. Medium SO001, SO013, SO014
CO003 Official OrCam materials describe the company as an assistive-technology provider for people with low vision, blindness, and reading or learning challenges. Medium SO001, SO003
CO004 The current public OrCam lineup includes MyEye 3 Pro, MyEye 2 Pro, Read 5, Read 3, Read, and Learn products. Medium SO003, SO009
CO005 MyEye 3 Pro is marketed as a wearable device that reads text, recognizes faces, identifies products and money notes, and describes surroundings. Medium SO004, SO012
CO006 Read 3 is positioned as a three-in-one product: handheld reading companion, smart magnifier with AI assistant, and stand-based stationary reader. Medium SO006, SO007
CO007 The OrCam mobile app controls device settings, changes voices, connects devices to Wi-Fi, helps locate devices, and routes support requests. Medium SO010, SO011
CO008 The OrCam home page says the company’s technology is used across 50 countries and 25 languages by tens of thousands of users every day. Medium SO003
CO009 OrCam’s about-us page says its AI solutions have transformed daily life for tens of thousands of people worldwide. Medium SO001
CO010 The official leadership page still lists Amnon Shashua as co-founder and chairman and Ziv Aviram as co-founder and director. Medium SO002
CO011 The official leadership page lists Elad Serfaty as CEO, Shmuel Turgeman as CFO, and Tzahi Israel as senior vice president of sales. Medium SO002
CO012 Caplight lists additional current operating roles including Tal Rosenwein as CEO - Hear and Inbal Levy-March in operations. Low SO014
CO013 OrCam’s research and manual pages indicate active technical support and product documentation, including MyEye software version 9.4. Medium SO008, SO023
CO014 Tracxn reports that OrCam raised a $15 million Series A round on March 27, 2014 with Intel Capital as lead investor. Low SO013
CO015 Tracxn reports a further $41 million funding round dated April 2, 2017. Low SO013
CO016 Globes, The Times of Israel, and Tracxn all support that OrCam raised $30.4 million in February 2018 at a $1 billion pre-money valuation led by Clal and Meitav. Medium SO013, SO016, SO017
CO017 Tracxn says OrCam has raised $86.4 million across three disclosed funding rounds. Low SO013
CO018 Caplight reports total funding raised of $98.9 million and labels the latest round as convertible debt dated July 1, 2024. Low SO014
CO019 Seedtable describes OrCam as having four funding rounds and shows a last funding date of February 19, 2018, which does not fully align with Caplight’s later-financing entry. Low SO014, SO015
CO020 Tracxn preserves a latest valuation of $1 billion as of the February 2018 round, while Caplight estimates a current private valuation around $1.03 billion. Low SO013, SO014
CO021 FDA.report lists ORCAM INC at 1115 Broadway, New York as a 2026 FDA registrant and initial importer. Low SO021
CO022 Distributor and partner pages show OrCam using third-party sales and service channels in addition to direct company marketing. Medium SO012, SO024
CO023 Current public pricing signals place MyEye 3 Pro at $4,250 through a distributor and Read 3 starting from $2,790 on an official OrCam page. Medium SO007, SO012
CO024 Veterans-focused sources say some legally blind or low-vision veterans with VA coverage may qualify for a fully funded OrCam device. Medium SO024, SO025
CO025 OrCam Learn for Schools targets educators and students with AI-assisted reading, comprehension feedback, and analytics on progress. Medium SO026
CO026 OrCam Hear is a separate hearing-focused product that uses AI-based voice isolation, earbuds, a dongle, and an app to amplify chosen speakers in noisy settings. Medium SO022
CO027 Calcalist reported in July 2024 that OrCam closed its glasses-development activity for the visually impaired and shifted focus to Hear because image-processing language models had made further low-vision development unnecessary. Medium SO019
CO028 The same Calcalist article said OrCam conducted three layoff rounds in 2024, including 100 workers in June and 50 three months earlier, leaving only several dozen employees after the latest cuts. Medium SO019
CO029 Calcalist said OrCam had once approached a $100 million revenue rate and profitability while planning a 2021 IPO at a valuation above $2.5 billion, but those plans stalled. Medium SO019, SO020
CO030 Globes reported in March 2025 that OrCam’s recovery plan involved a $12.5 million financing round backed in part by the founders, a split between vision and hearing activities, and a need to raise additional capital. Medium SO018
CO031 Globes reported that OrCam’s revenue fell from roughly $45-50 million in 2023 to $16 million in 2024. Medium SO018
CO032 Globes reported that internal estimates had pushed OrCam’s valuation down by more than 90% to about $150 million and said the company had less than 100 employees in March 2025. Medium SO018
CO033 Tracxn and Caplight list OrCam’s employee count at 171-172 in mid-2026, materially above the sub-100 headcount implied by 2024-2025 distress reporting. Low SO013, SO014
CO034 Caplight’s 2026 estimated valuation of $1.03 billion conflicts with Globes’ 2025 distressed estimate of about $150 million. Low SO014, SO018
CO035 Official product pages distinguish offline core reading features from newer AI-assistant or Smart Magnifier workflows that use broader information sources and connected software. Medium SO004, SO005, SO006, SO010
CO036 The public portfolio now spans wearable vision, handheld reading, education, and hearing products rather than a single blind-reading device. Medium SO001, SO003, SO022, SO026
CO037 The Blinded Veterans Association sponsor page says OrCam began in 2015 with the original MyEye and had evolved by 2024 to MyEye 3 Pro and related devices. Low SO024
CO038 Seedtable lists 76 patents, while OrCam’s research page emphasizes research-backed product development and scientific review. Low SO008, SO015
CO039 Current company-authored public materials do not disclose exact current revenue, ARR, gross margin, or a board-level capital-structure summary. High SO001, SO002, SO003, SO008
CO040 Current public governance visibility is partial because OrCam surfaces founders and executives but not a full board or committee structure. Medium SO001, SO002
CO041 The App Store listing shows the OrCam app at version 1.1 dated May 12, 2024, indicating at least one recent software release checkpoint. Medium SO010
CO042 OrCam’s current public materials say device interfaces support more than 20 languages, while Smart Magnifier features on current flagship products claim support for about 140 languages. Medium SO004, SO006, SO007
CM001 WHO says at least 2.2 billion people globally have a near or distance vision impairment. Medium SM001
CM002 WHO says vision impairment imposes an annual global productivity burden estimated at US$411 billion. Medium SM001
CM003 WHO says most people with vision impairment and blindness are over age 50. Medium SM001
CM004 WHO says more than 2.5 billion people need one or more assistive products today and that need could rise to 3.5 billion by 2050. Medium SM002
CM005 WHO defines assistive technology broadly to include physical products such as white canes and hearing aids as well as digital tools such as speech recognition and captioning. Medium SM002
CM006 WHO says many adoption barriers persist for assistive technology, including low awareness, high costs, limited access, procurement challenges, workforce gaps, and inadequate policy. Medium SM002
CM007 NEI and CDC both point to formal U.S. vision-loss surveillance infrastructure such as VEHSS, underscoring that blindness and low vision are tracked as real public-health issues rather than niche anecdotes. Medium SM004, SM005
CM008 The Business Research Company estimates the global low-vision assistive-devices market at $1.34 billion in 2026, growing to $1.89 billion by 2030 at about 8.9% CAGR. Low SM006
CM009 Research and Markets presents the same low-vision assistive-devices values of roughly $1.34 billion in 2026 and $1.89 billion by 2030. Low SM007
CM010 Public low-vision market reports explicitly include magnifiers, reading devices, wearable devices, screen readers, and related assistive tools inside the commercial category. Medium SM006, SM007
CM011 The same commercial market reports segment low-vision demand across personal use, healthcare, and education, and across children, adults, and elderly users. Medium SM006, SM007
CM012 TBRC estimates the broader AI-in-medical-devices market at $16.16 billion in 2026 and $42.43 billion by 2030. Low SM009
CM013 Grand View Research estimates the broader AI-enabled medical-devices market at $13.67 billion in 2024 and $255.76 billion by 2033. Low SM008
CM014 OrCam’s direct market is much narrower than the full AI-medical-device category because OrCam primarily monetizes assistive vision and reading hardware rather than hospital AI infrastructure. Medium SM006, SM008, SM009, SM024, SM025
CM015 OrCam’s current public portfolio spans low-vision, reading and learning, and hearing products, placing the company inside a broader assistive-technology envelope than just one wearable niche. Medium SM010, SM011
CM016 WHO says assistive technology can improve inclusion and participation in education, employment, and everyday life. Medium SM002, SM003
CM017 The National Federation of the Blind says its free white cane program has distributed more than 64,000 white canes since 2008 and frames the cane as a core independence tool. Medium SM022
CM018 APH ConnectCenter presents orientation-and-mobility training, non-visual cues, and cane-based travel skills as a practical independence pathway for blind and low-vision people. Medium SM023
CM019 Aira Explorer offers 24/7 professional visual interpreters, free AI image descriptions, access locations, and paid subscription plans. Medium SM016
CM020 Be My Eyes says its free app serves users across 150 countries and 180 languages and has over 750,000 users and more than 8 million volunteers. Medium SM017
CM021 Microsoft says Seeing AI is a free mobile app that can read documents, identify products, describe scenes, recognize people and currency, detect colors, and chat about scanned documents. Medium SM018
CM022 Apple’s accessibility updates expand Magnifier and Accessibility Reader and use on-device intelligence to improve low-vision reading and exploration inside the Apple ecosystem. Medium SM019, SM020
CM023 Envision Glasses offer many OrCam-like capabilities including instant text, scan text, handwriting, scene description, cash recognition, color detection, object finding, and people recognition. Medium SM021
CM024 The combination of free mobile accessibility apps, volunteer assistance, and competing smart glasses reduces willingness to pay for premium dedicated hardware in some use cases. Medium SM016, SM017, SM018, SM020, SM021
CM025 OrCam’s public materials imply multiple buyer paths: direct consumer, school procurement, veterans benefits, and partner or distributor channels. Medium SM011, SM012, SM013, SM014, SM015
CM026 OrCam Learn for Schools positions teachers and schools as economically important buyers because it emphasizes progress tracking, comprehension support, and reduced assessment burden. Medium SM012
CM027 Veterans-related sources show that public-benefit pathways can act as payer channels for OrCam devices in at least some U.S. cohorts. Medium SM013, SM014
CM028 Public low-vision market reports and OrCam’s reseller evidence both support a distribution mix that includes online or specialty channels rather than only institutional procurement. Medium SM006, SM015
CM029 TBRC says North America was the largest region in the low-vision assistive-devices market in 2025. Low SM006
CM030 Low-vision market growth is supported by ageing populations, rising visual-impairment prevalence, and diabetes-related vision loss. Medium SM001, SM006
CM031 TBRC highlights increasing demand for wearable low-vision devices and AI-powered assistive products as forecast-period growth drivers. Low SM006
CM032 WHO’s barrier list implies that large need bases do not automatically convert into paid device adoption because awareness, workforce, policy, and procurement gaps can still block access. Medium SM002, SM003
CM033 The global prevalence of vision impairment and assistive-tech need is much larger than the revenue market for low-vision devices, so any OrCam SAM must be a filtered subset of funded and reachable users. Medium SM001, SM002, SM006, SM007
CM034 A defensible OrCam market model must use the low-vision assistive-devices category as its direct commercial core rather than the entire global visually impaired population. Medium SM001, SM006, SM007
CM035 Research and Markets segments the low-vision market by product type, application, distribution channel, and end user, reinforcing that multiple lenses are needed instead of one headline TAM. Low SM007
CM036 AI-enabled medical-device market estimates are useful as technology adjacency but are too broad to function as OrCam’s direct TAM because they include hospital, diagnostic, and software domains far beyond assistive reading hardware. Medium SM008, SM009
CM037 The practical buyer journey often runs from end-user need to advocate or institution to funding path to training, rather than from awareness straight to a one-step hardware purchase. Medium SM012, SM013, SM014, SM015, SM023
CM038 Aira’s mix of free access offers, access locations, and personal subscription plans shows that ongoing-service models compete differently from OrCam’s upfront hardware model. Medium SM016
CM039 Apple says Magnifier and VoiceOver should not be relied upon for navigation, high-risk situations, or the diagnosis or treatment of medical conditions. Medium SM019, SM020
CM040 Taken together, Microsoft, Be My Eyes, Aira, Apple, and Envision show that accessibility substitutes are improving both at the low-cost smartphone layer and at the competing dedicated-device layer. Medium SM016, SM017, SM018, SM019, SM020, SM021
CM041 WHO’s global assistive-technology report explicitly frames assistive access as supporting inclusion, universal health coverage, and return on investment for governments and civil society. Medium SM003
CM042 OrCam’s expansion into learning and hearing adjacencies suggests the company is trying to participate in the broader assistive-technology spend pool, even though the core monetization question still centers on low-vision device adoption. Medium SM010, SM011, SM012
CP001 OrCam’s competitive set spans direct dedicated devices, service substitutes, platform substitutes, and status-quo mobility supports rather than only other smart-glasses vendors. Medium SP001, SP007, SP011, SP020, SP022, SP023
CP002 Direct dedicated-device peers visible in retained sources include Envision, eSight, IrisVision, and HumanWare. Medium SP009, SP016, SP018, SP019
CP003 Aira, Be My Eyes, Seeing AI, Apple accessibility features, white canes, and orientation-and-mobility training all function as substitutes or complements for parts of OrCam’s job to be done. Medium SP007, SP011, SP013, SP020, SP022, SP023
CP004 OrCam competes for daily reading, recognition, and scene-understanding tasks, not just for ownership of one wearable form factor. Medium SP001, SP002, SP011, SP013
CP005 Status-quo mobility tools remain economically relevant because white canes and O&M training deliver independence without premium-device pricing. Medium SP022, SP023
CP006 Multi-homing is plausible because users can combine dedicated hardware, apps, volunteer services, and cane-based mobility rather than choosing one exclusive stack. Medium SP007, SP011, SP013, SP022, SP023
CP007 OrCam is still primarily a dedicated-device vendor because its current flagship differentiation rests on MyEye and Read hardware rather than on a pure software platform. Medium SP001, SP002, SP024
CP008 The strategic battle for OrCam is increasingly against substitutes with broad installed-base reach, not only against one more specialized smart-glasses company. Medium SP011, SP013, SP020, SP021
CP009 Envision Glasses provide instant text, scan text, handwriting, scene description, object finding, face recognition, cash recognition, color detection, and companion calling. Medium SP009
CP010 Envision Home Edition uses Google Glass Enterprise Edition 2 hardware with an 8MP camera, 3GB RAM, 32GB storage, Bluetooth 5.x, and a body weight around 46 grams. Medium SP010
CP011 OrCam MyEye 3 Pro is publicly listed at $4,250, while OrCam Read 3 is publicly listed from $2,790. Medium SP003, SP004
CP012 eSight Go targets users with significant central vision loss and emphasizes magnification, image stabilization, smart autofocus, and a 45-degree field of view. Medium SP016, SP017
CP013 IrisVision Vista emphasizes augmented-reality-style low-vision enhancement, focus customization, up to 10× magnification, and one-on-one coaching rather than narrated OCR breadth alone. Medium SP018
CP014 HumanWare’s smart-reader category focuses on reading printed text aloud and describing images for blind or low-vision users. Medium SP019
CP015 OrCam’s main direct-device advantage versus eSight and IrisVision is breadth across OCR, object recognition, reading, and AI-assistant tasks rather than only magnified residual-vision enhancement. Medium SP001, SP002, SP016, SP017, SP018
CP016 eSight and IrisVision appear more specialized than OrCam for central-vision or residual-vision enhancement cohorts. Medium SP016, SP017, SP018
CP017 HumanWare is closer to OrCam Read in the reading-device job than to OrCam MyEye’s broader recognition-and-wearable proposition. Medium SP002, SP019
CP018 Envision overlaps most directly with OrCam MyEye because both combine hands-free text access and everyday recognition features in a wearable form factor. Medium SP001, SP009, SP010
CP019 Aira combines professional visual interpreters, free access locations, AI image descriptions, and personal subscriptions that start at $26 per month and scale far higher with minutes. Medium SP007, SP008
CP020 Be My Eyes provides a free app with volunteer assistance, Be My AI, a service directory, and reported scale of over 750,000 users and more than 8 million volunteers across 150 countries and 180 languages. Medium SP011, SP012, SP025
CP021 Seeing AI is a free Microsoft app that narrates the world and supports reading, product identification, scene description, people, currency, colors, handwriting, and document chat. Medium SP013, SP014
CP022 Apple is expanding built-in Magnifier and Accessibility Reader with Apple Intelligence-linked capabilities, increasing the quality of low-vision tools on mainstream devices users may already own. Medium SP020, SP021
CP023 Microsoft’s Seeing AI manual says the app is a class I medical device under EU MDR but also warns that it is not intended to be a primary or exclusive environmental-awareness technology and should not be used where harm could result. Medium SP015
CP024 Free or bundled alternatives such as Be My Eyes, Seeing AI, and Apple accessibility compress the price umbrella under which OrCam must sell premium hardware. Medium SP011, SP013, SP020, SP021
CP025 Aira is not a zero-price substitute, but it converts the accessibility problem from hardware capex into service opex and allows users to pay only for interpreting capacity. Medium SP008
CP026 Be My AI was introduced by Be My Eyes as a GPT-4-powered digital visual assistant that remains free to blind and low-vision users. Medium SP012
CP027 Platform substitutes are especially dangerous because they distribute through devices people already own instead of asking for a separate hardware purchase and learning curve. Medium SP013, SP020, SP021
CP028 OrCam’s defended channels include specialist distributors and publicly visible veterans pathways, which can offset some consumer-platform distribution disadvantages. Medium SP003, SP004
CP029 eSight also markets veteran coverage and coaching, showing that funded-access and support are not differentiators OrCam can assume it owns exclusively. Medium SP017
CP030 Dedicated-device competition is increasingly about form factor and vision-condition fit rather than about who can claim OCR or AI assistance in the abstract. Medium SP001, SP009, SP016, SP018, SP019
CP031 OrCam’s moat is strongest when buyers value a self-contained trained device with assistive-specific ergonomics, but weakest when good-enough phone apps can handle the task. Medium SP001, SP002, SP011, SP013, SP020
CP032 Switching costs in this market are real but not absolute because habits, accessories, and training matter, yet users can still multi-home across devices and apps. Medium SP001, SP007, SP011, SP023
CP033 Distribution power differs sharply by class: Apple and Microsoft ride default platforms, app substitutes ride app stores and network effects, while OrCam and other device specialists rely more on demos, referrals, and specialty sales. Medium SP003, SP008, SP011, SP013, SP020
CP034 OrCam’s strongest direct dedicated-device overlap is with Envision in hands-free wearable tasks, while its strongest substitute pressure comes from Seeing AI, Be My Eyes, and Apple. Medium SP009, SP011, SP013, SP020
CP035 The competitive field is narrowing OrCam’s differentiation from both ends: specialist visual headsets attack narrow high-value cohorts while platform apps erode broad low-end tasks. Medium SP016, SP017, SP018, SP020, SP021
CP036 Public sources do not provide clean competitor share, churn, or realized pricing data, so the moat assessment must rely on product architecture, distribution, and price-position evidence rather than on measured share. Low SP003, SP008, SP010, SP017
CI001 Public evidence supports a hardware-first revenue model centered on MyEye and Read devices. Medium SI001, SI002, SI003, SI024
CI002 OrCam MyEye 3 Pro is publicly listed at $4,250 and OrCam Read 3 starts at $2,790, indicating premium hardware price points. High SI001, SI002
CI003 OrCam publicly sells through both its own product surfaces and partner/distributor channels. High SI005, SI006, SI023
CI004 OrCam Learn is positioned as a school-facing product with educator analytics and student progress tracking, implying institutional rather than purely consumer monetization. Medium SI007
CI005 The free OrCam mobile app appears to support device setup, settings, support contact, and retention rather than operate as a separately priced software product. High SI011, SI012
CI006 Caplight classifies OrCam’s customer profile as hardware sales, subscription SaaS, and services & consulting, but official evidence most clearly supports hardware sales and leaves the rest only partially verified. Medium SI016, SI003, SI011
CI007 Calcalist reported that OrCam Hear was entering the marketing and sales phase in 2024, making it an emerging but not yet well-disclosed contributor to revenue. Medium SI004, SI015
CI008 Official FAQ and release-note surfaces show active product support infrastructure around the installed base. Medium SI008, SI021
CI009 The buy-now surface and distributor page indicate OrCam mixes direct selling with assisted channel selling. High SI005, SI006
CI010 OrCam promotes veteran eligibility for fully covered devices through VA-linked pathways, introducing a payer-funded route distinct from self-pay. Medium SI009, SI010
CI011 The Blinded Veterans Association sponsor page says qualifying veterans with VA health care may receive a fully covered OrCam device. Medium SI010
CI012 OrCam Learn’s school-oriented messaging implies budget ownership may sit with schools or special-education programs rather than with the end user alone. Medium SI007
CI013 Public pricing evidence is list pricing only; realized net price after channel discounts, institutional contracting, or payer funding remains undisclosed. High SI001, SI002, SI005, SI010
CI014 The free mobile app implies ongoing service obligations such as setup assistance, settings management, and support contact after device sale. High SI011, SI012
CI015 Institutional and funded channels likely reduce out-of-pocket friction for some buyers but also imply longer qualification and sales cycles. Medium SI007, SI009, SI010
CI016 Because OrCam sells dedicated hardware, its cost structure likely includes hardware BOM, manufacturing or assembly, logistics, and quality-control burdens that pure software substitutes avoid. Medium SI003, SI024, SI013
CI017 Support surfaces such as apps, FAQ, and release notes imply continuing service and maintenance cost beyond the initial sale. Medium SI008, SI011, SI012, SI021
CI018 Gross margin, realized ASP, CAC, payback, and warranty cost are not publicly disclosed in retained sources. Low SI001, SI002, SI011, SI016
CI019 List price should not be equated with gross profit in OrCam’s hardware business because partner discounts, support burden, and inventory risk are unknown. High SI001, SI002, SI005, SI011
CI020 Hardware transitions and reduced low-vision development raise the risk of inventory obsolescence or reserve pressure, but no public reserve data is available. Medium SI015, SI021
CI021 The public record is insufficient to underwrite efficient growth because most core unit-economics metrics remain unavailable. Medium SI016, SI017, SI018
CI022 The economics of low-vision hardware appear to be under pressure from smartphone-based generative AI substitutes, according to adverse reporting. Medium SI015
CI023 Tracxn reports OrCam has raised $86.4 million across three funding rounds. Medium SI017
CI024 Caplight reports total funding raised of $98.9 million and shows a July 1, 2024 convertible-debt last round. Medium SI016
CI025 Seedtable shows four funding rounds and a last funding date of 19 February 2018, adding further public inconsistency to the funding chronology. Medium SI018
CI026 Globes reported that OrCam’s revenue fell from roughly $45-50 million in 2023 to about $16 million in 2024. Medium SI014
CI027 Globes reported that founders and allies initiated a $12.5 million financing round for OrCam, of which about $7 million came from Amnon Shashua and a few million more from Ziv Aviram. Medium SI014
CI028 Globes reported that OrCam still needed an additional $12-15 million to rehabilitate the company beyond the founder-backed financing effort. Medium SI014
CI029 Globes reported that a proposed $2 million loan would keep OrCam afloat for only a month or two, implying very thin runway at that point. Medium SI014
CI030 Globes estimated OrCam’s valuation had fallen by more than 90% to about $150 million, versus Caplight’s still-visible $1.03 billion estimate. Low SI014, SI016
CI031 Calcalist reported three rounds of layoffs in 2024 and a shift away from low-vision-product development toward Hear. Medium SI015
CI032 Calcalist reported that OrCam once approached a $100 million revenue rate and profitability ahead of a planned 2021 IPO, but that historical operating state no longer describes the current business. Medium SI015
CI033 Even the latest financing event is not settled publicly: Caplight shows a 2024 convertible-debt round, while Seedtable does not surface a post-2018 financing date and Globes describes a rescue process that was still blocked in 2025. Low SI014, SI016, SI018
CI034 FDA.report lists an ORCAM INC registration with expiration year 2026, supporting the existence of an operating commercial footprint but not financial health. Medium SI013
CI035 The exact metrics required to underwrite recovery include cash on hand, burn, realized ASP, gross margin, units sold, channel mix, and inventory exposure. Medium SI014, SI015, SI016, SI018
CI036 Public information alone is insufficient to underwrite OrCam’s current financial profile in 2026 with confidence. Medium SI018, SI021, SI014, SI015
CI037 OrCam actively markets hands-on demos for OrCam Learn, implying a consultative school-sales funnel rather than a self-serve education checkout. Medium SI007, SI027
CI038 OrCam’s veteran customer-story content reinforces that funded or association-linked pathways can convert into real product delivery, but it does not disclose unit economics or volume. Medium SI010, SI026
CE001 OrCam’s public product family spans MyEye, Read / Read 3, Learn, Hear, and companion apps. High SE003, SE004, SE006, SE019, SE014
CE002 MyEye is positioned for blind or visually impaired users who need reading, recognition, and scene-description support in daily life. High SE003, SE023
CE003 Read and Read 3 are positioned as handheld reading devices that can read printed or digital text aloud and support magnification-related workflows. High SE004, SE005, SE024
CE004 Learn is presented as a school-focused tool for reading support, comprehension, and teacher analytics. Medium SE006, SE007, SE012
CE005 Hear is positioned as a hearing-in-noise product rather than a vision product, targeting selective listening in multiparty environments. High SE019, SE008, SE009
CE006 OrCam is attempting to productize multiple assistive workflows rather than rely on a single device or user problem. Medium SE020, SE021, SE019
CE007 The common workflow pattern across products is capture, AI interpretation, and audio guidance with minimal screen dependence. Medium SE001, SE004, SE019
CE008 Read 3 publicly discloses a 13MP camera, BLE and Wi-Fi connectivity, a 700 mAh battery, and both handheld and stationary-reader modes. Medium SE004
CE009 Read emphasizes full-page capture, offline reading, Smart Reading, and Smart Magnifier features. Medium SE004, SE005
CE010 The MyEye manual and product pages show interaction via gestures, voice commands, touch controls, and audio output for reading and recognition tasks. High SE001, SE003
CE011 MyEye’s public manual covers reading, face recognition, product identification, banknotes, colors, settings, and personalization. Medium SE001
CE012 Hear’s public architecture consists of TWS earbuds, a smartphone-connected dongle, and an iPhone app that manages selective voice amplification. High SE019, SE008, SE009
CE013 Engadget’s hands-on described Hear as creating speaker profiles and isolating selected voices, albeit with some delay and distortion in preview form. Medium SE009
CE014 The Hear App is publicly listed as a free iPhone app requiring iOS 16 and showing a large 401.1 MB package size. High SE008, SE019
CE015 Public sources do not fully disclose how inference is split between on-device, phone, and cloud computation across the product family. Low SE003, SE004, SE019
CE016 Deployment appears simplified through manuals, free apps, and audio-first interaction rather than through visually complex software interfaces. Medium SE001, SE014, SE015
CE017 The OrCam app supports volume, reading speed, reading voice, Wi-Fi connection, device finding, and support contact across devices. High SE014, SE015
CE018 Read 3’s stationary-reader mode and Learn’s school workflow indicate that deployment includes both personal and semi-structured institutional use cases. Medium SE004, SE006, SE007
CE019 Public support surfaces include FAQ, release notes, manuals, and app-store distributions. High SE001, SE013, SE018, SE014
CE020 The readable release-notes extract confirms continued updates but provides limited structured detail for outside audit of release cadence. Medium SE013
CE021 External CES coverage shows Hear generated credible reviewer interest, but that evidence reflects preview-stage product attention more than scaled commercial maturity. Medium SE009, SE010, SE011
CE022 Forbes described Hear, MyEye, Read 3, and Learn together at CES 2024, supporting the view that OrCam was still advancing a multi-product assistive roadmap at that time. Medium SE011
CE023 Calcalist’s 2024 report that OrCam was halting further low-vision development in favor of Hear conflicts with the continued public marketing of MyEye and Read surfaces. Low SE022, SE003, SE004
CE024 OrCam’s public differentiation is strongest in packaging assistive AI into constrained workflows and ergonomic hardware rather than in disclosing unique model IP. Medium SE001, SE004, SE019, SE011
CE025 Read’s offline reading and MyEye’s non-screen-centric interaction are examples of workflow packaging that mainstream apps do not automatically replicate. Medium SE005, SE001, SE003
CE026 Learn’s teacher analytics and guided reading workflow indicate a product design aimed at institutional reading support, not just generic text-to-speech. Medium SE006, SE012
CE027 Hear’s speaker-selection UI and dongle-plus-earbuds stack address a specific hearing-in-noise problem rather than generic audio playback. Medium SE019, SE009, SE011
CE028 External review and media coverage suggest OrCam can still produce technically legible demos that stand out in assistive-tech contexts. Medium SE009, SE010, SE011
CE029 Mainstream AI platforms threaten the underlying capability layer of OCR, summarization, description, and even selective assistance, reducing OrCam’s moat if packaging ceases to outperform. Medium SE017, SE022, SE011
CE030 OrCam provides public manuals, FAQ, release notes, and apps that support onboarding and device use. High SE001, SE013, SE018, SE014
CE031 FDA.report lists an ORCAM INC registration footprint, which supports commercial operating presence but does not establish device-specific safety or quality-system detail. Medium SE016
CE032 App-store surfaces disclose basic usage-data and diagnostics handling for OrCam apps, but they are not substitutes for full device privacy or security documentation. Medium SE008, SE014
CE033 Compared with Microsoft’s Seeing AI manual, OrCam’s public materials are less explicit about intended purpose, contraindications, and formal regulatory framing. Medium SE017, SE001, SE018
CE034 The public record does not expose detailed security architecture, incident-response process, or device-family certification scope for OrCam’s products. Low SE013, SE014, SE016
CE035 Public support and manual evidence show user-care effort, but not enough to conclude that trust and compliance are fully resolved technical strengths. Medium SE001, SE013, SE016, SE017
CE036 Public information alone is insufficient to fully underwrite OrCam’s product and technology stack in 2026 because architecture, compliance, reliability, and supply dependencies remain under-disclosed. High SE015, SE016, SE017, SE022
CE037 Additional preview coverage from Undecided and This Week in Hearing reinforces that Hear’s selective-listening demo resonated with reviewers and practitioners, but still in controlled showcase contexts. Medium SE026, SE027, SE009
CE038 Some official OrCam product surfaces, including the legacy MyEye page and schools.learn.orcam.com, are sparse or difficult to extract publicly, reducing outside auditability of workflow and compliance details. Medium SE028, SE029
CU001 OrCam’s end-user segments include blind or low-vision individuals, students with reading differences or low vision, legally blind veterans, and newer hearing-loss users. High SU002, SU004, SU007, SU023
CU002 The end user, buyer, and payer are often different in OrCam’s business model, especially in veterans and school segments. Medium SU003, SU008, SU009, SU022
CU003 Retail and family-supported purchases are supported by store pages that emphasize financing, guarantees, and direct online ordering. Medium SU005, SU006
CU004 Veterans form a distinct funded segment in which VA-related pathways may cover devices or training. Medium SU008, SU009
CU005 Schools and educators form a distinct institutional segment for OrCam Learn rather than merely acting as passive referrers. Medium SU002, SU003, SU010, SU022
CU006 Family members and caregivers appear in the adoption loop for individual readers and students, especially in testimonial-driven use cases. Medium SU001, SU004, SU007
CU007 The public customer map extends beyond low vision into reading challenges such as dyslexia and ADHD via Learn Basic. Medium SU002, SU001
CU008 Hear creates a potential adjacent customer segment, but public customer proof for hearing users is much thinner than for vision or reading users. Medium SU023, SU024
CU009 Scotty Smiley is a named blind veteran customer-story reference who uses OrCam MyEye in daily life. Medium SU007
CU010 Ashley Mizell is a named Read 3 user and blind advocate whose testimonial describes parenting and reading use cases. Medium SU004
CU011 Moon Hall School headteacher Michelle Catterson is quoted recommending the Learn Basic solution for student independence. Medium SU002
CU012 Charisa Cheek of Cooperative Educational Services Agency #5 in Wisconsin is quoted describing Learn as a tool that helps students become more independent with less adult support. Medium SU002
CU013 Aidan Lane, identified as a student at The Thomas Hardye School, is quoted saying Learn improved his schoolwork and grades. Medium SU002
CU014 Learn testimonials also surface named student stories such as Wendy with dyslexia, supporting home-and-school use cases. Medium SU001
CU015 Read 3 testimonials include a story in which Ashley Mizell helped Ela Mae with Batten’s disease receive a device for reading support. Medium SU004
CU016 Named public customer proof is strongest at the anecdotal deployment level and weakest at aggregate penetration level. Medium SU001, SU002, SU004, SU007
CU017 Live product, testimonial, demo, and app surfaces indicate an active installed-base support motion rather than a dormant historical product archive. High SU001, SU003, SU013, SU014
CU018 The school contact page’s request for contact details for a personal demo implies a consultative sales process for education customers. Medium SU003, SU010
CU019 Read store pages offer financing plans, free shipping, a 30-day guarantee, and a one-year warranty, showing efforts to reduce purchase friction. Medium SU005, SU006
CU020 The OrCam support app’s continued presence in both the Apple App Store and Google Play supports the existence of ongoing device users and post-sale servicing needs. High SU013, SU014
CU021 Read 3 onboarding materials and device-specific get-started pages indicate post-purchase setup remains part of customer deployment. Medium SU012, SU021
CU022 No public source in the retained set provides active-device counts, shipped units, or customer totals by segment. Low SU001, SU004, SU013
CU023 OrCam’s public customer evidence supports real deployment activity but not quantified adoption at scale. Medium SU017, SU018, SU019, SU020
CU024 Public retention metrics such as NRR, GRR, renewal rate, and churn are not disclosed in retained sources. Low SU001, SU004, SU013
CU025 Testimonials from veterans, students, and blind advocates imply positive user satisfaction and continued use, but do not substitute for structured retention data. Medium SU001, SU004, SU007
CU026 App-store support surfaces and device setup pages imply that the customer relationship extends beyond the original hardware shipment. Medium SU012, SU013, SU014
CU027 Cross-sell or expansion is plausible because OrCam serves multiple workflows across MyEye, Read, Learn, apps, and Hear, but public sources do not show actual account-level expansion rates. Medium SU021, SU022, SU023, SU025
CU028 Veterans channels, blinded-veteran partnerships, and school demos imply meaningful dependence on high-touch or funded routes to market. Medium SU003, SU008, SU009, SU010
CU029 Distributor, financing, and store support for Read devices show that consumer affordability friction remains material enough to require structured purchase assistance. Medium SU005, SU006, SU019
CU030 Adverse reporting that war froze purchases from Arab countries indicates geographic and channel concentration risk in parts of OrCam’s customer base. Medium SU019, SU020
CU031 Because no public repeat-purchase or renewal data is visible, customer durability cannot be underwritten from public information alone. Medium SU022, SU024, SU025
CU032 Named customer proof is sufficiently strong to prove relevance, but insufficient to prove diversified customer economics. Medium SU001, SU002, SU004, SU007
CU033 Management would need to provide segment-level shipments, active devices, funded-versus-self-pay mix, and channel concentration to substantiate expansion and concentration claims. Medium SU019, SU020, SU013
CU034 Public evidence supports several viable customer niches, but not a transparently diversified or retention-proven customer base. Medium SU001, SU004, SU019, SU020
CU035 OrCam’s customer economics likely hinge more on channel durability and funded access than on viral self-serve adoption. Medium SU003, SU009, SU019, SU020
CR001 OrCam maintains public legal and policy surfaces including accessibility, cookies, terms of use, privacy statement, product terms, and patent pages. High SR001, SR002, SR003, SR004, SR005, SR006
CR002 OrCam’s terms say the company is not a medical organization and that the website is not designed to provide diagnosis or medical advice. Medium SR003
CR003 OrCam’s terms identify multiple legal entities across Israel, the U.S., the UK, and Germany, increasing cross-jurisdiction compliance complexity. Medium SR003
CR004 The accessibility statement references WCAG, Section 508, ADA-linked accessibility efforts, and ongoing monitoring. Medium SR001
CR005 Public materials do not clearly resolve product-by-product regulatory classification, incident governance, or formal safety scope. Low SR001, SR003, SR021, SR024
CR006 The products privacy statement hub and cookies policy show privacy governance intent, but the readable extracts do not fully expose device-level data-flow detail. Medium SR002, SR004, SR028
CR007 FDA.report provides evidence of an ORCAM INC registration footprint, but not full device-family regulatory comfort. Medium SR015
CR008 The patent page shows that OrCam has a public patent surface, but the retained extract is too thin to prove a strong, actionable IP moat by itself. Medium SR006
CR009 Calcalist reported that progress in language-model image processing made further low-vision development unnecessary, directly supporting technology-obsolescence risk. Medium SR007
CR010 Globes reported that competition from AI companies was a key factor in OrCam’s recovery plan and business crisis. Medium SR012
CR011 OpenAI’s work with Be My Eyes shows that high-quality visual assistance can be delivered through a mainstream AI platform rather than through dedicated OrCam hardware. High SR009, SR027
CR012 Apple’s accessibility stack makes core assistive features available by design on mainstream devices, increasing substitute pressure on dedicated hardware. High SR008, SR011
CR013 Google’s 2026 intelligent-eyewear plans indicate that hands-free assistive perception is moving toward large-platform ecosystems with voice AI built in. High SR010, SR026
CR014 Seeing AI remains a free app and its public safety framing is more explicit than OrCam’s, raising both pricing and trust pressure. High SR014, SR021
CR015 If OrCam’s ergonomic and funded-channel advantages do not outweigh these platform substitutes, dedicated-device pricing power is at risk. Medium SR011, SR012, SR017
CR016 Public reporting of repeated layoffs, revenue collapse, and rescue financing indicates a high capital-stress environment. Medium SR007, SR012, SR013
CR017 A smaller workforce supporting multiple hardware and software products raises meaningful product-quality and execution risk. Medium SR007, SR023, SR024
CR018 Hardware businesses facing revenue pressure are exposed to inventory, warranty, and support burdens that are difficult to absorb without stable gross profit. Medium SR012, SR025, SR030
CR019 Sparse public release-history detail makes it hard to assess update cadence, incident response, or defect remediation maturity. Medium SR023, SR018, SR019
CR020 The privacy and cookies materials show governance intent, but do not resolve how assistive data is processed across devices, phones, and apps. Medium SR002, SR004, SR028, SR020
CR021 The public record does not show structured product incident metrics, returns, or recall history, leaving residual operational risk high. Low SR023, SR024, SR030
CR022 Because OrCam serves vulnerable accessibility users, support failures or unclear outputs can create outsized reputational and trust damage even when not formally regulated as medical incidents. Medium SR003, SR021, SR024
CR023 Public evidence is insufficient to conclude that OrCam has fully matured quality, safety, and security controls across all product families. Medium SR005, SR019, SR021
CR024 Veterans pathways, blinded-veteran organizations, and school-demo flows show meaningful dependence on high-touch channels rather than purely direct adoption. Medium SR016, SR017, SR022
CR025 Hear is visibly dependent on an iPhone app and broader smartphone ecosystem support in its current public form. High SR020, SR022
CR026 Apple and Google are both platform dependencies and substitute threats, since they host support surfaces while also building accessibility or eyewear alternatives. High SR008, SR010, SR018, SR020
CR027 Rescue-capital dependency increases partner risk because financing counterparties can influence governance, dilution, and product prioritization. Medium SR012, SR013
CR028 Distributor and financing-assisted sales imply that customer affordability and reach partly depend on partners whose economics are not public. Medium SR017, SR030
CR029 School and therapist-led deployments likely face budget and procurement friction that consumer apps largely avoid. Medium SR017, SR018, SR029
CR030 War-related freezes in Arab-country purchasing indicate that regional and channel dependencies can propagate into revenue risk. Medium SR012
CR031 The top residual risks are technology substitution, capital adequacy, platform dependence, and under-disclosed compliance depth. High SR010, SR012, SR013, SR021
CR032 A failure to close credible bridge or rescue capital would be a thesis-break event for a company already showing revenue and staffing stress. Medium SR012, SR013
CR033 A mainstream-platform breakthrough that matches core OrCam workflows at much lower cost would materially impair the dedicated-device thesis. High SR009, SR010, SR011
CR034 Loss or weakening of veteran, school, or distributor routes would materially increase customer-acquisition risk. Medium SR016, SR017, SR018
CR035 Deterioration in support quality, returns, or onboarding experience would be a practical kill signal because OrCam depends on trust-heavy assistive workflows. Medium SR018, SR019, SR023
CR036 If compliance diligence cannot resolve product-level regulatory and privacy questions, unresolved trust exposure should be treated as a gating issue rather than a footnote. High SR001, SR003, SR021
CR037 The strongest visible mitigations are funded access routes, assistive ergonomics, and legal/support infrastructure—not publicly proven technical exclusivity. Medium SR001, SR017, SR024
CR038 Because the company must solve capital stress and product differentiation at the same time, adverse events can transmit quickly into valuation and financing difficulty. Medium SR007, SR012, SR013
CR039 Several top risks are monitorable through financing closes, platform launches, channel health, and support metrics rather than being purely abstract concerns. Medium SR010, SR013, SR018
CR040 OrCam is not cleanly investable from public information alone in 2026 without resolving the highest residual risk gaps. Medium SR003, SR012, SR013, SR021
CV001 Caplight lists OrCam as private with a July 1, 2024 convertible-debt round, an estimated valuation of $1.03B, and total funding raised of $98.9M. Medium SV001
CV002 Tracxn lists OrCam with a current valuation of $1B while tying its latest funding round to the February 20, 2018 Series B round of $30.4M and total funding of $86.4M. Medium SV002
CV003 Seedtable’s retained profile shows last funding in February 2018 and explicitly says ownership is modelled from one priced round rather than from a filed cap table. Medium SV003
CV004 Times of Israel reported that OrCam’s 2018 financing round raised $30.4M at a $1B pre-investment valuation. Medium SV004
CV005 Calcalist reported that OrCam raised $50M in March 2021 at a $1.5B valuation and was aiming for an IPO valuation above $2.5B. Medium SV006
CV006 Globes reported in March 2025 that OrCam’s revenue fell from roughly $45-50M in 2023 to $16M in 2024 and that fair value had fallen by more than 90% to about $150M. Medium SV005
CV007 The retained public record contains two incompatible valuation stories: a vendor-estimated unicorn and a distressed recap candidate. Medium SV001, SV002, SV003, SV005
CV008 Caplight’s figure is best interpreted as a current-looking market-data estimate rather than as proof of a clean late-stage priced equity round at $1.03B. Medium SV001, SV003
CV009 Public evidence does not clearly confirm any disclosed priced equity round above the 2018 unicorn milestone. Medium SV002, SV003, SV004
CV010 OrCam still has live product and channel proof through Read 3, Hear, and veterans-related pathways. Medium SV021, SV023, SV025, SV026
CV011 Because product, partner, and support surfaces remain live, OrCam should be treated as a real but impaired operating business rather than as a zero-value shell. Medium SV021, SV022, SV023, SV025
CV012 Layoffs, substitute pressure, and recap friction justify a heavy valuation discount to any legacy founder-halo narrative. Medium SV005, SV006
CV013 Mobileye’s August 2026 market cap of about $6.77B against roughly $1.7B of 2024 revenue implies an approximate public market-cap-to-revenue multiple of 4.0x. High SV008, SV009
CV014 Sight Sciences’ August 2026 market cap of about $0.28B against 2025 revenue of about $77.4M implies an approximate multiple of 3.6x. High SV014, SV015
CV015 Glaukos’ August 2026 market cap of about $9.83B against 2024 net sales of about $383.5M implies an approximate multiple of 25.6x. High SV010, SV011
CV016 Sonova’s August 2026 market cap of about $16.54B and 2025/26 group sales of CHF 3.606B make it a scale benchmark for mature assistive-device leadership, not a like-for-like startup comp. High SV012, SV013
CV017 If OrCam were worth $1.03B against the $16M 2024 revenue figure reported by Globes, the implied multiple would be roughly 64x. Medium SV001, SV005
CV018 If OrCam were worth $1.03B against the $45-50M 2023 revenue range reported by Globes, the implied multiple would still be roughly 21x-23x. Medium SV001, SV005
CV019 Those implied OrCam multiples sit far above mainstream public hardware or eye-tech comp levels and only approach a premium public comparator if one uses the healthier historical revenue base. Medium SV005, SV008, SV010, SV014, SV015
CV020 Therefore, a current unicorn-scale mark requires either much better undisclosed economics than the public record shows or a strategic option value that public sources have not yet substantiated. Medium SV001, SV005, SV010, SV011
CV021 Intel’s 2017 agreement to acquire Mobileye for about $15.3B proves that strategic buyers can pay very large premiums for founder-linked Israeli computer-vision platforms. Medium SV007
CV022 Mobileye’s present public scale and revenue base are far beyond OrCam’s current public scale, so the precedent is directional rather than directly comparable. High SV007, SV009
CV023 A strong strategic exit for OrCam is conceptually possible, but Mobileye-sized strategic assumptions should not be used as a base-case valuation anchor. Medium SV007, SV009, SV010, SV015
CV024 Public evidence does not support near-term IPO readiness because price, growth quality, and cap-table clarity are all unresolved. Medium SV001, SV005, SV006
CV025 The bull case requires recapitalization success, continued profitability in the vision products that still generate revenue, and genuine commercial traction for Hear. Medium SV005, SV023, SV024
CV026 The base case assumes OrCam stabilizes as a narrower but still relevant assistive-device company supported by funded channels and premium use cases. Medium SV021, SV025, SV026
CV027 The bear case assumes further workflow substitution, punitive recap terms, or asset-level restructuring that keeps OrCam closer to distress than to renewed unicorn status. Medium SV005, SV006, SV017, SV018
CV028 The best-fit recommendation from public evidence is Research-more / Track rather than buy at current implied unicorn levels. High SV001, SV005, SV006, SV015
CV029 A reset or structured entry could still be interesting, but only after current cap-table terms and revenue quality are directly diligenced. Medium SV003, SV005, SV027, SV030
CV030 Public evidence cannot support a target-return underwriting model at a $1B entry because current price and preference structure remain unresolved. Medium SV001, SV003, SV005
CV031 OrCam looks more like a good company with a price problem than a bad company with no residual value. Medium SV005, SV021, SV025
CV032 Current cap-table terms, dilution protection, rescue financing mechanics, and common-equity seniority are the main blockers to a conviction valuation call. Low SV003, SV005
CV033 A bull valuation range of roughly $0.85B-$1.30B is only defensible if OrCam re-proves growth and quality near or above the Caplight estimate. Medium SV001, SV005, SV023
CV034 A base valuation range of roughly $0.35B-$0.70B best fits a stabilized niche-device outcome that is real but materially smaller than the legacy unicorn story. Medium SV005, SV014, SV015, SV021
CV035 A bear valuation range of roughly $0.15B-$0.35B is consistent with continued distress, reset financing, or asset-sale style outcomes. Medium SV005, SV006, SV015
CV036 A fresh financing that validates a deep reset below current vendor estimates would materially weaken the legacy-unicorn thesis. Medium SV001, SV005
CV037 Another major workforce reduction or visible support deterioration would weaken confidence in the installed base and commercial durability. Medium SV006, SV022, SV024
CV038 Loss of veterans or other funded channels would reduce one of the clearest demand-support mechanisms visible in the public record. Medium SV025, SV026
CV039 Evidence that Hear is converting into real paid adoption and that revenue has stabilized would materially improve the valuation case. Medium SV023, SV024
CV040 A transparently priced new round near or above the public unicorn line would materially improve the recommendation, but only if third-party demand and terms are clean. Medium SV001, SV003
CV041 If OrCam exits well from here, a strategic transaction or structured financing tied to specific product assets is more plausible than a near-term standalone IPO. Medium SV007, SV021, SV023
CV042 OrCam’s retained legal and regulatory shell pages reduce some trust discount, but they do not solve valuation opacity. Medium SV027, SV028, SV029, SV030
CV043 Caplight’s comparable list pointing to companies such as Gentex, Envision, and EssilorLuxottica implies strategic adjacency, but not direct proof that OrCam merits their valuation frameworks. Medium SV001
CV044 The combination of live product pages, manuals, partner references, and app surfaces suggests there is still an installed base worth serving and valuing. Medium SV021, SV022, SV024, SV025
Sources
IDPublisherTitleQuote
SO001 OrCam Welcome to OrCam – Transforming Lives Through Innovative Technology
SO002 OrCam ORCAM Leadership Team | Meet the Visionaries behind ORCAM Technologies
SO003 OrCam Experience the Power of Assistive Technology with OrCam's AI Devices
SO004 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SO005 OrCam OrCam Read - The Ultimate AI Reading Device for the Visually Impaired
SO006 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SO007 OrCam OrCam Read 3 NEW | Achieve Reading Freedom
SO008 OrCam Research
SO009 OrCam OrCam - Frequently Asked Questions - All the Answers You Need
SO010 Apple App Store OrCam App - App Store
SO011 Google Play OrCam - Apps on Google Play
SO012 Get OrCam MyEye 3 Pro | Get OrCam
SO013 Tracxn Orcam Technologies
SO014 Caplight OrCam | Valuation, Funding Rounds & Stock Price | Caplight
SO015 Seedtable OrCam Technologies — Funding, Investors & Team | Seedtable
SO016 Globes Mobileye founders co OrCam valued at over $1b
SO017 The Times of Israel OrCam raises $30.4 million, bringing startup to $1 billion valuation
SO018 Globes OrCam stymied by investor dispute with Shashua
SO019 CTech / Calcalist OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SO020 CTech / Calcalist OrCam tag page
SO021 FDA.report Orcam FDA Filings - FDA.report
SO022 OrCam OrCam - Enhances Hearing in Noisy Environments
SO023 OrCam OrCam MyEye Manual And Audio Guides
SO024 Blinded Veterans Association OrCam – Blinded Veterans Association
SO025 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SO026 OrCam OrCam Learn | A Revolutionary AI-Powered Reading & Learning Companion
SM001 World Health Organization Vision impairment and blindness
SM002 World Health Organization Assistive technology
SM003 World Health Organization Global report on assistive technology
SM004 National Eye Institute Eye Health Data and Statistics
SM005 CDC Vision and Eye Health
SM006 The Business Research Company Low Vision Assistive Devices Market Size and Growth Report 2026
SM007 Research and Markets Low Vision Assistive Devices Market Report 2026
SM008 Grand View Research AI-enabled Medical Devices Market Size, Share Report, 2033
SM009 The Business Research Company AI In Medical Devices Market Trends Anaysis Report 2026-2030
SM010 OrCam Welcome to OrCam – Transforming Lives Through Innovative Technology
SM011 OrCam Experience the Power of Assistive Technology with OrCam's AI Devices
SM012 OrCam OrCam Learn | A Revolutionary AI-Powered Reading & Learning Companion
SM013 Blinded Veterans Association OrCam – Blinded Veterans Association
SM014 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SM015 Get OrCam Shop | Get OrCam
SM016 Aira Aira | Aira Explorer App
SM017 Be My Eyes Be My Eyes App
SM018 Microsoft Accessibility Blog Seeing AI App Launches on Android – Including new and updated features and new languages.
SM019 Apple Newsroom Apple unveils powerful accessibility features coming later this year
SM020 Apple Newsroom Apple unveils new accessibility features, and updates with Apple Intelligence
SM021 Envision Envision Glasses - Smart Glasses for People who are Blind or Low Vision
SM022 National Federation of the Blind Seniors Division Free White Cane Program
SM023 APH ConnectCenter Orientation and Mobility: Navigating Your Environment with Confidence
SM024 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SM025 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SP001 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SP002 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SP003 Get OrCam MyEye 3 Pro | Get OrCam
SP004 OrCam OrCam Read 3 NEW | Achieve Reading Freedom
SP005 Caplight OrCam | Valuation, Funding Rounds & Stock Price | Caplight
SP006 The Business Research Company Low Vision Assistive Devices Market Size and Growth Report 2026
SP007 Aira Aira | Aira Explorer App
SP008 Aira Aira | Personal Subscriptions
SP009 Envision Envision Glasses - Smart Glasses for People who are Blind or Low Vision
SP010 Envision Store Envision Glasses: Home Edition - AI-powered smartglasses
SP011 Be My Eyes Be My Eyes App
SP012 Be My Eyes Introducing: Be My AI
SP013 Seeing AI A Visual Assistant for the Blind
SP014 Microsoft Accessibility Blog Seeing AI App Launches on Android – Including new and updated features and new languages.
SP015 Microsoft Seeing AI User Manual Revision C 13-Mar-2024
SP016 eSight Eyewear eSight - Electronic eyewear for the visually impaired
SP017 eSight Eyewear eSight Go | eSight Eyewear
SP018 IrisVision IrisVision low Vision Aid | Irisvision
SP019 HumanWare Smart reader
SP020 Apple Newsroom Apple unveils powerful accessibility features coming later this year
SP021 Apple Newsroom Apple unveils new accessibility features, and updates with Apple Intelligence
SP022 National Federation of the Blind Seniors Division Free White Cane Program
SP023 APH ConnectCenter Orientation and Mobility: Navigating Your Environment with Confidence
SP024 OrCam OrCam App - App Store
SP025 Be My Eyes Accessibility Technology for blind & low vision people - Be My Eyes
SI001 Get OrCam MyEye 3 Pro | Get OrCam
SI002 OrCam OrCam Read 3 NEW | Achieve Reading Freedom
SI003 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SI004 OrCam OrCam - Enhances Hearing in Noisy Environments
SI005 Get OrCam Shop | Get OrCam
SI006 OrCam Distributor
SI007 OrCam OrCam Learn | A Revolutionary AI-Powered Reading & Learning Companion
SI008 OrCam OrCam - Frequently Asked Questions - All the Answers You Need
SI009 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SI010 Blinded Veterans Association OrCam – Blinded Veterans Association
SI011 Apple App Store OrCam App - App Store
SI012 Google Play OrCam - Apps on Google Play
SI013 FDA.report Orcam FDA Filings - FDA.report
SI014 Globes OrCam stymied by investor dispute with Shashua
SI015 Calcalist Tech OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SI016 Caplight OrCam | Valuation, Funding Rounds & Stock Price | Caplight
SI017 Tracxn Orcam Technologies
SI018 Seedtable OrCam Technologies — Funding, Investors & Team | Seedtable
SI019 Times of Israel via Wayback OrCam raises $30.4 million, bringing startup to $1 billion valuation
SI020 Globes Mobileye founders co OrCam valued at over $1b
SI021 OrCam OrCam Release Notes
SI022 OrCam Welcome to OrCam – Transforming Lives Through Innovative Technology
SI023 OrCam Experience the Power of Assistive Technology with OrCam's AI Devices
SI024 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SI025 Amit Systems / Get OrCam Read 3 | Get OrCam
SI026 OrCam Blind Veteran Says OrCam MyEye Has Been ‘Life-Changing’ - OrCam
SI027 OrCam OrCam Learn for Schools - Exclusive Hands-on Demo
SE001 OrCam OrCam MyEye Manual And Audio Guides
SE002 OrCam Research
SE003 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SE004 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SE005 OrCam OrCam Read - The Ultimate AI Reading Device for the Visually Impaired
SE006 OrCam OrCam Learn | A Revolutionary AI-Powered Reading & Learning Companion
SE007 OrCam OrCam Learn for Schools - Exclusive Hands-on Demo
SE008 Apple App Store OrCam Hear App App - App Store
SE009 Engadget OrCam Hear hands-on: A surprisingly effective voice isolation platform for people with hearing loss
SE010 Reviewed The Reviewed Awards: CES 2024—The best of what’s to come
SE011 Forbes AR Helping The Handicapped To See And Hear At CES 2024
SE012 OrCam OrCam Academy
SE013 OrCam OrCam Release Notes
SE014 Apple App Store OrCam App - App Store
SE015 Google Play OrCam - Apps on Google Play
SE016 FDA.report Orcam FDA Filings - FDA.report
SE017 Microsoft Seeing AI User Manual Revision C 13-Mar-2024
SE018 OrCam OrCam - Frequently Asked Questions - All the Answers You Need
SE019 OrCam OrCam - Enhances Hearing in Noisy Environments
SE020 OrCam Experience the Power of Assistive Technology with OrCam's AI Devices
SE021 OrCam Welcome to OrCam – Transforming Lives Through Innovative Technology
SE022 Calcalist Tech OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SE023 Get OrCam MyEye 3 Pro | Get OrCam
SE024 Amit Systems / Get OrCam Read 3 | Get OrCam
SE025 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SE026 Undecided with Matt Ferrell 5 BEST Things I Saw in Vegas at CES 2024
SE027 Podtail / This Week in Hearing 219 - OrCam Hear: Leveraging AI Sound Source Separation to Tackle the Hearing in Noise Problem – This Week in Hearing – Podcast
SE028 OrCam OrCam MyEye
SE029 OrCam schools.learn.orcam.com
SU001 OrCam OrCam Learn Testimonials: Real User Stories & Feedback
SU002 OrCam OrCam Learn Basic | A Revolutionary AI-Powered Reading and Learning Companion
SU003 OrCam OrCam Learn for US Schools
SU004 OrCam OrCam Read 3 Testimonials: User Experiences & Reviews
SU005 OrCam OrCam Read 3: Transform Your Reading Experience Today!
SU006 OrCam OrCam Read: The Revolutionary Device for Easy Reading
SU007 OrCam Blind Veteran Says OrCam MyEye Has Been ‘Life-Changing’ - OrCam
SU008 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SU009 Blinded Veterans Association OrCam – Blinded Veterans Association
SU010 OrCam OrCam Learn for Schools - Exclusive Hands-on Demo
SU011 OrCam OrCam Read 5: Advanced Reading Aid for Visual Impairments
SU012 OrCam OrCam Read 3: Get Started with This Step-by-Step Setup Guide
SU013 Apple App Store OrCam App - App Store
SU014 Google Play OrCam - Apps on Google Play
SU015 WHO Vision impairment and blindness
SU016 CDC Vision and Eye Health
SU017 National Eye Institute Eye Health Data and Statistics
SU018 APH ConnectCenter Orientation and Mobility: Navigating Your Environment with Confidence
SU019 Globes OrCam stymied by investor dispute with Shashua
SU020 Calcalist Tech OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SU021 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SU022 OrCam OrCam Learn | A Revolutionary AI-Powered Reading & Learning Companion
SU023 OrCam OrCam - Enhances Hearing in Noisy Environments
SU024 Apple App Store OrCam Hear App App - App Store
SU025 OrCam OrCam MyEye 3 Pro - Revolutionize Your Vision with Cutting-Edge AI Technology
SR001 OrCam Website Accessibility Statement - OrCam
SR002 OrCam Cookies Policy - OrCam
SR003 OrCam terms-of-use
SR004 OrCam OrCam Products Privacy Statement
SR005 OrCam OrCam Products Privacy Terms & Conditions
SR006 OrCam OrCam Patent
SR007 Calcalist Tech OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SR008 Apple Accessibility
SR009 OpenAI Transforming visual accessibility
SR010 Google Intelligent eyewear is coming this fall
SR011 Apple Newsroom Apple unveils new accessibility features, and updates with Apple Intelligence
SR012 Globes OrCam stymied by investor dispute with Shashua
SR013 Caplight OrCam | Valuation, Funding Rounds & Stock Price | Caplight
SR014 Seeing AI A Visual Assistant for the Blind
SR015 FDA.report Orcam FDA Filings - FDA.report
SR016 Blinded Veterans Association OrCam – Blinded Veterans Association
SR017 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SR018 Apple App Store OrCam App - App Store
SR019 Google Play OrCam - Apps on Google Play
SR020 Apple App Store OrCam Hear App App - App Store
SR021 Microsoft Seeing AI User Manual Revision C 13-Mar-2024
SR022 OrCam OrCam - Enhances Hearing in Noisy Environments
SR023 OrCam OrCam Release Notes
SR024 OrCam OrCam MyEye Manual And Audio Guides
SR025 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SR026 Google Intelligent eyewear is coming this fall
SR027 OpenAI Transforming visual accessibility
SR028 OrCam OrCam Products Privacy Statement
SR029 OrCam Website Accessibility Statement - OrCam
SR030 OrCam terms-of-use
SV001 Caplight OrCam | Valuation, Funding Rounds & Stock Price | Caplight
SV002 Tracxn Orcam Technologies
SV003 Seedtable OrCam Technologies — Funding, Investors & Team | Seedtable
SV004 The Times of Israel OrCam raises $30.4 million, bringing startup to $1 billion valuation
SV005 Globes OrCam stymied by investor dispute with Shashua
SV006 Calcalist Tech OrCam closing glasses department, cutting dozens of jobs in third round of layoffs this year
SV007 Intel Intel to Acquire Mobileye
SV008 CompaniesMarketCap Mobileye (MBLY) - Market capitalization
SV009 SEC Mobileye Global Inc. Annual Report on Form 10-K for fiscal year ended December 28, 2024
SV010 CompaniesMarketCap Glaukos (GKOS) - Market capitalization
SV011 StockLight / SEC mirror Glaukos Annual Report 2025 Form 10-K (NYSE:GKOS)
SV012 CompaniesMarketCap Sonova (SOON.SW) - Market capitalization
SV013 Sonova Annual Report 2025/26
SV014 CompaniesMarketCap Sight Sciences (SGHT) - Market capitalization
SV015 Sight Sciences Sight Sciences Reports Fourth Quarter and Full Year 2025 Financial Results and Initiates Full Year 2026 Financial Guidance
SV016 StockLight / SEC mirror Sight Sciences Annual Report 2025 Form 10-K (NASDAQ:SGHT)
SV017 Google Intelligent eyewear is coming this fall
SV018 OpenAI Transforming visual accessibility
SV019 Apple Accessibility
SV020 Microsoft Seeing AI User Manual Revision C 13-Mar-2024
SV021 OrCam OrCam Read 3: Advanced Reading Aid for Visual Impairments
SV022 OrCam OrCam MyEye Manual And Audio Guides
SV023 OrCam OrCam - Enhances Hearing in Noisy Environments
SV024 Apple App Store OrCam Hear App App - App Store
SV025 Blinded Veterans Association OrCam – Blinded Veterans Association
SV026 OrCam VA Benefits for Legally Blind Veterans: Ultimate Veteran Benefits List - OrCam
SV027 OrCam terms-of-use
SV028 OrCam Website Accessibility Statement - OrCam
SV029 FDA.report Orcam FDA Filings - FDA.report
SV030 OrCam OrCam Products Privacy Terms & Conditions