Build a Live Meeting Cost Ticker with Hourly Rates and Agenda Timer in One HTML File

Creates a one-file meeting cost calculator that ticks up in real time from attendee counts and hourly rates, with an agenda timer and an end summary, so teams can decide if a meeting is worth its price.

You getThe complete HTML file in one code block, A 5-step usage guide and table of risks and missing information

The prompt

Prompt
Role: You are a front-end developer who designs lightweight team productivity tools with clear, honest numbers.

Context: The audience is a ten-person product team that holds many recurring status meetings (example value for {team_context}). The decision this tool supports is whether a meeting is worth continuing, shortening or replacing with an async update. Currency: USD (example value for {currency}). Default blended hourly cost per attendee: 60 (example value for {default_rate}).

Task: Build one self-contained HTML file (inline CSS and JS, no libraries or network) that shows the running cost of a meeting.

Inputs (list any you assume):
- Attendee groups: label, headcount, hourly cost (default to the blended rate)
- Planned meeting length in minutes
- Optional agenda items with minutes allotted
- Whether to include a 'context switch' overhead (off by default, editable minutes per person)

Workflow:
1. Write an Assumptions list: cost uses hourly rate divided by 3600 per second; overhead is excluded unless enabled; rates are estimates, not payroll data.
2. Build a setup panel with add/remove attendee groups and a live preview of cost per minute.
3. Provide Start, Pause, Resume and Finish buttons. While running, show a large cost counter, elapsed time, and planned versus actual time.
4. If agenda items exist, highlight the current item, show its remaining time, and mark it overrun in red text with a label when exceeded.
5. At Finish, show a summary: total cost, cost per attendee, minutes over or under plan, and a one-line prompt asking 'Was a decision made?' with Yes/No stored locally.
6. Keep the last 10 meeting summaries in localStorage with a clear-history button.
7. Use requestAnimationFrame or a timestamp-based interval so the clock stays accurate when the tab is in the background.

Constraints: Offline, no external requests, no sound by default. Respect prefers-reduced-motion. Do not store names of real people; groups are labels only. Keep the tone neutral and avoid shaming wording.

Output format:
1. Assumptions
2. The complete HTML file in one code block
3. A 5-step usage guide
4. Table of risks and missing information (risk, why it matters, next action)
5. Next actions: three optional upgrades

Acceptance criteria:
- A 4-person group at the default rate shows the correct cost after 60 seconds
- Pausing stops the cost; resuming continues without a jump
- Overrun agenda items are indicated by text and color
- History survives refresh

Quality checks: Verify the math with a worked example in a code comment, ensure elapsed time uses timestamps and not tick counts, confirm that zero attendees or a zero rate shows a helpful message, and state anything you could not test.

Dashed parts are example values, so the prompt runs as copied. Change them in Fill in the blanks.

Use realistic blended rates rather than individual salaries. Treat the result as an estimate for awareness, not an accounting figure. Good for team retrospectives and meeting-hygiene conversations.

Make it repeatable

Keep using this prompt without pasting it in every time.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Mini Apps & Tools