# An expense app chooses whom it is for

Companion to /learn/conversion/value-proposition/

## Outcome
Make a listing promise specific, supported and recognisable to the intended audience.

Fictional example, not a client result.

## Scenario
ClearExpense is a fictional app for freelancers who collect receipts before sending records to their accountant. Its headline says “Finance, simplified.” That line could describe a bank, investment app or bookkeeping platform. The product has a narrower job and needs a promise that helps the right person recognise it.

## Reasoning
Write four elements separately: audience, difficult job, supported outcome and product mechanism. Do not force all four into one crowded headline; use them to check whether the message has substance. Ask what the visitor would reasonably expect from the promise and whether the app can deliver that expectation in the current version.

## Action
Explore a direction such as “Keep receipts ready for your accountant,” supported by a capture-and-export screen sequence. Check whether the phrase fits the intended market and actual workflow. Avoid claims about tax savings or legal compliance unless the team can substantiate them. A precise modest promise is more useful than an ambitious statement that draws the wrong audience.

## Trap to avoid
Do not mistake a tone of voice for a value proposition. Sarcasm, confidence or premium language can make the brand memorable, but the visitor still needs to understand what the app enables and why it fits their situation.

## Advanced considerations
When two audiences need different promises, first decide which audience the default listing should prioritise. Record the trade-off instead of forcing incompatible benefits into a vague umbrella message. Investigate suitable audience-specific store surfaces where available, but keep each promise tied to the product experience the visitor will actually receive.

## Exercise
Five people call the headline “nice,” but three cannot explain what the app does. Is the message ready for production?

## Suggested answer
No. Preference feedback is different from comprehension. Ask them to describe the expected workflow and identify what remains unclear. Revise the promise or evidence, then review again with people who resemble the target audience.

## Your worksheet

### Priority audience
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Painful job and current alternative
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Supported outcome
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Mechanism and product evidence
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Likely misunderstanding
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Message draft and comprehension findings
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## Compare three message directions for ClearExpense
These fictional alternatives serve different expectations. Choose using audience and product evidence, not the apparent sophistication of the wording. None is a measured winning headline.

Illustrative message comparison. Product proof determines which promises are eligible.
Message direction | Expected meaning | Evidence or decision
Finance, simplified | Broad financial management | Too vague to identify the supported job on its own
Keep receipts ready for your accountant | Organise records for a handoff | Show capture, organisation and export if supported
Scan receipts as you go | Quick capture in the moment | Show the actual capture workflow; investigate whether this is the priority need
Finish your tax return in minutes | Completed tax preparation and filing | Reject: outside the fictional product’s capabilities

### Separate positioning from the final headline
Write the audience, situation, desired outcome and supporting workflow as a brief first. Then explore concise wording. A headline does not have to contain the entire brief, but it must not contradict it. For ClearExpense, the audience may be a freelancer preparing records; the proof is a usable capture-and-export workflow, not a promise of financial advice.

### Ask questions that can expose a misunderstanding
After showing the message, ask what the person believes the app does, what they would use it for and which feature they expect first. Ask what remains uncertain. Record their words before adding your interpretation. If they expect filing, reimbursement approval or a bank account, identify which phrase or visual created that expectation and revise it.

### Choose between two accurate promises
Both capture-first and handoff-first messaging may be truthful. The decision depends on the intended audience and arrival context. Explore which problem matters most to relevant people, then brief the supporting screenshots and a suitable evaluation. Keep the rejected alternative with its rationale: it may be useful for a different audience, but should not be declared inferior everywhere.

## Continue reading
- /learn/keywords/search-intent/
- /learn/conversion/screenshot-strategy/
- /learn/aso-and-user-acquisition/