Procurement is not opening 14 rate-card tabs. They drop a brief into Claude or Copilot: “two senior Java, remote, Poland, from October, budget X”. An agent that only has your HTML guesses. An agent that has an MCP calls a tool, gets a role dictionary, a lead time, and files a structured request.
This is not a 2028 slide. The official MCP registry already lists tens of thousands of servers. Lemon.io ships “hire developers from chat”. ATS vendors (Greenhouse, Ashby, Workable) have native MCP. The channel exists. The question is whether Polish nearshore is in it, or the agent ends on a US marketplace.
What this channel is not
It is not a shop with people on a shelf. Commoditech does not keep a named bench ready for tomorrow morning — and we will not fake that in JSON. The MCP collects a qualified brief (T&M or permanent hire). We source on demand. First CVs are not a start date. Start follows your interviews and a contract. If a vendor returns “3 senior Python, available Monday”, they are selling you CVs or lying.
1. Where the buyer actually sits
The website contact form catches marketing and sometimes HR. The T&M buyer often sits in an IDE. An engineering manager in Cursor plans the quarter, the agent sees a hole for QA or Fiori, and asks “who in Poland can staff this”. If you are not in the agent’s tools, you are not on the shortlist — regardless of your Google rank for “java staff augmentation Poland”.
The second buyer is procurement with an RFP. Banks and pharma, where we have worked for years, are starting to hand documents to agents for shortlisting. The agent will not read a 40-page proposal. It calls: compliance, rates, lead time, sector references. If you do not expose those as tools, you drop out on “no data”, not on price.
2. What we expose
Public server commoditech-staffing. Agents can:
- paste a JD and get a role match (Java ≠ JavaScript, Python CRUD ≠ RAG),
- get a range for time-to-first-CVs and time-to-start — separately for T&M and perm,
- get T&M bands or the success-fee policy (15–25%, no hire no fee),
- submit a brief to a company email; a human replies in 24 business hours.
Candidate data does not leave. The request does not write straight into CRM. Full CVs still go by email, after consent, as they have since 2012. How to connect: MCP for AI agents.
Hourly bands are the T&M card, not tomorrow’s invoice. The market map (what others post on NFJ and Hays) is separate: IT body leasing rates in Poland 2026.
3. T&M and success fee in one channel
Historically ~98% of our opportunities are time & materials. Permanent recruitment is coming back, because firms freeze junior headcount and open it for SAP, architecture, GRC. An agent that gets “hire a senior Fiori on payroll” must not receive an hourly card. It gets a success-fee model and a longer lead time (notice periods).
Same sourcing engine: contractor network + direct search. Different contract, different SLA, different cash. The MCP distinguishes time_and_materials from recruitment. If the brief is ambiguous, a human asks — the JSON does not guess.
The demand split (frontend drowning in CVs, SAP sitting empty) does not vanish because an agent filed a request. It stays. What changes is the brief: role, seniority, start, model, company email. Better than a “write a message” form.
4. What is sales, what is marketing
Volume will be small for the first months. Tire-kickers, competitors, one real brief. That is fine. The server is cheap to run. The value is triple:
- Funnel — a qualified request with no salesperson at the door. MVP success: one such request that became a call.
- Demand signal — even without a submit. If 40 agents a week call
get_rate_card(role=sap_consultant), you source SAP before the RFP arrives. - AI-service demo — “we will build you an MCP that your customers’ agents query”. That is T&M or fixed-price on engineers we already want to sell. A live server beats a slide.
We do not meter calls. An API key on day one would kill discovery. A paid market report — only after the audit log shows volume, not before.
5. How not to break it
- Do not ship a demo bench to production. Trust in the agent channel dies on the first invented headcount.
- Do not auto-quote a contract. Ranges and “this is not a quote” in every payload.
- Do not mix the internal CRM facade with the public one. Contact search on the internet is an incident, not a feature.
- Do not assume agents will find you. 100k servers in the indexes. You need a listing, llms.txt, this page, and CTAs on the body-leasing landings.
Connect and ask — or have us build yours
Staffing: drop a JD into an agent with our MCP, or write to us. An equivalent server for your vendor catalogue, knowledge base or buying process: same team, T&M or fixed-price. We are not selling a slide about agents. We are selling a server that already answers.