Why time. Why a season of voting beats a single conversation.
Indecisive together, hovering for weeks over a question neither of you can put down? Most apps and most dinner-table conversations try to settle a hard decision in a single sitting. Counsel.day is built on the opposite premise: a decision worth losing sleep over deserves a season of private voting, not a single conversation, and a season produces an answer a single moment cannot. This page is the argument for that premise, in full.
On the schooling decision James and Alex could not settle at the dinner table, the answer was obviously yes on Tuesday and obviously no on Thursday. The difference between Tuesday and Thursday was not new information · it was them. Tuesday was the evening after the open evening at the city school. Thursday was the evening after watching their son spend three hours sliding down a hill in the Canterbury countryside on the back of the dog. Both signals were real. Neither was the answer.
The argument below is the argument for not acting on either evening's answer in isolation. A decision worth losing sleep over deserves the whole arc · every Tuesday and every Thursday, for as long as the question needs · and the analysis on the final day reads the arc rather than picking the latest point.
Most hard decisions die at the dinner table on the first try.
When a couple brings a hard decision to a single sitting, whether to have a baby, whether to leave the city, whether to take the job, whether to leave the partnership, the conversation tends to fail in predictable ways. Whoever speaks first sets the anchor. Whoever speaks loudest moves the mood. Both partners, sensing the friction, drift toward each other to avoid argument. The result is a synthesis of two people performing reasonableness, not a synthesis of what either of them actually thinks.
The phenomenon has names in the literature. Psychologists call it the anchoring effect, the conformity drift, the dominant-speaker bias. Couples therapists describe it under the broader heading of pseudo-agreement: both partners report a decision they did not actually make, because the alternative was an argument neither of them had the energy for. The dinner table is the wrong environment for this work, because the dinner table is built for togetherness, and togetherness is exactly what these decisions cannot afford on the first pass.
If you have ever caught yourself agreeing with your partner about something you did not actually agree with, only to find the question returning the next month, tired and worse, you have lived this. The decision gets made on a single misleading data point, or it gets postponed, and the question circles back. Indecisive about marriage, indecisive about moving, indecisive about a child: the indecision is rarely a shortage of information. It is almost always the absence of a way to capture two people's honest positions at the same time, without either of them anchoring the other.
The mood you woke up in is not the mood you'll go to bed in.
Even if the dinner-table conversation did not anchor either of you, a single sitting captures a single mood. The Saturday morning you went to the open home and felt elated is not the same Saturday afternoon you came home and felt overwhelmed by the price. The Tuesday after a hard day at work is not the Sunday afternoon you spent in the garden with the dog and felt that you could happily live where you live for another twenty years. Your conviction, on any given day, is mood-congruent. If you decide on the Tuesday, you will say no. If you decide on the Sunday, you will say yes. Neither answer is a lie. Both are real. Both are partial.
There is a reason couples therapists meet with their clients across multiple sessions rather than asking the big questions in one sitting. There is a reason cognitive scientists distinguish between hot and cold cognition, between System 1 and System 2 reasoning, between the experiencing self and the remembering self. A single sitting captures one slice of one of those systems, in one mood, on one day. It does not capture the question; it captures the questioner, in the wrong instant.
This is the failure mode that lives underneath analysis paralysis and decision paralysis. The paralysis is not that you cannot decide. It is that you keep deciding differently, on different days, because your mood keeps changing, and you have no way to see the pattern underneath. The overthinking is not the bug. The bug is that you are doing all of the overthinking in one head, in one sitting, with no record.
The product separates the voting from the conversation, so that neither of you anchors the other before you have each been honest with yourself.
What you can see across thirty days that you cannot see in thirty minutes.
When a couple votes privately on the same question, every evening, for the duration the decision actually deserves, three things become visible that no single conversation can show.
First, the trajectory of each partner's conviction across the period. Whether your position is firming toward yes, drifting toward no, or holding steady. A rising trajectory across thirty evenings is qualitatively different information from a single yes spoken over a meal. It tells you something about the durability of the position, and durability is most of what you actually want to know about a partner's view on a hard question.
Second, the themes that emerged from the notes each of you wrote. Not the themes you predicted you would write about at the start. The themes that actually surfaced, in the words you used after work on a Wednesday, in the half-sentence you tapped out before bed on a Saturday. These are the themes the daylight version of you would not have brought to the dinner table on day one.
Third, the axis of disagreement. The single most useful thing a Counsel.day verdict produces is the sentence that names what you were actually arguing about underneath the surface question. Most couples come to a decision believing they are arguing about whether to do the thing. After thirty days of private voting, the analysis often reveals that they were arguing about something else entirely: who would lose more, who would carry the cost, what each of them would have to give up. The surface question is the visible shape. The axis is the structure underneath, and the structure is what the decision actually depends on.
Match the duration to the question.
Counsel.day decisions run from a week to ninety days on Solo, and from a week to a full year (365 days) on the Couple and Family plans (per-decision or annual). The duration is the second decision the product asks of you, after the question itself. A fortnight suits a house with a Sunday offer deadline. A month suits most career decisions and most home decisions. Sixty days suits questions about the shape of the partnership itself: marriage, ending it, moving countries together. Ninety days suits decisions whose answer needs to survive a full season of moods: having a baby, having another child, going through IVF.
The longer durations are not for procrastinators. They are for the class of decision that cannot honestly be resolved in less time. You set the duration once, by the weight of the question. The product holds you to it. The full guide, with worked examples for each duration, lives on the method page.
A category of one. The neighbours do not do this.
Counsel.day sits in a category of one. The closest comparable products solve problems near to it without solving the same one. The comparison below names each neighbour, what it does well, and what it does not do that Counsel.day does.
The unique selling proposition, stated cleanly: Counsel.day is the only product that splits the private vote from the shared conversation, captures the vote daily across a duration you choose, and produces an analysis of the underlying disagreement when the period closes. Everything else in the category is doing a different job. The five-layer analysis in particular (agreement rate, conviction trajectory, theme extraction, synthesis, conversation prompt) is impossible to replicate without the underlying longitudinal data, and nothing else in the category captures that data.
The verdict, and the analysis that arrives with it.
On the last evening of the decision, at the same instant for both of you, the two verdicts publish on the same page. Underneath them, a five-layer analysis: the agreement rate across the period, the conviction trajectory for each of you, the themes that emerged from the notes you wrote, the synthesis paragraph that names what you were actually disagreeing about, and one specific question to open the conversation that follows. Not "communicate more openly." A real, concrete question shaped by what the two of you wrote across the thirty (or sixty, or ninety) days.
The conversation still has to happen. The product comes before the conversation, with the data underneath it laid out plainly. We do not tell you what to decide. We tell you what you were deciding about.
Four classes of question, each a season long.
Counsel.day was built around a specific class of decision: the kind a couple has been circling for weeks or months without resolution, where the stakes are high enough that a single conversation would be irresponsible, and where each partner's feelings shift across days and weeks in ways that need to be captured rather than averaged. Four classes of question come up most often.
These are the questions that should not be answered in a single sitting because they cannot honestly be answered in a single sitting. They deserve a season. Counsel.day gives them one, on terms that are private to the two of you and held to the duration you chose at the start.
Questions about the argument on this page.
How long should I run a decision for?
Match the duration to the weight of the question. A fortnight suits a house with an offer deadline. A month suits most career and home decisions. Sixty days suits partnership questions: marriage, ending it, moving countries. Ninety days suits the decisions that need to survive a season of moods, especially family and reproduction. The duration is set once, at the start, and we hold you to it. You may extend, you may not shorten.
Does spreading a decision across days just delay it?
No. A delayed decision is one that has no end date and no captured data. A Counsel.day decision has a fixed end date set on day one, and captures both partners' positions every evening between then and now. Delay means deciding nothing for weeks; duration means deciding everything across weeks. Most couples find they have actually settled the question by the time the verdict publishes, because they have spent the period thinking about it deliberately for the first time.
What if our feelings change too much during the period?
That is the point. The whole product is built on the observation that feelings about a hard question shift across days and weeks, and that the shape of the shift is the most informative thing about the decision. A trajectory that rises from Lean No to Strong Yes is a different decision from one that holds Strong Yes the whole period; both end with a Yes verdict, but they are not the same answer. The analysis on the final day reads the trajectory as a first-class signal, not a contradiction.
Is this a substitute for couples therapy?
No. Couples therapy is the guided conversation, with a trained third party present. Counsel.day is the data underneath one specific decision: the captured private positions across the period, the themes from your notes, the synthesis. We have no clinical training and the product is not a therapeutic intervention. Many users will benefit from both, in sequence; bring the verdict to a therapist when the verdict reveals the decision sits on something larger.
Can I see my partner's votes mid-decision?
No, and we will not let you. The privacy is the mechanism. The only thing visible to either partner before the verdict day is whether the other has voted that evening, never which way. The database is built so the sealed read path is the only path, with no admin override and no support escape hatch. If either of you could see the other's drift mid-period, you would anchor, and the data underneath the verdict would not be honest. See the privacy section on the method page for the architectural detail.