Spread.co | Client Work

The build

Spread.co is a fully custom SaaS web application for an organic grocer, built from the ground up rather than assembled from a storefront template — because the ordering rules the business actually runs on cannot be expressed in one.

It is Postgres end to end: Supabase for data, auth, storage and realtime, Vercel for rendering, and no separate application tier to keep alive. The one exception is deliberate — the GIS boundary pipeline runs as scheduled GitHub Actions, off the request path, because chunking and joining tens of gigabytes is not work a page load should ever wait on.

Geography, commerce, and the pipeline between them.

Capability-driven region gating

Regions are PostGIS polygons — colour-coded and boundaried on the map — each carrying its own capacity ceiling, so availability reflects what the business can genuinely service rather than a postcode list that goes stale.

Worldwide smart address lookup

Addresses resolve through geocoding and smart lookup at global scale, so a customer types an address and the system knows which region it falls in.

50 GB of boundary data, off the request path

ADM0 through ADM3 administrative levels and Australia's G-NAF among them, chunked, built and joined into Postgres by scheduled GitHub Actions.

Stripe-synced subscription tiers

A tier builder synced directly to Stripe, with product listings wired through checkout and webhook reconciliation, plus free trial tiers.

Public and members-only, switched platform-wide

The whole platform moves between public and members-only, alongside saved favourites and an inbuilt CMS for the marketing pages and policy sections.

Lifecycle email through Make and Resend

Transactional email through Make and Resend across the grocery lifecycle — forgotten items, abandoned carts, and upcoming weekly reorder reminders.

An organic grocer, built properly.