the engine we sell as white label
Our product is IT outstaffing: an aggregator that finds the specialist itself and matches their public profile against a project across 20+ requirements. Inside the product runs the engine — and that is what we sell separately.
Came here from a tender meeting — you are on the right page: there is no need to work through the public site for specialists.
the home page stays with the specialist — here we are talking to the buyer of the engine
We keep two subjects apart
The first subject is our own product: IT outstaffing, the public site and the platform that specialists use. The second is the engine inside that product: white label, which the client installs on their own side. These are different conversations, and we do not mix them.
subject 01 · our own product
IT outstaffing
- for whom
- for the specialist — they receive an invitation and decide
- what it does
- matches a public profile against a project across 20+ requirements
- where it lives
- on the public site home page — and in the platform: the vacancy catalogue and the account area
subject 02 · the engine
white label
- for whom
- for the client — a company that installs the engine on its own side
- what we sell
- the same matching mechanism — under the client’s brand
- where it lives
- in the client’s environment — deployment in your own environment
the engine subject is not surfaced on the home page — white label is discussed on this page only
Where the engine runs
Two deployments — switch between them to see what changes. Our environment on the left, yours on the right.
the iconicompany environment
- runs here
The engine
- here
The data from our matches
- here
The public site, the vacancy catalogue and the account area
your environment
- not installed
The engine
- is not stored
The matching data
- iconicompany
The brand on the screens
deployment: our environment — the engine powers the iconicompany product
the mechanics of “deployment in your own environment” and the list of “data sovereignty” guarantees are not disclosed by the source — the diagram shows only the deployment model, with no timelines, stages or infrastructure requirements
The conversation is about three things
Exactly three — and not one beyond what is on record. Where the source is silent, we mark it rather than fill it in.
- item 01
The engine
The mechanism that matches a specialist’s public profile against a project across 20+ requirements and shows exactly what matched. Inside our product it runs every day — and that is what we sell.
the breakdown for the specialist — “why we contacted you specifically” — is produced by the same engine
how matching against 20+ requirements works
the engine’s feature set is not listed by the source — there is deliberately no list of modules or capabilities here
- item 02
Deployment in your own environment
The engine is installed in the client’s environment and runs there — under the client’s brand, that is, white label.
what changes with it is visible on the deployment diagram above
to the “where the engine runs” diagram
the mechanics of deployment are not disclosed by the source — we claim no timelines, stages or environment requirements
- item 03
Data sovereignty
The data the engine works with in your environment stays in your environment. On our side our own product goes on living — with its own data.
two environments — two independent records; the diagram assumes no shared storage
how specialists' personal data is processed
the list of data-sovereignty guarantees is not given by the source — we name no obligations, standards or certifications here
An industry environment is an instance, not a second product
With the engine we are taking part in a metallurgical plant’s tender. The metallurgical environment is an instance of the engine for a client, not a second product of ours and not a second audience for this page.
one engine
the same matching across 20+ requirements
instance 01
our product — IT outstaffing
runninginstance 02
the client’s metallurgical environment
stage: tender- subject
- the engine — white label
- environment
- metallurgical — an instance for the client
- stage
- taking part in a metallurgical plant’s tender
- client
- not named the name of the plant is not set by the source
- terms and timelines
- not claimed the source sets neither terms nor timelines for the tender
- audience
- the buyer of the engine. For the specialist — the public site home page
two doors
where to go next
for the client
Discuss deployment in your own environment
The engine, your brand, your environment. The conversation starts from exactly what is on record on this page — with no promises we never made.
for the specialist
You want the home page
This page is about the engine and about clients. The home page stays with the specialist: it covers how a project finds you, and the short “find me a project” form.
The public site for specialistshow to start a conversation
Discuss deployment
The subject of the conversation is already on record on this page: the engine, deployment in your own environment, data sovereignty. Below — where to write.
- a placeholder to be filled in the address is not set by the source
- phone
- a placeholder to be filled in the number is not set by the source
- who answers
- a placeholder to be filled in the manager’s name and role are not set by the source
- form
- a placeholder to be filled in the source sets neither the form fields nor a response time — so we do not invent them
- what is known
- the way into the conversation that the source names is tender meetings
the prototype sends nothing: the blank lines are placeholders for real values, not a missing contact