SalesFision Platform application
Written down once, found by whoever needs it.
Manuals, procedures, KPI definitions and house rules in one place — sorted into categories, tagged, and opened from the application where the question came up. An article goes live after a second person approves it, and every published version is kept.
Choose your applications Do the Business Scan
- A second reader approves by default; an exception is recorded on the version
- A change never disturbs the article your team is reading
- Every published version is kept, with its author and its reviewer
The answer exists. Just not where you are looking.
It lives in a chat thread, in someone’s head, or in a document three people have their own copy of. So the same question gets answered again, slightly differently each time.
- The same question is answered three times in a week, by three people.
- The manual is a document nobody dares to change, because nobody knows who owns it.
- Two versions of the same procedure are in circulation and both look official.
- A new colleague’s first week is one long list of questions.
What changes when knowledge has one address.
-
One place, sorted the way you think
Onboarding, the system manual, procedures, KPI definitions, the tools you use, policy — seven categories, with your own tags underneath.
-
Found from where you are working
The search bar you already use in every application searches the knowledge base too, and a link can sit next to the number or the step that raised the question.
-
A change never breaks what is live
Edit a published article and your edit waits beside it as a revision. What your team reads stays exactly what it was until someone approves the change.
-
You decide who reads and who writes
Rights do not follow job titles. Read, write, review and manage are handed out per person; colleagues inside your organisation read published articles, and anyone outside reads only what you deliberately grant. Knowledge costs nothing extra.
What your team can do with Knowledge.
Write it down
- Write an article with a title, a short summary and its own web address
- Write in Markdown, or bring a finished HTML page in and have it shown without scripts
- Put it in one of seven categories, and add your own tags underneath
- See who wrote it, who last changed it and when
Find it back
- Search on title and summary, and filter by category or by tag
- Search from the bar you use in every application and land on the article itself
- Read an article in Dutch or in English, with a visible note where a translation is still missing
- Look up which tools your organisation uses, with vendor, department, owner and licence
Publish with care
- Take an article from draft to review to published, and archive it when it is done
- Keep the published version live while a change is being reviewed
- Send a piece back with a reason, so the author knows what to fix
- Keep every published version, numbered, with its author and its reviewer
Decide who may what
- Hand out four rights that combine: read, write, review and manage the knowledge base
- Let internal colleagues read published articles without arranging anything
- Give someone outside your organisation access only when you deliberately grant it
- Keep rights separate from job titles — being a manager elsewhere grants nothing here
How a piece of knowledge gets written down.
The same path for every article, so what your team reads is something somebody checked.
-
Someone writes it down
A draft: a title, a summary, the text itself, a category and a few tags. Nobody else reads it yet.
-
It goes up for review
The author submits it. If the article is already published, the change waits beside the live text as a revision — the version your team reads does not move.
-
A second pair of eyes
A reviewer approves it or sends it back with a reason. Approving your own work is refused, unless the workspace has been set to allow it — a small team that would otherwise stall.
-
It goes live
The new version is published and numbered, with its author, its reviewer, the date, and whether the author approved it themselves. The version before it stays.
-
Someone needs it
They search from wherever they are working, or follow the link beside the number or the procedure that raised the question.
What your team looks at.
One workspace at work: a colleague looking something up, the versions behind that article, and who may do what.
Looking something up
Opened from the team report in Project Management
-
What our KPIs mean
-
Filling in your week
-
What we invoice, and what we do not
-
Your first week here
What our KPIs mean
Billable hours are the hours written to a customer project that end up on an invoice line. Internal work, travel and hours on a non-billable project are not counted.
The figure in the team report uses this definition. When a number looks wrong, it is almost always an hour booked to the wrong project rather than the sum itself.
A revision of this article is in review. Until somebody approves it, this is the text everyone reads.
One article, its versions
| Version | Published | Author | Reviewed by | Second pair of eyes |
|---|---|---|---|---|
| v4 | 12 May | Ilse | Sanne | Yes |
| v3 | 3 March | Ilse | Ravi | Yes |
| v2 | 14 January | Ravi | Ravi | Author approved · recorded |
| v1 | 2 November | Ravi | — | Taken over on migration |
Rights and access
| Colleague | Reads | Writes | Reviews | Licence |
|---|---|---|---|---|
| Ilse, internal | Published articles | Author | Reviewer | Included |
| Sanne, internal | Published articles | Author | Reviewer | Included |
| Ravi, internal | Published articles | Author | — | Included |
| Femke Bloem, outside your organisation | Only what you grant | — | — | Included |
Example data. Your own articles, categories and colleagues appear here as soon as the Platform is set up.
The instruction belongs where the work happens.
These are examples. Knowledge can be opened from every Platform application your team works in — from the sidebar, from the search bar, and from a link beside the number or the step that raised the question.
-
Knowledge and Project Management
How you run a sprint and what each figure in the team report means. The report links straight to the article, so the explanation sits one click from the number.
-
Knowledge and Service Management
How a request is handled, what you promise about a first response, and what you send back. Read while the request is still open, not afterwards.
-
Knowledge and HR
Your leave rules, your working week and what happens when someone calls in sick: written once, read on the morning it matters.
-
Knowledge and Vault
How you name an account, what belongs in a note and what never does. The Vault holds the account; the rule behind it lives here.
-
Knowledge and Sales
The path from first conversation to signature, written down the way your team actually walks it — including what you promise and what you do not.
-
Knowledge to Customer Portal
Where an article should also be readable by the customer, it belongs in the Portal. Want to make articles available to your customers too? That is what Customer Portal does — a product of its own with a fixed monthly price.
What Knowledge costs
SalesFision Knowledge is included free with selected paid apps and bundles. Knowledge is part of the Platform.
Knowledge costs nothing extra and never counts towards what you pay for the paid applications.
Access is arranged separately from licensing: any Platform user can be given it, rights decide who may read, write, review or manage, and anyone outside your organisation reads only what you deliberately grant.
Pick the applications your team needs; Knowledge comes with them.
What the licence covers, and what we agree with you separately:
Included
- The application, with the included users or capacity
- SalesFision Knowledge is included free with selected paid apps and bundles.
- Standard onboarding
- Regular support, maintenance and bug fixes
Separate proposal
- Additional consulting and training
- Complex integrations and custom work
- Migration of existing data
- Customer Portal (a product of its own)
Calculate your package See all pricing
Additional consulting, training, complex integrations and custom work are agreed with you up front, so you always know what you are buying.
What people ask before they start.
Who can change an article?
Whoever you give the author right to. A change to a published article goes up for review first, and while it waits your team keeps reading the approved text. By default nobody approves their own work.
Can something be published without a second reader?
Only if you ask for it. A second reviewer is the default and self-approval is refused, even for an author who also reviews. A workspace can be set to allow it — useful for a small team that would otherwise stall — and then it is visible: the published version records that the author approved it themselves, and so does the audit log.
Is Knowledge a paid application?
No. Knowledge costs nothing extra and does not count towards what you pay for the Platform, which is why this page has no calculator of its own. Access is a separate question: any Platform user can be given it, and rights decide who may read, write, review or manage.
Can our customers read it?
Only as a member from outside your organisation that you deliberately grant access to; they then read the same internal knowledge base. Want to make articles available to your customers too? That is what Customer Portal does — a product of its own with a fixed monthly price.
What happens to the old version?
It is kept. Every publication writes a numbered version with its author, its reviewer, the date and whether the author approved it themselves — so you can always see what the rule was in March.
Does it work in Dutch and English?
Yes. An article can carry both, and where a translation is still missing you get the Dutch text with a visible note saying so, instead of two languages quietly mixed in one page.
Put what your team knows in one place
Bring your manuals, procedures and KPI definitions across, agree the categories, and decide who writes, who reviews and who may read what.
Choose your applications Do the Business Scan
Questions about bringing an existing manual across, or about how your categories should be set up? Plan a meeting and we will size it.
