Your team already knows. Nobody asked them.
A StackUp Discovery Agent calls or messages up to fifteen people on a schedule you set and asks the questions you never have time to ask. You get a summary, three ranked actions, and every transcript underneath.
What your team tells an agent is not what they put in a survey. Free to run your first agent.
Real screen · sample round
The problem
The people who know are not the people in the meeting.
The person using the unapproved tool, the one who knows the integration is held together by one colleague, the one with the idea — they are two or three layers down, and the mechanisms for hearing from them are a survey nobody fills in and a skip-level you keep postponing.
Surveys get the polite answer
A form with your name on it, going to your manager, is not where anyone admits they have been pasting customer data into something they found.
Interviews do not scale
Fifteen half-hour conversations is a working week you do not have, and by the time you finish the first ten the picture has already moved.
So you find out late
Usually when something breaks, someone resigns, or a tool nobody approved turns up in a security review with two years of history behind it.
How it runs
You set it up once. It does the asking.
Point an agent at up to fifteen people
Name, role and contact details. Pick what you want asked — a tech health check, a specific project, shadow IT, or ideas — and how often it should run.
Each person takes it their own way
The agent reaches out, and the recipient chooses a voice call or a chat. It is a conversation, not a form: it follows what they say and asks the obvious next question.
You read the findings, not the transcripts
A summary across everyone who took part, three priority actions ranked by urgency, and every session recorded underneath if you want to check the wording yourself.
What to ask
Four things worth asking the whole team.
Tech health check-in
What is actually slowing people down, what keeps breaking, and which workaround has quietly become the process.
Project check-in
How a specific delivery is really going, asked of the people doing it rather than the person who writes the status report.
Shadow IT and AI discovery
Which tools your team has adopted without telling anyone, and what they are putting into them. This is the one that produces the surprises.
Idea generation
The improvement everyone mentions in the corridor and nobody ever writes down, collected from the whole team at once.
What you get
Three actions, ranked, with the calls behind them.
This is the actual screen, filled with a sample round rather than a customer's.
Findings, not a pile of transcripts
Fifteen conversations is a lot of listening. The results page does the reading: a summary of what came up across everybody, then the three things most worth doing something about, ranked by urgency rather than by who said them loudest.
- A summary across everyone who took part
- Three priority actions, ranked by urgency
- Every session recorded, so you can check the source
- Re-run it later and watch what changed
Why it works
People tell it things they would not put in writing.
Not because it is clever. Because of who is not on the other end.
No colleague forming a view
Nobody is deciding what your answer says about you. That removes most of the reason people soften what they tell their own organisation.
It asks the next question
A form takes what you type and stops. A conversation notices that you said 'we worked around it' and asks how, which is where the useful part usually is.
Everyone gets asked the same thing
Fifteen people, one question set, one week. When four of them independently name the same colleague or the same tool, that is a finding rather than an anecdote.
Who it is for
Anyone who needs to hear past the first layer.
CTOs and IT leaders
The shadow-IT picture you cannot get from a survey, and a standing check-in that does not consume your calendar or theirs.
Executives and CEOs
An unfiltered read from further down the organisation than you normally hear, gathered without anybody having to volunteer to be the bearer of bad news.
Fractional CTOs and advisers
Discovery across a client's team in days rather than a fortnight of interviews, with the transcripts to back up what you tell them.
What it costs
Run your first agent for nothing
Create an account, add your people, choose what you want asked, and send it. You get the summary, the ranked actions and every session record.
- No card, no sales call, no trial clock
- Voice or chat, whichever each person prefers
- Schedule it, or run it once and see
- Paid plans add more agents and the rest of the platform
Running discovery for a client? Advisers with portfolio access can point an agent at a client's team and share the findings with them.
Questions
The things people ask first
Ask fifteen people what you are not being told.
Point one agent at one team this week. The shadow-IT answer usually arrives in the first two minutes of the first call.