WINT.WIN™

Two humans, zero buzzwords

Two engineers walk into your server room.

There’s no punchline. That’s just how we work. One of us does the job. The other one watches and says “wait — what about this?” You’d be surprised how often that one question saves a whole bad week.

Tell us what broke Why two, though?
Engineers per job
2
Bus factor
2
Times we’ll say “synergy”
0

Standards we’re working toward

We’re putting the work in on these now. When there’s a certificate behind one, it’ll show up here with its number and the body that issued it — that’s the only kind of badge worth having.

  • ISO/IEC 20000-1 IT service management In progress
  • ISO/IEC 27001 Information security In progress
  • ISO/IEC 42001 AI management systems In progress

01 — Why two?

Nobody should be the only one
checking their own work.

Pilots fly in pairs. Surgeons don’t work alone. Nobody calls that overkill. The mistakes that cost real money are the ones nobody was looking for. Somewhere along the way, IT decided one tired person at 11pm was fine. We never believed that.

  1. 01

    You explain it once

    Both of us are on the call. We hear the same story. Then we compare notes before anyone touches a thing. A lot of wrong guesses die right there, before they cost you a dime.

  2. 02

    One drives, one watches

    We work side by side instead of taking turns. One of us is elbow-deep in it. The other checks it against the plan, writes down what changed, and keeps the undo button ready.

  3. 03

    Nothing ships unread

    Every change gets read by the one of us who didn’t write it. Not just the scary changes. It’s usually a boring one that bites you.

  4. 04

    Two people still remember

    Call us in eight months and you won’t have to explain your setup to a stranger. Two of us were there the first time. At least one of us will be free.

02 — What we fix

The stuff that breaks at 4pm on a Friday

Databases that got slow

It’s hardly ever the hardware. Usually it’s one old query, written years ago by someone who left long ago. We’ll find it and show you exactly which one it was.

  • Making slow queries fast
  • Cleaning up messy databases
  • Moving and merging data
  • Backups you’ve actually tested

Reports nobody trusts

Two teams show up to a meeting with two different numbers. Someone has to find out why. That’s usually us. And we write down the answer so it doesn’t happen again.

  • Reports the numbers agree on
  • Dashboards and scheduled emails
  • Tracking down bad data
  • Retiring the scary spreadsheet

Cloud bills and cloud mysteries

Moving to the cloud, paying for the right size, and figuring out what that one server nobody recognizes actually does — before someone turns it off and finds out the hard way.

  • Moving to the cloud
  • Cutting the monthly bill
  • Alerts that actually mean something
  • Written down, so it isn’t a mystery

Locking things down

We start with what’s actually open to the world, not what looks good on a checklist. We close the real holes first. Then we help with the paperwork if you need it.

  • Who can get to what, and why
  • Updates and safer settings
  • Practicing a restore before you need one
  • Risks explained in plain English

03 — Who shows up

John G, founder of Win Twin, in a server room Founder

John G

Founder · Over twenty years in IT

I started Win Twin™ after seeing the same thing happen over and over. One important system. One person who really understood it. And a company holding its breath every time that person took a vacation. I’ve been that person more than once. It’s not a good feeling for anyone.

My own corner is databases and reports. I run SQL systems, make slow things fast, and build reports that two teams can look at without starting a fight. My method is boring on purpose. Measure it. Prove it. Then change it. In that order, every time. Boring is how you avoid the kind of excitement nobody wants.

  • SQL administration
  • Making slow queries fast
  • Reporting
  • Cloud infrastructure
  • System design
  • Security
  • Backup & recovery
  • Writing it all down

04 — Where we work

Northeastern Pennsylvania,
and anywhere with a network cable.

We’re based in northeast PA and we’ll come to you across the area — Lackawanna, Luzerne, Wyoming, Monroe, Wayne, Susquehanna and the rest. Most work doesn’t need anyone in the room, though. So if you’re farther away, that’s fine too. Just ask.

05 — How we built this

We built this site as a pair too.
One of us was an AI.

Build notes · August 2026 · John G

It would be pretty rich to spend a whole page talking about checking each other’s work and then not tell you how this page got made. So here it is. I built it with an AI helper. This is what it did well, where it got things wrong, and why that’s the whole point.

What it did well

It wrote the first draft of almost everything: the page, the styling, that opening animation, the contact form, and the small piece of code that turns the form into an email. It also did the boring work. The logo showed up as a huge 1.5 MB image with a white box baked into it, which would have looked like a postage stamp on a dark page. The AI cut that box out, shrank the file to about 52 KB, and pulled the navy blue (#133461) straight out of the logo. So the colors here come from the logo, not from my taste. That’s probably for the best.

Where it was sure of itself and wrong

I asked for something “technical.” It went straight to a black screen with neon green text, like a hacker movie. That’s what the word looks like to an AI. It is not what it looks like when you’re asking a business to trust you with their data. It also made up a scrambled email address without doing the math, and left junk placeholder text in the styling file. All of it read fine. All of it was wrong. A person caught every bit of it.

And that’s the whole point

The same thing happens in real work, and the cost is higher. A rewritten query that runs fast and gives slightly wrong numbers. A data move that says it worked while quietly losing a rule. It looks right either way. You only catch it if you already know what you’re looking at.

AI is fast at the first eighty percent. The last twenty takes judgment, and judgment is what a second person is for. That’s the same point as the rest of this site. It doesn’t matter much whether the first draft comes from a new engineer, an old one, or a very fast robot. Nothing reaches your systems unread. We use AI where it helps, we check all of it, and we’ll tell you where we used it.

That’s also why ISO/IEC 42001 is on our list. It’s the standard for using AI responsibly, and we’ve started that work. Writing down how you use these tools, and who checks them, seems like the least you can do before going near someone else’s systems.

Under the hood

  • Hosting Cloudflare Pages, direct upload
  • Contact form Sends straight to our inbox, no middleman
  • Built by hand No website builder. Plain HTML, one style file, one script
  • Outside code None, except the Google map above
  • Analytics None. We are not watching you
  • Page size Under 100 KB of ours, logo and all

06 — Contact

Tell us what broke

Tell us what’s acting up, about when it started, and what it’s costing you in time or patience. Both of us read it. You’ll get a reply from a person, not a ticket number.