Marketing templates for app founders

Record repeatable AI-search observations for your software brand, with query context, actual citations and a baseline that avoids ranking promises.

Trace an AI answer’s product claims to its linked sources and distinguish accurate support, weak attribution and unsupported statements.

Prepare a concise public reference for an app’s identity, audience, capabilities, availability and limits with links to authoritative details.

Rewrite a useful page section into a clear direct answer with relevant conditions, evidence and a next step that still reads naturally.

Diagnose why a public resource cannot be fetched by a search crawler using status, redirects, robots rules and verified request evidence.

Find public inconsistencies in your app’s name, website, owner and description, then correct authoritative owned surfaces with evidence.

Document an inaccurate AI product answer, fix misleading owned evidence and preserve later observations without promising an immediate external correction.

Replace ambiguous page links with descriptions of their actual destinations and useful context, then verify the rendered link in its surroundings.

Decide what a product screenshot contributes to a marketing page and write a contextual alternative without dumping every interface label into it.

Review a demo’s captions against its real audio, timing, speaker changes and meaningful sounds before publishing the final player experience.

Rewrite unclear software copy around the reader’s task, concrete actions and necessary conditions while preserving factual meaning.

Plan meaningful section headings and a logical reading sequence so a marketing resource is navigable beyond its visual styling.

Specify clear labels, required inputs, useful formats and contextual help for a signup form before writing interface copy.

Map real form failures to clear affected fields, safe recovery instructions and appropriate feedback without exposing internal details.

Confirm the exact action a form completed, explain the real next step and avoid promising account access or email delivery without evidence.

Plan how a software recording communicates necessary visual changes through narration, an appropriate description track or an accessible equivalent.

Explain a chart’s essential values, units, relationships and limits in accessible text while checking that the visual and source data agree.

Create a consistent source, medium, campaign and content dictionary before tagging marketing links across a small founder team.

Define an audience, message, destination, outcome and stopping rule before spending time or money on a founder marketing experiment.

Compare creator placements using audience fit, disclosed sponsorship, tagged traffic and downstream product activity rather than follower totals alone.

Review founder marketing experiments using raw counts, user evidence, uncertainty and one concrete next decision for each action.

Ask new users how they discovered your app without forcing a channel answer or treating their memory as perfect attribution.

Review observable AI referral visits and their downstream outcomes while preserving unknown traffic and avoiding total-influence claims.

Define an acquisition or activation metric with its numerator, denominator, unit, event boundary and exclusions before comparing reports.

Plan a sequence of truthful app screenshots around a user task, visible interface evidence and a clear result.

Prepare an app preview with real interface footage, a complete task and production notes that prevent misleading edits.

Match one acquisition audience to an App Store product-page story using relevant screenshots, truthful copy and a traceable destination.

Write a testable store-listing hypothesis with a defined control, one creative change and a predeclared review decision.

Review translated store screenshots for product accuracy, interface language, text fit and cultural context before publishing a locale.

Check a specific community’s current rules and discussion context before deciding whether a proposed contribution belongs there.

Decide whether you can add a useful answer to a specific public question by checking expertise, context, prior replies and community boundaries.

Check whether a personally built project is genuinely ready for Show HN, with a usable experience and human-written discussion preparation.

Prepare verified technical and product facts for a maker discussion so the actual builder can answer in their own words.

Capture task questions and existing solutions from public discussions with context, source links and uncertainty instead of turning posters into a contact list.

Separate useful task evidence, product suggestions and subjective reactions after an approved community contribution without treating engagement as validation.

Structure a practical forum answer that resolves the question in place with a concrete method, example and honest limit.

Explain your actual relationship to a product plainly when a permitted discussion requires it, without treating disclosure as permission to promote.

Check whether a proposed community response genuinely answers the question or mainly funnels readers toward your product.

Draft a concise question about an ambiguous community rule with a specific contribution outline, full affiliation and an easy option to decline.

Invite relevant app users to a discovery conversation with a clear purpose, time request and optional participation.

Qualify interview participants using recent task experience, decision responsibility and workflow context before scheduling.

Understand the sequence behind an app cancellation without turning the interview into a retention pitch or blocking departure.

Reconstruct why a customer changed tools, from the first trigger to migration effort and the outcome of the new workflow.

Turn interview notes into observations, competing explanations and testable marketing decisions without inventing consensus.

Ask beta users for the task, expected result and observed behavior with optional safe evidence, without steering them toward praise.

Observe whether a relevant new visitor understands the product, access conditions and next action without giving them the intended answer.

Turn a product goal into a realistic test activity with a clear outcome, necessary context and no clues about which interface control to use.

Reconstruct a recent customer task through trigger, actions, interruptions and outcome while separating remembered events from researcher interpretation.

Document how a person completes a task with existing tools, including what already works, friction and the cost of changing the workflow.

Choose which marketing assumption to investigate next by recording the decision it affects, consequences of being wrong and available evidence.

Preserve evidence that challenges your audience or message hypothesis, then investigate the conditions that explain different customer experiences.

Keep participant statements, observed behavior, researcher interpretations and follow-up questions distinct in a usable private research record.

Compare task conditions across potential software audiences without confusing a small interview sample with market size or broad demographic conclusions.

Choose a neutral next question from a real evidence gap and explain which decision its answer could change.

Attach evidence, scope and review triggers to published marketing statements so statistics and product claims remain verifiable.

