Back to Blog
authfield-opssecurityno-dependencies

PIN Login Web App: A Secure Front Door With Zero Dependencies (Simply Explained)

A plain-language guide to PIN login web app. No jargon, no tech speak, just what it means for your business.

By Mike Hodgen

Want the full technical deep dive? Read the detailed version

One password for the whole crew is a problem

A window-treatment company came to me with a problem that had nothing to do with window treatments. Their installers were signing into the company app on their phones at job sites, and the login was a mess.

Everyone shared one password.

That meant no accountability. When a quote went out with the wrong number, there was no way to know who did it. When someone quit, you couldn't cut off their access without changing the password for the entire crew. And that password was sitting in a group text from eight months ago, slowly leaking to anyone who'd ever worked a shift.

A shared password isn't really a login. It's a liability dressed up as one. The whole point of a login is knowing who did what. Share it, and you lose that completely.

The normal login doesn't work on a job site

So just give everyone an email and password, right?

Try typing your email and a complicated password on a cracked phone screen, in direct sunlight, with work gloves half-on, standing in a customer's driveway. A normal login is built for someone sitting at a desk. On a job site it's a tax the crew pays a dozen times a day.

Then there's the bigger question every business owner asks me: do we need to pay for a fancy login service for an app used by 30 people? The companies that sell logins (Auth0, Clerk, and others) are genuinely good. If you're signing up thousands of strangers off the internet, pay them. They've solved hard problems you don't want to touch.

But this wasn't that. This was a fixed list of employees the company already has on payroll. Nobody signs themselves up. For that, paying a monthly per-person fee forever to log in the same 30 people who never change is just a subscription you'll forget you're paying.

I built the login myself using security tools that already came free with the software. No new service, no monthly bill, no recurring cost. The only thing I had to write was the logic for this specific company.

I built it to feel like a restaurant register

Here's the part the crew actually touches. I built the login to work like the touchscreen at a restaurant register, because that's something field workers already understand with zero training.

You open the app and you see a list of names and faces. You tap yours. No email, no typing. Then a number pad comes up and you punch in a four-digit code. You're in. A 20-second fight with the keyboard becomes a two-second tap.

Now, a four-digit code sounds easy to guess, and I won't pretend otherwise. So here's how I made it safe.

The codes are never stored as plain numbers. They're scrambled in a way that can't be reversed, so even if someone got into the database, they'd see gibberish, not the actual codes.

The real protection is the lockout. Five wrong guesses and that person's account locks for fifteen minutes. A four-digit code only has 10,000 combinations, which a computer could blow through in seconds if you let it. But you can't guess fast when you only get five tries every fifteen minutes. That lockout is what turns a flimsy PIN into a real front door.

This is exactly where most quick AI-built apps fall apart. They skip the lockout entirely. A PIN without one is a toy. A PIN with proper scrambling and a lockout is a serious lock.

And the office can finally manage people one by one. Someone forgets their code, the office resets it in a few clicks. Someone quits, you remove them from the list. Per-person control, finally.

The app shows each person only what they need

The login was half the job. The other half was what the crew sees after they're in.

Showing an installer the full back-office menu (inventory, accounting, reports, settings) is a mistake. It's noise. Every extra button is a chance to tap the wrong thing and end up somewhere they shouldn't be.

So the app knows your job the moment you log in, and it draws your menu to match. Installers get three buttons: check out the job, build the quote, log the install. That's the whole job in three taps. The office and admin folks see everything, the full dashboard and all the controls.

Same app, same login, completely different screen depending on who you are. You don't take the desktop tool and cram it onto a phone. You build the phone tool for the people in the field.

The trade-off, honestly

I'd rather draw the line clearly than oversell this. Building your own login is the right call in a narrow lane.

It works when you control the list of users, there's no public sign-up, the team is small to mid-size, and you want zero monthly cost. Known employees, a list you manage. A login service charging per person, per month, for a 30-person crew is a bill that runs forever and grows as you hire. A one-time build pays for itself fast and keeps paying.

It's the wrong call the moment you need people signing themselves up off the internet, or a regulation forces extra security steps. Then you pay the service and you don't argue about it.

And be straight about the cost: when you build it, you own it. The upkeep is yours. For a closed crew, that's a cost worth carrying. For a public app, it isn't.

The bigger point is this: the login wasn't a security box I checked at the end. It was a decision that made the crew faster and the company safer at the same time. The tap-your-name login removed friction. The lockout added real protection. The trimmed-down menu cut the clutter. None of it traded speed for safety. It delivered both.

That's the kind of call I make on every system I build. Where to pay for something off the shelf, where to build it yourself, and how to shape the tool around the person actually using it.

If you're staring at a login service invoice for an app a few dozen people use, or your field tool is just your office app squeezed onto a phone, that's a conversation worth having. Not every problem needs a vendor.

Want to explore what AI could do for your business?

Book a free 30-minute strategy call. No pitch deck, no sales team, just a real conversation about your operations and where AI fits.

Book a Discovery Call

Get AI insights for business leaders

Practical AI strategy from someone who built the systems — not just studied them. No spam, no fluff.

Ready to automate your growth?

Book a free 30-minute strategy call with Hodgen.AI.

Book a Strategy Call