MarkPoint

MarkPoint is an educational technology platform that teaches students to internalize cognitive frameworks rather than memorize content. After teaching 500+ HSC English students to Band 6, I identified a consistent pattern: students didn't struggle with content knowledge—they struggled with knowing what to prioritize and how to structure their thinking under time pressure. Existing resources were either too generic (YouTube crash courses) or too prescriptive (rigid templates). Students needed adaptable frameworks they could internalize and apply independently across different contexts. MarkPoint provides these frameworks through a web-based platform, focusing on systems thinking that works across high-stakes exam scenarios.

The gap in the educational market is clear: resources focus on content delivery or generic tips, but few teach the underlying cognitive systems that enable independent problem-solving. Students can recite essay structures and memorize quotes, but under exam pressure, they can't decide what to prioritize or how to adapt their knowledge to unexpected questions. This isn't a content problem—it's a frameworks problem. We built MarkPoint because: 1. **Existing solutions are insufficient:** YouTube videos are too generic; tutoring is expensive and doesn't scale; textbooks provide content but not thinking frameworks 2. **Personal validation:** After 500+ students, the pattern was undeniable—the students who succeeded had internalized frameworks, not just memorized content 3. **Scalability gap:** One-on-one tutoring works but doesn't scale; MarkPoint makes these frameworks accessible to students who can't afford private tutoring The pain point is acute: HSC English is high-stakes (affects university admission), time-constrained (3-hour exams), and requires sophisticated thinking under pressure. Students need frameworks they can internalize, not templates they memorize.

As a co-founder of MarkPoint, I serve multiple critical roles that shape both the product and brand: **Founding Developer:** - Full-stack development (Next.js, TypeScript, Prisma, tRPC) - Database design and schema evolution - Stripe payment integration and webhook processing - Deployment infrastructure (Vercel, Neon PostgreSQL) - All technical implementation and code **Brand Lead:** - Brand identity and visual design system - Marketing positioning and messaging - Content strategy and brand voice - Visual aesthetic across all touchpoints **UI/UX Designer:** - Product design and user research - Interface design and user flows - User experience optimization - Direct user feedback collection and iteration **Lead Frontend Developer:** - All frontend implementation - Component architecture and design system - Performance optimization - User experience refinement I work alongside my co-founder on product vision and strategy, while owning the technical implementation, design direction, and brand identity end-to-end. The decisions I make shape how MarkPoint looks, feels, and functions: choosing frameworks over content delivery, building custom platform instead of using existing course platforms, defining the visual language that makes learning approachable yet rigorous.

**Core Platform Infrastructure:** - Full-stack web application built on T3 Stack (Next.js 15, TypeScript, Prisma, tRPC) - PostgreSQL database with Prisma ORM for type-safe queries - Authentication system (NextAuth.js) with email and OAuth providers - Stripe payment integration (Checkout, Webhooks, Customer Portal) - Content management system for framework documentation - User dashboard for tracking progress **Framework Delivery System:** - Custom framework engine for presenting cognitive models - Interactive examples demonstrating framework application - Practice scenarios where students apply frameworks to new contexts - Progress tracking to show framework internalization over time **Operational Components:** - Automated onboarding flow for new students - Email integration for transactional messages (welcome, purchase confirmations) - Admin dashboard for monitoring user engagement - Feedback collection system integrated into platform - CI/CD pipeline for continuous deployment **Technical Decisions:** - Chose managed infrastructure (Vercel, Neon) over self-hosted to focus on product iteration - Type safety throughout (TypeScript + Prisma + tRPC) to minimize bugs while working solo - Server-side rendering for optimal performance and SEO - Stripe for payments to avoid building payment processing from scratch The system is designed for solo operation: minimal maintenance overhead, automated where possible, focused on core value delivery.

**Live and Operating:** MarkPoint is in production with real users. Students are actively using the platform to prepare for HSC English exams. **User Feedback:** Early adopters report that the framework approach helps them structure their thinking more effectively than traditional study resources. Several students have successfully applied the same mental models to other subjects beyond English, validating the transferability of the frameworks. **Technical Validation:** - Full production deployment with working payment processing - Type-safe API layer eliminating client-server contract bugs - Database schema handles complex content relationships - Zero downtime deployments via Vercel - Stripe webhook processing is reliable and idempotent **What Worked:** - Framework-first approach resonates with students who already understand content - Direct user feedback loop enables rapid iteration - Type safety catches bugs early, critical for solo development - Managed infrastructure lets me focus on product, not operations **What Didn't:** - Initial onboarding flow was too complex; had to simplify significantly - First pricing strategy didn't account for student budget constraints - Early framework library was too broad; had to narrow focus to core models

MarkPoint is actively operating with paying users. The platform is stable and functional, but I'm in an iteration phase based on user feedback. **Current Focus:** - Expanding the framework library based on user requests - Improving onboarding flow to help students internalize frameworks faster - Adding progress tracking to show framework mastery over time **Why Active (Not Scaling):** I'm intentionally keeping growth slow while I validate product-market fit. Each new user provides feedback that shapes the product. Scaling before nailing the core experience would be premature. **Resource Constraints:** As a solo founder with limited time, I'm prioritizing product quality and user satisfaction over user acquisition. Better to have 50 users who love the product than 500 who churn because the experience isn't polished. **Next Phase:** Once the core framework engine is validated (3-6 months), I'll focus on structured user acquisition. The foundation needs to be solid first.

**Frameworks > Content:** The biggest validation has been confirming that students don't need more content—they need better systems for processing the content they already have. This insight now shapes how I approach all educational products: start with the mental model, not the information. **User Research Timing:** I would invest more time in structured user research before building if I were starting fresh. My tutoring experience provided strong product intuition, but earlier interviews could have saved iteration cycles. Assumption: students want X. Reality: students need Y. User research bridges that gap. **Technical Stack Choices:** The T3 Stack (Next.js + TypeScript + Prisma + tRPC) has proven excellent for solo development. The full-stack type safety reduces cognitive load significantly and catches bugs early. This learning applies to future projects: type safety is worth the setup overhead when working alone. **Solo vs. Team:** Operating solo has taught me to be ruthlessly focused on core value proposition. Every feature must directly support framework delivery. With a team, it's easier to expand scope; solo forces discipline. This constraint has been valuable—it's made the product sharper. **Iterative Validation:** Shipping early and iterating based on real user feedback beats building in isolation. I shipped the MVP within 3 months and learned more from user interactions than I would have from 6 more months of development. Lesson: get to users faster, even if imperfect. **How This Informs Current Work:** - All new features start with user research, not assumptions - Type safety is non-negotiable for solo projects - Managed infrastructure is worth the cost for iteration speed - Framework thinking applies beyond education—any domain benefits from teaching systems over content