WORK THAT CAN BE INSPECTED

The small steps
that make work
work.

A booking that reaches the right place. A payout that adds up. A packing slip that helps the person holding it. I build practical workflow pieces you can test before we talk scope.

Two browser-local demos · synthetic data · source included
02Runnable examplesEdit inputs and inspect outputs
01Shopify sampleDev-store rendering checked
OPENInspectableFixtures, code, and verification notes

THE WORKING SAMPLES

Try the edge cases.
See the decisions.

These examples run in this page, using fictional records. Edit the inputs, run the logic, and download the result. They show how I structure a workflow; they are not connected to a live account.

01 / CALENDAR + CRM

A booking handoff
with a paper trail.

A lead comes in. The handoff checks the details, avoids repeat records, spots occupied time, then writes a local booking and audit event.

INTERACTIVE · SYNTHETIC
A
Send a requestAll times are UTC
B
Inspect the resultLocal demonstration records only
MOST RECENT RUNReady to run

Choose a scenario or edit the request and process it.

What it proves Input validation, deduplication, time conflict checks, inspectable records and calendar export.Download booking logic
02 / ORDER RECONCILIATION

Find the line
that doesn’t add up.

Compare order totals against settlement net plus fee. The tool separates matched rows from missing, duplicate, unknown, invalid and mismatched records.

INTERACTIVE · SYNTHETIC
A
Compare two CSVsPaste or edit the sample data

Amounts use a dot for decimals. This generic format is an example, not a payment-provider export adapter.

B
Review exceptionsExact cents, clear categories
—Orders
—Matched
—Exceptions

Run the sample to inspect its rows.

Reconciliation results
OrderStatusDifference
No results yet
What it proves Quoted CSV handling, exact minor-unit arithmetic and explicit exception reporting.Download reconciliation logic

THE EXISTING SHOPIFY SAMPLE

03 / PICK + PACK DOCUMENT

Useful in the
hands of a packer.

A compact Order Printer template that puts the pick and pack information in a clear reading order. Built as a fictional sample, then rendered in a Shopify development store on 30 September 2026.

01Preview the pageFictional order details; no buyer data.
02Review the evidenceDev-store rendering verification and limits.
03Get the templateExisting $25 Ko-fi product listing.

The store test used a simulated transaction. This is not a paid client deployment.

FICTIONAL SAMPLEORDER PRINTER / 01
Fictional Shopify pick and pack document preview
Fictional template previewDownload preview ↗

HOW A SMALL PROJECT STARTS

Clear scope.
Visible handoff.

A compact workflow should be easy to test and easy to take over. I start with one concrete input, one expected output and the failure cases that matter.

01 / DEFINE

One useful slice

Agree on the source format, target result and acceptance checks before work begins.

02 / BUILD

Working logic

Implement the happy path and the awkward cases, with sample data and a reviewable test run.

03 / HAND OVER

Files you can keep

Deliver source, run steps and a plain account of what was verified and what still needs access.

Look under the hood.The demos ship with source, fixtures, tests and local verification notes.Source includes a localhost webhook receiver with durable replay handling; browser and receiver states are separate.
Download source package ↓Download run instructions ↗

START WITH ONE BOTTLENECK

Have a handoff
that keeps sticking?

Send a redacted example of the input, desired output and what goes wrong. I’ll suggest a small first slice and acceptance checks.

No passwords, API keys or customer data.

PROPOSED FIRST STEPFixed-scope pilot
from $75

Price and deliverables are agreed in writing before work. Client credentials and any ongoing provider costs are separate.

Send a redacted example copperglassqa@atomicmail.ai