Case study · greyhouseops.com · published August 3, 2026

PruneQ built the entire Greyhouse Operations website

Greyhouse Operations is Breana Yarnall's med spa operations consultancy. Its website at greyhouseops.com is PruneQ's work, all of it. You can open it while you read this, and everything below is something you can check yourself.

By Christopher Buchner, founder of PruneQ. Published with the client's permission to name her, her business, and her site.

What was delivered

There was no existing site to clean up. PruneQ wrote the copy, built every page, designed the identity, set up the analytics and the search tooling, and moved the business onto its current domain.

A homepage that says what the business does, who it is for, and how the work starts.
An offers page describing three engagements and what each one delivers.
A digital contact card with a downloadable vCard, for handing over in person.
A fifteen question Operations Scorecard that runs entirely in the visitor's browser.
A sample deliverables page showing the format of the findings, roadmap, KPI dashboard, and leadership meeting notes a client receives.
An insights library with four articles, plus a press page, a resources page, and a talent network page.
Privacy, terms, and cookie pages, with a cookie consent control.
The move from the old domain to greyhouseops.com, including the redirects that keep older links working.

What is checkable, 2026-08-02

Every line below came from a read-only check of the live site on 2026-08-02. None of it is a score, and none of it is a number PruneQ invented.

Pages live: 16 public pages, plus robots.txt and llms.txt. Every one of the 18 returned HTTP 200 on a read-only check, 2026-08-02.
Old links still work: The bare domain and both hostnames of the previous domain redirect to www.greyhouseops.com and keep the path, so links published before the rebrand still land on the right page.
Security headers: Live responses carry a content security policy that starts from default-src 'none', HSTS for two years including subdomains, X-Frame-Options DENY, X-Content-Type-Options nosniff, a strict referrer policy, and camera, microphone and geolocation switched off.
Machine-readable identity: The homepage publishes structured data describing the business as a professional service, with organization, person and website entries, three service and offer pairs, and a nine question FAQ block. An llms.txt summary is published as well.
Analytics: Google Analytics 4 is installed in the client's own account, and the content security policy allows only Google's own measurement domains.
Scorecard privacy: The scorecard has no form element, no email gate, no network request, and no browser storage in its script. Answers are scored on the visitor's device and never leave it.

The client owns all of it

The domain, the hosting account, and the analytics property are in the client's own name, not PruneQ's. That was a deliberate build decision and it is now the standing rule for every PruneQ build. If she ever stops working with PruneQ she keeps the site, the domain, the history, and the logins, and there is nothing to hand back because nothing was ever held hostage.

The site is plain static HTML with no build step and no database, which is why a page edit is minutes of work rather than a release process. That is the right choice for a small site and the wrong choice for a large one, and PruneQ will say which one you have before quoting.

The part that had to be redone

An early draft of the About section carried a line that read like a machine wrote it. It was caught in review and cut, along with the punctuation habits that come with it. Because of that, a human read-aloud pass is now a required step in every PruneQ build, not an optional polish at the end.

This is on the page on purpose. A supplier who only ever publishes the good parts is telling you what they want you to believe, not what happened.

What the client says

There is no testimonial here yet, and this space is left empty rather than filled with something PruneQ wrote. If Breana Yarnall gives one, it will appear here in her own words, with a date, and nothing else will change on this page.

PruneQ does not write quotes for clients, does not publish a paraphrase as a quote, and does not buy or trade for reviews. An empty space is the honest version of not having one yet.

What this does not prove

Rankings. No position, impression, or click data is cited here. Search results are decided by Google, not by PruneQ.
Traffic. Analytics is installed and the account belongs to the client, so the numbers are hers. None are published here.
Leads or revenue. This page makes no claim about inquiries, bookings, or money. That claim would need data PruneQ does not own, and publishing it would be the exact move PruneQ tells buyers to distrust.
AI citations or recommendations. Crawler access and machine-readable identity were built in from day one. Being cited is a separate thing, and nobody can promise it.
That your site would go the same way. This is one build for one business. It is evidence that the work gets done and gets done carefully, not a forecast.

There is also no before and after here, because there was no before. This was a build, not a cleanup, so there is no earlier version to compare against. Anyone showing you a before and after for a brand new site is comparing it to nothing. The reasoning behind all of this is written out in what nobody can promise.