refund policy

01

The Ship-or-Refund guarantee (the Program)

“Complete the weekly work” is not a vibe — it's a published list. Every week of the program ends in named deliverables (your spec, your logged conversations, your working flow, your deployed product), plus an attendance rule: attend live or watch the recording within 7 days — both count equally. Your mentor marks each week submitted or not within 72 hours, and everything stays on the record in your cohort space. The deliverables are published week by week on /program, and what completion means is the appendix at the bottom of this page.

If you submit every deliverable through Week 5, meet the attendance rule, and still haven't launched by Demo Day — that's on us, and you get your money back. No sad-face exit survey, no “quality” judgment calls, no fine print that isn't on this page.

How to claim: email refunds@exp.club within 14 days after your cohort's Demo Day. We check your cohort record against the published deliverables and process approved refunds within 7 days of your request, to your original payment method.

The Grow It add-on. If you bought the Program together with the Grow It add-on as one purchase, a guarantee or cooling-off refund of the Program refunds the Grow It with it — you get back the full amount you paid. Grow It is an extension of the Program: it isn't sold or refunded on its own, and it carries a process promise, not a launch or traction guarantee (see /disclosures). If you added Grow It later, after Week 6, as a separate purchase, that purchase has its own 14-day cooling-off from its own date.

02

The 14-day cooling-off (the Program)

Changed your mind? Within 14 days of purchase you can get a full refund, no questions asked — even if your cohort has already started by then. Email us, we refund, done.

After the 14 days, and once your cohort has started, the Ship-or-Refund guarantee above is the refund path.

03

AI Product Sprint (Teams)

B2B sprints are governed by the terms in your sprint agreement, agreed at the scoping call.

04

The mechanics (all products)

• Refunds go to the original payment method, in the currency you paid.
• How long it takes: approved refunds are initiated within 2 working days, and the amount is credited back to your original payment method within 5–7 working days. International cards can take up to 10–12 working days to show the credit, depending on your bank. If it hasn't appeared by then, email us and we'll send you the refund reference number (ARN) from our payment gateway so your bank can trace it.
• Where exchange rates have moved between charge and refund, we refund the amount you were charged in your payment currency; we don't cover bank-side conversion differences.
• Regional (purchasing-power) pricing adjustments and promo codes don't change any of the above — you're refunded what you actually paid.

05

What the guarantee doesn't cover

• Removal from a cohort for code-of-conduct violations (harassment, plagiarized submissions) — that ends participation without refund.
• Claims where the weekly evidence simply isn't in the cohort space — the submission record is the whole basis of the guarantee, in your favor and ours.
• Product outcomes: the guarantee is that you launch. Users, revenue, and traction are your work, and we never promise them (see the Disclosures at /disclosures).
• Extra usage you chose to buy on top of the plan. Claude Pro–level access is included in your seat for the program (we call it Builder Compute) and is part of your refund. But if you top up beyond the included allowance, that extra usage is used up as you go and isn't refundable.
• Subscriptions in your own name. Anything you sign up for directly — your own Claude, Cursor, or other tool plans, hosting, including whatever you move onto after the Week 6 “own your stack” handoff — is a contract between you and that provider. We never charged it, so it isn't ours to refund.

06

Questions

Email refunds@exp.club. A human answers.

appendix

Appendix: what completing the work means

This is what the guarantee runs on. “Complete the work” means two things and nothing else: attend the weekly sessions, and submit each week's deliverables. The deliverables are the ones published week by week on /program — we do not keep a second list here, because two lists drift apart and the one you were never shown is always the one you are held to. They are fixed when your cohort starts and do not change mid-cohort.

How grading works

• Deadlines: each week's work is due before your next scheduled session, posted to the cohort space.
• Grading: your assigned mentor marks each week's deliverables submitted or not submitted within 72 hours. A deliverable is never failed for a quality reason, for a mentor's opinion of your idea, or for anything not published as that week's deliverable before the week began. Submitted is submitted.
• Cure window (once per program): one missed deadline can be cured by submitting the complete work within 72 hours, together with a mentor-agreed catch-up plan. A second missed deadline without a mentor plan fails that week.
• Disputes: you can escalate any fail to the founder within 7 days; the founder's written decision against the published deliverables is final.
• Records: all submissions and grades stay in the cohort space for the cohort's lifetime — they are the evidence base for any guarantee claim.

Attendance requirement (spans all six weeks)

For each of the 10 live sessions: attend live or watch the recording within 7 days of the session and post a one-line takeaway. Both count equally — this is a bar on engagement, not on being free on a particular weekend.

This is the same bar the completion certificate uses. There is deliberately only one: an earlier version asked for every session here and eight of ten for the certificate, which meant a builder could earn the certificate and lose the refund on the same attendance record, and find out only when they claimed.

The guarantee logic

• Conditions (“you completed the work”): every deliverable through Week 5 submitted (at most one cure window used) and the attendance requirement met through Week 6.
• The promise: if you meet the conditions and still don't have a publicly launched product by Demo Day, exp.club refunds 100% of what you paid. Week 6's deliverables are the launch — they define success, so they aren't preconditions of the guarantee. That is why the line sits after Week 5: Week 5 ends at a deploy candidate, and Week 6 is the public launch itself.
• Not grounds for refusing a refund: product quality, traction, revenue, a mentor's opinion of your idea, or anything not published as a weekly deliverable.
• Outside the guarantee: removal from the cohort for conduct (code-of-conduct violations, harassment, plagiarized submissions), and claims where the submissions are absent from the cohort space.