Not Sure What I Need

Problem framing before service selection.

​

What This Is

Not Sure What I Need is the entry point for uncertainty.

It allows work to begin without forcing a premature service choice. Instead of selecting a trade or package, the system starts by clarifying what is happening and what actually matters.

Confusion is treated as a valid starting state.

Why This Exists

Most people do not experience problems as services.

They experience symptoms.

Something leaks
Something smells wrong
Something stopped working
Something feels off

When platforms force service selection too early, the result is mis scoped work and wasted effort.

Not Sure What I Need exists to slow that moment down.

How the System Responds

The system guides discovery instead of asking for guesses.

It works through:

Observed symptoms
Location and timing
Recent changes or work
Known materials and systems
Visual evidence when available

The goal is to narrow the problem space before proposing solutions.

Relationship to Diagnosis and Planning

This entry point does not trigger execution.

It feeds into:

Problem diagnosis
Project definition
Maintenance evaluation
Escalation when needed

Only once the issue is framed does the system move toward pricing or scheduling.

Preventing Wrong Work

By starting with uncertainty, the system avoids:

Dispatching the wrong trade
Quoting unnecessary services
Stacking fixes on top of unknown causes

Clarity is established before money moves.

Operational Effects

This reduces noise across the platform.

Fewer incorrect requests
Less back and forth clarification
Higher first pass resolution

Time is spent solving the right problem.

Structural Role

Not Sure What I Need allows Cohos to accept reality as it is, not as a menu assumes it to be.

It keeps the system aligned with how problems actually show up in the real world.