AI-generated editorial illustration of a meeting-planning workflow; it does not depict a real company, team or financial record.
A short meeting is not automatically a useful meeting. A useful meeting has a decision to make, the right people in the room, a time limit and a written next step.
This guide shows a practical 30-minute format for small businesses, agencies and distributed teams. It uses the KuchhBhi Meeting Cost Timer as an estimate—not as a reason to rush people or exclude necessary voices.
First decide whether a meeting is needed
Use a live meeting when people need to debate trade-offs, resolve ambiguity, make a decision or handle a sensitive conversation. Use a written update when the work is mainly sharing status or collecting information.
Before sending an invite, finish this sentence:
By the end of this meeting, we will decide ________.
If you cannot name the decision or outcome, pause and rewrite the request. A vague topic such as “marketing discussion” is not enough. “Choose one of three campaign concepts and assign the launch owner” is actionable.
Estimate the meeting cost
Open the Meeting Cost Timer, choose the currency, enter the number of attendees and enter an average hourly rate. Start the timer when the working discussion begins.
For example, five attendees at an average â‚ą1,000 per hour for 30 minutes produce an estimated cost of â‚ą2,500.
That number is only a planning estimate. “Average hourly rate” can mean salary-derived time cost, billing rate or a fully loaded business cost—but those are not interchangeable. Agree which interpretation your team is using. The tool does not calculate payroll, benefits, taxes, revenue lost, exchange rates or the value of a good decision.
Use a decision-first 30-minute agenda
Minutes 0–3: state the outcome and roles
The facilitator reads the decision question. Confirm who is the decision owner, who is facilitating and who is recording actions.
People may hold more than one role in a small team. What matters is that responsibility is explicit.
Minutes 3–8: confirm facts
Review only the facts needed for the decision: customer requirement, deadline, budget, constraint and the options being considered. Link a pre-read in the invitation so the meeting is not consumed by silent reading.
If attendees disagree about a fact, record what must be verified. Do not turn an assumption into certainty because the clock is running.
Minutes 8–20: discuss options and trade-offs
Take each option in turn. Ask:
What customer or business need does this serve?
What does it cost in money, time and attention?
What could fail?
What evidence would change our view?
Who will be affected but is not in the room?
Use a “parking lot” for useful issues outside the current decision. Give quieter participants a deliberate chance to contribute. Cost awareness should improve focus, not silence questions.
Minutes 20–26: make the decision
The decision owner states the choice, the reason and any condition. If the team cannot decide, do not hide that outcome. Record the missing fact, the person who will obtain it and the next decision deadline.
Minutes 26–30: capture actions
Finish with a short action list:
action;
owner;
due date;
definition of done.
Read the list aloud. A meeting that ends with “someone should…” has not assigned work.
Prepare a one-screen invitation
Keep the invitation readable on a phone. Include:
Decision: the one question to answer.
Context: two or three sentences.
Options: links or a short comparison.
Pre-read: only what is necessary.
Roles: decision owner, facilitator and note-taker.
Agenda: timeboxed sections.
Access: location or call link and any language or accessibility needs.
Asana’s meeting-agenda guide, updated 10 January 2026, recommends a clear goal, attendees, discussion topics, time allocations and pre-reading. Atlassian’s inclusive-meetings play advises sending a detailed agenda in advance and framing agenda items as questions. These are useful prompts, not mandatory software choices.
Make multilingual meetings easier to follow
A mixed-language team should not have to choose between participating quickly and participating accurately.
Write the decision question and key terms before the call.
Avoid unexplained abbreviations and culture-specific jokes.
Let participants answer in the language they can use most precisely when the team can support it.
Summarise the final decision in plain written English, then add an agreed translation if needed.
Pause after complex points so people can ask for clarification.
Do not treat accent, speed or grammar as a measure of expertise.
If you record or transcribe a meeting, explain the purpose, access, retention and deletion rules, and obtain any consent required by your organisation and applicable law. The KuchhBhi cost timer itself does not record audio or meeting content.
Run a cost check without harming the meeting
Display the timer only if the team finds it helpful. A rapidly increasing number can create pressure, especially during difficult personnel, safety or customer conversations. In those cases, estimate the cost before or after the meeting instead.
The estimated cost can help you compare formats. For example:
six people for 30 minutes;
three people for 20 minutes followed by written notes;
a five-minute recorded update plus a 15-minute decision call.
But cost is not the only measure. A meeting may be worthwhile if it prevents rework, resolves risk or includes people whose perspective changes the decision.
Review the result after the call
Ask four questions:
Did we make the promised decision?
Did every action receive an owner and due date?
Were all attendees necessary for the whole discussion?
What should be asynchronous next time?
Save the agenda, decision and action list together. Do not publish sensitive rates or personnel assumptions in shared notes. If displaying meeting-cost estimates could expose compensation information, use a blended rate approved for internal planning.
Common limitations
The timer assumes one average hourly rate for every attendee. It does not support different rates per person or automatically stop for breaks. Currency presets are editable examples, not market rates. A running browser tab is not an accounting record.
The estimate also cannot measure meeting quality. A low-cost meeting can still waste time, while a higher-cost meeting can create substantial value. Use the number to prompt better design, not to rank people.
Frequently asked questions
Should I use salary or client billing rate?
Choose the measure that fits the decision and label it clearly. Salary-derived cost, fully loaded employment cost and client billing rate answer different questions.
Does a 30-minute meeting always cost half of a one-hour meeting?
Under the timer’s linear formula, yes, if attendee count and average rate stay unchanged. Real business impact may not be linear.
Should every attendee see the running cost?
No. Discuss it with the team first. If the display distracts or pressures people, calculate privately before or after the meeting.
Can I include freelancers and vendors?
Yes, but one average rate may hide major differences. For a more accurate internal estimate, calculate groups separately and add the results.
What if the decision needs more than 30 minutes?
Do not force a weak decision. End with the unresolved questions, owners and a new deadline. Improve the pre-read or split discovery from decision-making.
Is the calculator a payroll or accounting tool?
No. It is a browser-based planning timer based on attendee count, one average hourly rate and elapsed time.
Sources and review date
Reviewed 4 October 2026 against the released KuchhBhi calculator and the following current guidance:
The meeting format and example are KuchhBhi editorial recommendations. Adapt them to the importance, sensitivity and accessibility needs of the decision.
