For career switchers who keep hearing “no experience”. In 14 days, with Claude as your assistant, you write a requirements spec, user stories and a process map of your own. Every template comes with a finished example to learn from.
One payment of $27, delivered through Whop. The kit does not promise a job or an income.
An illustration of the idea, not a real scorecard. No kit can promise how an interview goes.
The kit is written for one situation. Check whether it is yours before you spend $27.
Three ticks or more: this kit was written for you.
Three documents that BA and PM work is built on. Each one comes as a blank template and as a finished example, so you never start from an empty page.
The document that says what a product must do, for whom, and why. You learn to state the problem, list the requirements, and draw the line around what is out of scope.
One story per important user action, each with Given / When / Then criteria that a team can build and test against.
How the work flows today, where it breaks, and how it should flow after the change. The document that shows you can see a whole process, not only a screen.
An instruction file you load into Claude. It interviews you about a case of your own, then drafts the three documents in the kit's format. You edit, question and correct the drafts until you can defend every line.
How to assemble the three documents into one portfolio, and how to talk through them when an interviewer asks. Includes the 14-day plan.
A tracker sheet for your applications and follow-ups, and a 25-minute daily routine with ready prompts for an AI assistant, so the search keeps moving while you build the portfolio.
One fictional case runs through all three examples: BookWell, online appointment booking for a family clinic. You see how a spec, its user stories and its process map connect to each other.
BookWell and the clinic are invented for teaching. Neither is a real product, client or employer.
About 60 to 90 minutes a day. Days 7 and 14, the shaded boxes, are lighter.
Read the three finished examples. Choose a case of your own: a process you know from your working life, with the names changed.
Four days on the requirements spec, one part a day. On day 7 someone outside your field reads the summary and tells you what they understood.
Story map and backlog first, then four or five stories in full with acceptance criteria.
How the work flows today, then how it should flow after your change.
Check the three documents against each other, export them, and practise the walkthrough out loud.
This is one full user story from the kit's finished example. Compare the finished BookWell example with the blank template you fill in yourself.
As a registered patient, I want to book one of the routine slots I can see, so that I have a confirmed appointment without phoning the clinic during my working hours.
This is the story the product exists for. Today 74% of appointments are booked by phone, and 23% of callers in the morning peak give up before anyone answers. In interviews, patients said they would trust online booking only if a slot they picked was really theirs. That is why the conflict case (criterion 2) matters as much as the normal path.
I wrote the conflict case before the happy path, because trust was the adoption risk named by patients. The 5-minute hold is a business rule and I gave it a number so it could be tested and changed. Criterion 6 came from the lead GP: an SMS can be read by anyone holding the phone, so it must not reveal why someone is seeing a clinician. After release I would track how often criterion 2 happens. If it is frequent, there are too few slots online.
Short title: verb + object. Copy this block once per story. Choose stories that show range: the main path, one with a conflict or error, one for a staff user, one with a business rule.
The “so that” part is the reason, and it is the part people skip. If the reason is “so that I can do the thing I just said”, think again about why the user cares.
As a , I want to , so that .
Two to four sentences. Why this story exists now and what goes wrong for the user without it.
Each criterion is one test a tester could run and mark pass or fail. Given is the starting situation, When is one action, Then is what must be true afterwards. Put real values in: “within 2 minutes”, “5 slots”, not “quickly” or “some”. Four to six criteria per story.
What a teammate might assume is included and is not. Point to the story that covers it, if there is one.
An edge case, data you still need, or a question for a stakeholder.
Three to five lines, for your own practice. What you decided, what you cut, how you would know it worked.
The example has five stories written in full. The spec and the process map follow the same pattern: template, finished example, interview notes.
The kit was built with Claude as a working tool, and it teaches you to work the same way. Every example in it is fictional, and none of it comes from an employer or a client.
Some short clips about the kit are narrated by an AI avatar. Those clips are always labelled as AI.
$27One payment, no subscription
Checkout and delivery are handled by Whop. You get access to the files there after you pay.
The kit does not promise a job, an interview or a salary. You get the files and the method, and the portfolio you build with them is yours.
No one can promise that, and this kit does not. Hiring depends on the market, the role, and you.
What the kit gives you is three documents of your own to show, and practice in talking through them. What happens in the interview is still up to you and the interviewer.
No. The kit is written for people who have not held the title yet. The finished examples show what a good document looks like, and the templates explain what goes in each field.
No. The examples are there to learn from. Your portfolio is the three documents you write about a case of your own.
This matters in practice: other buyers have the same examples, and an interviewer will ask why you made each decision. You can only answer that for work you did yourself.
The assistant is an instruction file written for Claude, and it also works in other capable AI chat assistants. You need an account with one of them. Plans and usage limits change, so check the provider's site for what the current free and paid plans allow.
The templates, the finished examples and the guide are ordinary documents. You can use them without any AI tool.
Working analysts and product managers already draft with AI. The skill an interviewer tests is your judgement: what you asked, what you cut, and why.
The assistant produces a first draft from your answers. The kit then asks you to edit it until you can defend every line. Say openly in the interview that you used an AI assistant.
Three templates, three finished examples, the Claude instruction file, the portfolio and interview guide, and the bonus job-search system.
The documents are editable Markdown files, which open in any text editor and paste cleanly into Google Docs, Word or Notion. The tracker is a CSV sheet that opens in Excel or Google Sheets.
You buy on Whop, and Whop gives you access to the files. This site does not take payments or store card details.
No. It is in English and the documents it teaches are used by BA and PM teams in many countries. The fictional case does not depend on any one country's rules.
No. The kit teaches how to write three work documents. It contains no legal, immigration, financial or clinical advice, and buying it does not create any professional relationship with Oren.