Retail software

// The problem

An apparel retailer with stores and a website runs its online shop on a theme it has outgrown, and customers keep asking for an app with their order history and in-store stock.

// What we would build

A headless storefront on your commerce platform's APIs, with an iOS and Android shopping app sharing the same catalogue, cart, accounts and loyalty, and store stock shown live so customers can reserve and collect.

// What is in it

// Stack

• Next.js
• React Native
• Shopify Storefront API or commercetools
• Algolia
• Stripe
• AWS

// The problem

A growing online brand's support inbox is mostly order status, returns and sizing questions, and response times stretch every time a promotion goes out.

// What we would build

An agent in chat and email that looks up the order, starts a return within your policy, answers sizing from your own size guides and hands anything unusual to a person with the history attached. It runs on a frontier model through its API, which handles high volume well and is the quickest to start; only what each answer needs is sent.

// What is in it

// Stack

• Frontier model API
• Python
• Next.js
• PostgreSQL with pgvector
• Zendesk or Gorgias API
• DigitalOcean

// The problem

A sneaker and streetwear label sees its products resold every day beside counterfeits, and resale buyers have no way to check that an item is genuine or who owned it before.

// What we would build

A digital certificate issued as a token on a public chain when an item is sold, bound to its NFC tag, which passes to the next owner on resale, with a web page where anyone can check an item. If you only need a genuine-or-not check and never track resale, a signed record in your own database is simpler and cheaper, and we will say so.

// What is in it

// Stack

• Solidity
• Base (Ethereum layer 2)
• Next.js
• NFC tags (NTAG 424 DNA)
• PostgreSQL

// The problem

A brand runs limited releases through its Discord, and resellers' throwaway accounts flood the raffle while real fans miss out and moderators burn out.

// What we would build

A Discord bot that runs drop raffles with entry rules you set, links Discord accounts to store accounts, screens out duplicate and throwaway accounts and sends winners a single-use checkout link.

// What is in it

// Stack

• Discord API (discord.js)
• Node.js
• PostgreSQL
• Shopify Admin API
• DigitalOcean

// The problem

A brand sells through wholesale buyers and two marketplaces, and every one of them wants the catalogue, the stock and the order updates in its own format, by spreadsheet, on a schedule somebody has to remember.

// What we would build

One API your buyers and marketplaces call for themselves: products, prices, stock and orders, with a key and a sandbox each, webhooks when stock or an order changes, and a developer portal they can read without asking you.

// What is in it

// Stack

• TypeScript
• Node.js
• OpenAPI 3.1
• PostgreSQL
• Redis
• AWS

// The problem

A retailer sells in stores, online and on two marketplaces, and its buyers see sales and stock for each channel separately, so they reorder too late in one place and discount too early in another.

// What we would build

A dashboard loaded every night from your store platform, point of sale and marketplaces, showing sales, stock cover and margin by product across every channel, with alerts for products about to run out and slow movers worth acting on.

// What is in it

// Stack

• PostgreSQL
• dbt
• Airbyte
• Metabase
• DigitalOcean