The Consultant’s First 90 Days, Delivered as Software

Every serious consulting engagement starts the same way. Before anyone proposes a fix, builds a roadmap, or stands up a transformation office, a team of consultants spends the first weeks doing something deceptively simple. They talk to people. They interview the function leader, then the leader's team, then the people upstream and downstream who feel the function's failures most acutely. They cut the findings by seniority and by tenure. They separate what leadership believes is broken from what the front line knows is broken. Then they hand back a prioritized map of the real issues and a plan to address them.

That diagnostic is the most valuable thing the firm produces, and most leaders never get to buy it on its own. It comes bundled inside a six-figure statement of work, it takes two to three months, and by the time you see the output the meter has been running long enough that someone needs the answer to justify the spend.

We built Verings to deliver that diagnostic as software. Not a survey tool dressed up with nicer charts. The actual diagnostic: an AI designs the assessment around your function, interviews your organization, and returns a confidential, segmented view of the issues plus a drafted intervention plan.

What the diagnostic has to do

A good opening diagnostic does three things at once, and they pull against each other.

It has to go deep. A checkbox survey tells you that 62 percent of people rated cross team collaboration "below expectations." It does not tell you why, where it breaks, or what to do about it. Depth comes from conversation, from following up on a vague answer until it becomes a specific one.

It has to be honest. People do not tell you the truth when their name is attached, especially about their boss, their boss's boss, or a project leadership is visibly attached to. Honesty comes from anonymity that people actually trust.

And it has to scale. Talking to twelve people gives you twelve anecdotes. Talking to four hundred gives you a pattern. The catch is that depth, honesty, and scale rarely come together. The consulting firm gets there by throwing bodies and weeks at the problem. That is exactly the part software can change.

How Verings runs it

You start by describing your function in plain language. Your objectives, your strategy, and your own honest view of where the problems are. That last part matters more than it sounds, and we will come back to it.

From there an AI designs the assessment. It pulls from a diagnostic framework built for your function, weights the dimensions that match your situation, and builds out the specific issues worth probing. You shape the scope. You can add a concern the model missed, drop one that does not apply, and adjust where the emphasis sits. You even sit through a sample interview yourself, as a respondent would, and tell the system what to sharpen before anyone else sees it.

Then you upload your roster. Your team, internal customers, suppliers, the board, whatever mix fits the question you are trying to answer. Everyone gets a private link and a conversational interview that adapts to their role. A finance analyst and a board member do not get the same questions, because they cannot speak credibly to the same things. Everyone answers a shared core so the results stay comparable, and the conversation branches from there.

What comes back is a readout. Not a spreadsheet of averages, but a prioritized set of issues organized under a handful of governing themes, each one backed by the evidence that surfaced it. Where senior and junior people disagree, you see it. Where long tenured staff and recent joiners experience two different organizations, you see that too. Then a second document drafts the intervention: the key decisions in front of you, the quick wins worth taking now, the structural moves that need sequencing, and the order to do them in.

The honesty mechanism

Anonymity is not a setting we toggle on. It is the thing that makes the input worth reading.

You never see an individual response. You see segments, cuts of the data by role, by sub function, by tenure. Any cut too small to keep a person anonymous gets suppressed or merged into a larger group before it reaches you. If three people sit in a segment, you do not get to read "what those three said." That floor is not a limitation we apologize for. It is the reason people answer honestly in the first place, and honest answers are the entire point.

The most useful page

Remember the part where you wrote down your own view of the problems. The system holds onto it, then compares it against what the organization actually reports. Sometimes the evidence confirms what you suspected, and now you have the mandate to act on it. Sometimes it surprises you. And every so often it shows you an issue you never thought to look for, sitting in plain sight in a part of the organization you do not hear from often.

That comparison is usually the most uncomfortable page in the readout. It is also the one most likely to change what you do on Monday.

Who this is for

If you have just taken over a function and need to understand it before your first board update. If you are integrating a team after an acquisition and the friction is hiding somewhere you cannot see. If you have inherited a persistent problem that everyone describes differently. The opening diagnostic used to be a privilege of organizations that could afford the firm. Now any manager can run one.

The first ninety days of an engagement were always where the value was. We just made them something you can start this week.