# Build the business case for a monitoring service

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

## Situation and outcome
Brennock Refrigeration is a fictional maker and servicer of industrial refrigeration compressors for cold stores and food plants. Brennock Sentinel is a retrofit sensor kit plus a monitoring service, sold as a yearly add-on for each compressor. A 26-week pilot ran at six customer sites from 30 March to 27 September 2026. The VP Service, the sponsor, proposes launching Sentinel to the whole installed base in 2027 (R001). The spend is above $250,000, so the Investment Committee, chaired by the CFO, decides on 14 October on finance's case rules, and every case compares its options with doing nothing (R002, R003).

An analyst agent drafted a business case overnight from the data room (analyses/ai-first-case.md). It is a draft, not an authority. Your outcome is the business case that goes to the committee, marked **proposed**: the options set against finance's rules, a yearly model, the assumptions the answer depends on with an owner for each, the risks with conditions and triggers, and your recommendation. A well-argued "not ready for approval yet, and this is what would change that" is a valid recommendation. The case does not make the decision, hold the stakeholder meetings, set the price, produce a new demand forecast, execute the investment or track benefits afterwards.

Three dates are easy to confuse. The evidence runs 2026-03-30 through 2026-09-30 inclusive (the pilot and the data room stop there). The committee decides on 14 October 2026. The yearly model you build covers the five years 2027 to 2031 that finance's rules require. Work with 56 records (proposal and strategy papers, finance rules, estimates, service data, pilot reports, sales notes, surveys and interviews, risk notes and outside claims) alongside an AI first business case. Use the supplied record IDs and source context; do not contact the fictional teams or seek private data or live queries.

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

You own the business case and its recommendation, marked proposed, for the Investment Committee on 14 October. You may propose options, conditions and triggers. You may not approve the investment, set the price (pricing lead), accept contract terms (legal) or change finance's case rules.

## About the team
A product team preparing an investment business case for a finance-chaired committee, with the sponsor pressing for a larger launch than the evidence may support.

An analyst agent drafts the first business case from the data room; customer notes are AI-summarised; an agent fills finance's template. People own the estimates, accept the assumptions and make the decision.

Finance owns the case rules; the pricing lead owns price; legal approves contract terms; the Investment Committee decides.

## Work to complete
1. Frame the decision: what the committee is asked to approve, which options it chooses between, over which period. The proposal lists only one option. Read sources/coverage-and-access.md before you make any claim about what the data covers.
2. Build the case to finance's rules: define each option you compare, including doing nothing; estimate its costs and benefits year by year from the records (use the price and adoption figures the records supply as assumptions, and test them in your low and high cases rather than inventing your own), with a range, an owner and a source for each estimate; and show a low and a high case.
3. Audit the AI first business case against the original records. Keep, correct or reject each line and say why. Tell apart a measured figure, a person's claim and a gap, and count accounts, sites, compressors and records separately. Treat severity separately from frequency.
4. Find what decides the case: which assumptions the result is most sensitive to, how far each can move, and how well the records support it. Name the person who owns each assumption and its review status, without accepting an assumption on its owner's behalf.
5. Apply the correction note (U001) in your download like the other sources. Carry each justified change through every file, and keep the original reading of any record or figure it changes visible next to the revised one. The revision log is your own account of how you worked.
6. Hand off clearly: a recommendation kept a proposal, the conditions and triggers that go with it, and what the committee still has to decide.

## 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-assumption-review-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).
- business-case.md: about 1,200 words plus an option table. The decision asked of the committee, the options, the yearly model with low and high cases, what decides the case, risks with conditions and triggers, and your recommendation. Mark it proposed.
- assumptions.md: the assumption register. Each key assumption with the value used and its range, the records behind it, its owner, its review status and the evidence still needed.
- evidence.csv: already has a row for every record, R001–R056, with the record ID and account ID filled in. Do not retype them. For each row, fill in assumption (name your own; use the same names as in assumptions.md) and stance (supports, contradicts, context, untestable or excluded are suggested; free text is accepted), and add a one-sentence rationale. If a record bears on more than one assumption, add a row for it. If the correction note changes a record, revise its row in place, set evidence_version to U001, and keep the earlier reading in the rationale or the revision log.
- revision-log.md: material changes, verification checks and remaining gaps. No private prompts or unrelated files.

Words are counted in the prose of each document you write; headings, tables, the evidence file 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 numbers
- Judges what the evidence supports
- Checks and repairs the AI draft
- Hands the decision to the right owners
- Explains their choices
- Builds the case and finds what flips it

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.
