palmscout: work starts before the contract is signed.
A workshop note on the product vision. palmscout connects recruiting, HR, and staffing — and is judged at concrete handoffs between people, not by feature lists.
Read the German original
A product in progress — intentionally visible
palmscout is a product developed by neurofunken. The vision connects recruiting, HR administration, staffing, job search, and collaboration with employers. This note describes the direction of development. It is not an announcement of already available features or a release date — and that is intentional: we want to talk about questions early, before we sell promises.
The central product question is: how can people with different roles work together reliably when work and employment are at stake? A shared context should provide orientation. Each role still needs a fitting view of the information and the next steps — not the same surface for everyone.
Take different perspectives seriously
For people looking for work, it may be about placing a role and understanding the status of an application. Employers need to clarify requirements and ownership. Staffing and HR accompany handoffs, ask follow-up questions, and coordinate agreements. These example needs are the starting point for product design — not an abstract “HR suite”.
palmscout should bring these perspectives together without forcing everyone into the same interface or the same amount of information. Which details a task requires, and who may see them, are central design questions. The connection between roles matters as much as the individual views.
Handoffs are the real product core
A thought example: after a conversation, employer feedback is still missing. The person looking for work wants to know whether they need to act. The agency needs clarity on who follows up. On the employer side it must be clear which decision is open. The same process raises a different question for each side — and that is where software either helps or merely documents.
We want to align product decisions with situations like these. A status helps when people understand its meaning and can derive the next step. The sheer number of managed records says little about whether collaboration got easier.
Design access for different people
Someone sending a first application brings different experience than someone who has accompanied HR processes for years. Age alone does not explain those differences. Language, vision, technical experience, and the device in use also shape how people can use an application.
The W3C Web Accessibility Initiative recommends considering accessibility, usability, and inclusion together. For the palmscout vision that means understandable terms, clearly recognisable actions, and checkable interaction paths. Those goals need technical checks and feedback from different people. Design intent alone does not prove accessibility — tempting as that checkbox may be.
Test the idea against concrete tasks
Further development therefore depends on concrete questions: do people find the information they need? Do they notice when details are missing? Does a handoff stay traceable? A draft should be judged against tasks like these. Possible AI support must also prove its purpose; it is not an end in itself for the product vision. An early concept view can help uncover misunderstandings. What matters is treating feedback first as learning material and deriving justified changes from it.
We want to make palmscout’s direction understandable early and talk about real development steps once they are evidenced. Scope, access, and availability will be described separately when they are settled. Until then this workshop note offers a view of the questions the product should orient itself by.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Meet palmscout