twimco.Let’s talk ↗︎
Menu
Selected work / Paddle8

The winning bid was only the beginning.

TWIMCO built Paddle8’s fine-art auction and marketplace platform, connecting real-time bidding with the shipping knowledge needed after a sale.

A marketplace that follows throughTWIMCO / Engineering the whole product
Fine art / Physical objects
From the auction room to the real world
Two sides of one transaction

The bid.
And everything after.

01
Real-time bidding

The moment of the sale

02
Shipping API

The knowledge behind fulfillment

Built before the AI era
Engineering for the auction people see and the operation that fulfills it.
The challenge
Connect a live auction to the practical work after a sale.
What we built
A fine-art marketplace, real-time bidding and a shipping API.
The foundation
Pre-AI engineering grounded in how the business operated.

An auction moves quickly. An artwork moves carefully.

Paddle8 was a fine-art auction house and marketplace. The online experience had to support buyers placing bids while the business also dealt with the practical work of moving valuable physical objects after a sale.

TWIMCO built the platform from the ground up. Our work included the real-time auction bidding engine and the operational systems behind the transaction. Those two parts put different demands on the software, but belonged to the same customer experience.

Build for the moment a bid is placed.

Live bidding sits at the center of the auction experience. Buyers need a system that can keep up with the event as it unfolds. Building that engine meant treating the transaction itself as a core part of the product, alongside the marketplace through which people encountered the work.

The engineering scope followed the business beyond that moment. A winning bid creates another set of responsibilities, including understanding how the artwork can reach its buyer.

Inside the engineering
  1. 01Shipping spreadsheets
  2. 02Route knowledge
  3. 03Shipping API
  4. 04Marketplace access
Operational knowledge became something the product could use through a defined software interface.

Turn shipping knowledge into something the platform could use.

Behind the sale, shipping depended on knowledge held in spreadsheets of routes. That information was part of the business’s operating expertise, but the platform needed a way to use it.

TWIMCO turned those spreadsheets into a shipping API. The change gave software a defined way to access operational knowledge that had previously lived in a separate working format. It connected the auction product to the logistics after the sale.

Carry the transaction into the operation.

Paddle8’s case brings together two concrete pieces of work: a real-time bidding engine and a shipping interface built from existing operational information. The point of connecting them was to make the platform account for the business that fulfilled the sale.

This was pre-AI engineering. The useful change came from understanding the process, choosing where software could take responsibility and making the relevant information available at that boundary.

Look beyond the feature that wins attention.

For founders building marketplaces, the visible transaction is often only one part of the delivery challenge. The operating knowledge behind it deserves the same attention as the customer interface.

Paddle8 demonstrates TWIMCO’s willingness to work on both: the experience customers come for and the less visible systems the business depends on. Bringing those responsibilities into scope early helps expose the work that might otherwise be discovered only after the product is built.

Related expertise

twimco.

What has to happen after your customer clicks buy?
Tell us what you’re building.