# Spendee ASO audit worksheet

Use alongside https://www.asoagency.com/briefs/spendee. Published copy proposals are hypotheses, not tested outcomes.

## Define your scope

- App and listing URL:
- Store, territory, language and device:
- Observation date and reviewer:
- Visitor intent and source:

## Your ASO assignment

1. Compare each captured still with the current interface and record any differences.
2. Trace one non-sensitive transaction through category review and budget impact.
3. Prepare a claim register and a sequence test with a defined baseline.

## Keep evidence separate from judgment

For each of your first three screenshots record: source URL, capture date, visible content, interpretation and proposed action. Identify the material that must remain unchanged.

## Review the proposed copy

Name: Spendee: Expense Tracker
Subtitle: Budgets, wallets & money plans

Reasoning: Lead with the brand and a recognisable tracking task, then use the subtitle to introduce budgeting and wallets. These are visible or publisher-described product concepts.

Tradeoff: The shorter name removes the explicit word app and shifts budget emphasis to the subtitle. Wallet terminology needs comprehension testing, and current search data must justify the allocation; no ranking lift is assumed.

Your alternative name:
Your alternative subtitle:
Character counts:
Important inclusions and exclusions:
Feature and entitlement checks:

## Plan one test

Example question: Does a current transaction-to-budget sequence improve understanding and qualified acquisition?

Your audience:
Control:
Treatment:
Randomization or other comparison method:
Primary metric and definition:
Real baseline and available traffic:
Minimum practical effect and sample requirement:
Guardrails:
Decision rule and review date:
Confounding changes:
What would make the result inconclusive:

## Handover

Include the original listing snapshot, source links, dated review sample and selection method, competitor observations, copy decisions, approved creative, test brief and remaining evidence gaps.

## Evidence still needed in this audit

- Current interface, category-correction behaviour and wallet access.
- Award, testimonial and comparative-claim provenance.
- Baseline conversion, query intent and setup comprehension.
