Nod asks your client one question at a time, in their words, with the cost of each answer written down. They answer in about twenty seconds. Your agent gets the answer back and carries on.
Twenty seconds, between meetings. That is the whole thing your client has to do.
One question, two to four answers, each with its cost written down. Your agent raises the call. Your client answers it. Nobody writes a status update.
The call on the right is the real thing, not a picture of one. This is what your client sees. Answer it.
Whatever you pick goes on the booking page in plain English, so it has to be one you will defend.
That took eight seconds. The agent had been sat waiting on it since Tuesday.
You have built it twice because nobody would answer. The model is not what slows you down, it is the fifteen small decisions a week that only the client can make, and every one of them arrives when they are with a customer.
So you guess and rebuild it next week, or you write them a paragraph on WhatsApp that they read on Thursday. Either way the branch sits there, and you are the one who looks slow.
Four projects running, four owners who answer when they feel like it. Put each of them on their own board and stop being the middleman.
You are the developer, the project manager and the person doing the chasing. Nod takes the third job off you.
Your decision-maker is down the corridor rather than on a client call, and no easier to pin down. Same problem, same twenty seconds.
No portal to log into, no board to keep tidy, no password to lose. The desktop view adds the queue for the weeks when there are five calls waiting, and answers from the keyboard.
One call. No list, no tabs, no scrolling to reach the answers.
Press 1 to 3 to pick, Enter to nod. The mouse is optional.
They should not have to open anything, so a call arrives where your client already is. Nothing to install, no account to set up.
Answered from the lock screen, without unlocking into an app.
Or a reply to a text, the same as they answer everyone else.
Clients who ignore your emails answer this. Not because of the screen, because of what the screen refuses to do. A call that breaks these rules is rejected before it ever reaches them.
Every call is kept: the question, what they chose, what it was going to cost, who settled it and when. So when somebody says they never agreed to that, you send them the line with their own name and the date on it.
Hand the whole history to your agent in one tap and nothing gets re-litigated six months later.
The receipt. Dated, attributed, in the client's own words.
Nod is an MCP server at nod.stumason.dev/mcp. Point any agent at it with a project token and it gets three tools: ask, get_call and list_calls. The twelve-word limit and the cost-per-option rule are enforced at the door, so a badly framed question never reaches your client.
Which client it belongs to, which repo, which issue: all of that stays on your side of the wall. Your client sees a question and three answers.
Every one of these has been asked for, and each would turn a decision back into a task, which is the thing your client already refused to do.
Nod is invitation-only while it is young. Tell me what you are building and who has to answer for it, and I will send you a link.
Already been sent one? It signs you straight in. There is no password to remember.