# Useful lead magnet app brief Define a helpful answer before adding a contact form. The workshop example below is fictional and has not been built or tested. Results in this worksheet begin **Not tested**. Related guide: https://www.overskill.com/learn/build-a-useful-lead-magnet-app ## Define the reader's decision - Intended reader: - Question they already need to answer: - Decision this app can help with: - Smallest useful result: - Inputs needed, with units: - Assumptions the reader must verify: - Source or explanation for each formula/rule: - What this app cannot conclude: - A useful next action even if the result is unfavorable: - Whether an account or saved result is genuinely needed: ## Copy the fictional workshop brief ```text Build a workshop contribution calculator using fictional sample data. Help an organizer compare ticket income with event costs. Inputs: expected paid attendees, ticket price, fixed event cost, and variable cost per attendee. Label all money in one selected currency. Sample: 20 attendees, $40 ticket, $300 fixed cost, $5 cost per attendee. Calculate contribution = attendees × (ticket price − variable cost) − fixed cost. Show $400 contribution for the sample, with the calculation visible. Let the reader change one input and compare with the sample. Reject negative amounts and fractional attendee counts with a clear message. Label outputs as estimates based on entered assumptions, not promised income. Keep results visible without requiring an email address. Do not save personal data, connect payments or send messages in this version. Explain whether inputs survive reload; do not imply they are saved if they are not. Provide a short checklist of assumptions to verify before planning the event. ``` Expected sample arithmetic: `20 × ($40 − $5) − $300 = $400`. This calculates contribution after the listed costs. It is not complete business profit: unlisted taxes, fees, refunds, staffing or other expenses are outside the formula. It does not establish that tickets will sell. Add relevant costs explicitly before using a version for a real decision. ## Test the calculation and experience Use a disposable version. Status choices: **Not tested**, **Pass**, **Fail**, or **Not applicable** with a reason. | Check | Expected | Observed | Status | | --- | --- | --- | --- | | Original sample | 20 × ($40 − $5) − $300 = $400 contribution | Not tested | Not tested | | Change fixed cost to $800; keep other inputs | −$100 contribution; the unfavorable result is visible and explained | Not tested | Not tested | | Restore fixed cost to $300 | Original $400 result returns | Not tested | Not tested | | Set attendees to 0 | −$300 contribution, not a division error or a promised sale | Not tested | Not tested | | Enter a negative cost or fractional attendee count | Clear validation; no misleading calculated result | Not tested | Not tested | | Leave a required input empty | The missing value is identified; no false complete estimate | Not tested | Not tested | | Use keyboard and phone-sized screen | Inputs, labels, calculation and next step remain usable | Not tested | Not tested | | Reload after an edit | Behavior matches the displayed saving policy | Not tested | Not tested | | View the result without supplying email | Result and assumptions remain available | Not tested | Not tested | Tested app/version: Date/browser/device: Evidence locations: Remaining failures or unknowns: ## Ask a potential user to explain the answer Record actual feedback, without filling it in beforehand. - Task given to the participant: - Did they understand the question? **Not tested** - Could they explain the result and its units? **Not tested** - Which assumption would they check next? **Not tested** - Did the next action help them? **Not tested** - Exact feedback, with permission to retain it: - Change to make before testing again: ## Add a next step only when useful - Proposed next action: - What the reader receives: - Why it follows from this result: - If contact details are needed, what data is requested and why: - What the person is told will be sent: - Consent/storage/deletion requirements to establish: - Connection/delivery tests: **Not tested** - Clear failure response: **Not tested** This worksheet establishes no leads, sales or conversion improvement. Those require actual results from the released app and a defined measurement method. Continue with https://www.overskill.com/learn/build-an-app-with-mcp and https://www.overskill.com/learn/ai-app-launch-checklist.