You have to give her credit for the business aspect of it. And I give her credit for wanting to help people.
Now, I don't mean to be rude or anything to this girl, but I disagree with this service. While I don't think much serious harm will come to it, it has the following flaws:
1) From a security perspective, this only looks at one aspect of password cracking: Brute force attacks. There are far more efficient ways to attempt to gain a password, from keyloggers to dictionary attacks.
2) She creates a false sense of security to those who don't know any better (They're going to get these passwords and think "Oh, my stuff is completely secure now!" - I don't blame her for this, I'm just saying that's the effect. As always, the best protection against hacking and other security threads is educating yourself.
3) This is made inherently less secure based on the fact that these passwords not only are generated by her, but pass through other hands via snailmail, before ending up at their final destination.
All that being said, she's actually on the right path, but the security could be improved in the actual password via padding
Passwords neither have to be random (as in, random from a computer or dice), nor do they have to be hard to remember. If you want to come up with secure passwords which are easy to remember, try these steps instead of paying someone:
1) Come up with a unique phrase. It can use dictionary words, doesn't matter. For instance: "Large Donkies Don't Bike"
2) Come up with a pattern of special characters and numbers you can remember, say: $$5% and then pad the previous phrase with that, so you have a password: "$$5%Large Donkies Don't Bike$$5%" - you now have a 32 character password, with special characters, numbers, caps, spaces, and punctuation. These are great passwords for use in things like KeePass to protect your other passwords. I recommend using an application such as KeePass over something like 1password because KeePass is local only, no online servers you have to worry about.
3) Optionally, if you can't use a password that long, or simply don't want to, use the abbreviations in a case-sensitive pattern you'll remember: "$$5%LDDb$$5%" - still 12 characters, contains special characters, numbers, upper and lower case letters, and no dictionary words.
I personally keep my KeePass database secured with a 50+ character long padded password, and it's as easy to remember as it was when I made it years ago. No one knows the phrase, and no one knows the pad.
Keep the pattern and phrase secret, even if you use abbreviations. I would highly recommend using two-factor authentication where you can to protect important things. I would also recommend using this method to come up with a secure master password to protect your other passwords in a service such as KeePass or 1password (I don't recommend 1password, simply because it's a third-party service that your passwords get stored on. That being said, I'm not saying it's bad.)
And as I said before, lack of ignorance is going to be your best bet in security. Even this method can easily be rendered useless using keyloggers. And, quite frankly, if you're holding something important enough and your attacker lacks morals: there's always rubber hose cryptography.
Anyway, sorry for the long post, maybe it will help someone out.