About the founder
Lee Rippy, founder
A small private school in Virginia got me through dysgraphia and on to a business degree. Now I build software for schools like it. I started Pearspark in June 2026, and I still write the code, answer the support email, and check every page on this site before it goes up.
- Started
- June 2026
- First school live
- July 2026
- People
- One
- Changes shipped since July 25, 2026
- 54

Where I come from
I grew up in a small private school in Virginia. In second grade I was diagnosed with dysgraphia. The school gave me the specialized help I needed, and because of it I graduated from the College of Business at East Carolina University in 2011. I know what a small school that fits a child can do, because one did it for me.
My wife and I homeschool our two kids. We are advocates for school choice.
How it started
A friend who co-founded Redeemer Classical, a hybrid classical school in Phoenix, had looked for software that fit her school's model and could not find any. She asked me to build a library system. So Pearspark began as a barcode book-checkout tool: scan the book, scan the card, done.
Then she asked for volunteer management. Then grades. After the third request I stopped answering one at a time and went all in on a full school platform. The first commit is dated June 6, 2026. Redeemer was running on it by July.
I did not set out to fix school administration. A school asked me for software, and I kept saying yes.
What I believe
Every student works and learns differently, and every school operates differently because of that fact. That is the whole philosophy behind Pearspark. It is why families keep starting schools that are built different: classical, Montessori, hybrid, co-op, microschool. The people who start them are teachers first and office staff by necessity. The software a small school can afford should not be the reason it fails.
So Pearspark bends to how a school is built instead of forcing one model on it, and it costs what a small school can pay. The price is public, and everything is in it.
How I work
- One person. There is no sales team and no support desk. When you write to support@pearspark.com, I am the one who answers.
- No sales calls. You sign up, which takes about three minutes, get thirty days, and try it. If it is not for you, it is month to month, and your data exports in one click.
- Ship often, and say so. Every change is dated the day it reached the schools running on Pearspark, on the release history. Nothing is listed there until it is live.
- Built with AI tools, under rules. I use AI to write code faster than one person otherwise could. Development runs against a fictional sample school. No AI system touches real student data, and none gets a production password. Nothing about your students is sent to an AI service, and the site runs no third-party trackers. The privacy policy says the same thing in the binding form.
How the pages on this site are written
Most of what you read on pearspark.com starts as a draft produced with AI tools, working from Pearspark's own code and from a list of competitor facts with a source and a date on each one. I would rather say that than pretend every page was typed by hand.
Then I read it. Product claims are checked against the code before a page goes up. Competitor prices come from the vendor's public pages, and the date we last checked is printed on the page. I decide what is published, and I put my name on it.
If a page is wrong, tell me at support@pearspark.com and I will fix it. This page was last checked against the code on .
Where to find Pearspark
- Email: support@pearspark.com
- YouTube: @Pearspark, where the how-to videos live
- LinkedIn: Pearspark
- Facebook: Pearspark
- X: @pearsparkED
- Instagram: @pearsparkED
Try it before you trust me
Thirty days free, month to month after that, and no call with anyone. The product is the argument.