I'm Andrew Bybee, and I've spent the last 8 years working in restaurants.

Every pay period, we were managing 20+ employees and reviewing hundreds of hours — where small payroll mistakes add up fast.

The problem is, most payroll tools look clean on paper… but don't reflect what actually happens during a shift.

Missed clock-outs.
Messy hours.
Last-minute fixes right before payroll runs.

Every week, I was dealing with the same issues:

• Employees forgetting to clock out
• Managers manually adjusting hours
• Dozens of timecards reviewed under time pressure

Most of the time, errors weren't caught until after payroll was already processed.

That's where money gets lost.

FixMyShift

FixMyShift started as a tool I built for our restaurant to catch those issues before they hit payroll.

It surfaces:

• Missed clock-outs
• Inflated hours
• Open shifts

…so managers can fix them early instead of scrambling at the end.

Built with Codex

As part of the OpenAI x Handshake Codex Creator Challenge, I expanded it into a full product.

Using Codex, I built:

• A working dashboard end-to-end
• Core logic for detecting payroll issues
• Simulated real payroll scenarios (high labor, missed clock-outs, clean periods)

To refine the product experience, I also used AI-assisted iteration to:

• Improve UX flows and clarity
• Stress test real-world edge cases
• Make the product feel intuitive and usable

The goal wasn't just to make something that works — it was to make something that feels real to use.

What makes this different

This isn't a theoretical tool.

It's built from:

• Real shift issues
• Real payroll mistakes
• Real workflows managers actually follow

Based in Los Angeles.