← Back to the MatrixBy Esoteric Paths Research · 8 min read

Product Launch Timing: How to Pick the Day You Only Get Once

You get one first impression per launch. Product launch timing turns a calendar guess into a readable decision using the three Xiao Liu Ren palaces.

The One-Shot Nature of Launches

You can iterate on a product indefinitely, but you launch once into a given moment. Product launch timing is the decision that most resists A/B testing, because there is no control group for the day you chose. Teams default to shipping when the build is done, which means the most consequential variable is set by engineering velocity rather than by judgment. A readable timing signal fills that gap.

Reading the Three Palaces for a Launch

The Month palace reads the market context you are launching into — whether the category is receptive. The Day palace reads your team's readiness and the state of the build. The Hour palace reads the immediate reception window. Su Xi at the Hour level is the cleanest go signal: the reception will be fast and favorable. Liu Lian means the launch will be ignored initially and needs sustained push. Chi Kou means expect public criticism or a competitive response. Kong Wang means the launch will land in a vacuum — reschedule rather than heroically ship.

Four Launch Scenarios

(1) Soft launch or beta: Liu Lian at the Day level is fine here, because a quiet start is the design. (2) Big public launch: wait for Su Xi at the Hour level; the difference between a strong first day and a flat one compounds through press coverage and algorithmic distribution. (3) Launching into a competitor's announcement: Chi Kou warns of a direct response — prepare the counter-narrative before you ship. (4) Launching a second product: Kong Wang at the Month level suggests the category has moved on; reposition before spending the launch.

Timing Inside the 72-Hour Window

Once the launch window opens, treat the 72-hour window as your commitment period: 0–24 hours to finalize assets and brief the team, 24–48 hours to resolve reversible issues, 48–72 hours to execute the push. Launches that drift past the window lose the coordination that makes a first day land. The deadline is not artificial urgency; it is the period during which your team's attention is genuinely aligned.

When the Read Conflicts With the Roadmap

This is the hard case: the palace says wait and the board says ship. The resolution is to treat the palace as a signal about quality of reception, not permission to stop working. Use the delay to strengthen the launch package — the press angle, the demo, the onboarding — rather than simply pushing the date. If the read is wrong, you have lost a week of nothing. If it is right, you avoided burning your single first impression on a dead day.

Launch Protocol

Launch when the Market palace is receptive and the Hour palace shows Su Xi. Delay when Kong Wang dominates, and use the time to reposition rather than to polish. Prepare a response plan whenever Chi Kou appears, because the friction it indicates is public and fast. For the method behind the palaces, see Xiao Liu Ren for Founders; for how timing differs from technical analysis, see the crypto entry timing guide.