Work

What was built, on what stack, in how long, and what it was for. Clients are named only where they have given written consent; the rest are described without identifying them, which is the default rather than the fallback. No client revenue, booking or fee figures appear anywhere on this site.

Offer and pricing

What the business sells, who to, at what price, and whether it is worth doing at all.

Systems and software

The website, the app, the integrations, and the processes and tools the business runs on day to day.

Customers and demand

Where customers come from, what happens when they arrive, and what brings them back.

Structure and compliance

Entity, records, insurance, and what the rules allow a business to claim. The things that bite later rather than today.

Each entry below says which of the four it covered and what was delivered in each. Most engagements cover two or three. An entry claiming all four is the exception, and the ones it did not cover are named rather than left out.

• ZAHARA Skin and Body

  Build

  A skin and body clinic in North Beach, Perth, with a working business and a website that did nothing for it. Now live on its own domain with the full treatment catalogue, and every route on it ends in a booking.

  The problem was never the design. Nothing on the old site led anywhere, and the booking system customers actually used sat somewhere else entirely, so the site and the business were running in parallel rather than together. The rebuild put them back in the same place. Seventeen treatment pages now carry the catalogue in the clinic's own words, each one ending in a booking, and the booking still happens in the system the clinic was already running, so no customer had to learn anything new and no member of staff had to be retrained. Gift vouchers and workplace massage were given their own routes, because they are different purchases arriving with different questions and burying them in a treatment list loses both. The clinic's email and mailing list were set up in the owner's own accounts from day one rather than created here and handed over later, which means there is nothing to unpick if the clinic ever changes supplier. The slowest part of the job was not the build. It was waiting for photographs.

  Three of four areas covered: · Offer and pricing, Systems and software, Customers and demand

  Client

  ZAHARA Skin and Body

  Stack

  Next.js, Vercel, Resend, Mailchimp

  Timeline

  Brief to live site in three days. Full catalogue and own domain live September 2026

• Poms in Perth

  Partner

  A community of UK families moving to Western Australia, with real trust and no way to earn from it. The work turns an audience living on someone else's platform into a business that owns its own list.

  Emigration has a narrow window in which help is worth paying for: the planning months before the move, and roughly the first two years after it. Inside that window people need a bank, a school, a mortgage, a removals firm and a dozen other things, and they ask the community rather than a search engine. A community sitting on rented land captures none of that, and loses the lot the day the platform changes its mind. The build gives the business its own list, a way to capture people at the moment they ask, and routing to partners who have been checked first.

  Four of four areas covered: · Offer and pricing, Systems and software, Customers and demand, Structure and compliance

  Client

  Poms in Perth

  Stack

  Next.js, Supabase, Vercel

  Timeline

  Live since September 2026, still in active build

• Pietro's Barbershop

  Build

  The first shop trading on Chairhouse, a booking and loyalty product built to serve many barbershops rather than one. Customers book, come back, and pay the shop directly.

  A booking page for one barbershop is a weekend's work. One system serving a hundred shops, where no shop can ever see another's customers or takings, is a different problem, and it is the one worth solving because it is the one that scales. Each shop's data is separated in the database itself rather than by application code remembering to filter, because the day someone forgets is the day every shop sees every other shop. Money settles to each shop directly rather than passing through us, so nobody is waiting on somebody else's payout run to be paid for last week's haircuts.

  Three of four areas covered: · Systems and software, Customers and demand, Structure and compliance

  Client

  Chairhouse

  Stack

  Next.js, Supabase, Stripe Connect, SMS

  Timeline

  First tenant live five weeks from an empty repository

• Georgian Land

  Build

  The public site for a land acquisition business, which grew a gated document library and an investor certification step without ever being rebuilt.

  It began as a marketing site and then needed to do something a marketing site cannot: hand regulated material to the people entitled to receive it, and to nobody else. The tempting version hides the document inside the page and reveals it when somebody ticks a box, which is not a gate at all, because the file reached the browser before the box existed. Here the document does not leave the server until a certification record has been checked and found valid. The site itself never had to be rebuilt to acquire any of that.

  Three of four areas covered: · Systems and software, Customers and demand, Structure and compliance

  Client

  Georgian Land Limited

  Stack

  Vercel, Supabase Edge Functions

  Timeline

  Live, iterated across three months

• Fathom

  Build

  An info-product business built to run end to end on its own: it senses what people are asking for, produces the product, checks it, publishes it, sells it, and withdraws it if refunds spike.

  The question worth answering was whether a business can genuinely run without a person earning attention by hand every day, and the only honest way to answer it is to build one and watch. Each stage can stop the next, so a product failing its own quality check never reaches a storefront, and one customers keep refunding removes itself without being asked. The measurements went in before the verdict rather than after it, because a checkpoint with nothing measuring it is a checkpoint in name only.

  Three of four areas covered: · Offer and pricing, Systems and software, Customers and demand

  Client

  Fathom Money

  Stack

  Next.js, Supabase, AWS Lambda, Vercel

  Timeline

  Sensing to storefront in under three weeks

• Life on God Mode

  Build

  A personal operating system for running a portfolio of businesses: an always-on assistant, scheduled briefings, a content engine, and a written constitution the machine is actually held to.

  Most operating systems for a business amount to a folder of documents nobody reads and a set of good intentions. The interesting part here is not the assistant. It is that every rule the system claims to follow is enforced somewhere a person cannot quietly step around, and that a rule written down but enforced nowhere is logged as a defect rather than tolerated as a policy. It has run every day since May 2026, which is the only test of an operating system that counts.

  Three of four areas covered: · Systems and software, Customers and demand, Structure and compliance

  Client

  HW Legacy Group

  Stack

  AWS, Claude, Telegram, GitHub

  Timeline

  Running daily since May 2026

