Before any courses, before any signups, we built quietly—just a small stack of tools, a whiteboard, and a lot of questions.

The first thing we worked on wasn’t the content. It was the experience. What does it feel like to ask for help? How fast should a response come in? What should a student see first when they log in?

We sketched out rough flows—nothing fancy, just lines and notes. Then we talked to students. “If you had a button to press for help, when would you use it?” One said, “Right before I give up.” That answer stuck.

From there, we built a simple demo. No dashboards. No flashy UI. Just a working request form, a messaging space, and clear language. The goal was to get out of the student’s way.

We also set rules for ourselves:

• Keep it clean.
• Make it fast.
• Don’t overbuild.

On the backend, we tested workflows by hand. Every request, every reply—manually tracked and reviewed. That helped us catch what felt clunky or slow. It also helped us stay close to the student’s experience.

We didn’t start with big features. We started with friction points—where students get stuck, quit, or feel ignored. Our job was to remove those one by one.

The platform’s still evolving, but the core idea hasn’t changed. It’s not about what we think is helpful. It’s about what students actually use.

And they’ve been clear: they want something that works the first time, and earns their trust.

We’re building with that in mind.

— Arnav Bonigala