# Propose pricing and packaging for a new AI feature

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

## Situation and outcome
Larkspan is a fictional company that sells Larkspan Contracts, contract-management software for mid-market legal and procurement teams. It is priced per full seat per month on three plans: Starter $35, Team $65 and Business $95. Requesters, who submit contracts for review, are free light users. Clause Warden is a new AI agent that reviews a third-party contract against the customer's playbook, flags deviations and drafts redlines for a lawyer to approve. 14 accounts have used it free in a pilot since 15 June, and it reaches general availability (GA) on 2 November. The CEO holds pricing authority and decides at the pricing council on 16 October; the proposal and validation notes are due on 13 October.

Your outcome is a pricing proposal, marked proposed, for the CEO's decision: the pricing model, value metric, packages, price levels or ranges, guardrails and rationale, with validation notes by function (what the supplied notes from each function confirm, what is open and who owns it), a revenue-effect range with its assumptions and the conditions under which a declined proposal could come back. At associate scope the same write-up is the recommendation you give your PM, as your scope says. A well-argued "the evidence cannot settle the price yet" is a valid result. The proposal does not approve prices, implement them in billing or customer agreements, run new customer research, interpret agreements, reprice the base plans or prepare sales guidance.

The period is 2026-07-20 through 2026-10-02 inclusive. Work with 59 records (pilot usage, interviews, a price survey, sales and customer success notes, competitor pages, and finance, billing and counsel notes), a current price list and an AI first proposal. The AI proposal is a draft, not an authority. 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 pricing proposal for Clause Warden for the CEO's pricing council on 16 October: model, value metric, packages, price levels or ranges, guardrails and rationale, with validation notes and the revenue effect. You may propose discount guardrails, but you may not approve prices, grant discounts, interpret agreements or commit pricing to pilot accounts.

## About the team
A product team proposing pricing for a new AI feature to the executive who holds pricing authority.

A pricing-research agent compiles competitor pages and drafts a first proposal; an AI note-taker summarises calls; each function reviews before the CEO decides.

Billing confirms what it can bill; counsel interprets contracts and anything promised to pilot accounts; the CEO approves any price.

## Work to complete
1. Frame the decision: what the CEO must decide on 16 October and which evidence it rests on. Read sources/coverage-and-access.md before you make any claim about what the evidence covers, and sources/current-pricing.md for the plans.
2. Work out how Clause Warden should be sold: what to count (the value metric), which plans or packages, a price level or range, and guardrails for heavy or unusual use, discounts and the pilot's move to paid. Show how each element fits how customers get value, what it costs to serve and what billing can run.
3. Audit the AI first proposal against the original records. Keep, correct or reject each row and say why. Keep evidence that points the other way visible, and tell apart a measured figure, a person's claim and a gap.
4. Count records, accounts, seats and uses separately, and say what each number is a count of. Treat a rare serious case separately from how common it is.
5. Write validation notes by function (billing, counsel, finance, sales, customer success) from the supplied notes: what each confirms, what is open and who owns it. Send agreement questions to counsel and billing questions to billing without answering them yourself.
6. 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.
7. Hand off clearly: the decision for the CEO with options and what each trades, the revenue range with its assumptions, and what would let a declined proposal come back.

## 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-billing-and-finance-check-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).
- proposal.md: at most about 1,100 words. The decision and options for the CEO, the value metric and why, packages and who buys them, price levels or ranges with what bounds them, guardrails, the revenue-effect range with assumptions, and the limits. Mark it proposed.
- validation-notes.md: at most about 700 words. Findings by function with status (resolved, open or routed), owner and records, and the conditions for resubmission.
- evidence.csv: already has a row for every record, R001–R059, with the record ID and account ID filled in. Do not retype them. For each row, fill in element (the part of the proposal the record bears on; metric, packaging, price, cost, competition, validation, revenue and transition are suggested and free text is accepted) and stance (supports, contradicts, context, limit or excluded are suggested), and add a one-sentence rationale. If a record bears on more than one element, 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: the disposition of each AI first proposal row, 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 off to the right owners
- Explains their own work
- Fits price to value and cost

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.
