Pluto Robot

Menü

Strategic Insights

From vision to value – how Pluto 7.0 became more than a robot.

Pluto 7.0 is the result of iterative learning, structured development, and a deep understanding of what people actually want. This section captures the strategic thinking behind Pluto’s evolution, using the SPALTEN methodology and principles of Product Generation Engineering (PGE).

We asked ourselves:

  • What does the customer really want?
  • How do we design for delight, not just delivery?
  • What makes Pluto viable -not just technically, but commercially?
 

To answer these questions, we dive into:

 

This section explores the thinking behind Pluto’s commercial viability, customer experience design, and future scalability.

Customer Needs & KANO Model

Before building Pluto 7.0, we asked the most important question: What does the customer truly care about? Using the KANO model and SPALTEN methodology, we translated vague wishes into clear design targets.

  • Basic needs like cold beer, safe transport, and reliable delivery were non-negotiable.
  • Performance needs: speed, transparency, and ease of ordering have shaped our control systems and user interface.
  • Excitement features like 24/7 availability, a built-in bottle opener, and the novelty of a robot delivery added delight.
 

This structured approach helped us prioritize features that matter most, and set targets for our engineering iterations that deliver most value!

Business Model Architecture

To get information on the value creation across different segments, we built a business model that connects technical feasibility with real-world value.

  • Value Proposition: Autonomous beer delivery that’s fast, fun, and sustainable.
  • Customer Segments: Students, faculty, campus events, and B2B partners.
  • Channels: Web app, campus kiosks, QR codes.
  • Revenue Streams: Delivery fees, event sponsorships, future subscription models.
  • Key Resources: Pluto bot, software platform, team expertise.
  • Key Activities: Maintenance, logistics, customer support.
  • Key Partners: AKK, KIT, HECTOR School.
  • Cost Structure: Hardware, software development, operations.
 

This canvas helped us align engineering decisions with market needs and prioritize what features we meet in our engineering phases. It delivers value.

Market Analysis

Understanding the terrain before we drive through it!

We tried building Pluto 7.0 that responds to real trends, real needs, and a rapidly evolving delivery landscape. Using SPALTEN and Product Profile, we analyzed the market to ensure Pluto isn’t just innovative, it’s relevant.

  • Megatrends like autonomous delivery, AI integration, and campus automation are shaping new expectations.
  • Competitors range from global players like Amazon to local student-run services, but few offer Pluto’s blend of fun, sustainability, and campus intimacy.
  • Demand Drivers include convenience, novelty, and the desire for sustainable solutions, especially among students.
  • Challenges like building access, legal boundaries, and insurance were mapped early to guide design and deployment.
  • Opportunities extend beyond beer: Pluto could evolve into a multi-purpose delivery platform for food, books, or campus gear.
 

This analysis helped us steer Pluto toward a future where delivery is not just fast, but thoughtful, delightful, and deeply integrated into campus life.

Through structured analysis, we translated fuzzy needs into concrete features, mapped market dynamics, and built a business model that supports sustainable growth. This is where engineering meets empathy, and where your beer arrives cold, fast, and with a smile 🙂

For more on what we prioritized for our engineering iterations and what actually went into building our Pluto 7.0, see here.