The work

Three live sites, three platforms, three different reasons

Every site here is one of ours. We built them, we run them and we pay their bills, which is why you can open all of them in full while client work waits on the client's permission.

Each one was built for a different job and runs on different software, and the software was chosen for the job rather than for us. That is the part worth looking at. A studio that builds everything the same way is selling you its habits.

Nothing on this page is a screenshot. Open the sites, read the build stamps, check the dates on the prices.

The sites

What each one had to solve

The interesting question about a website is never what it looks like. It is what would go wrong if nobody thought about it, and what was built so that it cannot.

Tony Pope, Business Broker

tonypope.com.au

Licensed practice

A licensed Queensland business broking practice, with listings, appraisals, a library of articles, and three pieces of software behind the public pages that were built rather than bought.

The risk here is the words, not the code. Everything on it is a representation somebody holding a licence has to stand behind, and appraisal and valuation are not interchangeable when you do. So the build refuses to deploy rather than publish something wrong: twelve guards run before anything goes out, every page carries the exact commit it was built from, and a check runs every two hours against the live site and raises a ticket the moment what is serving stops matching what was approved.

Three things behind it were built rather than bought. A customer record system that takes every enquiry, tracks it through to settlement and drives the marketing and the business listings off the same records. An appraisal tool that produces a defensible figure from a seller’s own numbers. And a live chat that answers on the site, inside written guardrails, with its own gate in the build so it cannot start saying things the licence does not allow.

A broker’s pipeline is the business. Renting it back from somebody else is how you end up unable to leave, so it sits in the same repository as the site and is deployed by the same pipeline.

What it shows. A professional services site where the hard part is accuracy and the record of it, with real software behind the front door rather than a contact form. If your trade is licensed, regulated or insured, this is the shape of the job.

Checkable today

Built on
Eleventy, static, deployed from a Git repository
Hosting
Netlify, with its own serverless functions
Pages
196 in the sitemap, 29 articles
Behind it
Customer records, appraisal tool, live chat
Stamp
In the page source of every page
Watched
Every two hours, against the live address

Built and operated by this studio. Every figure above is readable on the live site.

Dad Gifts Australia

dadgifts.com.au

Catalogue at scale

An Australian gift guide holding 398 ideas from 42 retailers, browsable by budget, occasion, decade and the age of the person you are buying for.

The hard part is that the facts move. A price read in August is not a price in October, and a site that quotes one is making a claim it cannot support. So every price is read off the live product page, the date is printed on the card, and the build refuses to publish a figure older than ten days without a person signing it off. The structured data sent to Google carries the same window, because telling a search engine a price is good for a month while the site calls it stale is two different answers to one question.

Where a link earns a commission it says so on that product, and where it does not it stays quiet. That distinction is per product rather than per shop, so a retailer with one paid link and eleven unpaid ones is never described as a commercial relationship it is not in.

What it shows. A large catalogue where the work is keeping hundreds of moving facts honest, and a site that notices when they go off rather than waiting for a customer to find out.

Checkable today

Built on
React, compiled to static pages before anyone visits
Hosting
Netlify
Pages
529 in the sitemap
Catalogue
398 ideas, 42 retailers
Prices
Dated on the card, refused past ten days
Disclosure
Per product, not per shop

Built and operated by this studio. Every figure above is readable on the live site.

Santas Vault

santasvault.com.au

Shopify, on purpose

A Christmas store selling personalised Santa sacks and gifts. The newest of the three and the smallest, which is what a store looks like in its first season.

This one is here because of what was not built. It runs on Shopify. We can write a checkout, and writing one here would have been the wrong call: the store has to take money reliably for about eight weeks a year, and a custom cart is not paid for once, it is paid for every year afterwards in maintenance, card compliance and the week in December when something breaks and there is nobody to ring.

So the work went where it changes the outcome. The product data, the personalisation options, the postage cut-offs that decide whether a present arrives, and the theme. Shopify keeps the parts that are somebody else’s problem and should stay that way.

What it shows. The platform decision going the other way. Being able to build a thing is not a reason to build it, and a studio that never recommends the off the shelf answer is selling you hours.

Checkable today

Built on
Shopify
Checkout
Shopify's, deliberately
Trade
Seasonal, about eight weeks
Stage
First season, small catalogue
Custom work
Theme, product data, personalisation
Ongoing cost
A subscription, not a maintenance bill

Built and operated by this studio. Every figure above is readable on the live site.

FigureThree sites we built, and the layers a visitor never sees under each one
The three sites drawn as stacks of layers Three isometric stacks side by side. tonypope.com.au has six layers: hosting, a static build, twelve guards, customer records, an appraisal tool and a live chat, with the appraisal tool picked out. dadgifts.com.au has five: hosting, a static build, the catalogue, the price clock and the disclosure rule, with the price clock picked out. santasvault.com.au has four: Shopify, the theme, product data and personalisation, with Shopify picked out because the checkout was deliberately not built. WHAT IS UNDER THE PAGEtonypope.com.au6 layers Hosting Static build 12 guards Customer records Appraisal tool Live chat dadgifts.com.au5 layers Hosting Static build Catalogue Price clock Disclosure santasvault.com.au4 layers Shopify Theme Product data Personalisation THE COLOURED PLATE IS THE LAYER THAT IS THE POINT OF THAT SITE
Every plate is read from the same file the three entries above are written from, so a site that gains a layer gains a plate. The stacks are different heights because the jobs were different, which is the whole argument of this page in one picture.

Side by side

The same three, in one table

Three different platforms is the point. Ask any studio to show you three builds and count how many are the same software wearing different colours.

The three sites, their platform, the constraint each had to solve and what was built for it
SiteWhat would go wrongWhat was built for it
tonypope.com.au A published claim a regulator can read back to you Static build, twelve guards, watched every two hours
dadgifts.com.au Quoting a price that moved three weeks ago, 529 times over Prices dated on the card, refused past ten days
santasvault.com.au A custom cart bought once and paid for every December after Shopify, and no custom checkout

Client work

Where a client build appears on this page

Client work appears on this site under the client's own name, with their written permission. Nothing else appears here.

A file in the repository this site is built from holds the list of permissioned work, and the build refuses to publish a client claim that no name in it answers for. That is what makes it a rule instead of an intention, and it is the same discipline every figure on the three sites above was built under.