Supply chain software

// The problem

A distributor tracks purchase orders, supplier confirmations and inbound containers across the ERP, carrier websites and a spreadsheet, so a slipped vessel is found when customers start calling.

// What we would build

A web control tower that joins ERP purchase orders, supplier confirmations and carrier and port milestones into one view per order, with alerts when a promised date slips and a list of the customer orders it puts at risk.

// What is in it

// Stack

• Next.js
• PostgreSQL
• EDI (X12 and EDIFACT)
• Carrier and port tracking APIs
• Microsoft Azure

// The problem

An apparel brand has to show where its cotton and trims come from, past its direct suppliers, and the answer is buried in mill invoices and declarations several tiers down that nobody can check.

// What we would build

A supplier portal where each tier, from the garment factory to the mill and the ginner, declares what it bought and from whom against shipping documents. Each declaration is recorded on a private permissioned ledger the brand, its main suppliers and an independent auditor each run a node of, so the brand sees the chain of custody and nobody upstream can quietly change a declaration once a buyer has relied on it.

// What is in it

// Stack

• Next.js
• Hyperledger Fabric (private, permissioned)
• PostgreSQL
• S3-compatible storage
• Google Cloud

// The problem

A procurement team learns about a supplier's fire, strike, sanctions listing or insolvency from the news, after the orders that depend on it are already late.

// What we would build

An agent that reads news, sanctions lists and public filings every day, matches them to your suppliers and the parts each one makes, and writes a short brief for the buyer. It runs on an open-source model in your own cloud account, because the supplier list, part numbers and spend are commercially sensitive.

// What is in it

// Stack

• Qwen or Mistral (open-source)
• vLLM
• Python
• PostgreSQL with pgvector
• Next.js
• AWS

// The problem

Customers and lenders ask for product carbon and sourcing data, and the sustainability lead collects it from hundreds of suppliers by spreadsheet every year.

// What we would build

A web portal where suppliers answer one shared questionnaire, upload their evidence and carry last year's answers forward, with a review queue for your team and exports in the formats your customers ask for.

// What is in it

// Stack

• Next.js
• PostgreSQL
• S3-compatible storage
• Transactional email service
• Google Cloud

// The problem

Purchase orders, supplier confirmations and carrier milestones arrive by EDI, by email and from four carrier portals, and every customer who asks where their order is gets the answer from a person reading a screen.

// What we would build

One API that states where everything is: orders, shipments, containers and milestones, read from your ERP and your carriers, with webhooks your customers and your own apps subscribe to instead of asking.

// What is in it

// Stack

• TypeScript
• Node.js
• OpenAPI 3.1
• GraphQL
• PostgreSQL
• Redis
• Azure

// The problem

A distributor's demand plan is a workbook of linked spreadsheets that takes a planner two days to refresh each month, and one broken formula can throw off purchase orders for weeks.

// What we would build

A move of the plan to a web app: we take the workbook apart, write down every rule and formula, test the new app against months of past plans, and give planners a screen where sales history, forecasts and purchase suggestions update from your ERP.

// What is in it

// Stack

• Next.js
• PostgreSQL
• TypeScript
• Playwright
• DigitalOcean