Built from real orders.
Made for the next chapter.

The business today

Personalised products, with paying customers.

We turn photos of pets, children and families into custom keepsakes, starting with acrylic shoe charms. Customers order through Etsy, send their photos and review a design proof before production.

Our products and ordering process have been tested through real sales, with the strongest demand from the United States, Canada, Australia and the United Kingdom. Our public Etsy shop shows the products, customer reviews and sales history behind the business.

The problem we're solving

A small order can still mean a lot of work.

Each custom order involves interpreting a request, preparing images, coordinating proofs, communicating with the customer and getting the right files into production. Repeating that work for every individual or small-batch purchase can consume the order's margin.

Our founder handled these tasks before building automation. That experience determines what the production hub needs to do: bring the order, artwork, proof and fulfilment steps into one repeatable workflow.

A production hub used for real orders.

Built with Claude Code, our internal pipeline connects the following parts of the order process. This is a description of the workflow, not a public software demo.

1. Order sync & pricing

   Bring Etsy orders and pricing into the production workflow.

2. Photo preparation & proofs

   Prepare customer images and the design proof used to review the order before printing.

3. Print-ready files

   Prepare the production files for the customer's custom design.

4. Shipping coordination

   Connect fulfilment work with the Korea Post shipping API.

How Claude is involved today: Claude Code is the development tool used to build the hub. The model-powered API features below are the next integration phase; we do not describe them as already deployed.

Give each request a clearer path to production.

We plan to use Claude API credits to develop and evaluate specific tasks inside the order workflow. The immediate focus is customer requests, message drafts and pre-print checks.

Our planned approach keeps message drafts and flagged issues under human review. Image-quality measurements and print-file validation also require dedicated checks; a model review alone will not establish print readiness.

What comes next

Prove the workflow, then expand.

Our first priority is making the internal workflow reliable for our own orders. We plan to compare time spent per order, revision counts and API cost per order as these features are introduced. These are evaluation goals, not measured results.

From there, we want to support more personalised products and make repeat designs and group orders easier to manage. We're building around demonstrated customer demand and the repetitive work we encounter in production.