Skip to content

Chapter 5: The Tomorobo Opportunity

Context

Scott flagged a specific connection in his email:

"Note the example where they sell the robot and then license various application software products on top. For Tomorobo this could be quality inspection, design inspection, or other types of compliance."

"Both AI and IoT could be factors if Tomorobo gets traction."

This chapter maps the HaaS models from the Hardfin blog directly to Tomorobo's potential business architecture.

The Plus One Robotics Parallel

Of the five companies profiled, Plus One Robotics is the closest analog to what Tomorobo could become:

Plus One Robotics Tomorobo (Potential)
Sells robotic workcells (hardware) Sells inspection robot hardware
Subscribes customers to PickOne (AI vision) Could subscribe customers to AI inspection software
Subscribes to Yonder (supervised autonomy) Could offer supervised/autonomous inspection modes
Targets warehouse/logistics Targets construction/manufacturing compliance
2,200–3,300 picks/hour value metric Inspections per day, defects caught, compliance rate

The model: sell the robot, subscribe to the intelligence.

Software-on-Top Revenue Streams for Tomorobo

If Tomorobo follows the hybrid model (hardware sale + software subscription), here are the potential recurring revenue layers:

Tier 1: Quality Inspection Module

  • AI-powered visual inspection of welds, concrete, steel, finishes
  • Defect detection and classification
  • Automated reporting with photo documentation
  • Value to customer: Replaces manual inspection labor, catches defects earlier, reduces rework

Tier 2: Design Compliance Module

  • Compare as-built conditions to BIM models or design drawings
  • Flag deviations from specs (dimensional, placement, material)
  • Integrate with project management platforms
  • Value to customer: Catches design-to-build gaps before they become change orders

Tier 3: Regulatory Compliance Module

  • Automated documentation for building code, OSHA, environmental compliance
  • Audit trail with timestamped, geolocated inspection records
  • Template-based reporting for different regulatory frameworks
  • Value to customer: Reduces compliance risk, accelerates inspections, creates defensible records

Tier 4: Analytics & Portfolio Intelligence

  • Cross-project defect trending
  • Predictive quality modeling (which projects/contractors have higher defect rates)
  • Benchmarking across sites, regions, or project types
  • Value to customer: Strategic quality management, not just tactical inspection

Revenue Model Options

Model How It Works Pros Cons
Hardware + SaaS Sell robot, monthly software subscriptions per module Immediate hardware revenue, predictable recurring SW revenue Customer may resist paying for both
Full HaaS Monthly subscription includes robot + all software Lowest barrier to entry, highest customer appeal Tomorobo carries balance sheet risk
Per-inspection Pay per inspection performed Aligns cost with value delivered Revenue is variable, hard to forecast
Hybrid Sell robot, base software included, premium modules subscription Gets hardware off balance sheet, upsell path for premium features Complexity in pricing/packaging

Recommended Starting Model

Hardware + SaaS (Vention/Plus One model) — sell the robot to get it off Tomorobo's balance sheet, then build recurring revenue through software subscriptions. This is the most capital-efficient path and the most financeable by partners like KLC.

IoT as the Data Foundation

Every Tomorobo unit deployed is a data-generating node:

Data Type Use Case
Location (GPS) Asset tracking, geofencing, utilization monitoring
Usage hours Maintenance scheduling, billing, residual value tracking
Inspection results Quality trending, AI model training, benchmarking
Environmental conditions Contextualizing inspection results (weather, lighting, etc.)
System health Predictive maintenance, uptime optimization

This data serves three audiences:

  1. Tomorobo — improve the product, train AI models, demonstrate value
  2. Customers — quality dashboards, compliance records, project analytics
  3. Finance partners (KLC) — real-time portfolio monitoring, utilization verification, residual validation

AI as the Value Multiplier

The robot hardware is the platform. AI is what makes the subscription worth paying for:

  • Computer vision — detect cracks, misalignments, material defects
  • Natural language processing — generate human-readable inspection reports from raw data
  • Predictive modeling — forecast where quality issues will occur before they do
  • Continuous learning — every inspection improves the model; the more units deployed, the smarter the system

This creates a data network effect: more deployments → more training data → better AI → more value → more deployments. This flywheel is what justifies HaaS economics over time.

The KLC-Tomorobo Financing Partnership

If Tomorobo goes to market with a HaaS model, KLC's role could be:

Option A: Customer Equipment Finance

  • KLC finances the robot purchase for the end customer
  • Tomorobo gets paid upfront for hardware
  • Customer pays KLC monthly for hardware + Tomorobo monthly for software
  • KLC risk: Standard equipment finance, collateralized by the robot

Option B: OEM Fleet Finance

  • KLC finances Tomorobo's fleet of deployed robots
  • Tomorobo pays KLC from subscription revenue
  • KLC risk: Tomorobo's credit quality + subscription book stability + robot residual

Option C: Embedded Finance

  • KLC provides a white-labeled financing solution embedded in Tomorobo's sales process
  • Customer sees a single monthly payment; KLC and Tomorobo split on the back end
  • KLC risk: Customer credit + Tomorobo partnership stability

Scott's Backstop Question Applied

"Who owns it if the customer doesn't like it or goes belly up?"

  • Option A: KLC recovers the robot. It has value as general inspection hardware if there's a secondary market.
  • Option B: KLC recovers the fleet from Tomorobo. Must redeploy or resell — requires OEM buyback agreement.
  • Option C: Same as A, but the relationship is tripartite — recovery requires coordination with Tomorobo.

Summary: Tomorobo's Path

  1. Start with hardware sales + software subscription (Plus One model) — lowest capital risk
  2. Instrument everything with IoT from day one — the data is the moat
  3. Layer AI modules progressively — quality → design compliance → regulatory → analytics
  4. Partner with a finance company (KLC) for customer financing to accelerate sales
  5. Consider full HaaS later — only after subscription economics are proven and a finance partner can backstop the fleet