Skip to content
SaaSQuillSaaSQuill

Selected work

Case studies

These are anonymized studies of real categories of systems we build. We don't publish client names without permission, and we don't invent performance numbers — what you'll find here is the actual engineering: the problem, the approach, and the system that resulted.

E-commerce · Marketplaces

Multi-Channel Customer Support Platform

Problem

A retailer selling across a storefront and multiple marketplaces handled support from separate inboxes. Agents had no shared view of a customer's orders or history, and issues raised on one channel were invisible on the others.

Approach

We shadowed the actual support workflow first: where requests arrived, what agents had to look up, and where resolutions stalled. The design followed the workflow — one queue, with order context attached before an agent ever opens the ticket.

Solution

A support platform that ingests requests from email and marketplace channels into a single ticket queue, links each ticket to the matching order and customer record, and tracks issues through templated resolution workflows with role-based access for the team.

Outcome

Support now runs from one system instead of five tabs. New agents onboard onto a single tool, nothing depends on a personal inbox, and every issue has an owner and a state.

  • Node.js
  • SQLite
  • IMAP/email ingestion
  • Marketplace APIs
  • Role-based auth

Wholesale · B2B

Wholesale & Dealer Management Platform

Problem

A growing brand's wholesale side ran on spreadsheets and email threads: dealer-specific pricing maintained by hand, orders transcribed manually, and no self-service view for dealers of their own history or balances.

Approach

We treated dealers as first-class accounts rather than a discount code. The system had to encode the pricing rules that previously lived in one person's head, and give dealers a portal that answers their questions before they email.

Solution

A dealer platform with tiered account pricing, self-service ordering against live product data, order history, and an admin side for managing dealers, terms and catalogs — integrated with the existing storefront rather than replacing it.

Outcome

Wholesale orders arrive structured instead of transcribed. Pricing is applied by the system, not by memory, and the wholesale channel can grow without growing its admin overhead.

  • React
  • Express
  • SQLite
  • Storefront integration
  • CSV import pipelines

Live selling · Fulfillment

Live-Commerce Operations & Shipping System

Problem

A live-selling operation compressed hundreds of orders into short broadcast windows. Labels were generated one by one after each show, packing was error-prone, and reconciling sales against inventory took the rest of the night.

Approach

The constraint was pace: everything had to keep up with the stream. We designed the workflow around capturing sales the moment they happen and pushing each one straight through to a printable label and a packing queue.

Solution

An operations tool that captures live sales as they occur, prints shipping labels in real time during the show, feeds a packing queue with per-order manifests, and reconciles sold items against inventory when the stream ends.

Outcome

Label printing moved from after the show to during it. Packing runs from a queue instead of a handwritten list, and post-show reconciliation became a report instead of a project.

  • Node.js
  • WebSockets
  • Carrier/label APIs
  • Thermal-printer workflow
  • Inventory ledger

E-commerce · Shopify

Large-Catalog E-commerce Infrastructure

Problem

A Shopify store with thousands of SKUs had outgrown manual catalog management. Product data, images, pricing and stock lived across exports and spreadsheets, and every bulk change was a risky, hours-long chore.

Approach

Rather than fighting the platform, we built the management layer above it: structured catalog data as the source of truth, with controlled pipelines pushing changes to the storefront.

Solution

Catalog and inventory tooling for bulk product management — categorized SKUs, image handling, stock ledgers with reorder signals, and import/export pipelines that make thousand-row updates a reviewed operation instead of a leap of faith.

Outcome

Catalog changes that took an afternoon of spreadsheet surgery became structured, reviewable operations. Stock levels are tracked in a ledger, not estimated from memory.

  • Shopify APIs
  • Node.js
  • SQL stock ledgers
  • Import/validation pipelines
  • React admin UI

Operations · Internal tools

Internal Team & Workflow Management Platform

Problem

A production business coordinated work assignments, quality control, payouts and team communication across chat messages and paper. Nothing was auditable, and scaling the team meant scaling the chaos.

Approach

We mapped every step from job assignment to payout, then built the platform to mirror that flow — including the role boundaries: what managers control, what team members see about themselves, and what requires an approval.

Solution

A role-based internal platform covering job assignment and tracking, quality-control review queues, a payout engine with per-person ledgers and deductions, self-service member portals, and audit trails on money-touching actions.

Outcome

The operation runs on one system with a shared, auditable record. Payouts compute from ledgers instead of being reconstructed, and each role sees exactly what its job requires.

  • React
  • Node.js
  • SQLite (WAL)
  • Role/permission engine
  • Append-only ledgers

Want the version of this for your business?

If one of these problems sounds familiar, the system behind it can be shaped to your operation. Tell us what yours looks like.

Tell Us What You're Building