LogoLogo
  • Introduction
    • Machine-to-Machine Learning White Paper Introduction
    • What is M2ML?
    • 3 Waves - Overcoming Limitations of Human Performance
  • Wave 1
    • Wave 1 – Vision & Identification
    • Wave 1 – Archetypes
    • Wave 1 – Opportunity Areas
      • Automating & Roboticizing Stodgy Industries
      • Accelerating Serendipitous Discovery
  • Wave 2
    • Wave 2 – Building an MVP
    • Wave 2 – Archetypes
    • Wave 2 – Opportunity Areas
      • Automating & Roboticizing Stodgy Industries
      • Accelerating Serendipitous Discovery
    • Wave 2 - The North Star: Building for the J-Curve
  • Wave 3
    • Wave 3 – Building a Platform
    • Wave 3 – Archetypes
    • Wave 3 – Opportunity Areas
      • Automating & Roboticizing Stodgy Industries
      • Accelerating Serendipitous Discovery
  • Insights
    • Identifying Winners Across Waves
    • Case Study: Rapid Robotics
    • Go-to-Market Playbook
      • Product
      • Sales
      • Platform
    • Waves in Motion
  • Conclusion
    • Why Now?
    • Get in Touch
Powered by GitBook
On this page
  1. Wave 3

Wave 3 – Archetypes

Getting to Market, and Transitioning from a Manual Solution -> Service-Oriented Analytics -> Self-Serve Product Platform

PreviousWave 3 – Building a PlatformNextWave 3 – Opportunity Areas

Last updated 3 years ago

1) Companies that enrich and mix datasets

This includes teams leveraging their own rich new datasets, open-source datasets and existing data stores to produce never-before-captured value.

2) Disintermediation of the hardware and software stack

At the early stage, the software-hardware stack is often tightly bundled. But later on, the software evolves to become hardware agnostic (e.g. ); from there, the key goal is speed to scale given the initial defensibility established.

3) Network effects

Whereby (n+1) task/device/implementation inside a system provides increasing value to the system at large through developing increased data density. Extensibility, and data-driven network effects can ease the burden of a land-and-expand go to market strategy.

4) Leveraging an as-a-Service (“aaS”) business model

Robotics (RaaS), Platform (PaaS), etc models​ are shifting CapEx to OpEx. The service business model (in and out of M2ML) is critical to incentivize quality customer servicing and continuous improvement, protecting against commoditization. These models are attractive as they align interests and become 'sticky'.

5) Enabling out-of-the-box automation

And solving for speed to deploy. This includes building with minimal marginal costs of expansion in mind (e.g. an extensible architecture) and owning the customer relationship (e.g. obviating the Systems Integrator) to align incentives and avoid ballooning deployment costs.

Linux
Page cover image