# Rollouts competitor analysis

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

## Situation and outcome
Brenhollow is a fictional developer-tools company with 140 people. Brenhollow Rollouts sells feature flags and progressive rollouts to engineering teams of 20 to 500 developers. You are the product manager for Rollouts. The Head of Product asks you to build the competitor analysis for Q4 planning and have v1 ready for publication by Monday 5 October, with a last-reviewed date and a watch list (R001). Product marketing and sales review the factual claims before it goes out. Proposed responses are proposals: roadmap items go to roadmap review, where the Head of Product decides, price questions go to the pricing council, which the CFO chairs, and positioning and battlecards stay with product marketing.

Your outcome is an analysis ready for publication and a way to keep it current. The analysis scopes the real alternatives to Rollouts, compares them on what customers hire a flag platform to do, states a confidence and a date for each claim, and proposes responses, each with the person who decides it. The first monitoring check of the watch sources is already in your download as a correction note. It brings new competitor moves. You judge which of them are material, revise the analysis and draft the alert for the people who need to know (text only, nothing is sent), or log no change with your reasons. A change is material when it alters a stated strength, a stated weakness or a proposed response. A well-argued evidence gap, such as a ranking you decline to publish because the records cannot support it, is a valid result. The analysis does not decide any response, price or positioning, write battlecards, interview customers or give legal advice.

The period is 2026-06-01 through 2026-09-30 inclusive; the snapshot is Wednesday 30 September, v1 is due on 5 October and the first watch-source check is on Tuesday 6 October. Work with 56 records (internal documents, competitor and analyst pages, community posts, closed-deal entries, call summaries and account notes) and an AI first draft of the analysis. The draft is a draft, not an authority. Use the supplied record IDs and source context, and follow the competitive intelligence policy in R003. 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 Rollouts competitor analysis: its scope, version, review date and the stakeholder alert. You judge materiality and propose responses, each with the person who decides it. You may not commit roadmap work, change prices, change positioning or battlecards (product marketing), or settle legal questions.

## About the team
A developer-tools product team keeping a competitor analysis current for roadmap review, the pricing council and product marketing.

A research agent compiles a weekly competitor digest from public pages and drafts the first analysis from the digest, the CRM export and the old battlecard; sales engineers review AI summaries of recorded calls; a person checks every claim before the analysis is published.

The Head of Product decides roadmap items at roadmap review; the pricing council, chaired by the CFO, decides price; product marketing owns positioning and battlecards; legal owns the intelligence policy; the product manager owns the analysis and its alerts.

## Work to complete
1. Frame the question: who the analysis serves and who decides what (R001, R005). Read sources/coverage-and-access.md before you make any claim about what the records cover.
2. Scope the set: the alternatives a buyer really has, not only the named rivals. Give each a reason for being in or out and a watch source.
3. Count field signals by account, once, and say what the closed-deal entries can and cannot represent. Keep what a competitor says about itself apart from what customers and prospects did.
4. Audit the AI first draft against the original records. Keep, correct or reject each line and say why. Keep evidence that points the other way visible.
5. Compare the alternatives on the customer jobs listed in the coverage file, with a confidence and a date for each claim. Treat severity separately from frequency.
6. Propose responses. Each is a proposal that names the person or forum that decides it. Say where Brenhollow wins, and where it should not compete.
7. Write v1 as if for publication: version, last-reviewed date, reviewers, known unknowns and a watch list. Nothing is really published or sent: you only prepare the text, name the reviewers and mark it "pending approval".
8. Run the monitoring pass on the correction note (updates/U001-monitoring-pass-v1.md). Decide which changes are material and which are not, and give the reasons. Carry each justified revision through every file and keep the earlier reading visible. The change log is your own account of how you worked.
9. Hand off clearly: what the analysis says, how sure it is, what changed, who decides what and who hears about it. Say that responses are proposals.

## 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-monitoring-pass-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 the correction note (U001) changed your work, or that it did not.
- analysis.md: about 1,300 words plus one comparison table by customer job. This one file is your final analysis; there is no separate baseline file. If the correction changes anything, it carries version v2 and the date of the watch-source check (6 October), and the change log keeps the v1 reading (5 October). If nothing changes, it stays v1. Version, last-reviewed date and reviewers, the set and watch list, the assessment by customer job with confidence and dates, proposed responses with deciders, known unknowns and limits. When you revise it, this file is the current version and the change log holds the earlier reading.
- evidence.csv: the template already has one row for each record, R001–R056, with its record ID and account ID filled in. Fill in the rest of each row and keep every row: the competitor or alternative it bears on most (a name of your own, or free text such as internal for records that bear on none), a use (supports, contrary, vendor claim, context or excluded are suggested; your own word is fine) and a one-sentence rationale. Do not retype or remove record IDs or account IDs. If the correction note changes a record, revise its row in place, set evidence_version to U001, and keep the earlier reading visible in its rationale or the change log.
- change-log.md: at most about 700 words. The monitoring pass (sources checked, what changed, material or not with reasons, actions), the version history with the earlier reading kept visible, and a stakeholder alert of under 150 words that names the changed sections and the record IDs. No private prompts or unrelated files.
- open-questions.md: at most 10 open questions, each with one suggested owner and the decision that depends on it. List disputed claims for the people who own them instead of settling them.

Keep every file within these limits: the reviewer reads all of it.

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 counts
- Weighs evidence and confidence
- Checks and repairs the AI draft
- Hands off to the right owners
- Explains their own work
- Compares by customer job

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.
