# MVP scope for first customers

Haskerfell · Product-management work sample
All company, customer and data in this exercise are original synthetic material.

## Situation and outcome
Haskerfell is a fictional company that sells Haskerfell Orders, order management for about 2,600 independent online merchants. It is defining Haskerfell Floor, a phone app that guides picking and packing in the merchant's own warehouse and is tied to Orders. Haskerfell hosts and runs Floor itself. The Head of New Products wrote the hypothesis (who the first customers are, the value claim and three things the MVP must demonstrate: D1, D2 and D3). Eight design partners agreed in July to try two prototypes on their own floors. The build is one squad for 12 weeks from 2 November.

You are the Floor product manager. Today is Wednesday 7 October. The proposed MVP definition goes to the build gate on Friday 16 October, where the Head of New Products decides and alone commits the squad. Your scope agent drafted a definition overnight from the records. Nobody has checked it.

Your outcome is a **proposed MVP definition**, a **review note** that recommends either approval with conditions or "not ready", and a **revision log**. "Not ready" is valid when the records support it, and then it comes with a blocker record in which every blocker has an owner and a re-review condition. Building Floor, recruiting customers, pricing, the launch, the build gate itself and the conversation with Nollaveth Home Group about its renewal are not part of this work. The engineering lead's and the data analyst's replies are already in your download, in the correction note (U001).

The evidence period is 2026-06-15 through 2026-10-01 inclusive. Work with 55 source records (the hypothesis memo and gate rules, capacity, partner commitments, prototype sessions, usage summaries, owner interviews, sales notes, support tickets, engineering estimates and a rival's page), a merchant directory and an AI-drafted definition. The usage figures are summaries; you cannot query anything live. The AI draft is not an authority. Use the supplied source IDs and context; do not contact the fictional people or merchants or seek private data.

## Your role
You are joining the team as Product Manager.

You own the proposed MVP definition and the recommendation to the Head of New Products: approve with conditions, or not ready with a blocker record. Where a decision belongs to the Head of New Products or the Head of Sales (whether food and drink is in the first segment, Nollaveth Home Group's request), you put it to them with bounded options and your recommendation. You may not approve the build, commit the squad, change the capacity or the build gate rules, promise anything to Nollaveth Home Group or any partner, or contact partners except through their account owners.

## About the team
A product team defining the minimum scope of a new warehouse phone app for the build gate chaired by the Head of New Products.

A scope agent drafts MVP definitions from the records, a call-notes assistant summarises owner interviews and sales calls (recordings are deleted after 30 days), the data analyst's agent writes usage summaries, and engineers build prototypes with coding agents. People own the roster, the recommendation and the build decision.

The product manager proposes the definition and recommends approval with conditions or not ready; the Head of New Products decides at the build gate and alone commits the squad; the engineering lead owns the estimates; the Head of Sales owns the conversation with the largest account; account owners arrange all partner contact; the Orders platform team owns the dependency date.

## Work to complete
1. Read sources/coverage-and-access.md before you make claims about what the records cover. The hypothesis memo and the gate rules are the first two records; the gate rules say what a definition must contain.
2. Audit the AI draft against the original records, row by row. Change only what the evidence warrants. A row that still stands is kept, with its reason.
3. Count merchants, not mentions, and use the merchant directory to see who belongs to the first-customer segment. A repeated or forwarded statement is not a second observation. Tell apart what a record shows, what an AI tool wrote, what a person claimed and what is only a plan. Keep contrary evidence visible.
4. Define the minimum scope that can show the must-demonstrate items with the first customers: each capability with the partners behind it and engineering's estimate, explicit exclusions with reasons, learning and adoption targets with each customer's own baseline and how it will be measured, and whether the total fits the build capacity.
5. Recommend approval with conditions or "not ready" in the review note. Give every condition or blocker an owner, and say what the account owners and the other people involved should hear.
6. Apply the replies in the correction note (U001). Carry each change through the definition, the review note, the revision log and the evidence table, and keep the earlier reading visible.
7. Keep to your role. You may propose and recommend; the people named in the records decide what is theirs.

## Time
You have 90 minutes of work time. The clock starts when you press Start.

After that comes a 10-minute break, then a written interview: up to eight typed questions about your own files, for about 15 minutes. If you submit early, your break starts straight away.

## Mid-task correction
There is no mid-task correction in this take-home. Everything you need is in the files you download at Start, including the correction note **updates/U001-engineering-and-data-replies-v1.md**. Read it with the other sources, apply it where it changes your work, and cite it as U001.

## Tools and help
Use any tools and help you like: AI tools and agents, search, your own notes, friends or colleagues. You don't need a paid tool, an API key or an account.

Nothing you do in your own tools is watched. Only your files and your interview answers are reviewed. When you submit, you can say which tools or help you used. That is optional, and leaving it empty is never held against you.

## Submission
Hand in one ZIP with these files at its top level. Start from the copies in the templates folder.
- README.md: list every file you hand in and say how you used the correction note (U001), at most 150 words.
- mvp-definition.md: the proposed definition, at most 1,000 words, table cells included, headings and record IDs not. Use the template's eight headings. Mark it proposed.
- review-note.md: your recommendation, the conditions or blocker record, what the correction note (U001) changed, messages for the account owners and what goes on next (named, not started), at most 450 words.
- evidence.csv: it already has one row for each record, R001–R055, with the record ID and merchant code filled in. Fill in the empty columns on every row: your own capability or target in the capability column, how you use the record in the disposition column (supports, contradicts, limits, context or not used are suggested) and a short reason in the rationale column. Add a row if a record bears on more than one capability. Do not retype or delete record IDs or merchant codes. If the correction note (U001) changes a record, revise its row, put U001 in the evidence_version column and keep the earlier reading visible.
- revision-log.md: what you changed after the correction note (U001) and what you kept, with the earlier figures still visible, at most 350 words.

Words are counted in the prose and table cells of each document you write; headings, table borders, record IDs and the README do not count.

Use plain text files only: .md, .txt, .csv or .json. Put your work in the files themselves; a link to a document somewhere else does not count. Your ZIP can be up to 5 MB, or 20 MB unzipped, with at most 39 files of up to 2 MB each. Programs, macros, password-protected ZIPs and ZIPs inside your ZIP are not accepted.

Upload your ZIP on your take-home page and wait for **Received and checked**. It normally appears within a few seconds of the upload finishing. If it has not appeared after a minute, upload the ZIP again; if it still does not appear, use **Help and support**. You can replace your ZIP until you submit. Submitting is final and starts your break.

If time runs out before you submit, the last ZIP marked **Received and checked** is handed in for you. If none was received, the team is told that you need support.

If something goes wrong, use **Help and support** on your take-home page. A technical problem is never counted against you. Writing to us does not pause the clock.

## What happens next
The written interview covers these parts of the job:
- Checks sources and counts
- Weighs evidence and risk
- Checks and fixes the AI draft
- Hands off a decision others can act on
- Explains the reasoning
- Cuts scope to what first customers need

An AI then drafts a review from your files and your answers. Each point quotes what it rests on. A person at the company reads the review and makes any decision. No one is hired, rejected or ranked automatically.