• Investment platform, document suite, CMS and CRM

  Build

  An investment platform for property and business opportunities in the North East, and the back office that makes it run. The first build, and the one this practice grew out of.

  The visible half is the public site and the opportunity pages. The half nobody sees is the half that decides whether the business works: a document suite, a content system the owner can edit without asking anyone, a CRM holding the pipeline, and the marketing surface feeding it. It has been running and changing since March 2025. A certification gate came later, once regulated material needed to sit behind something rather than on an open page.

  Four of four areas covered: · Offer and pricing, Systems and software, Customers and demand, Structure and compliance

  Client

  HW Legacy Group

  Stack

  React, Next.js, Supabase, Vercel

  Timeline

  From March 2025, iterated ever since

• HMLR search and map tool

  Build

  Search registered property across England and Wales by postcode, street, council area or owner, see the boundaries drawn on a map, and trace corporate owners through to the people behind them.

  Who owns a piece of land is public information and practically very hard to use. The answer is usually a company, that company is often owned by another, and the boundary you care about is a shape on a map rather than a row in a table. This puts the three together, so a search on a street returns the parcels, the registered owner, and where that owner is a company, its officers, controllers and charges. It is the one build here deliberately not on the house stack, because serving national map data and loading bulk registry files breaks the usual model rather than bending it, and an exception has to name the constraint it hits before it is allowed to be one.

  Two of four areas covered: · Systems and software, Customers and demand

  Client

  HW Legacy Group

  Stack

  Python, PostGIS, MapLibre GL, ECS Fargate, CloudFront

  Timeline

  From May 2026

• Henderson HV

  Build

  A corporate site for a high-voltage electrical and instrumentation contractor in Queensland, finished and then deliberately left unpublished.

  Almost everything a contractor's website says about what it can do is a regulated claim, and this business did not yet hold the state licence those claims depend on. So the site was built, reviewed line by line against a written list of what may and may not be said before the licence arrives, and the domain left unpointed. Holding a finished site costs nothing. Publishing one and retracting it costs considerably more than the build did.

  Two of four areas covered: · Systems and software, Structure and compliance

  Client

  EIWS Pty Ltd

  Stack

  Next.js, Supabase, Vercel

  Timeline

  Ten days, built and held

• Eranos Partners

  Build

  The public face of a firm that sources buyers, sellers and financing across physical commodity markets and structures special-situations real assets, with a gated deal room behind it.

  Counterparties in this market arrive by introduction rather than by search, so the site is not there to generate enquiries. It is there to answer the question an introducer's contact asks before a first call, which is whether this is a real operator and what kind of situations it actually takes. That answer has to be short, because the people reading it are busy and sceptical. Behind the public pages sits the deal room, which is an application rather than a page: its own back end, its own access control, and the place a qualified counterparty sees what is actually on the book. Two audiences with opposite needs in one build, and the second is the reason the first can stay brief.

  Three of four areas covered: · Offer and pricing, Systems and software, Structure and compliance

  Client

  Eranos Partners LLC

  Stack

  Next.js, Supabase, Vercel

  Timeline

  Seven days from ideation to live

• Datum (AU)

  Build

  Finds dormant Australian mining and petroleum tenements that already have quantified resources sitting under them, and works out who actually controls each one.

  The information is public and close to useless in the form it is published in. Several state registers, none of which agree on format, and holder names that turn out to be shell companies pointing at other shell companies. The work is turning the registers into one consistent picture, then following the corporate layers until a real controlling party appears. The output is not a licence number. It is a name somebody can approach.

  Two of four areas covered: · Systems and software, Customers and demand

  Client

  Eranos Partners LLC

  Stack

  Next.js, Supabase, PostGIS, Vercel

  Timeline

  From August 2026

• Lodestar

  Build

  A map of who actually moves physical commodities: the producers, refiners, traders and ports, and how they connect to one another.

  Anyone can buy a contact list. The question that matters is where each fact came from and when, because the first time somebody asks how you know something, the answer has to be better than that it was in a spreadsheet. Every fact here carries its source and its date, and nothing can be queued for outreach until it has passed a check standing in front of it. A contact with no provenance is a liability rather than an asset, and the whole design follows from treating it as one.

  Three of four areas covered: · Systems and software, Customers and demand, Structure and compliance

  Client

  Eranos Partners LLC

  Stack

  Next.js, Supabase, Vercel

  Timeline

  From August 2026

• Sextant

  Build

  A database of family offices, wealth managers and private banks, with a layer that decides whether a given firm may lawfully be sent a given communication, before anyone sends it.

  Built alongside Lodestar and deliberately kept apart. The two share a shape, a sourced counterparty graph with a check in front of outreach, but they do not share meaning, and merging two systems because their structures rhyme produces one that serves neither. What matters commercially is that permissibility is written down as rules over the data and evaluated automatically before an approach can be queued, rather than depending on somebody remembering what the rule was.

  Three of four areas covered: · Systems and software, Customers and demand, Structure and compliance

  Client

  Eranos Partners LLC

  Stack

  Next.js, Supabase, Vercel

  Timeline

  From August 2026