Cohort-Based Creative Skills Academy with Portfolio Showcase

A course workspace for independent creative educators to run timed cohorts, organize peer critiques, and turn approved student work into public portfolios.

Learning PlatformEducationInstructor subscription with per-cohort or seat-based tiers.
MVP time6-9 weeks
DifficultyIntermediate
Infra cost$7-$100
RevenueSubscription
Review the decision summary
11,821 views
Updated August 2, 2026

Decision snapshot

Is this worth validating?

Build this if

You already run paid creative cohorts and critique coordination is the clearest operational bottleneck.

Avoid this if

Your program is primarily self-paced video consumption with no peer review or portfolio outcome.

Validate first

Run one cohort of 10-20 learners and verify that at least 80% complete both assigned critiques without the instructor maintaining a separate tracker.

Problem and target customer

Why this exists

Customer problem

Creative cohort operators often coordinate lessons, submission deadlines, critique partners, and final showcases across video tools, forms, chat threads, and portfolio sites. Instructors lose visibility, while students receive uneven feedback and rebuild their work elsewhere after graduation.

Who pays

Independent design, writing, or multimedia educators who sell cohort-based programs and need one structured path from assignment to public showcase.

Business model

Per-cohort fee or monthly subscription for instructors, with student seats included in each cohort.

Editorial note

The narrow product is not another course library. Its value sits in the period between a learner uploading work and deciding that the work is ready to represent them publicly. That makes critique accountability and creator-controlled visibility the two decisions worth validating first.

Start with one creative discipline and one rubric format. Different media can share the same submission state model, but trying to support every file type, teaching style, and accreditation path in the pilot would hide whether structured peer feedback actually improves cohort completion.

Choose your next step

What do you need next?

Evaluate the operating tradeoffs quickly, or inspect how to build the MVP.

Evaluation preview

What would it take to run?

Directional infrastructure estimates for the current 500 assignment submissions assumption. Open the full calculator when you are ready to change it.

Open full cost and deployment
ManagedSelected
$5-$35/ month

Railway hosts the web app, worker, database, and small persistent volume.

Lowest operating effort
Lean self-hosted
$7-$20/ month

A Hetzner shared cloud server runs Docker services; R2 holds student media.

Lowest baseline cost
More control
$25-$90/ month

Larger or dedicated cloud instances isolate database and worker capacity.

Most separation and control

Build blueprint

Build the first paid use case

Product goal

Who it serves and what it must change

Target user
A creative educator running paid, time-boxed cohorts and learners completing portfolio-oriented assignments.
Problem
The operator cannot reliably see who submitted, who still owes a critique, or which projects are ready for public display when those actions live in separate tools.
Measurable outcome
In a pilot cohort, every submission, assigned critique, revision, and publication decision is visible from one timeline without spreadsheet reconciliation.

MVP scope

What ships now and what waits

Included

  • Create a cohort with dates, modules, assignments, and enrolled learners.
  • Accept media-backed submissions and assign two peers for rubric-based critique.
  • Let learners revise work and publish instructor-approved projects to a public portfolio page.

Excluded

  • Live video classrooms and recorded-video hosting.
  • Automated grading or AI-written critiques.
  • A marketplace for discovering unrelated courses.

UX and user flow

Screens, actions, and states

Cohort Timeline

Show lessons, deadlines, submission status, and critique completion by learner.

Add an assignmentOpen a late-work filterSend a reminder
Critique Desk

Present the assigned project, rubric prompts, feedback status, and revision response.

Submit feedbackRequest clarificationMark feedback addressed
Portfolio Editor

Turn selected submissions into ordered public case studies with creator-controlled visibility.

Choose a projectEdit project contextPublish portfolio

Primary flow

  1. An instructor opens enrollment and assigns the first brief.
  2. A learner uploads work before the deadline and receives two critique assignments.
  3. Peers submit rubric-based feedback; the learner posts a revision and response.
  4. The instructor approves the final project for the learner's public portfolio.

Loading, empty, and error states

  • Enrollment: draft, open, closed
  • Submission: not_started, submitted, revision_requested, approved
  • Critique: assigned, delivered, acknowledged
  • Portfolio project: private, ready, public

Core entity outline

Entities and business rules

Cohort

Defines the program dates, instructor, curriculum order, and enrolled learners.

Fields
title, starts_at, ends_at, enrollment_status
Relations
Has many assignments, Has many enrollments
Submission

Stores a learner's work, version, deadline status, and instructor decision.

Fields
assignment_id, learner_id, media_keys, submitted_at, status
Relations
Belongs to an assignment, Has many critiques, May become one portfolio project
Critique

Records a peer assignment and structured feedback against the instructor's rubric.

Fields
submission_id, reviewer_id, rubric_answers, delivered_at, status
Relations
Belongs to one submission, Assigned to one cohort learner
PortfolioProject

Keeps the public narrative and visibility settings for an approved piece.

Fields
submission_id, headline, context, sort_order, visibility
Relations
Belongs to one learner, References one approved submission

Business rules

  • Only enrolled learners may view cohort submissions, except projects explicitly published to a portfolio.
  • A learner cannot critique their own submission, and each submission receives no more than two active peer assignments.
  • Portfolio publication requires learner consent and an approved submission status.

Architecture and data flow

Components, integrations, and controls

