Removing friction is good advice in almost every trade. In coaching it’s half right. Coaching is one of the few businesses where part of what the client buys is the requirement to do something themselves, so some of that effort is the product. A tool that scores itself on steps removed counts every step as a gain, whichever kind it was.
- Admin is a kind of work. Friction is a cost, and it sits on the coaching half of your practice too. That’s where the expensive mistakes are.
- One question sorts most of it. Whose effort is this, and is it aimed at your logistics or at the thing they came to you about?
- Friction moves more often than it disappears. It lands on you, or inside the hour the client is paying for, or on the way out of the engagement.
- The largest pile of pure waste is elapsed time: the four days a message sat unread. Everything here says clear it.
Friction is not another word for admin
Which parts of your practice are arrangement and which are the work is a real split, and handing coaching admin to AI and staying yourself settles it. Friction cuts across that split. That’s why the two get confused, and the confusion is expensive.
Friction is what getting something done costs on top of the thing itself. The messages it takes. The waiting. The effort of composing. The small awkwardness of asking. In the arrangement pile that cost is dead loss. In the coaching half it’s often doing work, and the coaching half is full of it.
- The client writes the message instead of tapping something.
- The client waits until Thursday instead of getting an answer now.
- The client says out loud that they didn’t do the thing they said they would.
- You sit with a message you don’t yet know how to answer.
Ordinary software can smooth all four away today, cheaply. Three of them are worth keeping. The fourth is a judgment you make one message at a time.
The measure coaches get handed is what sends them wrong. Every tool in this category is sold on the same number: steps removed, minutes saved, emails eliminated. That number counts every step the same way, whether the step was idle or doing all of the work. Take it on its own and your practice drifts wherever it points. In coaching, that direction is a coin toss.
Whose effort was it
Here’s the second measure. Every piece of friction has somebody paying it, and sorting by payer does most of the work.
Yours. Time zone arithmetic. The fifth message in a scheduling volley. Hunting for the article you sent somebody in March. Retyping the cancellation policy for the two hundredth time. Your coaching survives every one of those going to software, and your clients value the work the same either way. Remove it and stop thinking about it. The rest of this guide is about the other piles.
Nobody’s. Dead time. A message that sat unread for four days under a software invoice. An agreement that sat unsigned for three weeks while it waited to be chased. A question a client asked on Sunday and you saw on Wednesday. This is the biggest pile in most practices, and it hides well. Friction gets counted in tasks. This kind is measured in elapsed days, and the days are empty.
The client’s. This is the one to slow down on. It’s the only pile where the answer takes thought. Here’s a test that holds up:
The client’s effort is doing work when it’s aimed at the thing they came to you about. Effort aimed at your logistics is waste.
Two messages, roughly the same length, arriving in the same inbox on the same afternoon.
What times do you have next week?
I’ve written this three times and deleted it. I think what I actually want to talk about is whether I want the promotion at all.
Take the effort out of the first and the client gets a few minutes back. Take the effort out of the second and the three drafts go with it. Those three drafts were the session starting early.
Four frictions that are doing work
The composing. Writing to you is often where the client’s thought gets made, rather than how a finished thought reaches you. The 2025 ICF Core Competencies, released in September 2025 and carrying the revision mark rev. 09.08.25 (checked September 6, 2026), put the verb on the client’s side in 7.09. The coach “Invites the client to generate ideas about how they can move forward and what they are willing or able to do.” Generate. That’s the client’s word.
So a between-session channel that reduces the client’s contribution to a tap takes away the part that was doing something. A mood slider. A number out of ten. A checkbox on a habit tracker. Each one is a real convenience. Each one swaps a paragraph the client would have written for a gesture that’s free to make and thin to read. The client who sends four rambling paragraphs and then apologizes for the length has usually done half a session for free.
The same thing shows up on the way in. When writing to you is free, more arrives and less of it has been thought about. Stay easy to reach; a coach who answers slowly to seem valuable has confused two different things. The shape of your between-session channel is a coaching decision, so give it five minutes before you pick the tool that implements it.
The remembering. The competency glossary defines accountability as “The responsibility to follow through on commitments and actions agreed upon during the coaching process.” A responsibility somebody holds. 8.02 has you partner with the client “to design goals, actions and accountability measures that integrate and expand new learning,” and 8.03 has you acknowledge and support “client autonomy in the design of goals, actions and methods of accountability.” Designed with them, owned by them.
An automated nudge on day four is a method of accountability your software designed and your software owns. It works, in the narrow sense that the action is more likely to get done. It also moves the remembering out of the client and into your tooling. Remembering an unpleasant commitment on your own is frequently the capacity the coaching was there to build.
The profession reached the same place from another direction, and it surprises most coaches. The ICF’s AI framework gives “habit-building quizzes made through a mobile application and email prompts relating to a specific goal or topic” as examples of an interactive application. That’s a category it treats as coaching delivered by software rather than as a tool assisting a coach. The classification and what follows from it belong to whether AI is okay for a coaching business. Here, the point is just that the taxonomy and the competency model agree. A nudge about the goal belongs to the coaching.
Two lines keep this usable rather than pious.
A reminder that Thursday is at 8:30 is about your calendar, not their commitment. The test is whether the client would have been the one responsible for remembering it. A session time is yours to hold, so send that reminder freely.
And if the client asks for the nudge, they’ve designed the method. That satisfies 8.03. A reminder the client chose is theirs. One that exists because your software offered the feature is yours. It’s worth knowing which one you’re running.
The awkwardness of asking to move a session. A client who wants to push Thursday pays a small social cost to say so. They write the sentence, and most of them feel faintly bad doing it. That cost is a signal, and it runs both ways. You learn something, and so does the client, who notices themselves asking.
Make rescheduling a single click and the second and third cancellation disappear into a calendar. The avoidance carries on. The record of it goes. A client who moves the session three times in the month they were meant to talk to their director is telling you something, and a one-click booking page can absorb the whole message before anyone reads it.
The fix is to keep the record while you remove the friction. A page where people move a session from your real availability is better for everyone, and booking links that show what you are genuinely free for is the practical version. You want the change made without you, and the fact of it still reaching you, in a form that adds up. Moved for the third time is a fact about a person. The harder case arrives as a sentence buried in an ordinary reply, and that’s catching a reschedule request buried in a thread. Whether the pattern means the client is busy or finished stays with you, and what AI should never touch in a coaching practice sets out that boundary properly.
The pause. Between a client writing to you and you answering there’s a gap. In coaching the client spends it thinking, and what they think is often the answer. Reply in four minutes and you may have answered a question they were three hours from answering themselves.
A fast reply can also read as a giveaway, because it breaks the tempo a client has learned to expect from you. That’s a different problem, and it belongs to the admin guide above. This one holds even where suspicion never enters. A quick answer to a coaching question is an intervention, and it stays one whether the speed came from your tooling or from a decision you made.
The practical form is that speed becomes a decision you make per kind of message, rather than a property of your software. Instant on logistics, where fast is simply the honest answer. Slower on anything where your reply is coaching. The discipline that sits alongside it, choosing the move before you read a draft, is worked through in keeping your voice when AI drafts your email replies.
Three that are only cost
Against those, three piles with nothing to weigh. Name them, so this guide reads as what it is: an argument for clearing them.
The volley. Six messages to place one hour. Your availability, their availability, a clash, a revision, a confirmation, an invite. Every coaching relationship is better off with all six gone, and scheduling without the email chain is the whole subject.
The search. Where’s the link. Which version of the document. What did they send in March. Did the signed agreement ever come back. Every minute here is yours, and it reaches the client only as a delay.
The dead wait. Say this one loudest. It’s the friction coaches skip past when they count, and it’s the one that does real damage. A message that sat four days costs the client their momentum. They wrote when they had it, and by the time you answer the thing they were going to do has passed. It costs you the reply you’d have given. And everything above was chosen. This was simply allowed.
That distinction is the whole argument. Every case here for keeping friction is a case about chosen friction, decided in advance, for a reason you could say out loud. Delay that happens because the message went unseen is a choice your inbox made for you. It reads to the client exactly like one you made. A coach who declines inbox tooling on authenticity grounds and then answers on day five has protected a feeling about the relationship, at the relationship’s expense. Reading a thread by its summary before you open it is the mechanic that makes clearing this pile cheap. It’s cheap because reading and answering cost wildly different amounts.
Where friction goes when you take it away
Friction is conserved more often than it’s destroyed. Take a step out and it usually turns up somewhere else. Knowing where is the difference between a decision and a surprise.
Onto you. A one-click reschedule takes friction off the client and puts it on your calendar. That’s frequently the right trade, and it’s the one most worth making on purpose. Made by accident, it becomes a week that reshapes itself around whoever moved something last.
Into the paid hour. An empty intake gives you a client who arrives at the first session cold. The fifteen minutes you saved them get spent in the hour they’re paying for, at a much worse exchange rate.
Onto a moment neither of you picked. This is the subtle one. Smooth eight things, leave the ninth, and the ninth becomes the message. Booking takes eight seconds and a real question takes four days. That gap teaches the client where they stand, and it teaches it on its own.
The way in and the way out
There’s a fourth destination, and it earns its own heading. It’s where automation does its most reliable damage to a coaching practice, and it happens by accident almost every time.
Signing up gets automated. Leaving does not. The booking page, the welcome sequence, the payment link and the calendar invite all get built in the first month, because those are the steps that were costing you clients. Cancellation, the pause, the request not to renew, the awkward conversation about stopping: each of those is still a message the client composes and sends to a person. That’s exactly the friction you removed from the other end.
The general form has a name and a regulator. The Federal Trade Commission’s staff report Bringing Dark Patterns to Light, published in September 2022 (checked September 6, 2026), lists “Roadblocks to Cancellation” among the practices it catalogs. It describes the practice plainly: “Making it easy to sign up but hard to cancel, by requiring people to go through tedious, time-consuming cancellation procedures.” The standard it applies comes from the Restore Online Shoppers’ Confidence Act, codified at 15 U.S.C. sections 8401 to 8405. That act requires online sellers using a negative option feature to provide “simple mechanisms for a consumer to stop recurring charges.” The report’s gloss is the sentence to remember: “negative option sellers should provide cancellation mechanisms that are at least as easy to use as the method the consumer used to buy the product or sign up for the service.”
If you sell a coaching package on a recurring charge, that reaches you. Most solo coaches sit a long way from the conduct the report describes. The ones who drift toward it get there by neglect rather than by design, and neglect is exactly what automation produces.
The professional version bites earlier and asks for more. Sub-competency 3.03 puts “termination” among the parameters you agree at the start, in the same list as logistics, fees and scheduling. Sub-competency 3.11 asks you to partner with the client “to close the coaching relationship in a way that respects the client and the coaching experience.” Both ask for more than a practice where joining is a button and leaving is an email that sits for a week.
The working rule is one line. Whatever you automate on the way in, build the mirror on the way out, or leave both by hand. If a client can book without writing to you, they can pause without writing to you. If the renewal is automatic, so is the notice before it falls due.
Friction worth adding back
Three additions, all cheap. Every one of them is a decision rather than a purchase.
A sentence on the way in. One question the client answers before they book: what do you want to use this session for. Sub-competency 3.06 asks you to partner with the client “to identify or reconfirm what they want to accomplish in the session,” and that partnering starts somewhere. A booking form is a cheap place to start it. It also changes who books and what they turn up with, so decide it on purpose. An inquiry that costs one sentence of thought gives you a different first conversation from one that costs a click. If you’d rather have the volume, take the volume. Make it a choice either way.
A beat before certain things leave. The reason is practical rather than theatrical. A message stays changeable right up until it goes. Anything that ends something, moves money, or was written while you were annoyed is worth holding until the next morning. Once it leaves, it’s sitting on somebody else’s server, and that’s the limit on undo.
A standing hold on the categories you already know. Which messages you write cold rather than start from a draft is settled in keeping your voice. The friction question here is only about when you decide. Put those categories somewhere the system leaves alone, so you make the decision once, in a calm hour, instead of forty times on a Thursday with four sessions in it.
Four things to count this week
The sorting above is a habit rather than a policy. Habits start from a number you actually looked at.
Messages per booked session. Take the last five sessions you placed by email and count the messages. Anything past two is waste, and it’s the most solved problem on this list.
Hours to first reply, counted twice. Your last twenty client threads, split into logistics and coaching. You want the first number small and the second number chosen. If they’re the same, your tooling is setting your tempo.
What went out that you didn’t decide to send. List everything your practice sent a client this week where the decision to send was made before that week. For each one, answer whose job it did. Anything that did the client’s job goes on the list to look at again.
Who moved a session. Your last ten reschedules, by name. If one name appears three times, your calendar has been absorbing something. Now you know it.
Which of these Point actually removes
Point sits on the Gmail or Microsoft 365 account you already have. You keep your address, your mail stays where it is, and your clients go on writing to the same place. Against the piles above, here’s what Point takes and what stays with you.
The dead wait is the pile Point clears. Your feed opens with what needs you today, weighed on how much a thing matters and how soon. A client’s question sits above a software invoice. Every thread carries a plain summary, so a full day of mail reads in a few minutes instead of an evening. When a message asks something of you, it becomes a task instead of a promise you were carrying. Threads still waiting on an answer come back before they go cold. What you handed off is tracked, with a reminder to chase it. Point runs the scheduling back-and-forth for you against calendars already reconciled. Clients take a slot from a page instead of writing to ask for one, and the volley goes.
Point’s reminders point inward. This is the fact that matters most for everything above. Point’s nudges come to you: chase this, this thread went quiet, this client has been silent since the session before last. Nothing goes out to a client on a schedule of its own, and a client has nothing to talk to. So the line about who does the remembering stays where you drew it, held there by you rather than moved by a feature.
Two things help you keep the record while you remove the friction. A thread stays in view after Point acts on it, so a booking handled is still a booking you can see, with whatever else the client wrote underneath. And a standing request to be told when a particular thing happens keeps watch for you. Tell me when this client asks to move a session again is the kind of thing Point holds. Whether three of those in a row means anything is yours to decide, and it should be.
Each type of action carries its own setting for how much Point does unaided. Three positions: Point suggests, or Point prepares the work and holds it, or Point goes ahead. A new account starts every type on the middle one. Mapped onto this guide, the rows worth raising are filing, times and chasing. The row for anything a client reads as a personal reply from you stays where it starts, past the point where holding it there still feels needed. The dial’s own page sets out what each position reaches. Each thing done for you is recorded, with the time and what it was acting on, and most entries can be undone from that record. That’s the activity log. Your standing instructions live as ordinary sentences you can read down and change, and that’s where the categories you want left alone go. A thread can also move to a channel locked end to end, which puts it out of Point’s reach entirely. The price is a thread with no summary, no place in the ranking and no draft.
Say the limit plainly, because it’s the whole second half of this guide. Point takes cost off the pile that was only cost. Adding friction back is yours: the question on your booking form, the message held overnight because you wrote it angry, the exit built to match the entrance. Everything in this guide about what to keep is a decision you make and then hold. The full inventory lists everything Point handles, and the coaching page walks the same list as a working week.
What this will not decide for you
Three honest limits.
The test sorts kinds of friction. The message in front of you stays your read, and the ones that matter arrive looking ordinary.
Friction preserved is one thing and effort produced is another. Leaving the composing in place gives a client the room to compose, and some of them use it. Take away the mood slider and the client who sends you two lines still sends two lines. Four paragraphs come from somewhere else. A silent between-session channel is a conversation to have rather than a setting to change.
And if everything in your week reads as friction, the problem may be volume rather than design. A practice with more clients than one person can hold in mind will feel like this whatever you buy, and software that remembers on your behalf treats the symptom cleanly. That question, and the part of it a compliance answer leaves open, is taken up in whether AI is okay for a coaching business.
Common questions
What counts as friction in a coaching practice?
Anything that costs effort, waiting or awkwardness while sitting outside the coaching itself. The messages it takes to book an hour. The days a question waits. The paragraph a client has to write. The small discomfort of asking to move a session. Admin is a category of work. Friction is a cost, and it sits on both halves of your practice, the arrangement half and the coaching half. The mistakes that matter happen in the second one.
Should I automate my between-session check-ins?
Separate the two things called a check-in. A reminder that Thursday is at 8:30 is about your calendar, and it’s yours to send. A prompt about the client’s goal or commitment is a method of accountability, and the competency model has those designed with the client and owned by them. The ICF’s own AI framework classifies goal-related email prompts as coaching delivered by software rather than as an assisting tool. That puts them in a different category of decision. If a client asks you for the nudge, they’ve chosen the method and it’s theirs. If it exists because your software offered it, it’s yours.
Is it bad to reply to a client too quickly?
On logistics, reply instantly. Fast is the honest answer there, and a client taking a 9:40 slot wants to know right away that they have it. On anything where your reply is coaching, speed is an intervention. The gap between a client writing and you answering is time they spend thinking, and a four-minute reply can close a question they were close to answering themselves. So the rule is about deciding. Speed becomes a choice you make per kind of message, rather than a property of your tooling.
Should I let clients reschedule themselves with a link?
Yes, and keep the record. Self-service rescheduling is better for the client and better for you, and it clears one of the largest piles in a coaching mailbox. The one thing it can quietly take with it is the pattern. A client who moves the session three times in a row is communicating something, and a calendar update on its own carries that message nowhere. Remove the friction, keep the fact, and read the names every couple of months.
My client asked me to send reminders about their commitments. Does that break the rule?
No, and the reason is the whole distinction. The competency model asks you to support client autonomy in the design of methods of accountability. A client who asks for a reminder has designed one. The guidance is aimed at the reminder that appears because a tool has the feature, and moves the remembering from the client to your software while you both look elsewhere. Agreed in the room, it’s a method. Switched on by default, it’s a substitution.
Will adding a question to my booking form cost me inquiries?
It will change what arrives, and probably how much. That’s the trade, so make it knowingly. A single question about what somebody wants to use the session for gives you a first conversation that starts further along, and it’s a cheap way to begin the partnering that sub-competency 3.06 describes. If you’re early in a practice and the volume matters more, take the volume. Just make that call yourself, rather than inheriting it from a tool that dropped the question by default.
Where does automation help a coaching practice most?
On the pile that goes uncounted: dead time. The message that sat four days under an invoice. The agreement that waited to be chased. The question asked on Sunday and seen on Wednesday. That waiting costs the client real momentum, and it costs you the reply you’d have given. Everything worth keeping was chosen, and this was simply allowed. After it come the scheduling volley and the search for things. All three sit outside the relationship, and clearing them buys the time for the parts that are the relationship.
The short version
Admin is a kind of work and friction is a cost. The instinct to remove all of it comes from trades where the customer’s effort is beside the point. In coaching, some of that effort is the product. The test is whose effort it is and what it’s aimed at. Effort aimed at your logistics is waste every time. Effort aimed at the thing the client came to you about is frequently the work itself.
Four kinds are doing work. The composing, because a client writing to you is often where the thought gets made. The remembering, because accountability is defined as a responsibility somebody holds, and an automated nudge moves it to your software. The awkwardness of asking to move a session, because it’s a signal a one-click calendar can absorb before anyone reads it. And the pause, because the gap before you answer is time the client spends thinking.
Three kinds are only cost, and they should go. The scheduling volley. The search for things. And above all the dead wait, the largest pile and the one that goes uncounted, where a coach who refuses tooling on principle does the most damage. Then watch where the friction lands when you take it out. It moves rather than disappears, and its favorite destination is the way out of the engagement. Whatever you automate on the way in, build the mirror on the way out.
A year from now, your practice will be smoother. The test is whether the client who needed to write four difficult paragraphs still had a reason to write them, and whether the one who moved Thursday three times in a row got asked about it.