Back to work

Web

Live

Wheni.sh

Turn a loose plan into time you can see.

Wheni.sh takes a goal such as training for a race, hosting a dinner, or protecting a weekly focus block and turns it into a scheduling recommendation grounded in the calendar.

01

A sentence becomes concrete requirements such as duration, frequency, timing, and deadline.

02

Calendar constraints and recurring preferences shape the recommendation before it reaches the user.

03

A review pass checks the reasoning and softens language that sounds more certain than the evidence.

The product problem

The plan arrives as a sentence.

People rarely begin with a clean scheduling specification. They say they want to train for a race, cook for friends, or find time for a project. The product has to identify what the plan requires before it can look for room.

Wheni.sh turns that sentence into details the calendar can test: how long, how often, which days work, what must stay protected, and when the plan needs to be complete.

Wheni.sh homepage with a field for describing a plan in plain language.
The scheduling flow begins with the plan as the user would describe it.

The decision

The calendar sets the boundaries.

Work hours, existing events, recurring availability, and user preferences remain the source of truth. The recommendation has to respect those facts and explain the tradeoffs when the original plan does not fit cleanly.

Trust

A second review catches overconfidence.

Before the answer appears, a separate review looks for weak reasoning, missed tradeoffs, and language that promises too much. The user receives a recommendation they can inspect instead of a confident sentence with no account of how it was reached.