demo classadmission advicecourse selection

The Demo Class Is the Sales Pitch — Ask These Before You Pay Anything

A senior mentor's plain guide to the five questions that separate a real course from a good sales talk, plus what to check with your own eyes.

WebPrims Team17 September 202610 min read

Why the Demo Class Matters More Than the Brochure

Every June we get families walking in here with a folder of brochures from three or four institutes. The brochures all say the same things — "best faculty," "100% placement support," "industry-oriented curriculum." The parents look at the papers. The student looks at the phone. Then they sit through a demo class at each place, and by the end of the day everyone is exhausted and confused.

Here's the thing nobody tells you: the demo class is not a sample of the course. It is a sales pitch. The person standing at the whiteboard is often the best speaker in the institute, not necessarily the best teacher. The class is designed to make you feel excited and capable within forty-five minutes. That is its job.

.

So the real task is not to decide whether the demo class was good. It's to decide whether the institute behind it is honest. You do that by asking questions — specific, awkward, practical questions that the sales person does not want to answer. Most people don't ask them because they don't want to seem rude or dumb. We tell students: you are about to hand over a few thousand rupees of your parents' money. Rudeness is the smaller risk.

Here are the five questions that matter. Ask them politely. Write down the answers. And if the person answering starts to hesitate or talk around the question, that itself is your answer.

Question One — "Can I See the Course Content for the Full Course, Not Just the First Module?"

The demo class will always cover something flashy. A website mock-up. A Python program that draws a pattern. A Photoshop trick. It's the first ten minutes of a longer topic, chosen because it looks impressive on a screen in forty minutes.

The question that separates institutes is what comes in week four, week eight, week twelve. Ask for the full syllabus, printed or on a screen. Read it there, in front of them. Look at the topics in the middle of the course — not the start, not the end. Are those topics the kind of thing you actually want to learn? Or are they filler, rehashed basics, theory that you could get free from a YouTube playlist?

A concrete example: last year a student came to us after paying a fee at another place. He had sat through a demo on building a simple calculator app. It went well. He paid the full course fee. By week five, they were still doing variables and if-else statements. The calculator app was the entire first month's content, stretched thin. He had paid for a six-month course that was really a one-month course with five months of practice problems.

So ask to see the full list of topics. Count how many of them are genuinely new things you don't already know. If the syllabus is vague — "advanced topics," "projects," "industry exposure" — ask them to name three specific topics in each of those categories. If they can't, they don't have a real syllabus. They have a slide deck.

Question Two — "Who Will Actually Teach the Full Course, and Can I Meet That Person?"

The demo class is often taught by the owner, or the most experienced faculty member, or even a guest trainer brought in for the day. That person might be excellent. But the person who teaches most of your batch might be someone else — a fresh graduate, a part-time trainer, someone who is still learning the subject themselves.

This happens more than you'd think. Institutes hire a strong trainer to run the demo sessions and maybe the first week. Then the regular faculty takes over. The students notice the difference by week two, but by then they've paid.

So ask directly: "Who teaches the batch that starts on this date?" And then ask: "Can I speak with that person for five minutes?" Not the demo trainer. The actual person who will be in the classroom with you on a Tuesday afternoon in the third month.

If they hesitate — if they say "he's busy right now" or "you'll meet him at the start of the course" — that's a warning sign. A good institute will have no problem introducing you to the faculty who will actually teach you. We do it all the time. If a student wants to ask our PHP trainer what the second project involves, we walk them to his desk. That should be normal, not a special request.

Question Three — "What Exactly Happens After the Class Ends?"

Every institute claims placement support. But "placement support" can mean anything from "we send your resume to three companies" to "we have a tie-up with HR managers who come and interview our students" to "we give you a list of job websites."

Ask for the step-by-step process. What happens in the final month of the course? Is there a mock interview? Who conducts it? Is there a portfolio review? Does someone sit with you to fix your resume, or do they just give you a template?

A parent asked us this last month, which was smart. She said: "If my son finishes the course, what is the next thing that happens? Week by week?" We could answer that clearly — resume review, project polishing, mock interviews with our senior faculty, then we send shortlisted students to companies we work with. But not every institute can answer that clearly. Some will say "we have a dedicated placement cell." That's a phrase, not a plan.

