Why Not Run: a product site that has to explain an engine.

The situation

Why Not is an indie running coach for iPhone — adaptive training plans for distances from 5K to ultra, built by one developer rather than a venture-funded team. It sits in a category full of apps that look identical in a screenshot.

The differentiator is real but abstract: the plans rewrite themselves as you train, recalibrating against what you actually ran rather than handing you a fixed template. That is a genuinely better product and a genuinely hard thing to put on a landing page. Say too little and it reads like every other plan app. Say too much and the page turns into documentation nobody finishes.

What got built

A product marketing site organised around the explanation rather than around the app store listing. The navigation names the argument directly — Engine, Features, Compare, FAQ, Tools — so a visitor who wants the mechanism and a visitor who wants the feature list each have a door.

Giving the engine its own destination is the central decision. Instead of compressing the adaptive logic into three bullet points on a homepage, it gets the room to be explained properly:

• Plans that recalibrate against real performance rather than a fixed template
• VDOT-based pace zones calibrated to the individual runner
• A real coach voice with pace targets and step-by-step guidance
• Plan pause for one to fourteen days, for the weeks life interrupts
• Apple Watch through Apple Health, with VO2 max tracking

A Compare section takes the competitive question head on rather than pretending it does not exist, and the privacy position is stated as a feature: no data harvesting, no social feed, and training data stored on the device rather than in somebody's database. For an indie app arguing against venture-backed competitors, that is a real differentiator and it is treated as one.

Trial policy, privacy, and terms each get their own page. For a subscription product those pages are part of the sales argument — a runner deciding whether to start a trial wants to know how it ends before they begin.

How it is built

Static HTML, no framework, no content management system. The site is separate from the app itself, which runs on a React Native plan engine and ships on iOS and Apple Watch with Android named as a roadmap item. A set of free calculators under the tools route gives the site a reason to rank for something other than its own brand name.

Where it stands

The site is live at whynot.run with the engine explanation, feature and compare sections, FAQ, tools, and the policy pages published, and a free trial as the primary call to action.