Meeting time is billable when it directly advances the client’s project — and charging for it at your standard rate is not padding; it is accurate accounting of where your expertise was spent.
Most freelancers and software consultants undercharge for meetings by 5–10 hours every week. Not because they are unaware of the hours, but because an unspoken fear creeps in: “I wasn’t writing code, so was I really working?” This thinking is flawed and expensive. Meetings where you gather requirements, review architecture decisions, or walk a client through a sprint demo are as cognitively demanding as development work. The billable line is not drawn at code output — it is drawn at client benefit. A clear meeting billing policy, set before work begins, eliminates the awkwardness permanently.
Why Developers Undercharge for Meeting Time
The root cause is rarely greed or oversight. It is a combination of imposter syndrome and unclear contracts.
When you spend three hours in a requirements workshop, you did not produce a commit. Nothing deployable exists at the end of that session. The psychological link between “visible output” and “legitimate billing” leads many consultants to quietly absorb meeting hours as a professional courtesy — even when the client never asked for one.
The second cause is contract ambiguity. Statements like “billed at £X per hour for development work” invite the question: does a status call count? Without explicit language, developers default to not charging rather than risk a dispute.
The result is a hidden subsidy. Industry research consistently shows that software consultants working on client projects spend 20–30% of their time in meetings. On a typical 35-billable-hour week, that represents 7–10 hours. At a £100/hr rate, that is £700–£1,000 per week written off silently — not because it was agreed, but because the contract was vague.
When Meeting Time Is Billable (and When It Is Not)
The guiding principle is simple: if the meeting exists to serve the client’s project, it is billable.
Billable meetings include:
- Client status and update calls
- Requirements gathering and discovery sessions
- Sprint planning and sprint review with the client present
- Architecture reviews and technical decision meetings
- Pair programming or code review sessions with the client’s team
- Onboarding and handover meetings where you transfer knowledge
- Incident response calls triggered by client systems
Non-billable meetings include:
- Internal team standups with your own company (not involving the client)
- Sales calls and pre-engagement scoping calls (before the contract is signed)
- Company all-hands and internal training sessions
- Networking and community events
Grey-area meetings require a judgment call:
- Initial scoping calls after an engagement begins: billable if the client asked for them to expand scope
- Post-project retrospectives: billable if the client is present and the retro informs their future decisions
- Ad-hoc Slack huddles under 10 minutes: most consultants apply a minimum billing increment (e.g. 15 minutes) and round up
The grey areas are best resolved in advance by the policy language in your contract, not case-by-case during invoice disputes.
Billing Models for Meeting Time
There is no universal model, but each of the four common approaches has a clear best-fit scenario.
| Model | How It Works | Best For |
|---|---|---|
| Flat rate | Meetings billed at the same hourly rate as coding | Most freelancers and small agencies |
| Reduced rate | Meetings billed at 50–75% of coding rate | Agencies trying to retain price-sensitive clients |
| Meeting cap | First N hours/month included, excess billed | Retainer clients with predictable cadence |
| Bundled retainer | All meetings included in a fixed monthly fee | Long-term relationships with stable scope |
Flat rate is the fairest and simplest model. Your expertise does not depreciate because you are speaking rather than typing. Requirements workshops, architecture discussions, and incident calls require deep domain knowledge — knowledge the client is paying for regardless of whether a keyboard is involved.
Reduced rate is a commercial concession, not a reflection of value. It can make sense when you are competing for a client on price and want to differentiate, but it should be a deliberate choice with a clear end date — not an indefinite habit.
Meeting caps work well for retainer relationships where the client has a predictable communication pattern. Including 4 hours of meetings per month in a £4,000 retainer and billing additional hours at your standard rate gives both parties budget certainty.
Bundled retainers are the cleanest from a client-relationship standpoint but require accurate forecasting. If meetings routinely exceed your estimate, you absorb the difference.
How to Set Meeting Billing Expectations with Clients
The easiest conversation about meeting billing is the one you have before work starts. Retrofitting a billing policy midway through an engagement always feels like a price increase, even if it is just formalising something that should have been agreed earlier.
In your contract or statement of work, add language such as:
“All project-related time is billed at the agreed rate of £X per hour. This includes, but is not limited to, development work, code reviews, technical meetings, client calls, requirements sessions, and any other time spent directly on deliverables for this engagement. Time is tracked and reported weekly.”
This language is clear, professional, and mirrors standard agency terms. It leaves no room for interpretation.
In your time reports, separate meeting time from development time. Use category labels like “Client Meeting — Requirements”, “Client Call — Sprint Review”, and “Development — Feature X”. Transparency here reinforces that you are not padding; you are accurately accounting for where your expertise was applied.
Automate meeting capture. Calendar integrations with your time tracking tool log meetings as time entries automatically, eliminating the risk of forgetting to track them. When the time report shows a status call entry with an exact start and end time, it reads as accurate data rather than approximation. If a client questions a meeting entry, you can point to the calendar invite they sent you.
When clients push back, the most effective reframe is: “My time in your meetings is time I cannot spend coding for you or any other client. The meeting was productive work on your project — it belongs on the invoice.”
How to Reduce Meeting Overhead (So Everyone Wins)
Billing accurately for meetings does not mean tolerating unnecessary ones. Reducing meeting volume protects your coding time, improves your hourly economics, and improves client satisfaction — clients rarely enjoy paying for status calls that could have been a written update.
Replace recurring status calls with async updates. A short Loom video walking through the week’s progress, or a structured Slack message with three sections (done, blocked, next), covers the same ground in 10 minutes of your time versus a 45-minute call. Clients who see async updates regularly tend to request fewer live calls.
Set agendas and time limits for every meeting. A 30-minute meeting with a clear agenda and a stated end time will almost always finish on time. An open-ended “let’s sync” will expand to fill whatever time is allocated.
Batch client meetings into one or two days per week. Context-switching between deep development work and client calls is expensive. Blocking Tuesday and Thursday afternoons for client meetings protects the rest of your week for deep work and reduces the cognitive overhead of constant switching.
Track your meeting-to-coding ratio. If meetings consume more than 30% of your working week, flag it to the client. Frame it constructively: “We have spent 12 hours in meetings this month against 28 hours of development. That is a high ratio — let us look at which meetings we can replace with async updates.” Most clients will reduce meeting cadence when they see the metric.
Use recorded demos instead of live demo meetings. A five-minute Loom walkthrough of a new feature, sent before a review call, means the review call is a 10-minute discussion rather than a 30-minute live demonstration.
Key Takeaway
Meeting time is billable when it serves the client’s project. Set this expectation in your contract before work starts, bill meetings at your standard rate, and reduce unnecessary meetings to protect coding time and improve client satisfaction.
Ready to Track Meeting and Coding Time in One Place?
Keito tracks meeting time automatically from your calendar and coding time from git commits. One tool, complete billing data — no manual entry, no forgotten hours.
Frequently Asked Questions
Should freelance developers charge for client meetings?
Yes. Client meetings are project work. If the meeting exists to advance the client’s project — requirements gathering, sprint reviews, architecture decisions — it is billable. Include explicit language in your contract to set this expectation before work starts.
What is a fair hourly rate for meeting time vs coding time?
The same rate. Your expertise, analytical thinking, and decision-making during meetings are as valuable as your coding output. Charging a reduced rate for meetings undervalues the knowledge transfer the client receives during those sessions.
How do I track meeting time automatically?
Use a time tracking tool with calendar integration. Meetings on your calendar are automatically logged as time entries, categorised by client and project. This eliminates manual entry and provides an accurate, timestamped record of meeting time for each invoice.
How many hours of meetings per week is too many?
If meetings consume more than 30% of your working week, your billable coding capacity drops significantly. Track the meeting-to-coding ratio and set boundaries with clients — replace recurring status calls with async updates where possible.
Should I charge for quick 15-minute client calls?
Yes, using your standard minimum billing increment. If you take four 15-minute calls per week, that is one billable hour. Apply a consistent rounding policy — rounding to the nearest 15 minutes is a widely accepted standard — and document it in your contract.