Reviews and app ideas need a clear queue, not a messy inbox.
TrailRunner should handle review requests, proof moderation, What You Need submissions, and creator-profit decisions with visible stages, safeguards, and next actions.
Verified customer proof
Collect feedback only after a customer has enough context to use the app, then moderate for privacy, disclosure, accuracy, and useful limitations.
What You Need submissions
Capture who the idea helps, what repeats, the first useful version, why people would pay, and whether the idea fits TrailRunner governance.
Publish, reject, hold, or scope
Every review or idea should leave the queue with a documented decision, a reason, an owner, and the next step.
Customer review request
Ask for honest feedback after the customer has completed the first success checkpoint and understands the app outcome.
- Required evidence
- Verified purchase or support context, app used, customer type, outcome attempted, permission to publish.
- Protection rule
- Never request fake praise, never suppress honest negative feedback, and disclose any relationship or compensation.
- Next action
- Moderate for privacy and accuracy, then publish balanced feedback or log why it was rejected.
Family or business outcome story
Turn a real workflow result into a short proof story that includes context, limitation, and measurable improvement.
- Required evidence
- Customer permission, before/after context, app used, support notes, measurable outcome, honest limitation.
- Protection rule
- Remove sensitive household, business, location, billing, or support details unless written permission covers them.
- Next action
- Draft a short case study, confirm attribution level, and route through proof moderation before publishing.
What You Need app idea
Evaluate app ideas from families and small businesses by repeated need, buyer clarity, feasibility, privacy impact, and support burden.
- Required evidence
- Audience, repeated problem, first useful version, willingness to pay, privacy concerns, likely support path.
- Protection rule
- Do not promise development, ownership, payout, or exclusivity before written scope and creator agreement.
- Next action
- Reject, hold for more context, or move to scope review with market fit and build feasibility notes.
Accepted idea partner decision
When TrailRunner selects an idea, the 25% proceeds path starts only after written terms define scope, acceptance, payout basis, and launch rules.
- Required evidence
- Accepted scope, idea partner identity, proceeds basis, support owner, launch gate, payout reporting cadence.
- Protection rule
- No payout representation should be made for rejected, duplicate, infeasible, unsupported, or unsigned ideas.
- Next action
- Prepare written creator agreement, document launch readiness, and add the app to the governance ledger if accepted.
How TrailRunner should process the queue each week
Review and idea operations should be boring in the best way: same intake fields, same review standards, same privacy checks, same written decision record.
- CaptureLog the app, customer or idea type, requested outcome, date received, and owner.
- ValidateCheck verified use, permission, privacy, conflicts, feasibility, support load, and market fit.
- DecidePublish, reject, hold for more context, or move into written scope and creator agreement.
- Close loopSend the customer or idea partner the decision, next step, and any support or agreement requirements.