FinSights

FinSights displayed a 50 MB file limit and a 100-page PDF limit in the UI, but the upload flow did not turn those limits into real validation or warning behavior before submission.

That gap created avoidable friction because users could upload documents that were too large or too long without knowing whether the request would fail, be trimmed, or continue with partial processing.

Designed a warning-and-confirmation flow around FinSights' upload constraints so files over 50 MB and PDFs over 100 pages could be flagged before users committed to processing.

Added backend document analysis and structured warning payloads for file size, page count, and pages-to-process metadata, which gave the frontend enough context to explain exactly what would happen next.

Updated the upload and summary flow to preserve state, surface inline warnings, and support an explicit Upload Anyway action when users chose to continue with a file that exceeded the recommended limits.

Turned static helper text into an actionable upload workflow, so FinSights could warn users clearly about oversize files and page-limit overages before processing began.

Improved trust in the document pipeline by making backend processing behavior explicit, including when only the first 100 pages would be used, instead of leaving users to discover that later in the request flow.