WELLINSTANCE BY GOODFOLK

sp_Blitz output in. A client-ready health-check report out.

You already run sp_Blitz. Your client can't read its output — so you spend an hour (or three) turning a results grid into a document you can put your name on. This pilot does that part: send us the CSV from one sp_Blitz run, get back a finished health-check report — your branding on the cover, an executive summary your client will understand, every finding explained in plain English and sequenced into an action plan, and the complete findings attached as evidence.

$29

One report, for one instance

One instance

Per report

3 business days

Delivered as a PDF

Your branding

On the cover

Buy the pilot report — $29

One report, for one instance — $29 one-time. A second report is a second purchase.

What the $29 buys

One report, for one SQL Server instance, from one sp_Blitz output file submitted in our published format. Delivered as a PDF within 3 business days. Produced by a fixed, documented process from sp_Blitz's findings — the same report, the same way, every time.

What it is not

Not a consultation (no calls), not remediation (we don't fix anything), not bespoke analysis (no custom investigation beyond your submitted output), and not a certification of your server's health. If what you need is an expert opinion on a specific performance problem, this isn't it — and we'll tell you so rather than take your $29.

Why $29, and why a pilot

We're testing whether this report is worth paying for as a product — the same report from the same input, no heroics. If it isn't useful to you as delivered, the honest answer helps us more than a polite one, and the delivery includes one question we'd like you to answer.

How to submit

One instance per report. Follow these steps exactly — the format is fixed and published so every report is produced the same way.

2
Install the FULL First Responder Kit (all scripts) on the instance. A sp_Blitz-only install silently produces incomplete output, with no warning in the results — the full kit is a hard requirement.
Run this on the target instance:
```
EXEC dbo.sp_Blitz @CheckServerInfo = 1;
```
Save the full result set — unfiltered, unedited — as a single CSV (in SSMS: right-click the results grid → Save Results As → CSV).
Email the CSV to healthcheck@goodfolkdigital.com with the subject line: Pilot submission — [your instance label]. In the body, include: the First Responder Kit version you ran; the instance label as it should appear in the report (a nickname like "Client A — Production" is fine and encouraged — the real server name is not required); the instance's role in one line (for example, "line-of-business app database server"); and, optionally, your business name as it should appear on the cover, a logo file, one accent colour, and the client name as it should appear.
We confirm within 1 business day whether your CSV is readable. Your 3-business-day delivery clock starts at that confirmation.

Never send credentials of any kind — no logins, no connection strings with passwords. Nothing in this workflow needs them.

What you send us, and what happens to it

You run Microsoft's and Brent Ozar Unlimited's free sp_Blitz script yourself, on your own server, and send us only its output file. We never connect to your server, and we never need — or accept — any password or login. sp_Blitz output describes server configuration and health; it can include database and file names. If you'd rather not share any particular name, redact it before sending — it won't change your report. Your file is used to produce your report and nothing else: not shared, not sold, not used to train anything. We delete your input file and working copies within 30 days of delivery; your finished report is yours to keep and send to your client. The report is generated from sp_Blitz's findings — the industry-standard First Responder Kit by Brent Ozar Unlimited (MIT-licensed) — and every report says so.

See a full sample report

SAMPLE — fictional instance

This sample report was produced from a test instance seeded with realistic faults, for a fictional client and a fictional consultancy, so you can see exactly what a paid report looks like. The findings are real output from the diagnostic named below; the names, branding, and business details are invented.

SQL Server Health Check

Meridian Freight Lines — Production (MFL-SQL01)

Prepared for: Meridian Freight Lines
Prepared by: Harborline Data Services
Instance: Meridian Freight Lines — Production (MFL-SQL01)
Report date: 6 November 2026
Diagnostic run: 6 November 2026, 12:50 (server time)
Basis: sp_Blitz output submitted by the DBA — one run, one instance

Prepared with WellInstance by Goodfolk.

Executive summary

What this server does. MFL-SQL01 is the database server behind Meridian Freight Lines' dispatch, load-planning, and billing application — the system roughly 120 staff use to book loads, plan routes, and invoice customers. It is a small server (4 processors, 3 GB of memory) holding three working databases totalling about a quarter of a gigabyte.

The overall picture, in one paragraph. The server is running a current, fully patched version of SQL Server and is doing its day-to-day work. The concern is not how it runs today — it is what happens on the day something goes wrong. As of this check, no database on the server has ever been backed up, the built-in corruption check has never completed on the server's own system databases, and no one is set up to be alerted if the server hits trouble. Those are fixable, inexpensive problems — but until they are fixed, a single hardware or storage failure could mean losing the dispatch and billing data outright rather than restoring it.

The three things to do first

1 · Back everything up — Take the first full backup of every database, and start regular transaction-log backups for DispatchOps. Today there is nothing to restore from.
2 · Run the corruption check — Run DBCC CHECKDB across the databases and schedule it. It has never run on the system databases, so silent storage corruption would currently go unnoticed.
3 · Set up alerts — The SQL Server Agent service is stopped and no alert operators exist. Configure both, so a severe error emails a human instead of waiting to be discovered.

What this report is — and is not. It is a point-in-time health check: the findings of one diagnostic run on 6 November 2026, organised and explained. It is not monitoring, not a security audit, and not a certification that the server is healthy — the absence of a finding is not a guarantee.

Engine: SQL Server 2025 (RTM, Cumulative Update 10), version 17.0.5035.5 — Enterprise Developer Edition (64-bit), on Ubuntu 24.04
Hardware: 4 logical processors · 3 GB physical memory · virtualised (hypervisor)
Data: 3 user databases, 0.23 GB total file size
Findings: 41 findings in the diagnostic output: 10 at priority 1 (the diagnostic's most urgent), 4 more at priority 10, 27 at lower bands, plus 18 server-information rows — all reproduced in full in the report's appendix.

SAMPLE — fictional instanceSend me the full sample report

Clicking opens your email client — no form, no signup. We reply with the complete sample PDF.

Refunds, in plain words

If your file isn't usable sp_Blitz output, we refund in full — no report.
If we miss the 3-business-day turnaround, we refund in full and still deliver the report when it's ready.
If the report is delivered as specified and you judge it not useful, there is no refund — but tell us honestly why. That answer is recorded and counts.
To ask for a refund, email healthcheck@goodfolkdigital.com.

Buy the pilot report — $29