Sell Project Feedback for Bootcamp Students

Bootcamp mentors, TAs, and alumni sell project feedback by packaging a capstone or portfolio review as one fixed-price offer: the student submits a repository plus context, pays upfront, and receives written or recorded notes inside a stated turnaround window. That replaces unpaid late-night Discord and DM reviews with a scoped, bounded, paid deliverable. Custom Work lets you offer clearly scoped commissions and services: you set the price, the scope and the delivery time, and followers submit a brief and pay before you start.

No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate. pricing

If you've mentored, TA'd, or graduated from a coding bootcamp, you know the DM: "Hey, can you look at my project before demo day?" A scoped, priced offer turns that request into planned, compensated work — no consulting practice, no booking calendar.

What counts as "project feedback" for a bootcamp student?

Project feedback means reviewing one complete deliverable — a capstone, a portfolio repository, or a multi-file assignment — rather than a single error message or one function. The reviewer judges architecture, product decisions, code quality, and demo readiness, then returns written notes, an annotated repo, or a recorded walkthrough inside a delivery time window the student sees before paying.

A bootcamp capstone is a full application, not a coding exercise. General Assembly's Software Engineering Bootcamp page states that for the capstone project a student will "mimic a team-client interaction, collaborating to build and deploy a full-stack application that fulfills provided specs," with a final result that "will integrate functionality from a third-party API" (General Assembly Software Engineering Bootcamp). App Academy's online software engineering course page tells students they will "design and complete four projects of your own and dozens of guided projects with your classmates" across a 24-week program (App Academy).

Capstone work also occupies a long, scheduled block rather than a weekend, which is why a review of one is a substantial job. Codesmith's Future Code NYC curriculum lists "Module 4: Capstone Project — Weeks 26–33" inside a program the school describes as "42 weeks, full-time, no tuition for eligible New Yorkers," with students identifying "a technically challenging problem to solve over the course of six weeks". Reviewing eight weeks of team-built application code is a different unit of work from answering one question about a stack trace.

Relatively few working developers came through a bootcamp at all, which is part of why grads seek out reviewers who have actually evaluated capstone-style projects. In the 2025 Stack Overflow Developer Survey question "How did you learn to code in the past year?", "Coding Bootcamp" was selected by 5.2% of 33,454 respondents — the lowest-scoring named resource, ahead of only the 3.2% "Other" catch-all — against 16.6% for "School (i.e., University, College, etc)" and 32.7% for "Online Courses or Certification" (2025 Stack Overflow Developer Survey). The same reviewing-one-complete-artifact model, applied outside a codebase, is what makes auditing a student's note-taking or planner system work as a paid offer too.

Many programs include a capstone or portfolio project, creating recurring review opportunities around demo days and graduation. Flatiron School lists a "Capstone portfolio project" as an included component of both its full-time certificate ("4 months 40 hrs/wk") and its part-time certificate ("13 months 15-20 hrs/wk").

A useful project-feedback offer typically covers:

• A full capstone or final project (frontend, backend, and any integrations)
• A portfolio repository being prepped for job applications
• A README, project write-up, or demo-day pitch
• Architecture or stack decisions across a multi-file project

A project-feedback offer typically does not cover open-ended debugging support, unlimited follow-up rounds, or live pairing — those need a different offer, such as async feedback on a recorded mock technical interview answer, or a clearly separate add-on.

Should you use a custom request or a Paid Question?

Use a custom request for a full project review and Paid Questions for one narrow ask. Custom Work lets the student attach files or include a repository link at checkout and lets the mentor set the delivery time; Paid Questions let a follower submit one private question and receive one written reply, privately.

For Custom Work, the follower can attach up to 5 files, 50 MB each, when they order, so you can ask for a zip, screenshots, a brief, or other project context before you start. Delivery back to the follower can include text plus files of any allowed type and/or a private link for anything larger; that one package completes the order, and if a file or link doesn't work, the student can still message you on the same order afterward.

Brillay's 5-day delivery time limit is a hard product cap, not an average: for Custom Work or Personalized Videos, you set the delivery time as a whole number of hours between 1 and 120 (5 days), and up to 5 days is the longest delivery time the product will accept. Pick a window inside that cap that survives a busy cohort week instead of defaulting to the maximum.

Price the two formats apart rather than folding them together. Test clearly separated prices, such as a $5 Paid Question, a $25 portfolio review, and a $50 capstone walkthrough, then raise or lower them based on the work involved and what students actually buy.