Turn a vague marketing idea into a specific proposed change, measurable expected behavior and a decision that evidence could change.

Define the user harms and operational regressions a marketing experiment must watch alongside its primary success measure.

Verify that eligible visitors see the assigned variant and that exposure and outcome events represent the experience actually delivered.

Gather the baseline, meaningful effect, assignment unit and planned analysis inputs needed to assess whether a controlled marketing test is feasible.

Record concurrent campaign, product and measurement changes that could alter an experiment’s exposure or interpretation.

Explain an inconclusive test through the original question, data quality, uncertainty and next decision without calling a small observed difference a winner.

Choose interviews, usability observation, controlled comparisons or descriptive analysis based on the question and evidence available.

Preserve a test’s original question, tested implementation, validity checks, result limits and final action in one reviewable record.

Brief a page’s opening around the visitor’s task, a truthful product explanation, visible proof and one appropriate next action.

Build useful product questions from real uncertainty, verified answers and a record of where each answer belongs on the page.

Justify a distinct app use-case page with a specific audience task, available workflow, original evidence and an honest next step.

Compare an acquisition message with the page and access journey it leads to so visitors receive the task, proof and offer they were promised.

Sort incoming launch issues by observed impact, affected journey and evidence so the right owner handles access failures before cosmetic requests.

Review a software launch’s intended audience, observed journey, attributed actions and support evidence before deciding what to repeat or change.

Decide whether a software launch is ready by checking the actual access journey, honest claims, support coverage and evidence for each critical step.

Coordinate a launch’s central product statement, audience-specific context, proof and access action across channels without creating contradictory promises.

Give a teammate one reliable inventory of approved launch copy, media, destinations, usage constraints and current versions.

Prepare realistic fictional demo data that reveals the intended workflow without exposing customer records or presenting sample outcomes as real results.

Draft a maker introduction that explains the task, why you built the product, what is available and the specific feedback you want.

Write release notes around the actual version, user-visible changes, necessary actions and limitations with a reliable reference to the shipped iteration.

Explain a changed launch plan with the verified access impact, what subscribers should do and a credible next update without inventing a new deadline.

Confirm an app waitlist signup with an honest availability statement, clear update expectations and one optional research question.

Give an approved beta participant the correct sign-in path, account identity, scope and support details without promising public availability.

Explain a pending or unselected beta application clearly while separating waitlist updates from confirmed product access.

Announce an actually available app to opted-in subscribers with a clear use case, truthful access conditions and a working next step.

Explain one shipped feature through the existing task it improves, a concrete usage path and clearly stated availability limits.

Guide a new app user through one meaningful task with the necessary setup, an observable result and a practical support route.

Offer help after a verified setup stall without pretending you know the cause or pressuring someone who simply chose to stop.

Ask for focused feedback on a task someone actually attempted, with an easy reply and no requirement to leave a public review.

Let an existing subscribed audience choose relevant update topics or frequency without making full unsubscribe difficult.

Share a factual development update with subscribed followers by showing what changed, what remains uncertain and one optional next action.

Define a software audience through a real task, trigger, current workaround and reachability instead of broad demographic labels.

Map the tools, manual steps and do-nothing options a customer actually uses before framing your app’s positioning.

Write a clear product introduction from the audience, real task, available capability and meaningful distinction you can support.

Connect each product feature to a user task, a defensible benefit and the evidence needed before making a marketing claim.

Keep website, email, demos and AI-readable summaries aligned on which capabilities are released, limited, planned or not offered.

Explain who an app is useful for, the relevant task conditions and when another workflow is a better fit.

Prepare fair answers to product concerns by separating the actual question, verified facts, limitations and an appropriate next step.

Turn permission-appropriate customer language into message hypotheses while preserving context and avoiding invented testimonials or exaggerated claims.

Inventory public app-marketing URLs with their purpose, response, canonical, discovery links and indexing evidence before changing the site.

Map duplicate public URLs to a justified preferred version while keeping redirects, internal links and sitemap signals consistent.

Review crawl rules against public and private route intentions without treating robots.txt as authentication or a reliable removal mechanism.

Verify a public sitemap’s URLs, canonical consistency, modification dates and submission evidence after a content release.

Map old public URLs to relevant destinations and verify status, path preservation, redirect chains and final canonical behavior.

Draft a descriptive page title from the actual user task, visible heading and product facts, then record the live implementation separately from search display.

Write a page-specific search description that states the useful answer, audience and available resource without fabricated benefits.

Connect related app-marketing resources through useful reader next steps, descriptive anchors and verified destinations.

Compare overlapping public pages by user intent, unique value and link history before proposing a merge or preserving separate resources.

Update a public marketing resource by recording changed claims, checked sources, preserved examples and the reason its modification date changed.

Compare JSON-LD fields with the actual visible product page and supporting evidence before treating valid syntax as a finished schema implementation.

Write a video opening that matches the title promise and starts demonstrating a real app task before a long founder introduction.

Brief a thumbnail around a truthful visual promise, supporting title and readable product evidence instead of unrelated clickbait.

Inspect video exits, top moments and replay spikes with timestamped hypotheses and concrete editorial changes.

Plan one compact app tutorial around a visible task, real steps and a completed result that makes sense without sound.

Give a founder or creator a precise recording brief with real setup, screen sequence, proof points and claims to avoid.