# Paperwork case study: shipping an opinionated cross-platform product

URL: https://wonderful.so/blog/paperwork-case-study
Markdown URL: https://wonderful.so/blog/paperwork-case-study.md
Content type: Case study
Published: 2026-04-03
Updated: 2026-04-03
Author: Rulian at Wonderful
Asked by: Rulian
Tags: Case Study, AI, Products

## Question

Paperwork case study: shipping an opinionated cross-platform product

## Answer

Paperwork is the software version of my own project-management beliefs.

I built it because I think a lot of teams are suffocating under process they do not need. Too many tickets. Too much ceremony. Too much management theater around work that should feel lighter and clearer.

Paperwork was my attempt to build the opposite.

## The Build

I started it in late January 2026 and finished it in March 2026. I spent roughly 150 to 200 focused hours on it.

Without AI, I would estimate something closer to six months of full-time work and north of $60,000 for the same scope, especially because it involved multiple platforms.

With AI, I had a proof of concept in about a week. After that, the work became product iteration: refining the idea, tightening the value proposition, and improving the feel of the product.

## Where AI Helped

AI helped most with implementation speed. My product opinions were already strong. The leverage was in moving faster through the code, not in discovering the philosophy.

The more important work was mine: deciding what belonged in the product, protecting the framework from feature bloat, choosing the stack and architecture, and keeping the product simple without making it weak.

## What It Proves

Paperwork is useful proof of how I like to work. Strong opinion. Clear scope. Product restraint. Cross-platform delivery without turning the thing into mush.

It is live now, launching, and already getting positive early feedback. More than anything, it proves that speed is useful only if you still know what to leave out. That is the same argument behind my [MVP development approach](/services/mvp-development) and why I prefer [working in phases](/services/fixed-price).