You sense something needs doing, but you don't know what exactly. That's the best moment to come see us, not the worst.
Many of our first meetings start with "I don't know yet." No spec, no formed request, just a feeling: a role that's stuck, a number you can't get out, a sense something should be better. At many agencies, this sentence closes the door. For us, it's the real signal we can help.
Why "I don't know" is a better entry than a spec
A spec arrives after someone has translated a fog into specifications. That translation is itself a filter: it removes what the person couldn't formulate, and keeps what they found words for. When you arrive with "I don't know yet", that translation hasn't happened: we have access to the fog, which often holds more information than the filtered version. Three projects out of ten would have been very different if we'd listened to the fog before signing the spec.
What we do when you arrive with fog
We don't ask you to clarify before the meeting. We come with a notebook, we listen for half an hour, we observe for a morning. By the end, either we can name a precise need, and you have a brief we would have had you write but you'd have taken three meetings to produce. Or we name nothing, and we tell you so: there may be nothing to build, and you've saved a project. Either way, you leave with something: a path, or confirmation there isn't one.
Three questions we ask when you don't know
"What made you take this meeting today rather than last year?" You say what shifted: often the real entry to the need. "If someone took away a daily tool tomorrow, which would you miss most?" You say what's essential: we avoid proposing a replacement where you're attached. "What does your team tell you isn't working, that you haven't had time to look at?" You say where the real signal is: we avoid handling a need only you see.
What we've seen on the ground
A manager came to us saying "I don't know, something's off with my scheduling but I can't put my finger on it." Two hours of observation later, we identified the problem: his scheduling software didn't surface planned absences beyond three months out, so he always hired in emergency mode. The real subject wasn't the schedule, it was visibility. We solved it by adding a four-month rolling view.
FAQ
Do I pay even if we build nothing? First meeting is free. If we observe on-site and name that there's nothing to do, we bill the observation (half-day package). The price of avoiding a useless project.
How long from "I don't know" to a real brief? Half a day to two weeks, depending on complexity. No more. If we can't manage in two weeks, there's probably nothing concrete to build right now.
You sense something's there but you don't know what. That's why we exist. Tell us what you sense. Let's talk →