WarrenBarr
SEC-01
Advisories
Published findings
OPS-02
Methodology
How an engagement runs
ENG-03
IT & Dev
Build and administer
ARM-04
Software
Tooling I wrote
MSP-05
MSSP
Flat-rate managed
REC-06
Case Studies
Work, in full
WEB-07
Websites
Sites that convert
SUP-08
Gear
Coming soon
DOC-09
Doctrine
What I will not do
WHO-10
About
Who you'd be hiring
Portfolio · Websites & Web Apps

Two shipped builds,
taken apart.

Not templates and not mockups. Both of these are live, both were built from an empty folder, and both are doing real work for a real business right now. Here is what is inside them.

Shipped
02
both still live
Templates used
0
written from scratch
Backends built
2
auth + data, not forms
Handed over
100%
client controls the data
UNIT 01 · HOSPITALITY kalispellgrand.com — live

Kalispell Grand Hotel

A historic 1912 downtown hotel with a direct-booking system it actually owns — instead of renting the customer relationship back from an OTA.

https://kalispellgrand.com
Kalispell Grand Hotel homepage
The public homepage — direct booking above the fold

A full hotel website with a custom guided booking engine, a staff-facing property-management dashboard, an in-browser site editor, and a library of Glacier National Park trip guides built for search.

Not a template — a working reservation funnel wired to swap straight into the live PMS backend. The hotel keeps the booking relationship instead of renting it back from an OTA at fifteen percent.

Specification

TypeSite + booking engine
BackendLive availability + PMS
AdminClient edits in-browser
Design★ Deming by Design
StatusIn service
Booking EnginePMS Dashboard Admin EditorSEO Guides Live Availability
UNIT 02 · LOCAL BUSINESS palmerdetailing.com — live

Palmer Detailing

A one-man detailing business that now runs entirely from a browser — bookings, clients, pricing and schedule, all owned by the operator.

https://palmerdetailing.com
Palmer Detailing homepage
Public site — mobile-first, booking in two taps

Not just a site — a full-stack web app. A fast public booking front end backed by a secure staff dashboard: clients, scheduling, live pricing, and customer self-booking on a real authenticated serverless backend.

The public site pulls live data Palmer controls himself. Zero hardware to maintain, and nothing that stops working if I disappear.

Specification

TypeFull-stack web app
BackendServerless + auth API
DataOperator-controlled
HardwareNone to maintain
StatusIn service
Booking AppStaff Dashboard Serverless BackendAuthenticated API Mobile-First
Why these are built this way

The person who built these also breaks into things for a living.

That is not a fun fact on a bio page. It is the reason the login is where it is, the reason the customer list is not sitting in a third party's database, and the reason there is no plugin stack quietly accumulating vulnerabilities behind your booking form.

Most people who build small-business websites have never had to get into one. I publish security advisories under my own name — you can read exactly how I think before you decide to hire me.

Build

From an empty folder

No theme, no page builder, no twelve plugins each with their own CVE history. Every line is one I chose to put there, which means every line is one I can explain.

Ownership

Your data, your account

Bookings, customers, logins — hosted in your name, exportable any day. If you ever stop working with me nothing switches off and nothing gets held hostage.

Support

My actual phone number

Not a ticket queue, not a chatbot, not a level-one script. The person who wrote the code is the person who answers when it matters.

“A website is just an application with a nice front door. Somebody is going to try the handle. It should be me, first, on purpose.”

Warren Barr · Barr Cyber LLC · Kalispell, MT
The honest comparison

What local businesses get sold, versus what they needed.

There is nothing wrong with a template if a template is genuinely all you need — and I will tell you when it is. The problem is being sold a subscription when what you actually needed was a system you own.

 
The usual arrangement
What I build
Cost shape
A subscription you can never stop paying
Built once, hosted for a few dollars a month
Bookings
A third party takes a cut of every reservation
Direct booking — the customer stays yours
Your data
Lives in somebody else's database
In your account, exportable any day
Support
A queue and a stranger reading a script
The engineer who wrote it
Security
Somebody else's problem until it is yours
Hardened by someone who attacks these for work
How it goes

Four steps, and you are talking to the person doing the work in all of them.

Step 01

A real conversation

What the business actually needs to do online. Sometimes the answer is smaller than you expected, and I will say so.

Step 02

A fixed number

Scope and price agreed before anything starts. No hourly meter, no discovery phase that bills while nothing ships.

Step 03

Built and shown

You see it working on real infrastructure, not as a slide. Changes happen while it is being built, not after launch.

Step 04

Handed over properly

In your accounts, in your name, with the admin access and a walkthrough. Then I stay reachable.

Need a site that actually does something?

From a simple fast business page to a full booking engine with a backend — built by an engineer who also secures what he ships.