Who We Are
Meet the Diverse Team Behind Twine
In Our 20+ Years Serving Schools, we've Learned a Few Things.
Back in 1998 our staff began working with schools that wanted to build community, improve learning outcomes, and streamline operations. We’ve helped our customers find and deploy the best available technologies, and served as a guide and partner in implementation, helping to drive adoption and ensure effectiveness.
With both public and private school customers, we noticed several years ago that the best developers in education were focusing almost exclusively on public school districts with large budgets. Many private schools were being left behind, with old, clumsy, difficult-to-use legacy systems; or having to cobble together solutions from consumer-oriented or single-classroom tools designed for individual teachers. Our small, focused team decided we could do better, leveraging the best platforms available but scaled for individual schools, with professional services to match.
Twine was born as a result, tying together everything we had been doing over the past decades: school websites, staff intranets, parent communications, online classrooms, assessment, report cards, transcripts, and more. All this, wrapped up in a clean, easy-to-use package that’s just the right size for private schools.
Our Core Values
There is – quite literally – nothing more important to our future and our communities than ensuring every child gets the education they deserve. To play a part in making this happen for our customers is more than just a job for us, it is an honor and a calling.
Running a School is Difficult Business
School leaders face a crazy number of challenges. Not only are you dealing with all the logistics and concerns of running a business with budgets and staff and regulations, your success or failure has enormous stakes for your customers. Learning is complex; working with kids is different than manufacturing widgets where a fixed process gets the same results each time. And because your customers care so much about your product, emotions can run high when difficulties arise.
Simplicity is Important
The best tools are those that get used. To be effective, the software you choose needs to make people’s lives easier, save them time, and help them do the things they want to do, quickly and easily. The most sophisticated and feature-rich product in the world has no value at all if nobody wants to use it.
Community is Essential
Every member of every school — from teachers working in their individual classrooms finding creative ways to engage students, to staff in offices working to support the school, to parents at home and work, and even students working through challenging material — all of them benefit when they can connect with others. It isn’t just that keeping parents informed about classroom activities helps to avoid problems; making connections builds trust, and encourages partnership that results in the best possible outcomes for our students.
Security is Critical
Protection of your sensitive data is critical to our operations and to your reputation. Our policy is simple: Secure everything. No in-platform advertising. No selling of customer data.
We’re proud to have earned status as signatories to the Student Privacy Pledge as a result of our commitment to data privacy and security.
Meet the Twine Team
Overseer of Twine strategy & operations; Guy who stays up nights worrying about whether Twine customers and staff are happy.
I’m the guy whose job it is to make sure that the various different pieces of Twine are tied together into a solid and seamless whole; the one who gets up at night when Gary’s worried about Twine customers.
Support & Implementation Specialist
I’m the primary point of contact when you click the “blue question mark” or email firstname.lastname@example.org.
I spend a lot of energy trying to make sure that every word and image we use tells the right story. In all spheres of my life, I take delight in the process of self-evaluation, improvement, and re-evaluation.
I’ve lost count of the number of hats I wear, but generally, if any two parts of Twine aren’t getting along, I step in and put them in the corner until they play nicely.
Support & Implementation Specialist
I’m the one who writes the code that makes Twine…uh…tick. I get to develop, test, evaluate, retest, evaluate, retest, and evaluate the Twine engine … wait, did I mention the testing part?
Beth W. V. Adjutant
I enthusiastically support school leaders looking to learn more about Twine! If I don’t know the answers, I always know which member of our team does.