# Recommend how to source invoice capture

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

## Situation and outcome
Brelmoor is a fictional company that sells accounts-payable automation to about 640 mid-market customers in the US and EU. Its product, Brelmoor Payables, reads supplier invoices, matches them to purchase orders and goods receipts, and routes exceptions to buyers. The first step, capture, turns an invoice (PDF, scan or email) into header fields and line items. You are the product manager for capture and matching. On Monday 28 September the Head of Product asked you to recommend how Brelmoor should source capture, for the CPO's review on Wednesday 21 October (R002). Today is Wednesday 14 October. The records are the snapshot of Monday 12 October, and the correction note (U001) holds the notes sent since.

Your outcome is a sourcing recommendation marked proposed, an option matrix with a dependency-risk register, and an evidence table. The recommendation says what you propose and on which conditions, which options you rejected and why, what you assumed, what counsel and procurement must answer, what waiting would cost and who acts next. It leaves the decision record blank for the CPO. A recommendation that says plainly that no option is ready to decide, with the gates that would release a decision, is a valid result. Your work does not decide, sign, negotiate, give a legal view, select a vendor or tell customers anything.

The period is 2026-06-01 through 2026-10-02 inclusive: every record is dated inside it, and the snapshot is Monday 12 October. Treat the records and the correction note (U001) as your evidence; the correction note is dated 14 October, after the period, and still counts. Do not rely on outside material or on anything you remember about real companies. Work with 62 records (strategy, requirements, usage, customer, sales, market, engineering, benchmark, vendor and reference-call records) and an AI first draft of the recommendation. The draft is a draft, not an authority. Use the supplied record IDs and source context; do not contact the fictional teams or vendors, and do not seek private data or live queries.

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

You own the sourcing recommendation, marked proposed, for the CPO's review on 21 October. You may propose an option, conditions, a fallback and revisit triggers. You may not sign or negotiate with a supplier, accept contract or data terms (counsel and procurement), move the connector program (Head of Engineering), approve spend (CPO and CFO) or speak to customers about the vendor news.

## About the team
A B2B software team preparing a build, buy or partner recommendation for the chief product officer's review.

An analyst agent drafts the first recommendation from the sourcing folder; CRM and call notes are summarised by AI; the evaluation team runs a scripted benchmark; procurement uses an assistant to summarise vendor terms; a person checks every figure against its source before the review.

The chief product officer decides; finance signs spend above the delegated limit; counsel answers legal questions; procurement and partnerships run any vendor or partner step; nobody speaks to customers or vendors about a pending decision.

## Work to complete
1. Frame the decision: what the CPO is asked to decide on 21 October, and what you propose. Read sources/coverage-and-access.md before you make any claim about what the records cover.
2. Judge the need and whether capture sets Brelmoor apart: how many customers feel the problem and how sure that is, and what the records, not the people asserting it, show about differentiation.
3. Assess every option on the same terms: build, each external option, and keeping the current engine supported for now. Compare fit to the stated requirements, time to availability, three-year cost on like-for-like units, and what each takes from other work.
4. Assess dependency risk and lock-in for each option: data, security, contract terms and the way out. Put each in the register.
5. 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, and tell apart a measurement, a person's or a vendor's claim and a gap.
6. Write the proposed recommendation and hand it over: conditions, questions for counsel and procurement (listed, not answered), what waiting costs, and the next owner for each outcome.
7. Read the correction note (U001) with the other sources and apply it. Carry each justified revision through every file and keep the earlier reading visible. The revision log is your own account of how you worked.
8. Keep the decision with its owners: who decides, who signs spend, who answers the legal questions and who may speak to customers.

## 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-vendor-and-leadership-notes-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.
- recommendation.md: at most 1,000 words, counted in sentences and table cells (table pipes and dashes do not count). The need and differentiation judgment, the proposed recommendation and its conditions, the options you rejected and why, assumptions, questions for counsel and procurement, the cost of waiting, the next owner for each outcome and revisit triggers. Leave the decision record at its end blank for the CPO.
- options.md: at most 600 words, counted the same way. An option matrix comparing every option on the same criteria, and a dependency-risk register.
- evidence.csv: the template already has one row for each record, R001–R062, with the record ID and organisation ID filled in. Do not type IDs or add or delete rows. For each row, fill in the topic it bears on most (name your own topics), the stance (supports, contrary, context, excluded or unverified are suggested; free text is accepted) and a rationale of one sentence. 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 revision log.
- revision-log.md: at most 500 words. Which draft lines you kept, changed or rejected, then what the correction changed. No private prompts or unrelated files.

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

Words are counted in the prose and table cells of each document you write; headings, table borders, 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
- Compares build, buy and partner

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.