Cohort web app

Serve instructor, learner, critique, and public portfolio experiences with role-aware routing.

Relational store

Persist enrollment, assignment, submission, critique, and publication state atomically.

Media service

Issue signed upload and download URLs for student work without exposing storage credentials.

Notification worker

Send deadline and critique reminders from an idempotent job queue.

Integrations

  • Object storage for submitted and portfolio media
  • Transactional email for invitations and deadlines

Data flow

  1. The client requests a signed upload URL, uploads media directly, then saves the returned object key with the submission.
  2. A submission transaction creates peer assignments while enforcing enrollment and self-review rules.
  3. Approval copies only portfolio metadata; the media remains referenced by its protected object key.

Failure handling

  • Keep an upload in draft until all media objects are confirmed
  • Retry email jobs without duplicating critique assignments
  • Allow an instructor to reassign a critique when a reviewer withdraws

Security

  • Enforce cohort membership on every private read
  • Use expiring signed media URLs
  • Keep public portfolio fields separate from private feedback

Rate limits

  • Limit signed upload requests per learner
  • Throttle reminder sends per cohort and deadline
  • Restrict repeated public portfolio edits

Deliverables and acceptance

Definition of done for the MVP

Deliverables

  • Responsive instructor and learner app
  • Cohort and critique permission model
  • Signed media upload flow
  • Public portfolio route
  • Seeded pilot cohort and automated tests

Acceptance criteria

  • An instructor can create a cohort, enroll three learners, assign a brief, and see each submission state.
  • The system assigns two eligible peers without assigning the author to their own work.
  • A learner can revise an approved project and publish it without exposing private critique text.
  • If a media upload fails, the submission stays editable and can be retried without creating a duplicate record.

Recommended stack

Enough technology for the first version

Web application

Next.js and TypeScript

One codebase can serve authenticated cohort tools and indexable public portfolios.

Database and auth

PostgreSQL with Auth.js

Relational constraints fit enrollments, reviewer eligibility, and submission states.

Media

Cloudflare R2

Direct signed uploads keep large creative files away from the application server.

Notifications

Resend with a database-backed job queue

Deadline reminders need retries and idempotency, not a separate automation platform.

Why this is sufficient

The first release needs reliable permissions and state transitions more than real-time collaboration. A relational monolith plus direct object uploads keeps the critique loop auditable and the public showcase simple.

Not required for the MVP

LLM APILive collaboration serverSeparate search cluster
Next stepTurn the blueprint into an execution plan

Copy the build prompt, model the operating cost, and choose where to deploy.

Build and ship

Execution

Build, price, and deploy the MVP

Once the blueprint is clear, use the prompt, cost model, and deployment options to start building.

Build prompt

Copy this into a builder

Start with a full-stack TypeScript app because cohort permissions, critique assignments, deadlines, and portfolio publishing share one transactional data model.

Build prompt

Your build prompt is ready

Open the prompt pack whenever you are ready to take this blueprint into your builder.

Based on the blueprintReady for your builderFollow-up steps included

Cost calculator

Model the MVP operating cost

A technical run-cost estimate for the first production version. Team, acquisition, payment fees, and business COGS are excluded.

Estimated monthly total$5-$35

$5-$35 per 500 assignment submissions

Assignment submissions / month500 assignment submissions
Selected pathEasiest
Pricing checkedAug 2, 2026

Usage assumptions

Use beta workload metrics when available.

Infrastructure approach
Railway hosts the web app, worker, database, and small persistent volume.
Cost breakdown

$5-$35 per month

Low and high values allow for usage variance and plan headroom.

Managed app deployment

Railway hosts the web app, worker, database, and small persistent volume.

500 assignment submissions included, then $2-$8 per 500 assignment submissions
$5-$35
Transactional email

Enrollment, deadline, and critique messages; the free tier covers the default pilot volume.

3K assignment submissions included
$0
Portfolio media storage

Estimate assumes compressed submission files and portfolio images backed by R2 storage and operations.

500 assignment submissions included
$0

Included

  • Web and worker compute
  • Relational database
  • Beta-scale transactional email
  • Portfolio media storage estimate

Not included

  • Instructor labor
  • Video hosting
  • Payment fees
  • Custom domains
  • Marketing and course production

Pricing basis

The estimate combines the selected infrastructure path, required operating modules, selected optional modules, and usage above included monthly allowances. Taxes and regional uplifts are excluded.

Deployment options

Pick the operational tradeoff

Choose based on operating preference, not only the headline price.

EasiestRecommended

Railway

Deploy the app and worker quickly while keeping media in R2.

$5-35/month before email and media usage

Good fit

  • Fast launch
  • Managed runtime
  • Simple previews

Limitation

Resource usage can grow beyond the plan minimum.

Cheapest

Vultr

Run the app, worker, and database on one small Vultr VPS with Docker Compose and explicit backups.

$7-20/month before backups and add-ons

Good fit

  • Low baseline
  • Docker portability
  • Predictable capacity

Limitation

The operator owns patching, backups, and recovery drills.

More control

DigitalOcean

Separate application, worker, data, storage, and backup responsibilities as the workload grows.

$25-90/month before email and media usage

Good fit

  • More headroom
  • Private networking
  • Custom backup policy

Limitation

Higher operations burden than a managed platform.