Tell us the problem.Someone knowshow to solve it.
Some problems require more than search. They require context, judgment, and someone who already knows how.
A private network of people worth knowing.
Someone Knows exists for the problems that do not fit neatly into a job post, a Google search, a software category or a standard vendor brief.
You bring the problem. We find whoever already knows how to move it forward — the context, judgment or lived experience it takes.
Sometimes that person is an operator. Sometimes a builder. Sometimes a domain insider, supplier, advisor, fixer or small team.
The point is not to access more people. The point is to find whoever already knows how.
The kind of people behind the network.
The best people are often not the easiest to find. They are the ones someone calls when the problem is awkward, specific or hard to explain.
The Owner
The person with skin in the game. Not advice from the sidelines. Not theory from a deck. Someone who understands what a decision costs because they live with the consequences.
They know what looks good in theory, what breaks in practice, and what a decision really costs when money, time and reputation are on the line.
The Peer
Someone one step ahead. Same terrain. Similar constraints. A mistake already paid for. Sometimes the most valuable answer is not expert advice. It is a conversation with someone who just went through it.
Not a guru. Not a consultant. Not a framework. Just someone who has already made the decision you are about to make.
The Insider
Every market has a public version and a real version. The real version is made of incentives, habits, gatekeepers, local rules, buyer behavior and things nobody writes down.
How buyers behave. Who controls supply. Which shortcuts are dangerous. What everyone in the sector knows, but nobody puts on a website.
The Supplier
Search gives you options. A good supplier network gives you confidence: who delivers, who overpromises, who understands the context, and who is worth the first call.
A maker. A distributor. An implementation partner. A specialist provider. The problem is not always building. Sometimes it is knowing who is actually worth calling.
The Builder
Some projects fail before a line of code is written. The wrong scope. The wrong tool. The wrong assumption. The wrong person owning the problem. A good builder shapes the work before building it.
Not just code. Not just automation. Not just execution. Someone who can turn an unclear business problem into a working system.
The Operator
The real process is rarely the documented one. It lives in shortcuts, exceptions, handoffs, forgotten spreadsheets, WhatsApp threads, and the one person everyone quietly depends on.
The spreadsheet nobody owns. The approval that always waits. The handoff everyone pretends is fine. The process that only works because one person remembers everything.
What people come here with.
Most useful requests arrive messy. The first task is not to force the problem into a category — it is to understand who might know what to do next.
Manual drag
+A recurring job is still moving through spreadsheets, screenshots, calls, approvals, memory or handoffs.This is rarely just an automation problem.
The useful move is finding someone who can remove the drag without breaking how the team already works.
Domain gap
+The problem only makes sense inside a specific market, workflow or regulatory environment.Public advice gets shallow quickly here.
What matters is context: the constraints, habits, incentives and failure modes that only someone inside the sector would know.
Odd build
+The project is real, technical and valuable, but too strange for a standard agency or SaaS tool.It needs more than execution.
It needs someone who can shape the work, reduce ambiguity and own the path from unclear idea to working system.
Unknown market
+The right supplier, expert or maker probably exists, but is hard to find through public search.The problem is not lack of options.
The problem is knowing which world to look inside, who is credible there, and who is worth the first conversation.
No category
+You know the business pain, but not whether the answer is software, process, people, procurement or something else.This is where many projects go wrong.
Choosing the solution type too early usually creates expensive work in the wrong direction.
Small room
+The work does not need a large agency.It needs two or three sharp people with the right context, working close to the problem.
Small enough to stay precise. Experienced enough to matter.
Before action
+The next step is not building, hiring or buying.The next step is deciding what is worth doing.
Some problems need judgment before execution — because moving fast in the wrong direction is still waste.
Tell us what is stuck.
Describe the problem in your own words. It can be vague, specific, operational, technical, sensitive or hard to categorize. You do not need to know the exact role, tool or supplier you need.
We find whoever knows how.
We review the request manually and think through the context it needs — an operator, builder, specialist, domain insider, supplier, advisor or small team.
We introduce selectively.
If there is a real fit, we make the introduction with context. No public profiles. No random intros. No open marketplace.
Two paths into the same network.
One side arrives with a problem. The other is made of people others already call when something needs to get done. Between them: someone who already knows how.
Bring a problem.
For founders, operators, companies and teams facing problems that require judgment before execution.
You do not need to know the exact solution. You only need to describe what is stuck.
Join the network.
For builders, operators, specialists and domain experts who are already the person someone calls for a specific kind of judgment, context or execution.
If people come to you when something needs to be figured out, fixed, built or introduced, you may belong in the network.
Someone Knows is not a public directory, a freelancer marketplace or a social network.
People are not listed publicly. Requests are reviewed manually. Introductions are made only when the context fits.
The network is valuable because it is selective.
Bring a problem, or join the network.
Both paths begin with a conversation. We review everything manually. If there is a real path worth pursuing, we will follow it.