Live online batch · Cohort
Live cohort with weekly accountability.
For learners who understand the public syllabus but need weekly live checkpoints, peer rhythm, and a reviewed project to keep the work moving.
GitHub
Git
Cloudflare- Price
- INR 14,999
- Support
- Cohort
- Fit-check
Fit-confirmed support
Cohort
INR 14,999
per cohort batch
Decision lens: Choose cohort only when schedule, peer presence, and live Q&A will change consistency more than self-paced support.
Current status: First cohorts open after fit-confirmed learner interest
Ready now: Batch dates are confirmed manually on WhatsApp once enough right-fit learners are ready; no automated calendar or checkout is shown before the batch is real.
No automated checkout: WhatsApp fit-check before payment.
Fit audit
Before choosing Cohort, compare the support surface.
The right support path is not the most expensive path. It is the smallest support layer that changes the work you can finish, review, and explain.
Read first: The public syllabus stays available without signup, email gate, checkout, or login.
Choose optional support only if it changes output: An optional support path must improve the learner artifact: repository, demo, roadmap, project review, or workshop output.
No outcome promise: The page may describe support and proof, but not placement, salary, hiring access, or hidden partnership claims.
Public proof
Stay public if reading is enough.
Use the 20 lessons, blog, glossary, and reading paths first. Do not pay before you know what support would change.
INR 0
Lower layer
Job-Ready Track may already be enough.
If Job-Ready Track can produce the needed proof outcome, start there instead of overpaying for founder time.
INR 4,999
This path
Cohort changes one specific layer.
A learner who stalls in self-paced courses, needs scheduled live accountability, and can attend Saturday/Sunday IST calls. Proof outcome: Module demos, peer accountability, a reviewed final project, and cohort call notes from the live learning cycle.
INR 14,999
Upgrade only if
Mentorship changes the work.
Move higher only when Cohort is too thin for the support, accountability, or review surface you actually need.
INR 49,999
Operating model
Cohort works only when live rhythm changes consistency.
This path is for learners who abandon self-paced courses and need scheduled checkpoints, peer accountability, live Q&A, and a reviewed final project.
No support path is sold as magic. The learner or institution brings context, ABCsteps provides the support surface, and the final standard is inspectable proof.
Input
What you bring
Bring weekly progress, commits, demo links, errors, and questions from the public lessons before each group call.
Fit-check
What gets confirmed first
The fit-check confirms call timing, batch viability, and whether live accountability is actually needed.
Delivery
How support is delivered
Delivery runs through four live group calls, cohort WhatsApp group, module recaps, common-pitfall reviews, and a final project review.
Proof
What should exist after
The outcome should be module demos, cohort notes, a reviewed final project, and visible progress across the batch.
Stay lower if
Job-Ready Track already solves it.
Do not choose Cohort if Job-Ready Track can already create the proof outcome you need.
Choose this if
Cohort changes the artifact.
Choose this path only when it improves the expected proof outcome: Module demos, peer accountability, a reviewed final project, and cohort call notes from the live learning cycle.
Upgrade only if
Mentorship is truly needed.
Move above Cohort only when the higher support surface changes the work more than this path can.
What changes in practice
Cohort turns private intention into visible weekly progress.
The cohort page should not feel like a bigger checkout package. It exists for learners who need a live rhythm around the same public syllabus: prepare before calls, bring real blockers, show progress, and finish with a reviewed project.
Decision lens: Choose cohort only when schedule, peer presence, and live Q&A will change consistency more than self-paced support.
Weekly rhythm
Calls are checkpoints, not passive lectures.
Each week should surface lesson progress, repository state, demo blockers, and the exact question stopping the learner.
Peer pressure
The group makes progress harder to fake.
Small-batch accountability keeps learners returning to the editor, terminal, and browser until the project becomes inspectable.
Reviewed finish
The final project must survive explanation.
The outcome is not attendance. It is a reviewed repo, demo path, and project explanation that another engineer can inspect.
Before you message
Make the first WhatsApp message useful.
The fastest enrollment conversation is not a sales call. It is a fit-check with enough context to decide whether the public syllabus is enough, or whether Cohort will actually change your output.
This is still a static page: no form, no checkout, no account, no hidden learner database. Send the context directly on WhatsApp only when you are ready.
01 · Level
Current starting point
Share your current lesson progress and whether self-paced learning has stalled before.
Send: my current lesson, current repo state, and why live accountability may help.
02 · Time
Weekly study runway
Live group support only works if the schedule is real for you, not aspirational.
Send: my timezone, weekend availability, and whether I can attend live calls consistently.
03 · Proof
Target artifact
Name the final project or module demo that scheduled group rhythm should help you finish.
Send: the final project, demo, or portfolio artifact I want reviewed by the end.
04 · Boundary
What you expect from support
Be clear whether you need live accountability, peer presence, final review, or a lower self-paced support layer.
Send: why cohort support is needed instead of Job-Ready self-paced support.
Current delivery
Choose only when this delivery solves the need.
These pages state what can be delivered now, who the right-fit learner or institution is, and what proof should come out of the engagement.
Current status
First cohorts open after fit-confirmed learner interest
Ready now
Batch dates are confirmed manually on WhatsApp once enough right-fit learners are ready; no automated calendar or checkout is shown before the batch is real.
Right-fit learner/team
A learner who stalls in self-paced courses, needs scheduled live accountability, and can attend Saturday/Sunday IST calls.
Proof outcome
Module demos, peer accountability, a reviewed final project, and cohort call notes from the live learning cycle.
Value split
What the support changes.
Every support path must earn its price by changing the learner's work, institution output, or project decision, not by hiding the syllabus. Use these four checks before choosing this path.
Ready now
Current delivery is explicit.
Batch dates are confirmed manually on WhatsApp once enough right-fit learners are ready; no automated calendar or checkout is shown before the batch is real.
Support value
The fee buys guided support.
Everything in Job-Ready support + four 90-minute group calls (Saturday/Sunday IST) + a final project review
Proof outcome
The engagement must leave evidence.
Module demos, peer accountability, a reviewed final project, and cohort call notes from the live learning cycle.
Fit guard
This support path is not for everyone.
Pure self-pacers who would skip live calls anyway (Job-Ready support is enough)
Best for
- Learners who do better with scheduled accountability than pure self-pace
- Career switchers who want peer presence — small group of ~15 learners
- Anyone who wants their final project reviewed by Divyanshu personally
- Learners who want their questions answered live, not async
Not the right fit if
- Pure self-pacers who would skip live calls anyway (Job-Ready support is enough)
- Senior engineers who already know the curriculum (Architecture Review is the right fit)
What you receive
Included with Cohort
Everything in Job-Ready support (recorded walkthroughs + study pack)
Four 90-minute live group calls — module recap, Q&A, common pitfalls
Peer cohort group (~15 learners) for accountability and questions
One personal project review at the end of the cohort
Cohort-only learner WhatsApp group for the duration of the batch
Honest exclusions
- Private 1:1 founder time during cohort weeks (that is the Mentorship support path)
- Recordings of cohort calls are shared only with cohort members
Delivery proof
What this support path actually helps you practice.
The support path is useful only if it turns study into inspectable work: repositories, demos, review notes, deployment decisions, and project explanations.
Tool and platform logos are context references only: no affiliation, endorsement, interview access, hiring promise, salary promise, or placement guarantee.
Live checkpoints
Progress becomes visible.
Group calls are centered on commits, demo links, deployment errors, and concrete project blockers.
Build rhythm
The group keeps the work moving.
The cohort format keeps learners returning to the editor, AI pair, and browser project instead of only watching lessons.
Final review
The project must be explainable.
The review looks for a repository, repeatable runtime, reachable demo, and clear explanation of what changed.
How a typical engagement runs
From enquiry to outcome.
- 01
Enquire on WhatsApp
Send a message to confirm the next cohort start date and your fit for the batch.
- 02
Confirm enrollment
Lock your seat in the cohort. Receive the Job-Ready study pack and pre-cohort orientation.
- 03
Self-paced first half
Move through the first 10 lessons before the live calls begin. Calls are recap and depth, not first-pass teaching.
- 04
Live group calls
Four 90-minute Saturday/Sunday IST calls — module recap, common pitfalls, live Q&A, learner project demos.
- 05
Project review
Submit your final project. Divyanshu reviews it personally and writes back specific next-step direction.
Honest answers
FAQ
How big is a cohort?
About 15 learners per cohort. Small enough that everyone can speak in a 90-minute call, large enough for diverse projects.
What if I miss a live call?
Cohort calls are recorded and shared with cohort members only. You will not lose the content — but the live energy is the value, so attend when you can.
When are calls scheduled?
Saturday or Sunday evenings IST, exact slot confirmed before enrollment so it works for the batch. The default proposed slot is Sunday 7-8:30 PM IST, but the first live batches remain manually scheduled.
How is this different from Job-Ready?
Job-Ready is self-paced support with async Q&A. The Cohort adds scheduled live presence, peer accountability, and a personal final-project review.
Can I bring my team?
For 3+ teammates from the same company, ask about Institutional Workshops instead — usually a better fit.
Decision gate
Decide from fit, not urgency.
These support paths use real founder time. The right answer is sometimes to keep using the public proof layer, sometimes to ask one focused question, and sometimes to choose the support surface.
Choose only if
This support changes the work.
Choose Cohort only when the support surface helps you produce the proof outcome: Module demos, peer accountability, a reviewed final project, and cohort call notes from the live learning cycle.
Stay lower if
A lower path already solves it.
Pure self-pacers who would skip live calls anyway (Job-Ready support is enough)
Ask first
Fit is confirmed directly.
Send the page you read, the blocker or goal, and the outcome you expect. The next step can be reading, one question, or enrollment.
Direct fit-check
Message or call Divyanshu when this support would change the work.
Every support enquiry is intentionally human-confirmed: a short WhatsApp conversation matches the learner, founder time, and expected proof outcome before any payment step.