Idea Evaluation

Physical AI

Does your physical AI product actually require atoms?

A structured evaluation for physical products: who the user is, what pain remains unsolved, why it truly requires hardware, and what could kill the company.

Standard

Physical AI

Expansion

What it checks

User clarity, active constraint, deployment sequence, production reality, supply chain risk, service economics, and whether demand is evidenced or only assumed.

Trust model

Your product details are private. This evaluator does not store or share your idea outside this session.

Define your idea

Standard fields

Product name *

Target user *

Who pays, who operates it day to day, and whose workflow breaks if this fails?

Problem *

What pain is frequent, expensive, and specific enough that someone will change behavior to solve it?

Why now *

Constraints *

What is the active bottleneck right now: data, hardware, safety, service, regulation, production, demand, or something else?

Physical AI specific

Is the problem physical? *

Could software solve this instead? What specifically requires atoms?

Form factor *

What physical shape is your robot?

First deployment environment *

Where does the first paying customer use this? Start controlled, not consumer.

Build vs buy

What are you building in-house vs. procuring? Also: which part should be deleted, simplified, or made less custom before you scale?

Manufacturing strategy

How do you physically produce this, and what changes between prototype and production?

Demand validation approach

What evidence says this pain is real before you commit to hardware: signed demand, workflows observed, budget already allocated?

Fundraising strategy

Who funds this category, what round are you raising, and what story are you selling to investors?

Materials strategy

What materials are you using for the structure and why? Steel, aluminum, carbon fiber, polymers?

Hardware refresh cycle

How long should the hardware last, and what can improve through software only?

Service and maintenance model

What happens when the robot breaks in the field? Response times, spare parts, module swaps, and who carries the operational pain?

Regulatory path

What certifications are required? Which markets first? Timeline?

Deployment model

Who installs, configures, and maintains the robot post-sale?

Unit economics target

Target BOM cost, sale price, margin, recurring revenue

Tech tree risk

What is the single assumption that, if wrong, kills the company? This should be the truth you most need reality to test.

Privacy: your idea stays in this session only.

Specific input beats vague input. Name numbers, not hopes.

Evaluation output

The evaluation scores user clarity, deployment sequence, demand evidence, supply chain risk, service readiness, and more.

Is the problem actually physical?

Timing readiness (are enabling tech mature?)

Build vs buy risk (supply chain concentration)

Deployment path clarity

Demand validation quality

Regulatory surface

Hardware vs software moat

Idea Evaluation

Physical AI

Does your physical AI product actually require atoms?

A structured evaluation for physical products: who the user is, what pain remains unsolved, why it truly requires hardware, and what could kill the company.

Standard

Physical AI

Expansion

What it checks

User clarity, active constraint, deployment sequence, production reality, supply chain risk, service economics, and whether demand is evidenced or only assumed.

Trust model

Your product details are private. This evaluator does not store or share your idea outside this session.

Define your idea

Standard fields

Product name *

Target user *

Who pays, who operates it day to day, and whose workflow breaks if this fails?

Problem *

What pain is frequent, expensive, and specific enough that someone will change behavior to solve it?

Why now *

Constraints *

What is the active bottleneck right now: data, hardware, safety, service, regulation, production, demand, or something else?

Physical AI specific

Is the problem physical? *

Could software solve this instead? What specifically requires atoms?

Form factor *

What physical shape is your robot?

First deployment environment *

Where does the first paying customer use this? Start controlled, not consumer.

Build vs buy

What are you building in-house vs. procuring? Also: which part should be deleted, simplified, or made less custom before you scale?

Manufacturing strategy

How do you physically produce this, and what changes between prototype and production?

Demand validation approach

What evidence says this pain is real before you commit to hardware: signed demand, workflows observed, budget already allocated?

Fundraising strategy

Who funds this category, what round are you raising, and what story are you selling to investors?

Materials strategy

What materials are you using for the structure and why? Steel, aluminum, carbon fiber, polymers?

Hardware refresh cycle

How long should the hardware last, and what can improve through software only?

Service and maintenance model

What happens when the robot breaks in the field? Response times, spare parts, module swaps, and who carries the operational pain?

Regulatory path

What certifications are required? Which markets first? Timeline?

Deployment model

Who installs, configures, and maintains the robot post-sale?

Unit economics target

Target BOM cost, sale price, margin, recurring revenue

Tech tree risk

What is the single assumption that, if wrong, kills the company? This should be the truth you most need reality to test.

Privacy: your idea stays in this session only.

Specific input beats vague input. Name numbers, not hopes.

Evaluation output

The evaluation scores user clarity, deployment sequence, demand evidence, supply chain risk, service readiness, and more.

Is the problem actually physical?

Timing readiness (are enabling tech mature?)

Build vs buy risk (supply chain concentration)

Deployment path clarity

Demand validation quality

Regulatory surface

Hardware vs software moat