What was the specific moment or frustration that made you decide to build SemorIQ?

The moment that pushed me to build SemorIQ came when I realized how much time students were wasting just trying to keep track of everything. A typical semester could involve a timetable in one system, assignment deadlines in another, notes spread across different documents, study materials in cloud folders, and important updates buried inside WhatsApp groups. Even simple questions - such as what needs to be submitted this week or where the notes from a specific class were saved - could require checking several different places. What frustrated me most was that the existing tools each solved only one small part of the problem. Students were expected to create their own complicated system by combining calendars, task managers, note-taking apps, spreadsheets, and group chats. Instead of helping them feel organized, the number of tools often created even more stress. That was when I decided to build SemorIQ, one central platform where students could manage their courses, schedules, assignments, notes, projects, and study materials. I wanted the product to reduce the mental load of staying organized, so students could spend less time managing information and more time actually learning.

What's one growth tactic that worked and one that completely flopped?

I haven’t started actively marketing SemorIQ yet, so I don’t have enough data to honestly say that a particular growth tactic has worked. The product is still in the pre-launch stage, and most of my focus has been on building the platform, improving its reliability, and preparing it for real users. The approach I plan to test first is direct outreach to students because it will allow me to introduce the product personally and get detailed feedback rather than relying only on anonymous traffic. I also plan to test student communities, social media content, and SEO once the product is ready for broader promotion. The tactic that has effectively flopped so far is waiting too long to think about marketing. I initially treated marketing as something that would begin after the product was complete, but I have learned that distribution should be developed alongside the product. Building more features does not matter if potential users do not know the platform exists.

What do your customers complain about most, and how have you handled it?

SemorIQ has not launched publicly yet, so I do not have enough customers to identify a recurring complaint. I would rather be transparent about being in the pre-launch stage than invent feedback that I have not actually received. At the moment, my focus is on preparing the product for its first real users and creating a clear process for collecting, organizing, and acting on their feedback. Once students begin testing SemorIQ, I plan to pay close attention to onboarding difficulties, confusing navigation, missing features, technical issues, and whether the value of the platform is clear from the beginning. I also want to understand where users hesitate, which features they ignore, and what prevents them from returning after their first session. When complaints begin coming in, I will look for repeated patterns rather than making major changes based on every individual request. Problems that stop users from getting started, completing important tasks, or understanding the product will receive the highest priority. My goal is to treat early criticism as valuable product research and use it to shape SemorIQ around the real needs of students, rather than relying only on my own assumptions about what they want.

What's one thing about your market that most people get wrong?

One thing most people get wrong about this market is assuming that a student platform must offer a completely new type of feature to be valuable. Most of the people I have spoken with initially said that SemorIQ sounded similar to tools that already exist. In one sense, they are right, calendars, task managers, note-taking apps, file storage platforms, and study tools already exist. The difference is that students usually need five or more separate websites and apps to manage their academic life. Their timetable may be in one system, assignments in another, notes in a third, files in cloud storage, and important updates buried in group chats. The problem is not that students have no tools available. The problem is that those tools are disconnected. SemorIQ is designed to bring those essential functions into one platform. Instead of constantly switching between services and manually keeping everything synchronized, students can manage their courses, assignments, schedules, notes, projects, and study materials in one place. The value is not one isolated feature - it is the convenience, clarity, and reduced mental load created by having the entire student workflow connected.

What's next for SemorIQ in the next 6-12 months?

Over the next 6–12 months, my main goal is to move SemorIQ from a strong pre-launch product into a platform that students can use throughout their entire academic routine. One major area of development will be note-taking. I plan to add better formatting, organization, linking between notes and courses, and tools that make it easier to turn class material into useful study resources. I also want to introduce small educational games and interactive study activities. These could help students review material through quizzes, flashcards, challenges, and other short exercises that make studying feel more engaging. AI will be another important part of the roadmap. I am exploring features such as a personal study coach that helps students plan their workload, break down assignments, prepare for exams, and stay consistent. I also want students to be able to upload photos or scans of handwritten notebook pages and automatically convert them into organized digital notes, summaries, flashcards, or practice questions. Alongside these features, I will focus on launching to early users, collecting real feedback, improving onboarding, and making sure every new feature genuinely saves students time rather than simply adding more complexity.

Before you started building, what was your relevant experience? Had you worked in this industry, built other products, or were you starting from scratch?

Before building SemorIQ, I was already familiar with the problem from both a technical and personal perspective. I am currently a third-year software engineering student, so I experience the challenges of managing student life every day. I have had to use several separate products to keep track of lectures, assignments, schedules, notes, study materials, and deadlines. Each tool may work well on its own, but constantly moving between five different platforms creates unnecessary friction and makes it easier for information to become scattered or forgotten. I also had relevant development experience before starting SemorIQ. I had already built multiple websites and worked on different web development projects, which gave me experience in designing interfaces, creating useful features, managing data, and turning an idea into a functioning product. I was therefore not starting from scratch technically, although building a complete SaaS platform has introduced new challenges in areas such as product strategy, onboarding, payments, reliability, and future marketing. My advantage is that I am building for a problem I personally understand. I am both the developer and part of the target audience, which helps me evaluate whether each feature genuinely improves a student’s workflow.

What's the biggest mistake you've made so far building this product, and what did you learn?

My biggest mistake was spending too long building before speaking to enough potential users and preparing a clear marketing plan. I focused heavily on adding features and making SemorIQ feel complete, but I learned that a product does not need to be finished before people can start reacting to it. By delaying validation and marketing, I missed the chance to learn earlier which features students actually care about, what feels confusing, and how they describe the problem in their own words. I also learned that more features do not automatically make a product more valuable. Sometimes they can make onboarding harder and distract from the core benefit. The lesson has been to launch earlier, speak to users sooner, and build around real feedback rather than assumptions. Going forward, I plan to test features in smaller stages, prioritize the most important student workflows, and treat marketing and distribution as part of product development, not something that begins only after the product is finished.

If you could go back to day one, what would you do differently?

If I could go back to day one, I would start talking to potential users much earlier and build a smaller first version of SemorIQ around the most important problem. I spent a lot of time trying to make the platform feel complete before validating which features students actually needed most. Instead, I would begin with direct interviews and simple demos, then focus on one clear workflow - such as managing courses, assignments, and notes in one place. I would release that version quickly, observe how students use it, and let their feedback guide the next features. I would also start working on marketing and distribution from the beginning. At first, I treated marketing as something to do after development was finished, but I learned that building the product and finding users should happen together. The main change would be to replace long periods of building based on assumptions with shorter cycles of launching, learning, and improving. That approach would have helped me validate the idea faster and avoid spending time on features that may not be essential.