Apps & artefacts
Small tools, sharply scoped.
The local-running utilities and educational artefacts I build alongside engagements. Public artefacts live below; client-side tools (catalogue-input automation, internal copilots) ship privately and stay on the merchant's machine.
Built privately, alongside engagements
Client-side tools that don't ship to a public page.
A growing slice of the work is small, local-running utilities I build for merchants — particularly around catalogue-input automation. The shape is usually:
- · Supplier data arrives as PDFs, spreadsheets, or scraped HTML.
- · A small tool runs on the merchant's machine, structures it into Shopify-ready records, and surfaces edge cases for human review.
- · The catalogue data never leaves the building. No SaaS, no vendor lock-in, no extra data-retention policies to negotiate.
- · The merchant owns the tool at the end of the engagement.
These don't appear above because they're client-specific. If you've got a similar bottleneck — supplier data going from "messy file" to "live product" through a human team — talk to me about a Plus-Fit Assessment.
Want a small, focused tool of your own?
The Plus-Fit Assessment is the way in — three meetings to decide whether the tool is the right call, and what "small and focused" actually looks like for your problem.