Build a user persona from actual research notes instead of inventing demographics that don't affect design decisions

Build a user persona from the research notes below — not a padded demographic template with an invented name, age, hobbies, and stock-photo description that doesn't change a single design decision.

RAW RESEARCH NOTES
5 interview transcripts with small-business owners: 3 mentioned struggling to reconcile invoices manually at month-end; 2 said they check the app only on mobile during commutes; 1 explicitly said they don't trust automated categorization without a review step.

HOW MANY PEOPLE THIS IS BASED ON
5 semi-structured interviews, no broader survey yet.

DESIGN DECISION THIS PERSONA WILL INFORM
Whether to build a one-tap 'auto-approve' feature for expense categorization or keep a manual review step in the flow.

RULES
Include a trait in the persona only if you can point to where in the research notes it came from and explain what design decision it would change if it were different — no trait earns a place in the persona just because personas conventionally include that category of information. If the notes don't support a detail some templates expect (age range, income, family status), leave it out entirely rather than inventing a plausible-sounding placeholder; an invented detail that happens to be wrong will misdirect the exact design decision this persona is meant to inform. Be explicit about confidence: state which traits are well-supported by multiple points in the notes versus which are inferred from a thin signal (one mention, an assumption bridging a gap in what was said), so whoever uses this persona later knows where the research is solid and where it's a working guess. If the sample size given is small, say so plainly in the output and note that this persona represents a hypothesis to validate further, not a confirmed segment.

WHAT NOT TO DO
Do not invent a name, stock-photo description, or "day in the life" narrative flourish — these read as complete but add nothing a design decision can act on. Do not average conflicting research notes into a bland middle description; if the notes show two genuinely different user types, say so and suggest this might be two personas, not one blended one.

OUTPUT FORMAT
A short persona with: a one-line summary of who this is and their core goal, then a table of Trait | Evidence from notes | Confidence (strong / inferred) | Design implication. End with an explicit note on sample size and confidence, and whether the notes suggest more than one persona is actually present.