WorkGoldmark × Draft Pick · my own business

Two brands, one shop, and every order accounted for.

Goldmark and Draft Pick needed one online shop that could sell for two brands. I built it, put it in front of trusted customers, then checked it against my own build standard and fixed four issues before it took a single real payment.

The Goldmark × Draft Pick website home page
Live site · goldmarkdraftpick.com

Start here: this one is mine. Goldmark Craft Beers and Draft Pick Brewing Company are businesses I own, and I built both storefronts myself. Read this as a worked example rather than an independent reference. What you get in exchange is the full picture, including exactly what I fixed before launch.

01The business

Goldmark has brewed cask beer in Poling, near Arundel. Draft Pick is a newer keg brand brewed alongside it, first released in September. Same brewery, same small team, two brands with different beers and different customers.

02The challenge

Goldmark's old Squarespace shop worked. It took orders every week. But it was built around one brand, and Draft Pick was about to go to market as a second one. Moving off it meant rebuilding the storefront rather than restyling it: one site that could carry both brands without either one feeling like a guest on the other's shop.

Two brands, one shop, one launch window, and a build that worked perfectly every time I clicked through it.

That is the state most small business websites launch in. Somebody builds it, somebody checks the page loads, somebody puts a test item in a basket and watches the payment page appear, and everyone agrees it is finished. The parts that only fail under real conditions stay broken until a real customer finds them. The failure mode is not a crash. It is a customer who pays and then hears nothing.

03What I built

One site for both brands, with a shop for each and a single basket and checkout between them.

  • A page for every product, with sizes and colours where they apply.
  • A basket that offers collection from the brewery or delivery by post, and shows the VAT.
  • Postage worked out from the weight of what is in the basket, not a flat rate guessed at launch and argued about afterwards.
  • Consumer terms and a returns and cancellation page, written from scratch.
  • Sign-in, and an admin portal built into the site, where orders are managed.

On 8 August it went into pre-production. I ran it fix-forward: a small group of trusted customers and users used it for real and told me what they found, and I fixed as I went.

04How I did it

Using a site is a good way to find what is annoying about it. It is a poor way to find what is broken underneath. So while the site was in pre-production, and before the new checkout took a real payment, I ran the Build Standard over my own work.

That is a less comfortable exercise than it sounds. A standard finds defects you were not looking for, which by definition includes the ones you were confident were not there. A snag list only finds what you already suspected.

What it turned up, all of it in a build I had made myself:

The checkout was not recording orders. No webhook endpoint had ever been registered, so a payment could complete without the application ever learning it had happened. Behind that, the site was connected to a test account at the payment provider that nobody had properly set up, not the business's real one. That is why earlier attempts to connect it had failed. Two gates, both invisible from the front end, and both invisible from the happy path I had been testing.

Diagnosed, fixed, and then proven with an order recorded end to end rather than assumed.

Nobody could sign in. The login, register, forgot-password and reset pages all existed and had all been written. None of them had ever been routed, so /login returned a 404. Nobody had reported it because nobody could get far enough in to notice it was missing. I found the same thing on this site, running the same standard over it. That is how I know it is a property of the platform rather than a lapse on one project.

An open redirect in the checkout. A security defect in the code that creates the payment session, patched before the checkout took real payments. That class of defect is what turns a legitimate checkout link into a phishing vector.

The consumer terms did not properly exist. Written from scratch: cancellation rights, who pays return postage on a change of mind and who pays when the item is faulty, the exemptions that apply to perishable goods, and a commitment on how quickly complaints are answered.

What those four have in common is that none of them shows up on the happy path. You can click through a basket, reach a payment page and see a confirmation screen with every one of them still in place. Trusted customers using the site would not have found them either, which is the point. That is why a written standard finds them and a careful look does not.

05How it runs now

An order arrives as an email in the brewery's shared inbox, so all three of us see it the moment it is placed. Marta, who runs customer engagement, and I pick up most of them. Ethan, our head brewer, can pick one up too.

Everything after that happens in an admin portal built into the site, where each order is worked through to closed. Only people I have given admin access to can reach it, and I manage who that is.

Beer is collection only, from the brewery in Poling, during published hours. Merch goes by Royal Mail, priced by weight band and added to the basket automatically. Every price on the site includes VAT.

That part is not software, and it is half of what made the launch work. A checkout that records an order is only useful if someone knows the order is there and knows it is theirs.

06The result

The site is live at goldmarkdraftpick.com, and the old shop's address now redirects to it. Every feature on the old site has been switched off.

The checkout was proven on 9 September with an order recorded end to end, alongside a sign-in that works and terms that would survive a customer reading them.

The wider point, and the reason this is the first case study on the site: every one of those defects was found by running a written standard over the build, not by being clever about it. The checkout fault had already survived repeated attempts to fix it by someone looking straight at it. The standard found it because the standard asks whether an order was recorded, not whether the payment page loads.

The uncomfortable part is whose build it was. I wrote the standard, and it still caught four things in my own work that I was ready to ship. That is the argument for having one, and it is easier to make with my own business than with a client's, because I can tell you exactly what was broken.

07Questions worth asking about your own business

  1. When did you last see an order recorded from start to finish, rather than a payment page that loaded?
  2. Signed out, on a phone, can you get to your own login page and back in?
  3. If a customer read your terms today, would they know who pays to send something back, and when?
  4. When an order comes in, who sees it first, and whose job is it to close it off?

Start with the diagnostic, or just ask.

Four questions, about a minute, no email needed. If you would rather talk, the first call is free.

I reply within 2 business days.