Agent-built demo / Before audit
Settleline
Fintech · Nov 8, 2026
3 measured views. Local app. Design grades compare the actual screen with published product references. N/A means there was no applicable sample. Unverified means evidence was insufficient.
Product specificity and generic signals · F
At 1440, named payments, references, amounts and Match deposit establish settlement work. At 390, the opening message remains generic and the deposit/action are outside the capture, weakening recognition of the actual decision. (/)
Visual specificity before deductions C. Weighted design base C. Distinct signal deductions 4.
Product specificity supplies 55% of the base, and the five visual design dimensions share 45%. Round the base to the nearest letter. Each distinct verified generic signal lowers it by one letter, down to F. Foundations are reported separately. The detector ceiling is F. Vision reviewed 1 of 1 measured routes.
- Template copy · −1
- “all-in-one solution” does not identify a product task or outcome. (/, 1440 px, Detector and vision.)
- Gradient hero · −1
- A gradient fills the opening section around the visible heading. (/, 1440 px, Detector and vision.)
- Emoji bullets · not observed
- No instance was identified in the reviewed views.
- Default shadcn grays · −1
- 4 separate visible panels repeat the same near-default neutral border, fill, width and corner treatment. (/, 1440 px, Detector.)
- Purple on white · −1
- A prominent purple action or heading sits on a white surface. (/, 1440 px, Detector and vision.)
- Centered everything · not observed
- No instance was identified in the reviewed views.
Compared with the 2026 references
- / · fintech-1 keeps dated records compact and status consistently visible. Settleline exposes useful references and amounts on desktop, but loses status legibility and decision proximity on phone. Commercial grade: F after the three observed generic-signal letter deductions from the C-level foundation. Actual Budget · account register
Visual design
- Hierarchy
- D
- At 1440, the large hero and summary cards precede the unmatched record and low-positioned action. At 390, their vertical footprint pushes the deposit comparison and action beyond the opening view. (/)
- Typography
- B
- Both widths use clear section headings, bold customer names and readable body text. At 390, customer names wrap across lines; the clipped status is principally a layout failure. (/)
- Spacing
- D
- Desktop cards and table rows have clear separation. At 390, generous hero/card spacing consumes the opening view while the table lacks enough horizontal room for its four columns. (/)
- Copy and labels
- C
- Incoming payments, Unmatched and Match deposit describe real work. At both widths, “Your finance dashboard” and “The all-in-one solution for modern payments” occupy prominent space without explaining the settlement decision. (/)
- Imagery
- N/A
- This reconciliation task needs no illustration. The lone rocket emoji supplies no decision evidence.
Foundations · D
Contrast, responsive layout and keyboard reach are sampled separately. The foundations grade is the lowest verified result in this group.
- Color contrast
- A
- At least four opaque text samples per view passed the contrast threshold. Verified across 3 measured views.
- Responsive layout
- D
- The document is 398 px wide in a 390 px viewport. (/, 390 px.)
- Keyboard access
- B
- Checked 3 Tab probes reaching a visible target across the captured views. No issue detected by this check.
Fix these first
- Name the object, action and result in the heading.Product specificity · / · 1440 px
- Replace the opening gradient with a view of the product doing its work.Product specificity · / · 1440 px
- Give the primary task, supporting information and actions distinct visual roles.Product specificity · / · 1440 px
- Choose an action color grounded in the product and separate it from status colors.Product specificity · / · 1440 px
- Constrain the overflowing content and replay this width without horizontal scrolling.Responsive layout · / · 390 px
Evidence from the screens
Gray blocks conceal form values or sensitive text. Numbered outlines identify measured issues.
- “all-in-one solution” does not identify a product task or outcome.
- The document is 398 px wide in a 390 px viewport.
- A prominent purple action or heading sits on a white surface.
- 4 separate visible panels repeat the same near-default neutral border, fill, width and corner treatment.
- A gradient fills the opening section around the visible heading.
- “all-in-one solution” does not identify a product task or outcome.
- “all-in-one solution” does not identify a product task or outcome.
Independent task review
The reviewer assesses each route against its user task using desktop and phone evidence. Its task grades describe the interaction evidence available for that route.
/
Audit Settleline’s working settlement screen at /. Decide whether the $1,840 Morrow Foods payment TX-091 matches bank deposit BNK-407, then use “Match deposit.”
Reviewed at 1440 × 900 and 390 × 844.
- Task hierarchy
- D
- At 1440, the unmatched payment and matching deposit are visible, but a large promotional hero precedes the work and the action sits near the bottom. At 390, the table clips the status column and the matching deposit and action fall outside the supplied opening view, separating the decision from its evidence.
- Landing message
- N/A
- This is an internal settlement screen. Its generic promotional introduction is assessed as task hierarchy and copy friction.
- Interaction feedback
- Unverified
- No Match deposit activation or resulting state was supplied. The images cannot establish confirmation, updated status, persistence or retry behavior.
- Access and recovery
- D
- At 390, payment content extends beyond the card and viewport, obscuring status. Checks report one visible desktop control and zero visible mobile controls; Tab reached a visible target at both widths. Complete keyboard operation, focus appearance and recovery were not established.
- Release evidence
- Unverified
- The supplied local renders and checks establish opening layout, control counts and a reachable Tab target at both widths. They do not establish successful matching, saved state, recovery or deployed behavior.
First action
Replace the promotional hero with a compact settlement heading and bring the Morrow Foods payment, BNK-407 deposit and Match deposit action together. At 390, use a stacked record layout that keeps the amount, reference and status inside the viewport.
How to verify Recheck at 1440 × 900 and 390 × 844: confirm both records and the action are readable without horizontal clipping. Then activate Match deposit with keyboard and pointer, observe explicit feedback, confirm the payment status and unmatched count update, and reload to check persistence. Contrast measurements remain unverified.
What a repair could look like
Settleline is an agent-built fintech settlements demo. Both captures show the same task.
