The Preflight Feature Audit: 9 Search & Signal Checks to Decide If a Feature Should Be Built

The Preflight Feature Audit is a 9‑check funnel that moves from low-effort, high-signal checks (search intent, SERP behavior) to higher-effort validations (A/B pricing, pre-sales). Each check is scored 0–2 (0 = fail / absent signal, 1 = ambiguous or mixed, 2 = strong supporting evidence). Sum the scores (max 18). Use thresholds such as: 0–6 = Stop, 7–11 = Iterate / test small, 12–18 = Build MVP / pilot.

The checklist is intentionally ordered to minimize wasted engineering time: you start with public, passive evidence (what people search and buy today), then layer on internal analytics and direct buyer signals. This preserves momentum for features with clear demand and kills nice-but-unused ideas early.

1) Problem-search volume and intent: Look for searches that describe the problem (’how to’, ‘fix’, ‘reduce’) and commercial queries (’best X’, ‘X tool’, ‘X alternative’). Volume alone is noise—prioritize queries whose intent matches a paid solution. Tools like Keyword Planner, Ahrefs, or simple SERP inspection show whether queries resolve to product pages or how‑to content; product-oriented SERPs are a positive signal.

2) SERP and ad behavior: A results page filled with product pages, paid ads, and ‘alternatives’ listings implies buyers. If competitors are bidding for keywords and ads have been running consistently, that’s a durable commercial intent signal. Conversely, if results are tutorial blogs and forum threads without product landing pages, the intent is likely informational.

3) ‘Alternative’ & comparison demand: Search queries that include ‘alternative’ or ‘vs’ are strong evidence people are evaluating paid options. Capture autocomplete suggestions, People Also Ask, and related queries to quantify how many prospective buyers are in the evaluation stage.

4) Competitor product and pricing mapping: List direct competitors and map whether they sell the same feature as part of core product, as paid add‑on, or not at all. Frequent placement of a feature as paid add‑on across competitors is a strong revenue signal; absence across competitors can mean either an uncovered opportunity or a non‑market.

5) Competitor traction signals: Look for sustained ad spend, active product updates, review volume, job listings, and funding announcements. Multiple indicators of investment against a feature—ads, dedicated landing pages, release notes—are an operational signal that people buy solutions in this area.

6) Voice-of-customer across public channels: Aggregate complaints, feature requests, and reviews from places like product review sites, Reddit, and App Store comments. Recurring mentions of the same pain with tangible ‘if only’ statements are higher-quality signals than single compliments.

7) Product analytics & funnel evidence: Instrument a short hypothesis in your product or landing page—capture event-level interest signals like clicks on a feature CTA, signups for a feature waitlist, or funnel drop-offs that the feature would fix. A measurable lift in prototype click-throughs or signups is stronger than anecdotes.

8) Low-cost monetization tests: Before building, run a paid landing page or ad campaign that drives to a feature-focused page with a pricing option, pre-order, or gated demo. Even a small conversion rate on a paid ad shows a non-zero willingness to pay. Alternatively, use sales conversations with a concrete pricing ask (LOI, prepayment, refundable deposit).

9) Price sensitivity and commitment signals: Use short surveys with anchoring questions, pricing ranges, or simple experiments (discounted preorders vs free trials) to estimate WTP. Methods range from direct ask in discovery calls to structured experiments (A/B price lines, small pre-sales). The presence of committed payment or signed intent is the highest score.

After scoring, translate the total and per-check notes into clear next steps: Stop, Test Small, or Build MVP. Include the raw evidence links and screenshots for each check so contractors or junior PMs can reproduce the audit. Keep the brief two pages: hypothesis, audit table with scores and notes, required deliverables (landing page copy, ad creatives run, analytics events to capture), and a timebox (typically 1–4 weeks).

Ship the contractor-ready template with acceptance criteria: what counts as a 2 vs 1 vs 0 for each check. For example, for Search Demand a ‘2’ = >500 monthly searches for buyer-intent queries and top SERP results are product pages; a ‘1’ = product and informational mix; a ‘0’ = mostly informational queries and no product pages. This removes ambiguity and forces reproducible evidence collection.