What should a bootcamp project-feedback package include?

A bootcamp project-feedback package should name five things before the student pays: the input they submit, the deliverable they get back, the delivery time window, the revision policy, and the explicit exclusions. Vague scopes like "I'll look at your project" invite mismatched expectations on both sides and, in practice, make declines or refund conversations more likely.

Define, at minimum:

• Input: Public repo link, deployed URL, or a zip file, plus the assignment or job-target context.
• Deliverable: Written notes, an annotated repo, a recorded video walkthrough, or a combination.
• Delivery time: A window you can reliably meet, set anywhere from 1 hour to Brillay's 5-day maximum.

Students can already get an instant automated read on their code, so the human judgment in a paid review is the part worth naming explicitly. In the 2025 Stack Overflow Developer Survey question "How did you learn to code in the past year?", 44% of 33,454 respondents selected "AI CodeGen tools or AI-enabled apps," placing it above "Blogs or podcasts" at 34.8% and "Online Courses or Certification" at 32.7%.

The specific failure mode a human reviewer catches is code that looks finished but is subtly wrong. The 2025 Stack Overflow Developer Survey reports that the biggest single frustration with AI tools, "cited by 66% of developers," is "AI solutions that are almost right, but not quite," followed by "Debugging AI-generated code is more time-consuming" at 45.2% (2025 Stack Overflow Developer Survey: AI). Spelling out what you judge — architecture, product decisions, hiring-manager readiness — is what separates a paid human review from a generated one.

For example: "One recorded video walkthrough reviewing your capstone's architecture, code quality, and demo flow, plus a written checklist. This is one completed delivery."

How much should mentors typically charge for a project review?

No audited public dataset benchmarks what bootcamp mentors charge for capstone reviews, so price by scope against the job you are actually promising rather than an hourly rate a student cannot estimate. The figures below are examples to test, not market guidance or an earnings claim.

A capstone review runs far longer than one written answer, so price it as its own scoped Custom Work package rather than folding it into a single-question rate.

You set your own prices on Brillay (how-it-works), so treat the ladder as a starting hypothesis to test with your own audience, not an earnings claim or an industry benchmark.

A two-figure review is small next to what the student already paid for the program itself. Turing School's financing page states that "tuition for our program is $25,000 for all students," with "no additional fees," a "new Macbook Air" included, and "a $1,200 deposit to secure their seat" (Turing School financing). Codesmith lists tuition of $22,500 for its Software Engineering + AI/ML Immersive (Codesmith), and Flatiron School lists "$14,900 Total tuition" for both its full-time and part-time software engineering certificates. Against a $14,900–$25,000 tuition, a $50 capstone review is a rounding error a graduating student can justify.

Some students have not paid cash at all yet, which changes how a small paid review lands. App Academy's online software engineering page lists its tuition as "Zero deposit. Pay only after you're hired earning $50K+. Then, 15% of salary for 3 years (max $31K)" (App Academy). A student on that agreement has strong financial reason to make the capstone land before demo day.

Program length varies enough that "a bootcamp capstone" is not one fixed size, so ask which program the student attended before quoting. Codesmith lists the format of its Software Engineering + AI/ML Immersive as "14 weeks full-time or 39 weeks part-time (evenings and Saturdays)". App Academy lists its online software engineering course at "Course Length: 24 weeks" on a schedule of "Mon-Fri, 8am-5pm (Pacific Time)". General Assembly lists its Software Engineering Bootcamp as full-time at "8 hours a day" graduating "in 12 weeks," or part-time at "15 hours per week" graduating "in 32 weeks", and Flatiron School lists "4 months 40 hrs/wk" full-time against "13 months 15-20 hrs/wk" part-time. A 12-week capstone and a 39-week part-time capstone are different review jobs.

Why do bootcamp students need paid feedback beyond the program itself?

Bootcamp students need paid outside feedback because cohort programs allocate instructor time to a group on a fixed schedule rather than to one student's capstone. Class sizes run into the dozens, staffing runs to a handful of instructors per cohort, and the calendar is set in advance — so an unhurried one-on-one review of a full capstone before demo day rarely has a scheduled slot.

