Amools

Amools replaces a scattered stack — a blog here, a course host there, a booking widget somewhere else — with one customer-facing operations layer. BuildsInfinity engineered the product for creators and service SMEs who sell knowledge or appointments and need a clean path from content to purchase or booking.

• Structured content publishing without a separate CMS maze
• Courses packaged with a clear purchase path
• Appointment and slot booking wired to how the business runs

The live product is at https://www.amools.in/. It serves Amool Saxena’s brand and the broader creator/SME use case: publish, teach or package programmes, and take bookings with practical payment flows. Creators and local SMEs often outgrow WhatsApp catalogues and single-purpose tools — full LMS suites are heavy, link-in-bio tools too thin — so Amools targets that middle. This case study focuses on engineering and product shape, not invented subscriber or GMV figures.

Amools sits at the intersection of SME tooling and creator/education-lite operations — content, courses and bookings for small businesses and independent educators who need a modern web product without enterprise bloat.

Three jobs — content, courses, bookings — usually mean three vendors, three logins and inconsistent branding. The challenge was unifying customer journeys without building an enterprise suite. Payments had to feel practical for Indian and SME contexts; admin UX had to stay approachable for non-engineering operators.

• One brand-facing experience across content and commerce actions
• Booking flows that match real availability, not demo calendars
• Auth and roles that separate operator and customer cleanly

We mapped how a creator or coach actually works: publish an update, offer a paid programme, open slots for calls or sessions, collect payment, follow up. Edge cases included incomplete profiles, abandoned booking attempts and content that must stay public while checkout stays gated. Those journeys shaped the information architecture.

Amools is a TypeScript web application: Next.js/React for customer and operator surfaces, Node.js APIs over MongoDB for content, course and booking records, REST boundaries between modules, and auth for protected actions. Deployment follows CI/CD onto a Vercel-friendly web tier so iteration stays fast for a live SME product.

The shipped surface matches the product catalogue we maintain publicly.

• Content publishing structured for customers and learners
• Courses and programmes with a clear purchase path
• Appointment and slot booking aligned to business hours and offerings
• Payment collection for courses and bookings through practical flows

Next.js, React, TypeScript, Node.js, Express-style APIs, MongoDB, REST APIs, auth, responsive design, Vercel and CI/CD. The stack favours speed of iteration for a live creator/SME product over premature microservices.

Customer-facing flows stay short: find the offering, understand it, book or buy. Operator surfaces emphasise publishing and schedule control without enterprise navigation trees. Responsive design is essential — many customers arrive from mobile social traffic.

Public content should load quickly; authenticated booking and payment paths must stay protected. Auth gates mutations. We keep API contracts predictable so content and booking modules do not leak operator-only fields to public responses.

Growth here means more content, more course SKUs and busier booking calendars — not necessarily a sudden global multi-tenant enterprise. The architecture supports adding offerings and slots without redesigning the customer path each time. Payment and booking modules are structured so gateways and rules can evolve.

Amools is live in production at amools.in. The outcome we can state honestly: a unified content, courses and booking platform in use, built and delivered by BuildsInfinity. We do not invent course enrolment totals or revenue multiples for this page.

Amools is a vertical-enough SME tool without pretending to be an enterprise LMS. The standout is product focus — three jobs done in one branded system — and a public production URL you can open today.