Peerfold — full product detail Source: docs/feature-overview.md (the product documentation, converted to plain text) Canonical: https://www.peerfold.com/llms-full.txt # Peerfold — Feature Overview The CRM-native learning platform. Peerfold is a standalone, multi-tenant LMS that treats your CRM as the system of record: every enrollment, lesson, quiz, certificate, and credit a learner earns lands on the contact and company records your team already works from. It is also the first LMS built agent-first — a complete REST API, MCP server, and agent devkit mean your team (or your AI tools) can build and run courses without opening the admin at all, and where an agent does open the admin, the screens themselves publish tools it can drive. A workspace can also run a community — cohorts, discussions, member profiles and moderation — on the same member identity as the academy, either as an add-on to any plan or as the Community plan on its own. The four Community: sections below cover it. The same workspace can run a partner program: partners who sell, refer or resell on your behalf, their tiers and permissions, the leads and deals they bring, what they are owed for the ones that close, and a signed-in area of your own portal where they do all of it. The four Partner program: sections below cover that. Everything else on this page is the academy. ## Course authoring - Three-pane visual editor — outline, canvas, and inspector with autosave, undo, drag-and-drop, and click-to-edit text directly on the canvas. Publish is explicit and versioned: learners always see a consistent, immutable revision. - 21 content block types — rich text, headings, images, video, audio, embeds, files, resource lists, buttons, dividers, quizzes, timers, accordions, columns, callouts, plus interactive learning blocks: process walkthroughs, flashcards, sorting exercises, gated continue buttons, a discussion, and an interactive experience of your own. - Peerfold AI course builder — paste source material (up to 64k characters) or describe the course you want; Peerfold AI drafts the outline for your review, then generates every lesson with live per-lesson progress, grounded in your source material. Quiz drafts are flagged for human review, and nothing ever auto-publishes. - Quizzes & exams — server-graded quizzes with configurable pass thresholds, timed exams, open-ended questions with a manual grading queue, and retake controls. - SCORM, natively — import SCORM 1.2 and 2004 packages and play them in a first-party runtime (no per-learner fees, no third-party player). Multi-SCO packages become multi-lesson courses; a completion inspector shows admins exactly what the package reported. Single-package courses can launch straight into the content. - xAPI and cmi5 too — the same import, the same player, the same completion inspector, for the format your authoring tool publishes rather than the one it does not. Each launch carries its own credential and its own statement record, and the lesson's completion rule is set against what the package actually reported when you played it. - Interactive experiences you build with AI — a block that runs a small app of your own inside a lesson: a drag-and-drop sorter, a branching scenario, a calculator, a simulation. The inspector hands you a prompt that teaches Claude, ChatGPT or Grok the contract; you upload the one .html file it gives back, or a .zip with index.html at its top. Peerfold gives it somewhere safe to run, remembers where each learner got to, and can make finishing it complete the lesson. A test run shows you what it reported before anybody else sees it. - Whether the experience is working — three counts per experience across everyone enrolled, what learners did inside it, and the per-learner record, so the question "is this thing any good" has an answer that is not a hunch. - Archiving and deleting — archiving takes a course off the shelf and keeps everything. Deleting removes it from learners at once and holds it for 30 days, reversible the whole time, before the content is erased for good. Certificates people already earned keep working either way, permanently, and the CRM record of what they did stays where it is. - First-party video hosting — upload once, stream everywhere: adaptive playback, chapters, hover-scrub, speed controls, captions auto-generated with an interactive click-to-seek transcript. Or point a video block at files you already host. Optional must-watch gates tie completion to genuine watch coverage (scrubbing earns nothing). - Thumbnails & theming per course, immersive full-width layout option, and one-click Preview as learner deep into any lesson. ## Audio lessons (Professional+) - The lesson you already wrote, read aloud — one button in the lesson inspector narrates it and puts an audio player at the top of the page. There is no script to write and nothing for the learner to install: play, pause, scrub, elapsed and total time, and a speed control, built from real controls so the keyboard and a screen reader both work. - Bring your own speech account — ElevenLabs for premium narration and a large voice library, or Google for roughly a tenth of the cost per narrated minute and thirty stock voices. The minutes are billed to you at your provider's prices with nothing added. A workspace already running Peerfold AI on its own Google key can narrate with no second key and no second bill, and the key is validated before it is stored, encrypted, and never shown again. - A run you can walk away from — a long lesson is read in several passes with a progress bar; close the editor and Continue picks up where it stopped, so no passage is read twice and none is billed twice. A provider rate limit makes the run wait its turn instead of failing. - Audio never regenerates itself — change the lesson text and the panel says the narration is out of date while the old file keeps playing. Regenerating is a button you press, because every regeneration spends your credits. Rearranging blocks without changing the words changes nothing. - Switching providers changes nothing you already made — existing narration keeps playing in the voice it was generated with, a run finishes on the provider it started on, and each provider remembers its own narrator. - Learners are never told how it was made, and listening does not complete a lesson: audio behaves like a video with no watch requirement. ## Programs & landing pages - Learning pathways & certificate programs — bundle courses into an ordered program with required and optional courses, soft sequencing, program-level certificates with their own serial numbers, and credit totals rolled up from the courses. - Coursera-style landing pages — every program (and any course) gets a customizable public landing page: hero with optional video trailer, outcomes, the course series with expandable details, credential showcase with a real certificate preview, instructor section, FAQ, and a pricing band. Section-level editing, tenant branding throughout. - Certificate verification — every certificate carries a serial and a public verification page; landing pages link straight to it. ## Reuse, duplication & multiple workspaces - Borrow a lesson from another course — copy it, or LINK it. A linked lesson stays live: republish the source and every course borrowing it updates, while the borrowing course shows a read-only canvas with a route back to the source and a warning before you publish something stale. - Curated courses — assemble a course out of lessons the workspace already teaches, in the order you choose. It is born unlisted, so the direct link opens for enrolled learners only, and you add the people or the whole organization it was built for. - Duplicate a course in place when you want a variant: a fresh draft, with no learner attached to it. - Clone or move across workspaces — an agency or a multi-brand team can lift a course or a program into another workspace they administer. Media bytes are copied rather than shared, so the two workspaces are independent afterward; a program brings or maps its courses; and a move is a clone that archives the original once nobody is enrolled. Learner data never crosses, in any direction. - A clone report that names every setting the copy deliberately did not inherit, so nothing arrives in a new workspace by accident. ## Learner experience - White-label learner portal on your own domain — tenant branding (logo, colors with automatic accessibility contrast, Google Fonts), in eleven built-in languages plus one of your own, each learner reading in the one they picked, with navigation that collapses into a menu on a phone and search always within reach. - Frictionless sign-in — passwordless email codes, recognition of returning visitors and known CRM contacts ("Continue as r•••@…"), post-purchase claim links, and zero-login membership assertions for HubSpot-hosted portals. - Progress that resumes everywhere — per-lesson time tracking, video resume positions, SCORM bookmarks, and a personal dashboard that picks up where the learner left off. - Learner profiles with CRM-synced details, certificates, and credits. ## Languages & translation - Five built-in portal languages — English, Spanish, French, Italian and Norwegian bokmål, one of them the workspace default, with a live sample of three real portal labels under the picker so you can check the choice before saving it. - Every learner picks their own — a chooser under the email box on the sign-in screen, so even the first six-digit code arrives in their language, and again on their profile. It offers only what the workspace can actually display. A learner's own choice always wins, and a first-time visitor whose browser asks for one of your languages gets it without anyone doing anything. - A custom workspace language, in any language at all — pick any language the product knows, give it your own name if you want one, and Peerfold AI seeds all 555 portal labels from English in a batched, resumable run. A grouped, searchable editor takes it from there, with revert-to-AI-draft and show-English-here per label, and a refusal to save wording that has dropped a value the product fills in. Anything you have not written shows English, so a half-finished language is a usable one. Seeding needs the same plan feature as the AI course builder; editing by hand never does. - What a learner's language decides — the portal chrome, their emails (sign-in codes, deadline and renewal reminders, certificate notices, purchase confirmations), and the way dates and prices are written. The AI tutor falls back to it when a message is too short to tell. - Certificates follow the COURSE, not the reader — a certificate is a document a third party verifies, so two people who finish the same Spanish course get the same Spanish certificate. Course language is a field on the course, drawn from the full 81-language list rather than the five, and it travels to the CRM. - Language demand, measured — a report in Settings and again on Reports, with two columns: learners who chose a language, and what their browser asked for at sign-in. Each learner counts once, staff previewing the portal never count, and the two columns are labeled differently because a work laptop pinned to English is not a preference. Evidence before you commission a translation. - Emails and certificates use the eleven built-in languages. A custom language covers the portal, and the admin side is English today. The product says so on the screen where you make the choice. ## Peerfold AI for learners (Enterprise) - A tutor inside the course — a learner asks a question in the lesson they are standing in and gets a grounded, cited answer built from that course's own material: its lessons, its brief, the knowledge you add to the workspace, and SCORM text where an author has vouched for it. The tutor knows which lesson is open, so "explain this differently" needs no further context, and it says when the course does not cover something instead of filling the gap. - A tutor for the whole program — one thread per program that answers what to do next and why, reading the pathway's structure, the briefs of every course in it, and the learner's own progress. - Ask Peerfold AI from search — a learner searching the portal gets a final row that carries the words they just typed into the tutor. It appears only for learners who have a course or program with a tutor in it. - Retrieval that follows the meaning — semantic and keyword retrieval run together and their rankings are fused, so a question asked in the learner's own words still finds the lesson that teaches it. - Yours to supervise — a monthly message allowance per workspace, a tone you set, and transcripts admins can read. ## Certificates & credits - Drag-and-drop certificate designer (Enterprise) — design custom certificates on a visual canvas with merge tags, brand palettes, images, and shapes; issued certificates pin their design forever. - CEU / continuing-education credits — define your own credit types (CEUs, contact hours, HRCI, anything), assign multiple types per course, display them on courses, catalogs, and certificates, and keep an append-only earned-credits ledger per learner — synced to the CRM. - Credit filed with ACCME, automatically (Enterprise) — an accredited provider's completions become learner records at ACCME's Program and Activity Reporting System, which passes MOC credit to the certifying board. Map a course to a PARS activity, or register the activity from the course editor; the ledger shows every record filed, and a detail you got wrong is corrected by withdrawing and resubmitting rather than by emailing anybody. It needs your own provider ID and the web-services account ACCME issues you. ## Badging & credentials - LinkedIn Add to Profile (Professional+) — one click puts a Peerfold certificate on a learner's LinkedIn profile, prefilled with the credential name, your company page, the issue and expiry months, the serial and a link back to your verification page. LinkedIn posts the addition to the learner's feed and the learner auto-follows your company page, so every completion becomes organic reach. Placed in the completion email, on the learner's certificate surfaces, and on completed courses on their dashboard. - Completion email — a branded message the moment a certificate is issued, carrying the serial, the verification link and the share button; idempotent, so a retry never sends it twice. - Standards-compliant Open Badges 2.0 (Professional+) — every certificate is also a machine-verifiable badge served from your own portal: issuer profile, one badge class per course or program, one assertion per certificate, hosted verification, and no per-badge platform fee. Recipient emails are published only as a salted one-way hash. - Per-tenant issuer identity — the issuer is your workspace: your name, your portal address, your logo, your contact address. No platform identity appears anywhere in the credential chain. - Badge artwork with no authoring burden — a square badge is generated from your brand color, your workspace mark and the course name, with a per-course image override when you have your own. - Revocation that verifiers can read — a revoked certificate keeps a live badge address that reports it as revoked, rather than disappearing and looking like an outage. Unknown serials resolve to nothing. - A human and a machine link for the same credential — the public verification page anyone can read, and the badge document any other system can fetch, each pointing at the other. - Issuer connectors (Professional+) — issue the same completion through an outside credential network as well as your own portal. Accredible connects today: your Accredible groups become the templates you map courses to, issuance rides the same retrying outbound queue every CRM write uses, and revoking a certificate revokes the credential downstream. Credly, Badgr / Canvas Credentials and Certifier adapters run on the same framework. - The provider's credential becomes the shareable one — where a connector has issued a certificate, that provider's credential page is what the LinkedIn button points at. Same button, one field, no second workflow to run. ## Deadlines & compliance - Training deadlines on any enrollment or seat assignment — explicit dates, or automatic "due N days after enrollment" rules per course or program. - Reminder rail — branded emails at 7 days, 1 day, and a capped weekly overdue cadence, all idempotent (never a duplicate send). Deadlines are always advisory: an overdue learner keeps full access. - Overdue visibility everywhere — admin dashboard attention row, learner-list filters and exports, org-portal rollups, and due/overdue fields on CRM contact records for list-building and workflows. - Recertification cycles — a certificate that expires can be renewed without re-enrolling anyone. Set a renewal window and the learner is notified before expiry; the final exam reopens, and passing issues a NEW certificate with its own serial while the old one stays the immutable record it always was. Credits are earned again each cycle, reminders are cycle-qualified, and a renewal can carry its own price. ## Commerce & monetization - Sell courses directly — price any course, hosted checkout, guest purchase with email claim links, refund handling with configurable access policy. - Cart on your marketing site — a 5KB embeddable cart drawer for any website, with abandoned-cart recovery emails. - Memberships & tiers — recurring or lifetime membership tiers covering all or selected courses, free trials, promo codes, self-serve billing portal, tier switching with proration. - Organization seats — sell or grant seat pools to companies; org admins distribute seats from their own portal. Tier-scoped pools make "50 seats of Gold for Acme" one purchase. - Lead-gen mode — flip a course from paid to lead capture: the course page becomes the form, submissions land in your CRM with attribution, and the learner is enrolled the moment they verify their inbox. ## Organizations & teams - Customer-org admin portal — companies you train get their own portal: seat assignment, per-location progress, certificate expiry views, signup links, exports. - Workspace teams — invite teammates with roles; authors see authoring surfaces only. ## CRM-native sync - HubSpot, deeply — enrollments become My Course records; status, percent complete (with partial credit for videos and SCORM), exam scores, certificates, membership tier/status, earned credits, and training deadlines all live on the contact. Timeline notes on completions and milestones. Optional membership deals in your chosen pipeline. List-based access rules enroll and revoke automatically. - Day.ai — the same learning signals mirrored onto Day.ai people and organizations, with activity timeline entries — connect a workspace in minutes with per-tenant OAuth. - Sync health — a live console showing every outbound write, with automatic retries, self-healing for deleted CRM records, and alerts on dead letters. - HubSpot CMS theme — run the learner experience inside your HubSpot website with the companion theme: shared login, embedded SCORM player, and progress that flows back to Cloud and the CRM. ## Automation & integrations - Zapier (Professional+) — wire training into the rest of the stack without writing anything. Eight triggers (learner enrolled, course completed, certificate issued, new learner, purchase completed, training overdue, live session registration, live session attended), six actions (find or create a learner, enroll in a course, enroll in a program, unenroll, set a training deadline, register for a live session) and three searches (learner, course, program). You authorize from Zapier's own screen, and Settings → Zapier shows the connection, what it can do, and the Zaps built on it. Invite-only today. - Everything else, through the open surfaces — signed webhooks, the REST API and the MCP server carry any integration the catalog above does not, including credential platforms without a native connector of their own. ## Live sessions - A live lesson type: schedule sessions with join links and calendar (ICS) invites, automatic reminders, and a join window around start time. - Attendance is completion — verified from Zoom, GoToWebinar, or Microsoft Teams participant reports, by self check-in, or from a manual roster — so live attendance earns certificates and credits like any other lesson. - Webinar platforms as well as meeting platforms — Contrast and Wistia Live connect with a key you paste rather than an OAuth trip, and they answer the question the meeting platforms cannot: who watched the recording afterward. Attendance from a replay counts the same way attendance in the room does. ## Community: cohorts & discussions (Community plan or add-on) - Cohorts are the rooms — one per group you run, created from Community → Cohorts with a name, a web address, a description and a sort order. Comments, likes and video embeds are switches on the cohort itself, so one room can be read-only without changing any other. Archiving takes a cohort out of every listing and stops new posts and joins while the people already in it keep reading; deleting is refused once anybody has written in it, so nobody's thread disappears with the room. - Four visibility tiers, decided on the server — public reads with no session at all, signed-in members is the default, members only admits any authenticated member of the workspace, and invite only needs a membership row: that room is absent from the listing and its address opens for nobody else. Every read on every surface — the portal page, the feed, the REST API, an MCP tool, a discussion block embedded in a lesson — goes through the same decision, so there is no client-side half of the rule to get around. - Threads and comments — a rich composer with a cover image and tags, comments under every thread, and a moderator's two marks: pin a thread to the top of its cohort, and mark the comment that answered the question so it sorts to the front. - Four reactions, and thread follows — Like, Celebrate, Insightful and Question, and somebody may pick more than one, because nobody should have to give up "this is useful" to also say "well done". A post nobody has reacted to shows no row of gray zeroes, a listing shows one combined count, and the cohort's Likes switch covers all four. A follow keeps a thread in the follower's feed. - Polls — ask the room a question with two to six options, an optional closing date, and a choice about when people see the numbers. - Ideas boards — a cohort shaped as a suggestion box with a roadmap attached: ranked ideas, one vote per person that they can take back, and five statuses a moderator sets, two of which ask for the one-line reason a board lives or dies by. Voting closes only on Declined, because the count on a shipped idea is a record of how much people wanted it. A cap on how many ideas one person may have open is set for the workspace, per board, or for one person. - Announcements at a set time — a moderator writes now and it appears on Monday morning: absent from the room, the feed, search and the counts until then, and nobody is notified early either. Members who moderate nothing never see the control. - Events in the room — a live session can be attached to cohorts, and each room carries its own calendar of what is coming. - Mentions — type @ in any composer, pick a name, and that person is told. - Find it again — the portal's ⌘K search gains a Discussions group, matching a thread's title, its opening words and the name of the room it is in, because people remember it was "in Onboarding". It only ever returns rooms the reader can already read. - Joining — an open cohort admits anyone signed in, and posting in one joins them automatically; an invite-only cohort is joined only by an admin or a moderator adding somebody by email. Removing a member takes away their access to that room and leaves everything they wrote exactly where it is. ## Community: profiles, follows & the feed (Community plan or add-on) - One member across both halves — a community profile is a sidecar on the same member record the academy uses. No second account, no second sign-in, no second password: whoever signs in to your portal is who posts in your community. - The profile is minted when they act, and named when they post — a like or a follow creates the profile row with no username, because choosing somebody's public name for them the instant they tap a heart is a decision the product should not be making on their behalf. They are asked for a username exactly once, at their first post, where a public author identity starts to matter. Reading, liking and following never need one. - A member directory — searchable, a card per member, each linking to their profile page and the threads they have written. Visibility is theirs: public profiles read without a session, visible ones need one, and hidden leaves them out of the listing and 404s their profile page. Hidden means unlisted, not anonymous — their name still appears on what they wrote, and the product says so rather than implying a privacy it cannot deliver. - Member follows — a plain follower→followed graph between members, shown on both profiles. - A for-you feed — recent threads from the rooms a member belongs to, plus the threads they follow, newest first. Every candidate passes the same visibility decision the cohort page makes, so a member removed from a private room stops seeing its threads in their feed rather than keeping a window into it. - Achievement badges and a leaderboard — First post, Solution author and Top contributor are awarded automatically out of the box; rename them in your own words, add your own, or hand one out and take it back. An activity score ranks who is doing the most. These are decorations, not credentials: the certificates and Open Badges your learners earn for finishing training are a different thing entirely, and one switch turns the whole community layer off without touching them. - A bell, an inbox, and a browser — the last fifteen things that happened to a member sit behind a bell in your portal header. Each kind of community email has its own frequency, set by the member, and a member who wants their browser to tell them enables that from their own profile. Nobody is ever notified about something they did themselves. ## Community: moderation & member permissions (Community plan or add-on) - Two moderator roles, independent of each other — a cohort moderator runs one room, set from that cohort's own page; a workspace moderator runs every room, invite-only ones included, set on Members & roles. Neither is needed by somebody who administers the workspace. - Moderation happens where the discussion is — a moderator pins a thread, marks a solution, or takes a post out of view from the portal itself. Hiding is not deleting and restoring is not editing: the words are never touched, and Restore puts the post back where members read it. - A moderation queue in the admin — two lists on one screen, because the work arrives from two directions. Posts out of the portal (hidden by a moderator, or withdrawn by their author) oldest first, since the oldest unhandled item has been unfair to somebody the longest; and abuse reports from members. A report records what the reporter said and the address they were reading, and it survives the thing it names being deleted, which is the usual outcome of acting on one. Marking a report handled closes the report and touches nothing else. - Workspace defaults with per-member overrides — four switches for whether members may edit and delete their own threads and comments, plus whether a username is required before a first post. Each one can be set to Inherit, Allow or Deny for a single person, so one member can be given editing rights without opening editing to everybody, or have it taken away without closing it for everybody. ## Community: in your courses, API & packaging (Community plan or add-on) - A discussion block in any lesson — the block registry carries a discussion type that points at a cohort or a thread by its web address and draws it as a card, or as a preview listing the most recent threads or comments. The lesson body holds a pointer rather than a copy, and the reader's own standing decides what resolves: a private room shows nothing to a learner who is not in it. A course carried into a workspace that has no community resolves to a quiet card instead of an upsell. - The same community over REST and MCP — twenty-four endpoints under /api/v1/community covering cohorts, threads, comments, reactions, polls, ideas, follows, the feed, the directory, badges, notifications, search, profiles and reports, and thirty-one MCP tools over the same service layer, so an assistant can open a cohort, add its members, start a thread on somebody's behalf and work the moderation queue. Every write is audit-logged, and the authorization matrix is one function all of them call rather than a rule reimplemented per surface. - Community webhooks — thread created, comment created, member joined a cohort, thread deleted, content reported, idea created, idea status changed, event scheduled, reaction added and badge awarded: ten signed events delivered on the same rail as every other one. - Headless community — the whole of it answers the public API, so it can be built into your own React app or a HubSpot theme with your screens and your navigation. - A plan of its own, or an add-on — the Community plan is community without an academy: cohorts, discussions, member profiles, your own domain and the developer API. On Starter, Professional and Enterprise it is an add-on bought from Settings → Billing that leaves the plan exactly as it is. Moving between them keeps every cohort, thread and member where it stands. - Community-first onboarding — a workspace that arrives through the community door gets a setup checklist that asks for a cohort where an academy's asks for a course: it opens a General cohort, posts a welcome thread signed with a username chosen on the spot, and adds the first members by email. ## Partner program: partners, tiers & their portal (Add-on) - A partner is somebody who sells, refers or resells for you — give them a tier and they get their own signed-in area of your portal at /partner, reached with the same emailed code your learners use. If that person already learns with you, they keep the account they have and gain a partner area beside it. Nobody ends up with two logins, and somebody who is not a partner never sees the link. - Tiers carry the rules — a default commission rate, the HubSpot pipeline and entry stage a tier's deals are created in, the stages that mean won, and a deal-name template with a live preview as you type. Tiers are yours to name: Gold, Referral, Dealer, whatever your program already calls them. - Eight permissions per tier — whether the tier may register leads at all, take a lead nobody holds, take one whose protection has run out, hand a lead back early, create deals, type the deal amount, earn commission, and see the assets library. A permission that is off removes that surface from the partner's portal, so nobody is shown a locked door. - Companies, or people — one program-level choice decides whether a partner's own tier wins or their organization's does, so a program run with dealerships reads correctly without changing how a program run with individuals reads. The other row stays the fallback either way, and switching costs nobody their tier. - Rename the vocabulary — "partner" can read as dealer, installer or reseller throughout, because the word your program already uses is the one your partners will recognize. - Run the roster — a commission override on one person shows in full ink beside inherited rates so a negotiated deal is visible at a glance; suspending hides their portal and stops new registrations while commission already earned still pays; View as partner opens their portal read-only and writes an audit entry; and removing somebody takes away the partner role and leaves their account, courses and certificates untouched. - Their portal — a dashboard, their leads and deals, an assets tab filtered to what their tier may have, their referral links, a profile they own, and a commissions tab where the tier earns them. Their tier and organization are shown and not editable: those are yours to set. ## Partner program: leads, deals & the CRM (Add-on) - Registering a lead, and the five answers — a partner registers a company from their portal and the duplicate check replies: nobody has it, and it is theirs for the window their tier sets; they already have it, and their details update without buying more time; their own registration expired, and Register again starts a fresh window while keeping the history; another partner holds it live, refused, naming the company and the date it clears; or it is already your customer, refused, pointing them at your account team. Every refusal keeps what they typed, says what to do next, and writes nothing to your CRM. - A protection window that means something — the date is stamped at registration, so shortening the window next quarter never reopens a claim somebody already made. - Your lead book and your deals — every registration in the program, whoever made it, with a status you set and a reassignment or release that is logged with who did it. Deal stage, amount and close date belong to your team; the partner's own notes and forecast confidence belong to them and are never overwritten. - HubSpot, prepared in one press — the contact, company and deal properties and the labeled associations the program writes to are added where they are missing and reported where they already exist. Nothing is renamed, archived or deleted. A workspace already running the RocketPRM HubSpot theme has all of it: both products write the same fields, on purpose. - Sync runs both ways, and they are not the same thing — what you and your partners do here is queued out to HubSpot; what your sales team does in HubSpot comes back every thirty minutes. The inbound pass only reads: it never writes, never invents a deal or contact, and never changes a lead's status, because a lead's status is your decision. Opening a record that has not synced for a while refreshes that one record in the background, after the page has already drawn. - Every record keeps its history — stage moves as HubSpot dated them, beside the registrations, claims, status changes and reassignments as they happened here. Settings → Sync carries a card with the last run, how far behind HubSpot it is, and any errors. - Partner screens read Peerfold, never your CRM — which is what keeps them fast for people outside your company, and why a slow or disconnected portal never makes a partner's dashboard hang. ## Partner program: commissions & payouts (Add-on) - Eight figures, one answer — leads registered, accepted, deals created, open deals, pipeline value, closed won, win rate and average days to close, over a window of 30, 60, 90 or 365 days that lives in the web address so you can send somebody exactly what you are looking at. Every partner sees the same eight for themselves, from the same place, so a partner ringing you about their pipeline is looking at your number. - A dash is not a zero — win rate and days-to-close show a dash where nothing was decided in the window, which is a different fact from 0%. The trend under a figure compares your window with the one before it, moving counts in per cent, rates in points and days in days. - Commission is worked out once — on the day a deal crosses a won stage, from the deal amount at that moment times the rate that answered (the partner's override, or their tier's default, with the line recording which). Changing a tier's rate next quarter cannot rewrite what somebody was already owed. - Accrued, payable, paid — an append-only ledger with a fourth state for the ones that come back: un-winning a deal voids its commission and leaves the line on the statement with a negative amount so the balance still adds up. A commission already paid is never reversed automatically, because money that has left your bank is not un-spent by a stage change. - The partner's statement — every line with its deal, its rate, where the rate came from, its status and a running balance, and the totals on their dashboard. A tier that earns no commission has no such tab and no such card: the surface is absent rather than empty. - Payout runs — approve what you agree with, void what you do not with a reason that stays on the partner's statement, then open a draft run that reserves its lines so a colleague cannot pick up the same ones. Record how you paid and the reference, and the page tells you exactly what pressing the button will do before you press it. A recorded run is a receipt and never changes afterward. - What recording writes back — commission paid, its date, the amount and the commission status, on each HubSpot deal in the run, queued rather than immediate. Stage, amount, close date and owner belong to your sales team and are never touched. Every run has a CSV for whoever does your accounts. - Peerfold keeps the ledger and never moves the money — you pay your partners the way you already do, by check, transfer or bill.com, and record it here. Disbursing in-product would drag in partner onboarding, identity checks and tax forms, and the screens say so out loud instead of leaving an admin to work it out from a missing button. ## Partner program: assets & referral links (Add-on) - A library partners take to a prospect — one-pagers, decks, logo packs, case studies and price lists, as a file up to 50MB or a link to something you already host. Tags become the filter buttons above their grid, and a language list prints under the title. - Tier-gated, on the server — every partner, or only the tiers you tick. An asset a partner may not have never reaches their browser, so a price list marked Gold-only cannot be found by a Silver partner who knows where to look. Unpublishing takes an asset away from everybody without deleting it. - A link that says who sent them — every partner gets one, and can build extra links pointing at a particular page, each counting its own clicks and signups so they can tell which is working. An asset marked as a referral asset copies with their code already in it. - One script tag — installed once before on your marketing site. It sets no cookies. Nothing is credited until your own form calls identify() with an email address it has learned, because the snippet deliberately does not read your form fields by itself. The attribution window, 30 days out of the box, is yours to set. - A registered lead always beats a referral click — where another partner's protection window is still running, the signup is recorded as not attributed with the reason on the row and the existing registration stands. A click never takes a lead away from anybody and never registers one on a partner's behalf: registering stays something they do deliberately, with the duplicate check in front of them. - Attribution reaches the CRM the same way everything else does — the contact's lead status is set and the referring partner is associated to them, on the outbound queue every other write rides, so a visitor's signup never waits on your portal. ## Developer & agent platform - REST API, spec-first — a complete OpenAPI 3.1 surface for both the learner plane and the admin plane, with API keys, per-tenant CORS, rate limits, and idempotency built in. - MCP server — 120 tools over the Model Context Protocol: an AI assistant with a connection can build a complete course, author exams, enroll learners, set pricing, check org progress, and publish — every write audit-logged, every guardrail enforced server-side. - The documentation is a tool too — search_help answers an assistant out of this deployment's own Help Center, on the same ranking the search box in the admin uses, and every hit names the guide to read in full and the page to send a person to. An agent that cannot find your documentation answers from its training data instead, which is how somebody gets told about a screen this product does not have. - WebMCP page tools — the admin also publishes tools to the browser's own agent surface, so an agent running in the browser works the app the way a person does: the signed-in session, no key, no server-to-server call. Tools are registered per screen and vanish when you leave it, so what an agent can see is what is true right now. Every one of them reads, navigates, or stages: staging opens the dialog a person would open, fills in what it was given, and stops with the cursor on the button. Creating a course, sending an invite, publishing and connecting HubSpot are named in code as controls a plan may focus and may never press, and a test fails the build if a plan presses one. The surface is inert until a deployment registers for the browser's origin trial. - Agent DevKit — one download gives any coding agent everything it needs to build on your portal: CLAUDE.md, AGENTS.md, Cursor rules, Replit/Lovable/Copilot files, llms.txt, and a personalized .env — never containing secrets. - SDKs & embeds — typed API client, React hooks, a small browser bundle, and the embeddable cart. - Webhooks — a twenty-three-event catalog, HMAC-signed, with delivery management in the UI. Ten of the twenty-three are the community events above; a workspace without the community never sees them fire. - Headless auth — PKCE flows, token exchange, and sandbox tenants with test keys so integrations are built safely. - Developer docs in the app — the REST API, MCP, WebMCP, webhooks and learner-auth guides sit at /help/dev, beside the Help Center the rest of the team reads. ## Help & Peerfold AI in the admin - A help panel on every admin screen — a round button in the corner opens three doors: the guide for the page you are standing on, Peerfold AI, and an email address that reaches a person. It follows you around the app, holds its conversation while you navigate, and comes back as you left it after a reload. Learners never see it. - Cited answers, and a refusal instead of a guess — Peerfold AI answers from this deployment's own Help Center and nothing else, names the guides it drew on as chips you can open, and says it has no documentation on something rather than inventing a setting name. It cannot see your workspace's data and it cannot change anything; it tells you which screen makes the change. - Take me there — where an answer is about a screen, a button under it opens that screen with the panel still open, so reading the next step and doing it are one motion. Destinations are derived from the guides the answer cited, never from the model's prose. - "Show me" walkthroughs — for the tasks people ask about most (create a course, publish one, set a price, invite a teammate, connect HubSpot) the answer can run a spotlight on your own screen: the page dims except the one control, clicking it or pressing Next advances, Esc leaves, and a step that lives on another screen offers to take you there and resume. A walkthrough only points; it never clicks for you. When a control genuinely is not on your screen it stops and says so instead of highlighting something near it. - Ask out loud, on deployments that switch it on — an Ask pill in the top bar opens a panel that listens, shows the words as you say them, and answers in speech and in writing from the same guides with the same citations. Each screen offers two to four questions written for it. A spoken question about a screen opens that screen for you, with Stay here to undo it; a typed question never moves you. Block the microphone, or use a browser that cannot listen, and the same panel becomes a text box. - "Did this help?" — one question under every answer, and the only signal that says which guide is letting people down. The question, the guides it cited and the verdict are kept. Nothing about the workspace is, because the assistant never saw it. - One assistant, one allowance — 25 questions an hour across both doors, with the documentation and the support address open the whole time. - In-app Help Center — task-shaped guides for marketers, course builders, org admins and developers, updated in the same release as the feature they describe. ## Enterprise & security - Single sign-on — OIDC/SAML for admins and OIDC for learners, with domain-based routing, just-in-time provisioning, enforced-SSO with owner break-glass protection, and per-organization connections a customer org can configure for its own people (DNS-verified, tenant-controlled). - Certificate designer, admin API, and embed allowlists are Enterprise-tier capabilities. - Security posture throughout — tenant credentials encrypted at rest (AES-256-GCM), single-use signed grants for impersonation and claims, httpOnly sessions, per-tenant CORS and frame-ancestor allowlists, audit logs on every mutation, and strict tenant isolation on every query. ## Platform & operations - True multi-tenancy — isolated workspaces, custom domains with managed SSL, a workspace switcher for agencies running several. - Email from your own address — verified sending domains or your own SMTP, customizable message text within safe platform-controlled templates, live preview and test send. - Analytics & reports — real-time dashboard, activity reporting, per-learner records, CSV exports everywhere. - Billing built in — plans with trials, usage visibility, and add-ons (commerce, org seats) purchasable à la carte. - Modern admin — grouped navigation, a searchable settings hub with live status, and a ⌘K command palette over every page, record, and action. The top bar carries the docs link, search, the Ask pill where it is enabled, and an account menu with the workspace switcher inside it. Some capabilities are plan-gated (marked Enterprise or Professional+ above). The community and the partner program are add-ons; the community is also a plan of its own. # Pricing Full pricing page: https://www.peerfold.com/pricing. Seven-day free trial with every feature on, no card. Billed annually, every plan is about 28% cheaper than monthly. ## Starter — $209/mo, or $149/mo billed annually ($1,788/yr) Launch your academy. - 1,000 active learners a month - Courses, programs, live sessions, certificates + CEUs - Sell courses & memberships — 0% fees - Your domain + HubSpot list rules - HubSpot, Salesforce & Day.ai sync - Public API, webhooks, MCP + agent devkit - Zapier, Slack, Canva + lesson audio - Embedded video — YouTube, Vimeo, Wistia ## Professional — $816/mo, or $583/mo billed annually ($7,000/yr) The AI-era academy, with SSO. - , plus: - 5,000 active learners a month - AI course builder - AI Tutor for learners - Certificate designer + Open Badges credentials - SAML/OIDC single sign-on - HubSpot theme repoint - 2,400 minutes hosted video ## Enterprise — $1,800/mo, or $1,292/mo billed annually ($15,500/yr) Standards, scale, your front end. - , plus: - 20,000 active learners a month - SCORM + xAPI/cmi5 import (10 GB) - Headless — your front end on the learner APIs - Organization seats + customer admin portal included - Credit reported to ACCME PARS - 5,000 minutes hosted video ## Add-ons - Community — $350/mo · $3,000/yr, on any academy plan - Organization seats — $99/mo on Starter & Professional · included with Enterprise ## Community — standalone plan: $700/mo, or $500/mo billed annually ($6,000/yr) Academy features not included. ## Every feature, every plan Columns: Starter · Professional · Enterprise · Community (standalone). 01 Create - Courses, lessons & 21 block types: yes / yes / yes / no - Interactive blocks — flashcards, walkthroughs, sorting: yes / yes / yes / no - Interactive experiences you build with AI: By arrangement / By arrangement / By arrangement / no - Quizzes, timed exams & the grading queue: yes / yes / yes / no - AI course builder: no / yes / yes / no - Embedded video — YouTube · Vimeo · Wistia: yes / yes / yes / no - Hosted video minutes: no / 2,400 / 5,000 / no - Lesson audio — your own ElevenLabs or Google account: yes / yes / yes / no - SCORM + xAPI/cmi5 import: no / no / 10 GB / no - Programs, pathways & public landing pages: yes / yes / yes / no - Borrow, curate, duplicate & clone across workspaces: yes / yes / yes / no - Live sessions — Zoom · Teams · GoToWebinar · Contrast · Wistia: yes / yes / yes / no 02 Certify - Certificates, CEUs & public verification: yes / yes / yes / no - Custom certificate designer: no / yes / yes / no - Open Badges 2.0 + credential connectors: no / yes / yes / no - LinkedIn Add to Profile: yes / yes / yes / no - Credit reported to ACCME PARS: no / no / yes / no - Deadlines, reminders & recertification: yes / yes / yes / no 03 Sell - Sell courses & memberships — your own Stripe: yes / yes / yes / no - Transaction fees: 0% / 0% / 0% / no - Cart drawer on your own site + abandoned-cart recovery: yes / yes / yes / no - Lead-gen mode — the course page becomes the form: yes / yes / yes / no 04 Learn - White-label learner portal, in your branding: yes / yes / yes / yes - Portal languages, chosen by each learner: yes / yes / yes / yes - AI Tutor for learners · 500 messages/mo: no / yes / yes / no 05 Operate - Active learners / month (soft cap): 1,000 / 5,000 / 20,000 / 1,000 - Your own domain, with managed SSL: yes / yes / yes / yes - HubSpot, Salesforce & Day.ai — every result on the record: yes / yes / yes / yes - HubSpot list access rules: yes / yes / yes / no - Zapier, Slack & the no-code apps: yes / yes / yes / no - SAML/OIDC single sign-on: no / yes / yes / no - Organization seats + customer admin portal: $99/mo add-on / $99/mo add-on / Included / no - Workspace teams, roles & audit logs: yes / yes / yes / yes - Email from your own sending domain: yes / yes / yes / yes - Help Center + Peerfold AI in the admin: yes / yes / yes / yes - HubSpot theme repoint: no / yes / yes / no 06 Build - Public API, webhooks + MCP agents: yes / yes / yes / yes - Webhook endpoints: 10 / 10 / 10 / 10 - Admin API: yes / yes / yes / no - Headless — your front end on the learner APIs: no / no / yes / no - Agent devkit, typed SDKs & React hooks: yes / yes / yes / yes 07 Community - Cohorts, threads, polls & ideas boards: Add-on / Add-on / Add-on / yes - Member profiles, follows & the feed: Add-on / Add-on / Add-on / yes - Moderation queue & member permissions: Add-on / Add-on / Add-on / yes - Community REST, MCP & webhooks: Add-on / Add-on / Add-on / yes - Discussion lessons inside courses: Add-on / Add-on / Add-on / no 08 Partner program - Partner tiers, permissions & their portal: Add-on / Add-on / Add-on / Add-on - Lead registration with protection windows: Add-on / Add-on / Add-on / Add-on - Commission ledger & payout runs: Add-on / Add-on / Add-on / Add-on - Asset library & referral links: Add-on / Add-on / Add-on / Add-on ## The fine print, plainly - What counts as an active learner? A learner who signs in or makes course progress in a calendar month. Counts reset monthly. - What happens at the cap? Nothing breaks. Caps are soft — we nudge you toward the next plan, we never lock learners out. - Transaction fees? 0% from us. Commerce runs through your own Stripe account. - How does the trial work? Seven days, every feature switched on, no card required. Pick a plan when you're ready. - AI Tutor allowance? 500 messages per month wherever AI Tutor is included. - Annual billing? Pay for the year up front and save about 28% on any plan.