Turing School's own FAQ page states that the typical student-to-teacher ratio is "around 12:1" and that "each cohort is typically assigned between 2 and 3 instructors who teach classes in real-time and are available through Zoom and Slack" (Turing School FAQs). The same FAQ says "there are usually 30-35 people in each cohort" (Turing School FAQs), so two or three instructors are supporting roughly thirty students at once.

At Turing School specifically, its FAQ says about half of instructors had worked as developers before joining, so some students may also seek an outside review from a currently practicing engineer. The same FAQ says "the majority of us have professional experience as instructors, either teaching K-12 or in college or corporate settings".

The calendar leaves little slack either. Turing School's FAQ states that "the full 7 month program consists of 4 modules," that "each module is 6 weeks long with a 1 week intermission," and that there is "a one week intermission every 7 weeks". A six-week module with fixed deliverables is not where an individually paced, hour-long capstone review fits.

Where one-on-one time does exist, it is a scheduled check-in rather than a deep review. Flatiron School's software engineering page lists "1:1 WEEKLY Mentorship" as "weekly check-ins throughout the program" giving "personalized feedback on projects and career direction" — a recurring slot sized for progress and direction, not a line-by-line pass over a finished capstone the week before demo day. For a narrower issue, a Brillay Paid Question lets the mentor answer in writing inside the delivery window they set, without booking another check-in or coordinating calendars.

A free automated read on a capstone is available to every student in seconds, which is precisely why a named human review still sells. In the 2025 Stack Overflow Developer Survey question on AI accuracy, 26.1% of 33,244 respondents somewhat distrusted and 19.6% highly distrusted the accuracy of AI tool output, against 3.1% who highly trusted it.

"More developers actively distrust the accuracy of AI tools (46%) than trust it (33%), and only a fraction (3%) report 'highly trusting' the output." — Stack Overflow, 2025 Developer Survey: AI

The same survey page adds that experienced developers are the most cautious of all, "with the lowest 'highly trust' rate (2.6%) and the highest 'highly distrust' rate (20%), indicating a widespread need for human verification for those in roles with accountability" (2025 Stack Overflow Developer Survey: AI). That is the demand a paid capstone review meets: verification by a named human who has evaluated projects like this one before.

What if a project needs more work than what the student paid for?

If a submission falls outside the advertised scope — a project far larger than a "one repo review," or open-ended debugging inside a review offer — decline it before delivery rather than absorbing unpaid work.

Preventing an oversized submission is cheaper than untangling one after the fact. Stripe's refund documentation states that "Stripe's processing fees from the original transaction aren't returned" when a payment is refunded (Stripe refunds documentation), and Stripe's published pricing lists those processing fees at "2.9% + $0.30 per successful transaction for domestic cards" (Stripe pricing). On a paid $90 capstone review that later has to be refunded, that processing fee is the kind of cost you want to avoid by scoping clearly before delivery.

A clear size boundary in the listing prevents most oversized submissions before they arrive. For example: "Covers one repository up to roughly 2,000 lines of application code. Larger monorepos or multi-service projects should message first for a custom quote." Stating that boundary up front, and routing oversized requests to a custom-quote conversation, keeps the standard price honest for the typical case.

What else can a bootcamp mentor sell alongside project feedback?

Project feedback does not have to be a mentor's only paid offer. A bootcamp mentor can run Custom Work for full reviews alongside Paid Questions for narrow asks, Personalized Videos for a student's first dev job, Tips for one-time thanks with nothing to deliver in return, and Goals for funding a free resource. Brand Collaboration Inquiries can also sit on the same page as a "Work with Me" form that collects a company's budget, timeline, and deliverables into a separate brand inbox.

• Paid Questions: A narrow question about one design decision, library choice, or error message.
• Personalized Videos: A congratulations message for a student who just landed their first dev job.
• Tips: A one-time thank-you from a former student, with nothing to deliver in return.
• Goals: Funding toward a free resource you're building, like a curated project-idea list or a study guide.

Put Custom Work, Paid Questions, Personalized Videos, Tips, and Goals behind one Brillay link with no follower minimum or platform application. Students can pay by card without creating an account; there is no monthly fee, and creator payouts are available in 41 countries. A Personalized Video, tip, goal, or brand inquiry that goes unused simply never triggers a platform fee.

If your audience also sends one-off code questions unrelated to a full project, selling code reviews online covers that narrower offer, selling a dashboard review covers the same structure for data work, and the best Brillay offer for developers and designers covers how the different offer types fit a technical audience overall.

