Why 2026 is a strong year to onboard as a Refonte course provider
The online-learning market has matured past the 2020-2022 gold rush and past the 2023-2024 AI-content flood. What remains, and what learners are willing to pay for in 2026, is teaching that visibly comes from a practitioner. That single shift, from generic courseware toward instructor-signal, is exactly what a platform like Refonte Learning is built to reward. If you already ship code, run data pipelines, operate cloud infrastructure, tune models, or advise teams, you have the raw material for a course that will actually sell.
Getting started as a course provider is not primarily a marketing exercise. It is a packaging exercise. You are taking work you already do, distilling it into learning outcomes, wrapping it in a listing that meets platform requirements, and pricing it against comparable programs. Most first-time providers underestimate the packaging effort and overestimate the marketing effort. The platform handles a large share of demand generation; your job is to give it something worth surfacing.
This guide walks through the full onboarding path in the order you will actually experience it. We cover eligibility, application, profile setup, curriculum scoping, pricing, listing review, first-cohort operations, and the feedback loop that determines whether your second course launches to a bigger audience than your first. It is written for the practitioner who has never taught formally, as well as the corporate trainer who has taught for years but never on a marketplace. If you fall somewhere in between, skip the sections that are already familiar and go deep on the ones that are not.
A note on scope. This article is intentionally operational. It does not try to convince you that teaching online is a good idea in 2026, and it does not spend time on abstract pedagogy. It assumes you have decided to try, and it focuses on the concrete steps between that decision and your first paid enrollment. For the strategic case and the wider ecosystem view, the pillar overview on how to sell your course on Refonte Learning covers positioning, market fit, and revenue models in detail.
Who Refonte Learning accepts as a course provider
Refonte Learning is a vertical marketplace. That means it is not trying to be Udemy for everything. It is trying to be the credible destination for professional training in AI, data, cloud, DevOps, cybersecurity, software engineering, and the adjacent domains where employers actually hire. The provider bar is set to protect that positioning. If your teaching topic sits inside those verticals, you are in scope. If it sits outside them, no amount of production polish will get you approved, and that is by design.
Beyond topic fit, the platform looks for three signals in an applicant. The first is demonstrated practice. This does not mean a fifteen-year resume; it means you can show artefacts. A GitHub profile with real repositories, a portfolio site with case studies, a published paper, a conference talk recording, a Kaggle profile, a public dashboard, an open-source contribution history, or a client testimonial from work you have shipped. Practitioners with two or three years of high-quality output are frequently approved over ten-year veterans who cannot show anything public.
The second signal is teaching aptitude. You do not need a teaching credential. You do need to demonstrate that you can explain a hard concept in writing or on video without losing the audience. The application asks for a short teaching sample, usually two to five minutes of you walking through a technical concept. Reviewers are looking for structure, clarity, and calibration to a specific learner level, not production values. A screen recording made with OBS on a quiet afternoon is fine. A polished promo trailer is not what is being evaluated here.
The third signal is reliability. Marketplaces live or die by whether providers deliver on their commitments. If you say your cohort starts on the fifteenth, it starts on the fifteenth. If office hours are Thursdays at 18:00 UTC, they run Thursdays at 18:00 UTC. The application does not test this directly, but your subsequent onboarding, response times, and how you handle the first small commitment (uploading a course outline by a deadline, for example) all feed into how quickly your listing gets promoted.
Eligibility is documented in more detail in the course listing requirements article, which is the reference you want open in a second tab when you are preparing your application.
The application: what you submit and what reviewers look for
The application form lives at the become an instructor on Refonte Learning page. Plan to spend roughly two to four focused hours on it. That estimate assumes you already have a portfolio or GitHub link handy and that you know which course you want to teach first. If you are still deciding on your first course topic, do that thinking before you open the form; the application is not the right surface to figure it out.
The form has five main sections. Identity and contact are straightforward, with the caveat that the email you use here becomes your provider identity across the platform, so use a professional address you intend to keep. Professional background is where you paste links to public work, list relevant employers or clients, and describe your specialty in three or four sentences. Do not write a resume; write a positioning statement. "Senior data engineer, ten years building Snowflake and dbt pipelines for fintech, specialising in cost optimisation and slowly-changing dimensions" beats a chronological career history every time.
The teaching sample is the section that most applicants underinvest in. Reviewers watch dozens of these a week and calibrate quickly. What works: pick a narrow, concrete concept (not "an introduction to Kubernetes", but "why a Kubernetes readiness probe is different from a liveness probe and when that matters"), teach it in three to five minutes, and end with a check-for-understanding question you would actually ask a student. What does not work: reading slides, giving an abstract overview, or trying to cover too much.
Course concept is where you describe the specific course you want to launch first. Include the target learner (be specific about seniority and prerequisites), the learning outcomes (three to six concrete capabilities the learner will have at the end), the format (self-paced, cohort-based, or hybrid), the estimated total learner hours, and the rough curriculum outline. Reviewers are checking whether the concept is well-scoped and whether it fills a real gap in the current catalog. A course on "Python for beginners" competes with a hundred existing options; a course on "debugging PyTorch training runs when your loss goes NaN" does not.
Availability and commitment closes the form. This asks how many hours per week you can dedicate, when you want your first cohort to run, and whether you are open to co-teaching or being paired with a teaching assistant. Answer honestly. Over-promising here creates problems in the first cohort that damage your provider rating.
Review typically takes seven to fourteen business days. You will get one of three outcomes: approved, approved with feedback (usually a request to tighten the course concept), or declined with a specific reason. Declines are not final; most declined applicants who address the feedback and reapply after three to six months get approved on the second attempt.
Setting up your provider profile
Once approved, you move into the provider dashboard. The first task is your public profile, and it deserves more attention than most new providers give it. Your profile is what a prospective learner sees before they click into your course. A course listing with a strong profile behind it converts substantially better than the same listing with a thin profile, even when the course content is identical.
The profile has a headline, a longer bio, a photo, links to public work, a list of specialties, and optionally a short intro video. Treat the headline as ad copy: it needs to say what you teach and why you specifically. "Cloud architect teaching AWS cost optimisation, ex-Airbnb infrastructure" is a headline. "Passionate educator and lifelong learner" is not. The bio should be three to five short paragraphs, written in first person, that cover what you do, what you teach, how you teach it, and one or two specific outcomes past students or colleagues have achieved. Avoid marketing adjectives. Prefer concrete nouns and verbs.
The photo matters more than you think. Use a recent, well-lit headshot with a neutral background. It does not need to be professionally shot, but it should look like you. Group photos, sunglasses, distant shots, and cartoon avatars all reduce conversion. There is no ideological reason for this; it is simply that learners are choosing to spend money and time with a specific human, and they want to see who that human is.
The intro video is optional but strongly recommended. Ninety seconds, filmed against a plain background, covering three things: who you are, what you teach, and what a student can expect from your teaching style. This is a positioning statement in video form, not a course promo. Do not talk about a specific course here; talk about you as a teacher, because the profile persists across every course you eventually list.
Specialties are a structured field, and it drives some of the platform's internal categorisation and recommendation logic. Pick three to five that genuinely describe your expertise. Do not pick everything you have ever touched; the platform's ranking treats a provider with three deep specialties more favourably than one with twelve shallow ones. This is consistent with how learners actually search: they are looking for the person who is known for the thing, not the generalist.
Scoping your first course
Your first course is a calibration exercise as much as a product launch. You are learning how learners in the Refonte Learning ecosystem respond to your teaching, how much production effort your workflow requires, and how much time cohort operations actually consume. Choose a course scope that lets you learn those things without burning out before the second cohort.
A good first-course scope has four properties. It is narrow in topic, so you can go deep. It is short in duration, ideally four to six weeks for a cohort course or eight to twelve hours of content for a self-paced course. It is aligned with a specific job outcome or workplace capability, so learners can articulate why they enrolled. And it draws on work you have already done, so you are packaging existing knowledge rather than researching a new domain while trying to teach it.
Common mistakes at this stage include scoping a comprehensive twelve-week bootcamp as a first course (too much production work, too much cohort operations risk), scoping around a trendy topic you do not have deep experience in (learners will find the gaps in the first Q&A), and scoping around what you find interesting rather than what learners actually pay for. The intersection of what you know deeply and what learners are trying to accomplish at work is where a viable first course lives.
Outcome design is the core of scoping. Write down three to six learner outcomes as verb phrases: "design a dbt project structure for a mid-sized analytics team," "debug a Kubernetes pod that is stuck in CrashLoopBackOff," "fine-tune a small language model on a custom dataset without overfitting." Every module in your curriculum should map back to one of these outcomes. If a module does not map, it is scope creep and should be cut. This discipline is what separates a course that finishes in six weeks from a course that sprawls to twelve.
Once your outcomes are locked, sketch the curriculum backwards. Start from the final project or capstone that would demonstrate the outcomes, then work backwards to figure out what the learner needs to know in the second-to-last module to succeed in the final one, and so on. This backwards design produces tighter curricula than forward design, because every earlier module has a clear reason to exist.
Pricing your first listing
Pricing is where new providers overthink and underprice. The impulse is to price low to attract the first students. That impulse costs you money, positions the course as low value, and attracts learners who are less serious and more support-intensive. A more useful mental model: your price signals what you think your course is worth, and learners largely agree with that signal unless the course itself contradicts it.
The platform's course pricing guide walks through the full pricing model, including tier bands, revenue splits, and promotional pricing mechanics. In brief, first courses tend to price in one of three bands: an entry band for short self-paced courses, a mid band for cohort courses with instructor time, and a premium band for cohort courses with capstone review, one-to-one office hours, or job-outcome guarantees. Which band you sit in should follow from your format and the depth of instructor involvement, not from a guess about what learners will pay.
Anchor your price against comparable courses in the platform catalog, not against the general internet. A cohort course with weekly live sessions and instructor feedback is not competing with a five-dollar Udemy course; it is competing with other cohort courses in the same specialty. Look at three to five comparable listings, note their prices, format, and instructor involvement, and place yours in a defensible position within that range. Underpricing relative to comparables is not a strategy; it is a signal that you do not believe in the course.
Do not build discounts into your launch pricing. Set the price you intend to hold, and then run occasional structured promotions if you want to drive enrollment at specific moments. Providers who launch at a discounted rate and never raise it find themselves stuck at that price forever, because raising a public price without a strong reason is difficult. Providers who launch at their intended price and run a limited early-bird promotion for the first cohort preserve their pricing power.
Revenue mechanics, including the platform split, payout timing, refund handling, and how promotional pricing affects your take, are covered in detail in the guide on how course providers earn on Refonte. Read it before you finalise your price. The take-home number after platform economics is what actually matters for your planning, and it is often different from the sticker price by more than new providers expect.
Building the listing itself
With pricing settled and curriculum scoped, you are ready to build the actual listing. The listing form is more involved than a simple product page, because it drives both search ranking within the platform and conversion from listing view to enrollment. Plan a full working day for this, not an hour.
The listing has a title, subtitle, long description, curriculum outline, prerequisites, learning outcomes, target audience, format details, schedule, price, and media. Every field influences either discovery or conversion, so none of them are optional in practice even when they are technically optional in the form. The title should be concrete and outcome-oriented: "Debugging PyTorch Training Runs" beats "Advanced Deep Learning". The subtitle adds specificity: "A five-week cohort course for ML engineers with production model training experience".
The long description is your sales page. Structure it in this order: the problem the course solves, who it is for and who it is not for, what learners will be able to do at the end, how the course is structured, who you are as the instructor, and what past learners or beta students have said. The "who it is not for" section is unusual and worth doing; it filters out learners who would enroll and then complain, and it signals confidence to learners who fit. A course that is honest about its prerequisites gets fewer refund requests than one that soft-sells them.
The curriculum outline should list modules with titles and one-sentence summaries. Do not paste your full lesson plan; you are giving learners enough to evaluate fit, not a preview of the entire content. Prerequisites should be specific and testable, ideally with a link to a self-check that lets a prospective learner verify they meet them. "Comfortable with Python" is not a prerequisite; "can write a function that reads a CSV, filters rows, and writes the result to a new file, without looking up syntax" is.
Media matters. A course with a short trailer video (60 to 120 seconds) converts better than one with only a static image, and a course with sample lesson excerpts converts better than one without. If your production capacity is limited, prioritise the trailer over the samples; the trailer is what wavering learners watch before deciding. Screenshots of the actual course environment (lesson interface, project rubric, sample dashboards) build credibility when the topic is technical.
For a full field-by-field walkthrough with examples of strong and weak listings, the free listing explained article covers the mechanics of no-cost listing creation and the fields that new providers most frequently get wrong.
Passing listing review
Every listing goes through review before it goes live. Review is not a rubber stamp, and roughly a third of first listings come back with revision requests. Understanding what reviewers look for shortens the round-trip.
Reviewers check five things. Accuracy: does the description match the curriculum, and do the outcomes match what the curriculum actually delivers. Specificity: are prerequisites, target audience, and outcomes concrete enough that a prospective learner can self-select in or out. Fit: does the course belong on the platform given its verticals. Pricing coherence: does the price make sense given the format, duration, and instructor involvement. Media quality: is the trailer watchable, are screenshots legible, and is the profile photo appropriate.
The most common revision request is specificity. New providers describe target audiences as "anyone interested in data" or outcomes as "understand machine learning better." Reviewers push back on both. Rewrite audiences as roles with seniority ("mid-level data analysts moving into analytics engineering") and outcomes as capabilities ("build a production-ready dbt project with tests, documentation, and a CI pipeline"). This single change often clears review on its own.
The second most common revision is pricing incoherence. A four-week cohort course priced at the entry band, or a two-hour self-paced course priced at the premium band, both get flagged. Not because the price is wrong in absolute terms, but because the price does not match the format signal. Fix this by either changing the price or changing the format description, whichever is closer to what you actually intend to deliver.
Media issues are usually solvable in a day. If your trailer is flagged, it is almost always because the audio quality is poor, the trailer is too long, or the trailer talks about you as an instructor without saying what the course is about. A cheap USB microphone and a second take usually solve the first two. Rewriting the trailer script around the course outcome solves the third.
Review turnaround is typically three to seven business days for a first submission and one to three days for a revision. Plan your launch date accordingly; do not schedule a cohort start date until your listing has cleared review, because the cohort start date shows up in the listing and cannot be moved late without hurting your provider metrics.
Running your first cohort or launching your first self-paced course
Delivery is where new providers either build a reputation or damage one. The launch itself is a moment; the six weeks after are what learners actually remember and review.
For a cohort course, treat the first week as a shakedown. Send a welcome email two to three days before the start date that includes the schedule, the office-hours link, expectations for weekly work, and how to reach you between sessions. Run the first live session tight and on time. Learners are watching to see whether you are organised, and the first session sets their expectations for the whole cohort. Have a backup plan for the inevitable technical glitch: a second device to join from, a recorded backup of the session plan, and a way to communicate with the cohort if the main platform has an outage.
Office hours are the highest-leverage activity in a cohort course. Run them at the same time every week, show up early, and treat them as the primary channel where learners get unstuck. Providers who cancel or reschedule office hours in the first cohort get lower ratings than providers who protect that slot religiously. If you cannot commit to a weekly slot, run a self-paced course instead; do not commit to a cohort format and then dilute it.
For a self-paced course, the equivalent commitment is response time on learner questions. Set an expectation (24 hours on business days is typical), publish it in the listing, and hit it. Self-paced learners assume they are on their own; when they discover the instructor actually responds within a day, they leave better reviews than the underlying content quality alone would produce.
Collect feedback continuously, not just at the end. In a cohort course, run a short mid-cohort survey after week two or three. Ask what is working, what is not, and what one change would improve the experience. Read every response and adjust in the remaining weeks. Learners who see their feedback acted on within the same cohort become your strongest advocates and often leave the most detailed public reviews at the end.
Handle refund requests professionally and quickly. Refunds inside the platform's refund window are largely mechanical, and disputing them beyond what is warranted damages your provider metrics more than the refund itself does. When a learner asks for a refund, ask once for feedback on why (this is useful data), process the refund without friction, and move on.
Iterating from first cohort to second
The gap between your first and second cohort is the most important part of the whole onboarding arc. Providers who treat their first cohort as a one-off event tend to plateau. Providers who treat it as a prototype and systematically iterate tend to grow steadily.
Start the iteration review within two weeks of the cohort ending, while the details are still fresh. Look at four data sources: the exit survey, the public reviews, your own delivery notes, and the platform's provider dashboard metrics (completion rate, satisfaction score, refund rate, question-response time). Each source tells you something different, and together they reveal where to invest.
Completion rate is the metric that most predicts long-term listing health. If less than 60% of cohort learners completed the course, look for the drop-off point in the curriculum. Usually it is a single module where the pacing broke, the prerequisites were mis-scoped, or the assignment was unclear. Fix that one module rather than redesigning the whole course; small targeted fixes compound faster than big rewrites.
Satisfaction and reviews tell you about delivery, not content. If learners rate the course highly on content but lower on responsiveness or session quality, the fix is operational rather than curricular. Common operational fixes include tightening session pacing, adding a second office-hours slot in a different timezone, or introducing a discussion channel that runs between sessions.
Use your second cohort to test one or two specific changes, not a wholesale redesign. Keep everything else constant so you can attribute the effect. Providers who change ten things between cohorts learn nothing about which changes actually mattered. Providers who change two things and measure the impact learn quickly and improve steadily.
By the third cohort, you should be in a position to raise the price if satisfaction and completion metrics are strong. This is also the point at which you can consider adding a second course to your listing set, ideally one that either builds on the first (a natural next step for graduates) or serves a related audience with a different problem. Course portfolios that share an audience compound in reach; unrelated courses on the same profile dilute it.
Common failure modes and how to avoid them
A few failure patterns repeat across new providers. Recognising them in advance is cheaper than living through them.
Over-scoping the first course. Symptoms: the curriculum has twelve modules, the estimated learner hours exceed forty, and the launch date keeps slipping. Fix: cut half the modules, defer them to a future advanced course, and launch the tight version. You can always add depth in a follow-up; you cannot recover the momentum lost from a delayed launch.
Under-pricing to feel safe. Symptoms: the course is priced below comparable listings, the first cohort fills quickly, and the provider is exhausted because the low price attracted a high volume of support-intensive learners. Fix: raise the price to the comparable range for the second cohort, and accept that fewer learners will enroll at first. The higher-price cohort is usually less work per enrolled learner and produces stronger reviews.
Ghosting learners between sessions. Symptoms: office hours are the only touchpoint, the discussion channel is dead, and learners quietly disengage. Fix: post a short weekly recap after each session, tag learners who asked good questions, and prompt discussion with a specific question rather than a generic call for engagement. Ten minutes of asynchronous presence per day dramatically outperforms weekly-only presence.
Over-producing the content. Symptoms: every video is polished, animated, and re-edited, but the launch keeps slipping and the provider is burning out on production rather than teaching. Fix: accept that screen recordings with clean audio and a competent narrative are the delivery standard, not cinematic production. Learners come for the expertise, not the animation quality. Save the polish for evergreen assets after the first cohort has validated the content.
Ignoring the platform's data. Symptoms: the provider dashboard has metrics that would clearly indicate where the course is losing learners, but the provider does not check them. Fix: build a fifteen-minute weekly review into your calendar during any active cohort, and a longer review at the end of each cohort. The metrics are there specifically to shorten your feedback loop.
Your first ninety days as a Refonte course provider
A rough timeline for the first ninety days looks like this. Days one through fourteen: application submitted, profile drafted, first course scoped. Days fifteen through thirty: approval received, profile finalised, curriculum outlined, pricing decided. Days thirty-one through forty-five: listing built, listing submitted for review, revisions completed, launch date confirmed. Days forty-six through seventy-five: first cohort delivered (or first two weeks of self-paced enrollments handled). Days seventy-six through ninety: cohort wrap-up, review analysis, iteration plan for the second cohort or expansion of the self-paced course.
This timeline assumes you are doing the work in evenings and weekends alongside a day job. If you have full-time bandwidth, the whole cycle can compress into six to eight weeks. If you have less than five hours a week to invest, extend the timeline rather than shortcut any single step. The steps do not compress well; skipping profile depth, curriculum outcome design, or listing specificity in the interest of speed produces a listing that does not convert, and no amount of downstream marketing rescues it.
Throughout, keep two documents open. The first is your own working log: a running list of decisions, questions, and things you want to revisit after the first cohort. The second is the pillar guide on selling courses on the platform, which anchors your decisions in the wider platform context. Between them, you have a fast-feedback loop against your own thinking and a slower-feedback loop against the ecosystem.
Refonte Learning is designed to make the mechanics of getting started as straightforward as possible, but the substance of a course, the thing that actually gets a learner from where they are to where they want to be, is still your work. That is not a limitation of the platform; it is the point of the platform. Learners are paying for you, mediated by a marketplace that handles distribution, payments, and infrastructure. Your job is to make sure the thing they are paying for is worth the money.
When you are ready to begin, become an instructor on Refonte Learning is the single link to bookmark. Complete the application, and the rest of this playbook becomes your operating manual for the next ninety days.
About Refonte Learning
Refonte Learning is a vertical marketplace for professional training in AI, data, cloud, DevOps, cybersecurity, and software engineering. It is operated by Refonte Infini Infiniment Grand, a French SAS registered with the INPI under SIREN 949 841 605 (verifiable at https://data.inpi.fr/entreprises/949841605), with an operational office at 1 Poulton Close, Dover, Kent, CT17 0HL, United Kingdom. Refonte Learning works with practitioner-instructors worldwide to bring hands-on, employer-aligned training to learners who need to grow specific technical capabilities.