FAQ
Clear answers before a pilot starts.
These questions cover the buying, rollout and adoption points teams usually need before they commit to testing Linker.
Rollout
How fast can we launch a useful pilot?
A focused pilot can start in two weeks when the scope is limited to one workspace, one user group and one operational module.
Do we need to replace every existing tool?
No. Linker works best when it first centralizes the information and workflows that are currently hardest to find or govern.
Can we start with a single site?
Yes. A single-site rollout reduces risk and creates proof before expanding to other teams or locations.
Product
Which modules are available?
Documents, training, products, tasks, incidents, maintenance, announcements, messages and admin access control.
Does Linker support field teams?
Yes. The interface is mobile-first and includes offline-oriented patterns for documents and operational reference content.
Is training required?
Administrators need onboarding. Most end users should understand the main actions through clear labels and short paths.
Commercial
Is pricing fixed?
The public plans are indicative. Final terms depend on user count, modules, integration needs, security requirements and support level.
Can customers pay without contacting sales?
Yes. Start and Pro can use Stripe Payment Links for self-service checkout once the Stripe links are added to the local configuration. Scale can remain quote-led or receive its own Stripe link after terms are fixed.
Can we request a security review?
Yes. Security reviews are expected for larger or regulated organizations and can be included in the pilot process.