The Document Scan That Unlocked Paywork's Core Features

The Document Scan That Unlocked Paywork's Core Features

How I replaced manual input with OCR to increase authentication completion 1.5x

How I replaced manual input with OCR to increase authentication completion 1.5x

Shipped

APP/WEB

B2B SaaS

Timeline

Jun 2023 - July 2023

Jun 2023 - July 2023

My Role

Product Design

UX Research

User Interviews

Product Design

UX Research

User Interviews

Team

1 Product Designer (Me)

1 Product Owner

3 Front-end Developers

2 Back-end Developers

1 Product Designer (Me)

1 Product Owner

3 Front-end Developers

2 Back-end Developers

Tool

Figma

Amplitude

Jira

Confluence

Figma

Amplitude

Jira

Confluence

Overview

Paywork is a business document management platform for small business owners in Korea, many of whom are in their 50s and 60s. Users can create and manage essential business documents in one place, including estimates, transaction statements, and tax invoices.


To access Paywork’s core paid features, including tax invoice issuance, users first had to complete business authentication. However, many users dropped off during this required step and never reached the product’s paid value. This project focused on helping more users complete authentication by reducing its biggest source of friction, manually entering business information. We introduced OCR to automate data entry, making it easier for users to complete authentication and reach Paywork’s paid features.

Key Objectives

Amplitude analysis revealed an overall authentication completion rate of just 41.4%.

The largest losses came at the two manual input steps, which required nine fields in total. The steepest single drop, 31.4%, happened at the business information step. Six of the nine fields (business name, registration number, representative name, address, business type, and category) were already printed on the business registration certificate users had in hand.


User interviews confirmed what the funnel suggested. Re-entering information they already had was the main reason they gave up.

Existing Paywork Business Authentication Flow

Existing Paywork Business Authentication Flow

Amplitude Business Authentication Funnel Analysis

Amplitude Business Authentication Funnel Analysis

Amplitude Business Authentication Funnel Analysis

May 2023 - June 2023

May 2023 - June 2023

Strategy

The goal was to eliminate manual re-entry entirely.

Round 1. Third-party business registry API (Rejected)

We first explored an API that auto-fills fields from a registration number alone.

Testing revealed two blockers. Sole proprietor data, the majority of Paywork's user base, came back incomplete because the API relied on credit lookup systems. And every query was billed whether the data came back complete or not, which meant paying per lookup for mostly empty results at scale.

We ruled it out.

Round 2. OCR (Selected)

OCR resolved both issues. It extracts data directly from the user’s uploaded certificate image, so sole proprietor fields are never missing and there is no per-query cost. It was the option that satisfied both accuracy and cost requirements.

Design Solution

I designed an OCR authentication UX flow where uploading a business registration certificate auto-fills all required fields in one step.


OCR could still misread fields, especially from low-quality photos. So I designed two ways to recover.

A review step lets users check and edit each extracted field before submitting, and a rescan option lets them retake the photo when the extraction itself went wrong.

I designed an OCR authentication UX flow where uploading a business registration certificate auto-fills all required fields in one step.


OCR could still misread fields, especially from low-quality photos. So I designed two ways to recover. A review step lets users check and edit each extracted field before submitting, and a rescan option lets them retake the photo when the extraction itself went wrong.

Impact

Paywork's core users are small business owners in their 50s and 60s who needed to send invoices quickly.


For this group, having to manually type critical business information was not just friction, it was a real barrier before they could use any paid feature. By introducing OCR to remove that barrier, we saw the following results.

1.5x

increase in authentication completion rate

increase in authentication completion rate

41.4% → 62.8%, measured over one month post-launch using Amplitude (July to August 2023).

41.4% → 62.8%, measured over one month post-launch using Amplitude (July to August 2023).

5x

faster completion time

faster completion time

Average completion time dropped from 2m 42s to 30s, measured using Amplitude over the same period.

Average completion time dropped from 2m 42s to 30s, measured using Amplitude over the same period.

Takeaways

The design decision happened before any screen was drawn

The design decision happened before any screen was drawn

Testing the registry API against our actual user base revealed that it could not reliably support sole proprietors, who made up most of Paywork's users. Rejecting that option and choosing OCR shaped the entire solution. Evaluating data sources and technical constraints is part of design, not something that happens before it.

THANK YOU
FOR VIEWING

THANK YOU
FOR VIEWING

THANK YOU
FOR VIEWING