Skip to article
James Dimachkie
Menu
All work

Catchwright

Product design, archived project2 min read

I designed Catchwright’s review so a person checks eight fields against the relevant clauses before using the confirmed hourly rates in a pay comparison.

The comparison uses only the four confirmed hourly rates and shows the entered pay, source rate and gap together. A held hourly-rate field keeps the hourly comparison incomplete. This example uses one fictional agreement and memory-only state; I retired the product in July 2026.

A retired product, reconstructed as a demonstration around one fictional PDF; not a compliance tool and not an operating service.

Full scope and limits

Retired July 2026; this September reconstruction uses one fictional digital-text PDF. State stays in memory and resets on refresh. No OCR, arbitrary-document uploads, employer records or production records. Travel and subsistence terms can be captured and exported; eligibility and payroll-line checks are not implemented. The hourly-rate comparison is not a compliance determination. This is not an operating service.

Who did what

Me
I directed the product, made the workflow decisions and chose to retire it. I also directed the September demonstration and its fictional agreement.
AI
Implementation of the September interface around the preserved source modules.
Catchwright’s document workspace, showing a proposed hourly wage with its exact source clause and confirmation controls.
Open full screenshot

A decision and its outcome.

Situation
By July 2026, Catchwright faced a choice between a narrow position among established vendors and a lower-cost entrant, or expansion into a full subcontractor-management platform.
Decision
I decided to retire the product.
Reason
I did not think either position justified continuing to build. I could preserve the engineering without maintaining an operating service.
What changed
I kept the engineering privately and reconstructed the source-confirmation workflow here, including the states that withhold a result.

Check it yourself.

Only confirmed rates reach the comparison.
Open Try Catchwright, choose North or South, use Flag for review on one hourly-rate field instead of confirming it, then go to the comparison: it stays incomplete until that rate is confirmed.
A written number has to be read by a person.
Find the threshold the agreement writes as “sixty (60)”: the demonstration leaves its value empty for you to enter from the clause it shows beside the field.
State lives in memory only.
Refresh after confirming a few fields: everything resets. The PDF is fictional and the product has been retired since July 2026.

Reviewing beside the source

Catchwright was a project for checking contractor paperwork against source documents. This example reconstructs one workflow from its preserved source.

The demonstration reads the digital text of a two-page agreement. As you review each field, the PDF follows the relevant clause and shows the source beside the proposed value. You can confirm a field, mark it absent, or hold it for review. The interface keeps those choices distinct.

Trying the rate comparison

Choose North or South, then review the rates and travel terms. One threshold is written as words in the agreement: read the clause and enter the value yourself. Review the confirmed terms together, then attest that you checked them against the agreement.

The sample-pay comparison uses only hourly rates you have confirmed. Enter matching pay, then change a paid amount to see the difference. Clearing an input stops that comparison until the value is complete. You can download the confirmed terms and comparison as JSON files.

The fictional straight-time comparison shows entered pay of 52 dollars, a confirmed source rate of 56 dollars, and a four-dollar hourly gap.
A sample comparison after confirmation. The entered pay, source rate, and hourly difference remain visible together. Open full image

What I kept from the original implementation

The document-reading, confirmation, export, and fixed hourly-rate rules come from thirteen archived source modules, preserved byte-for-byte in the recovery package. The responsive interface is a new demonstration around that implementation.

Why I retired the product

I retired Catchwright in July 2026. I chose not to expand it into a full subcontractor management platform or compete for a narrow position between established vendors and a lower-cost entrant. I preserved the engineering privately and stopped pursuing the operating product.

Return to all work
Next project

Sandy Pines Nesting Place

I directed a site for a retreat still in planning, so visitors can compare five proposed stays and find the details still being worked out. Booking and signup are not yet available.