And be honest with yourself about what you're paying for. A course that teaches you a skill is different from a course that gets you a job. Both are legitimate, but they cost different amounts and they require different things from you. If the institute promises a job, ask which companies, ask how many students from the last batch got placed, and ask to speak to one of them. If they hesitate on any of those, treat the promise as marketing, not fact.

Question Four — "What Happens If I Miss a Class, or fall Behind?"

This sounds like a small logistical question, but it reveals how the institute treats students as individuals or as numbers.

Ask: "If I miss three classes because of college exams, what happens?" Listen carefully to the answer. Do they say "you can watch recorded sessions"? Fine, but ask if those recordings are the same as the live class. Do they say "you can join the next batch for those topics"? That's decent. Do they say "we will help you catch up during the lab hours"? That's genuinely good.

The answer you don't want is "don't miss classes." That's not a policy. That's a warning. You will miss classes. You are a student, and life happens. Your college has a sudden seminar, your scooter breaks down, you get a fever. A course that cannot absorb a missed class is a course that has no real teaching plan — it has a fixed script, and if you fall off it, you're on your own.

We tell students this plainly: if you are the kind of person who will attend every single class on time without fail, then this question is less important. But most people are not that person. And the institute knows it. The honest ones have an answer ready.

Question Five — "Can I See the Last Batch's Projects, Not the Demo Projects?"

The demo class will show you sparkling student projects. A working e-commerce site. An Android app with a login screen. A portfolio website that looks professional.

Ask to see the projects from the previous batch — not the best one, but two or three average ones. Look at them honestly. Do they look like something you could build after this course? Or do they look like something the trainer built and the student just clicked "deploy"?

We see this mistake every year. Students are shown a project that took the trainer three weeks to build, and they think they'll be able to build it in the last month of the course. Then they hit the reality of debugging, of broken code, of the gap between following a tutorial and building from scratch.

So ask to see actual student work, from the actual previous batch. If they don't have any, ask why not. If they show you one stunning project, ask to see another one. If they can't, that one project was probably the exception, not the norm.

What to Do With the Answers

Write down the answers in front of them. This does two things: it signals that you are paying attention, and it gives you something to compare when you visit the next institute. You will visit more than one, right? Because now you have a list of questions, and you should ask the same five at every place. Compare the answers. The institute that gives clear, specific, boring answers — those are the ones to trust. The ones that give smooth, vague, exciting answers — those are the ones to walk away from.

And one more thing: ask about the fee structure itself. Not just "how much" but "what does the fee include?" Does it include study materials, or is that extra? Does it include exam fees, or are those separate? Does it include software licenses, or do you bring your own laptop? We do not list our own fees here because every course is different, but the principle is the same: ask exactly what is covered, and get it in writing. If they hesitate to put it in writing, that is your answer.

The demo class is the first test. It's a test of how they present themselves, not of how they teach. The real test comes in week three, week seven, week eleven. The questions above help you see week eleven before you pay for week one. That's the whole point.

.

Common questions

Do we need to bring our own laptop, or does the institute provide one?

Most institutes in Amritsar expect you to bring your own laptop, because the course continues at home. If they provide one, ask about the condition and whether you can take it home for practice. Bring your own if you can — it makes practice ten times easier.

.

Is a shorter course with fewer topics ever worth it over a longer, cheaper one?

Yes, if the shorter course teaches fewer topics but teaches them properly — with projects, debugging practice, and revision. A six-month course that is mostly repetition is worse than a three-month course that is packed and intense. Compare the syllabus contents, not the duration.

Can we sit in a regular ongoing class before paying, not just the demo?

Always ask for this. A good institute will let you sit at the back of a real batch for one session. If they say no, that's a strong warning sign. The demo is a performance. A regular class is the truth.

What if we pay and then decide the course is not for us — any refund policy?

Ask this before paying, and get the answer in writing. Most institutes offer a refund within a week or two, minus an administration fee. Some don't offer any refund. Both are legal, but you need to know which one you're signing up for. If they cannot explain their refund policy clearly in one sentence, do not pay that day.

.

Come and sit a class before you decide

Reading about it only gets you so far. Pick a day, sit in on a class that is already running, write some code, and talk to the students in it. Free, and nothing to pay afterwards unless you want to join.

demo classadmission advicecourse selection

Found this useful?

Share it with someone who is learning.