At 12, Steven Gittleson sat at a Commodore computer and wrote a game in BASIC. Three years later, he sold his first piece of software. It is the kind of beginning that can make a young programmer believe code is less a trade than a master key: learn the right language, turn it with enough force, and any locked problem will open.
That belief carried him a long way. Gittleson became a technical leader across several distinct eras of the internet. At NetCreations, he worked in email marketing. At Omnipod, he helped build enterprise messaging. At The FeedRoom, the problem was web video. Each job asked software to move information faster, more securely or at greater scale. He also became a founding partner, technology chief or investor across more than ten startups. Some produced significant exits. Most, by his own account, failed.
Then came a more stubborn system: a child, a book and the long distance between opening the first page and wanting the second.
“It is those lessons I come to visit and utilize every single day at the helm of LightSail.”Steven Gittleson, on what unsuccessful startups left behind
A library that could pay attention
In 2011, Gittleson was invited to join the founding group behind LightSail Education. The company assembled educators, social entrepreneurs, literacy specialists and businesspeople around a blunt observation. Many digital reading products were long on passages and short on pleasure. The content could be worthy, aligned and measurable, yet still leave a young reader cold.
Gittleson's assignment as co-founder and CTO was to build the platform. LightSail would offer a large library of fiction and nonfiction that students might actually choose, then adapt that library to each reader's measured level and interests. Assessments would sit inside the text. Teachers would see reading time, comprehension and growth data without waiting for a separate testing season. The shelf would rearrange itself as the reader changed.
It was a serious technical proposition wearing the friendly clothes of a bookshelf. LightSail used the Lexile framework to connect reading level with text difficulty. It surrounded books with questions, annotations, vocabulary tools, writing modules, progress reports and teacher dashboards. But its most important design choice was more ordinary: let children find something interesting.
A reluctant reader rarely dreams of generating a useful data point. A teacher rarely wakes hoping to admire an algorithm. The product had to respect both realities. Choice brought the student in. Measurement helped the teacher respond. The technology had value only when it tightened that loop.
The market began paying attention in 2013. LightSail took top honors in the Gates Foundation's Literacy Courseware Challenge and received a $500,000 grant. That year it also won the SXSW V2V education competition and announced a $3.5 million Series A round, following an earlier $1 million seed round. The awards and capital did more than decorate a pitch deck. The Gates grant supported an HTML5 interface intended to move the product beyond its original iPad setting and onto Android, Windows and Mac devices. For a company trying to fit into real schools, device flexibility was not a cosmetic improvement. It widened the number of classrooms that could plausibly participate.
The early recognition also made the central bet legible. LightSail was not merely distributing ebooks. It was connecting complex texts, authentic assessment, student activity and teacher scaffolding in one place. The difference sounds tidy in a competition entry. Making all those pieces behave together, every school day, was where the romance ended and the operating work began.
The third-party problem
Books, unlike lines of code, arrive with owners, contracts and locked doors. Early LightSail depended on third-party digital-rights and encryption software required by publishers. Gittleson later described that outside code as a source of instability. The company lost customers when pieces it did not control made the reading experience unreliable.
This is the unromantic founder work that disappears from glossy product demos. The child sees a page that will not load. The teacher sees a lesson going sideways. Somewhere behind both is a chain of vendors, rights and brittle integrations. Nobody in the classroom cares whose fault it is.
In 2018, LightSail invested heavily in building its own DRM, e-reader and encryption systems. Bringing those critical parts in-house gave the company more control over stability and made direct relationships with publishers possible. It was expensive plumbing. It was also the difference between offering a clever reading idea and operating a dependable reading product.
When a dependency owns the moment your customer experiences as “the product,” it is no longer merely a dependency. It is part of your reputation.
The engineer gets humbled
Gittleson's most revealing account of LightSail is not a claim about speed, scale or predictive algorithms. It is an admission. After years of believing software could answer nearly every question, he found education humbling. The decisions he valued most were the ones centered on students and educators. Technology became a tool and an enabler, shaped by what the education team and users were saying.
That sounds simple. It is difficult precisely because software companies reward the visible artifact: the feature shipped, the model tuned, the dashboard filled. A classroom rewards something quieter. Can a student find a book without feeling labeled? Can a teacher see a signal without drowning in metrics? Can the system help while remaining modest enough to leave the relationship between reader and teacher intact?
LightSail kept broadening its answer. It added fluency, writing, vocabulary and communication modules. Students could publish their own work, join reading tournaments and earn badges. Teachers could monitor activity, build content and communicate with classes. The company developed an offline-oriented Literacy-in-a-Box concept for places where connectivity and electricity could not be assumed. By 2021, Gittleson said distribution partners had expanded from two countries outside the United States in 2017 to more than ten.
The code became more capable. The founder's philosophy became less enchanted with capability for its own sake.
A career in four lines
The résumé moves through different categories, but the recurring job is translation. Convert an unruly human activity into a system without sanding off the reason people do it. Email without surrendering privacy. Messaging without losing security. Video without collapsing under scale. Reading without reducing a reader to a score.
Even in 2001, while serving as vice president of technology at NetCreations, Gittleson spoke publicly about encrypted addresses, restricted database access and audit trails. The language was technical, but the concern was trust. Two decades later, the users were younger and the stakes had shifted, yet trust remained the hidden architecture.
The acquisition and the next page
By the time MindPlay acquired LightSail in March 2023, the platform had traveled far beyond its tablet-era beginnings. MindPlay brought decades of literacy instruction. LightSail brought a content-rich digital library, embedded support, social features and a system designed to keep students reading across subjects. Gittleson called it the next phase of a literacy journey, extending from reading-to-learn toward learning-to-read.
The transaction price was not disclosed, which is almost refreshing. The more interesting arithmetic sits elsewhere. A boy starts with one small computer and a conviction that software rules the world. He spends decades building systems, watches startups fail, helps others reach exits, then takes on a problem that refuses to be solved by engineering alone. His company survives long enough to join a larger one. Along the way, certainty becomes judgment.
There is a playful symmetry in Gittleson's story. His first program was a game. At LightSail, games and badges eventually became part of the machinery used to motivate reading. Yet the deeper loop is not gamification. It is attention. The system notices the reader. The teacher notices the signal. The builder notices the limits of the system.
Good software likes a clean abstraction. Education keeps returning the exceptions: the book one child loves and another abandons, the measure that clarifies one lesson and distorts the next, the classroom where a feature becomes useful in a way its designer did not predict. Gittleson's career at LightSail suggests that maturity is not eliminating those exceptions. It is building closely enough to them that the product learns some manners.
Build the machinery. Listen to the room. Keep the part that helps a person take the next step.
For the 12-year-old at the Commodore, the thrill was making the machine obey. For the CEO, the harder achievement was learning when it should not lead. A book still needs a reader. A reader sometimes needs a teacher. The software can arrange the meeting, keep careful notes and suggest what comes next. Then, if it has been built well, it can have the grace to get out of the way.