How do you get a project-feedback offer live?

Getting a project-feedback offer live takes four decisions: whether most incoming requests are full-project reviews or narrower single-question asks, the input format you accept, the deliverable you return, and the delivery time and exclusions you can reliably hold to. Publish all four in the listing text before sharing the link anywhere.

Setup checklist — from zero to a live listing:

1. Create your Brillay page at /start and complete Stripe onboarding, which is required before any money can reach you.
2. Add a custom request and title it for the exact job, e.g. "Bootcamp capstone review — written notes + annotated repo." The student can attach up to 5 files, 50 MB each, and your delivery back can include text, files, and/or a private link.
3. Set the price for the smallest package you will actually deliver, then add a second, larger service rather than stretching one price.
4. Set the delivery time as a whole number of hours between 1 and 120 — up to 5 days is Brillay's maximum.
5. Write the scope block into the description: input, deliverable, revisions, exclusions, and a codebase size limit.
6. Decide the delivery scope before publishing, because delivery is one-time.
7. Put the link in the bio, pinned comment, or Discord channel where the "can you look at my project" messages already arrive. One link that carries every offer, with nothing to moderate and no community to keep warm.

Listing template you can paste and edit:

Bootcamp capstone review — written notes + annotated repo

What you send: a public repo link (or a zip), your deployed URL, the assignment
brief or the job you are targeting, and your single biggest worry.

What you get back: a written review of architecture, code quality, README and
commit history, and demo-day readiness, plus inline comments on the repo.

Delivery time: 72 hours from the time you order.
Revisions: or follow-up questions are included; order another
custom request if you need a separate review.
Size limit: one repository up to roughly 2,000 lines of application code. Larger
monorepos or multi-service projects — message first for a custom quote.
Not included: live debugging, pair programming, mock interviews, or unlimited
chat support.

You can enable Custom Work or Paid Questions regardless of whether you have a teaching certification or bootcamp employment. No credential requirement is a platform detail rather than a substitute for accuracy: describe your actual background — TA, mentor, alumni, or working engineer — honestly, and avoid implying an affiliation with a specific bootcamp you don't currently have.

Payouts run through Stripe's standard payout timing to the creator's own Stripe account inside Brillay. Stripe's payouts documentation states: "After you successfully receive your first live payment, Stripe typically schedules your initial payout to complete within 7–14 days" (Stripe payouts documentation). Stripe's same documentation page adds that the first payout "can take longer depending on your industry, country of operation, and risk level," so plan the first paid capstone review around that window rather than expecting same-week cash.

Frequently asked questions

Short answers: no teaching credential is required, a full capstone fits a custom request while a single question fits Paid Questions, oversized submissions should be declined before delivery rather than absorbed, and Brillay charges only when a follower pays: 8% when a follower pays for work, 5% on tips and goals.

Do I need to be a certified instructor to sell bootcamp project feedback?

No. Custom Work and Paid Questions are available regardless of whether you have a teaching credential. Describe your actual experience — mentor, TA, alumni, or working developer — accurately, and don't imply a current affiliation with a bootcamp you no longer work with.

Should I review the whole project or just answer one question?

Match the offer to the request. A full capstone or portfolio review fits a custom request, which accepts follower file attachments or repo links and a delivery time of 1 to 5 days, with up to 5 days as the hard maximum. A single design decision or error message fits Paid Questions: a follower pays your set price to ask one private question, and you send back one written reply, privately.

What if the student's project is much bigger than what they paid for?

Decline the request before delivery rather than completing unpaid extra work, or point the student to a custom quote before starting. Stating a size or scope limit in the listing (for example, "one repo up to ~2,000 lines") prevents most oversized submissions upfront.

How is this different from a mock technical interview?

Project feedback reviews a static deliverable — code, structure, and documentation — that a student submits once. A mock interview evaluates real-time performance, communication, and problem-solving under pressure, which needs a live or recorded interaction rather than a submitted repo.

What does Brillay charge?

Brillay has no monthly fee and no follower minimum; it takes a small platform fee only on the reviews and other offers students actually pay for, at the paid-work and tips-and-goals rates shown in the pricing line near the top of this page. Typical US card processing is separate — Stripe's published pricing lists "2.9% + $0.30 per successful transaction for domestic cards".

Create your free Brillay page and turn the next "can you look at my capstone?" DM into a clearly scoped, paid offer.