TL;DR — Making a family create an account and password before they can even start an application is one of the quietest ways to lose them. The parent most likely to give up is the one with the least time. The fix isn't a better login screen — it's no login screen. With Lazarus, families apply, enroll, and pay without ever creating an account.

Picture the parent you most want to reach.

They heard about your school from a friend. They're interested. One evening, after the kids are finally down, they open your enrollment page on their phone to start an application. And the first thing they see isn't a question about their child. It's a form that says: Create an account to continue.

Enter an email. Make a password — eight characters, one number, one symbol. Check your inbox for a verification link. Come back. Log in. Now you can begin.

Somewhere in there, a lot of families close the tab. Not because they lost interest in your school — because they lost the thread. The moment is gone, the baby's crying, and the application can wait until "later," which quietly becomes never.

The account wall costs you the families you can least afford to lose

Here's the uncomfortable part: the account wall doesn't filter out the uninterested. It filters out the busy.

A parent juggling two jobs and three kids is exactly the person who starts an application at 9:40pm with ten minutes of attention to spare. Ask them to invent and remember a password first, and you've spent their ten minutes on your software instead of your school. The family with more time and fewer demands pushes through. The family you were most hoping to serve doesn't.

Every extra step before the first real question is a place to lose someone. An account is several steps stacked together:

  • An email to verify before they've answered a single question.
  • A password to invent — and forget by the next time they log in.
  • A login screen standing between a ready family and your form.
  • More steps for the parent who has the least time to spare.

None of this tells you anything about the child. It's pure overhead — friction you've added to your own front door.

"But we need accounts to keep their information organized"

This is the usual reason, and it's a real need stated backwards. You need the information organized. The family doesn't need to manage a login to give it to you.

Those are two different things, and good enrollment software keeps them separate. The school gets a tidy, structured record of every applicant. The family gets to answer questions and move on with their evening. The account — if it exists at all — is the school's problem to manage, not the parent's homework.

When you make the family responsible for the login, you've handed your organizational need to the person least equipped to carry it, at the worst possible moment.

The best first step is no step at all

With Lazarus, there's no account to create and no password to remember. A family opens your enrollment link and starts answering questions about their child — immediately. They apply, enroll, and pay, all without ever logging in.

One application covers the whole family, and each child can be accepted on their own. A parent fills it out once; you review each child independently. Nobody resets a password at 10pm to finish what they started.

The effect is simple: the families who were going to apply actually finish applying. You stop losing people in the gap between "interested" and "started."

What to do this week

If you're not sure whether your enrollment front door has an account wall, test it like a parent would: open your application link on your phone, in a browser you've never logged into, and count the steps before the first real question about a child. Every step before that question is a step a busy family might not take.

Then decide how many of those steps actually need to be there. Our guess, based on the schools we work with: fewer than you think.

FAQ

Doesn't skipping accounts make it less secure? No — it moves the security burden to where it belongs. The school's records stay protected; the family simply isn't asked to manage a login to hand you information. Removing the parent-facing password removes a weak point (reused, forgotten passwords), it doesn't add one.

How do families come back to finish later if there's no login? They pick up from the same link — no credentials required. The design goal is that "later" never depends on remembering a password.

Can one parent apply for several children at once? Yes. One application covers every child in a family, and each child can be accepted independently, with sibling discounts calculating on their own.