Products we built while working with clients
Both came out of a need that kept recurring in implementation projects, not from a decision that we ought to have a product. Today they run in client production environments.
In production since 2022
SNOK MDM
Master Data Management for enterprise scale
We help organisations bring order to their master data, so that key systems operate on consistent information about customers, products, materials, employees and business partners. SNOK MDM supports data quality control, reduces discrepancies between systems and makes it easier to build reliable management reporting. As a result, data becomes a stable foundation for decisions, automation and the organisation's further growth.
Proven in day-to-day organisational use
SNOK.me
People, time, projects and profitability in one environment
SNOK.me helps organisations bring order to their teams' day-to-day work as well as to project and employee-case management. The platform combines time tracking, workload planning, project delivery, billing and management reporting in one coherent environment - giving the leadership team an up-to-date view of work, costs and profitability.
Which of the two you need
Start with SNOK MDM if the problem is the data itself
The same customer, material or supplier described differently in every system. Reports that need manual reconciliation before anyone trusts the number. A migration or an S/4HANA conversion that keeps stalling on record quality. SNOK MDM works across six master domains at once and runs on-premise where policy requires it.
Start with SNOK.me if the problem is visibility into the work
Who is on which project, how much time it has consumed, whether it still earns money. SNOK.me brings time tracking, workload planning, projects, billing and management reporting into one environment.
If both hurt, the order matters
Master data first. Reporting built on inconsistent records does not reveal the inconsistency - it repeats it faster and with more confidence.
Why an implementation company builds its own software
We never planned to become a software vendor. Both tools started as answers to specific problems in client projects - and only when the same problem kept returning at other organisations did we turn the proven method into code that can be deployed again. That is the reverse of a typical software company: practice came first, the product second.
How a product differs from a project
In a custom project the scope is designed from scratch and priced from scratch. A product inverts that: the core is ready and proven in production, so implementation work covers configuration, integrations and data - not building foundations. In practice this means a shorter path to first results, a predictable scope, and a roadmap funded by all users of the platform rather than a single client.
How the engagement works
Implementation, integrations and support are handled by the same team that writes the code - there is no seam between vendor and integrator, so a ticket never travels between companies. Where security policy requires it, we work inside the client's own environment.
Who this is for - and who it is not for
We build our products for mid-size and large organisations that want to solve a specific problem without replacing their system landscape. If you are looking for a global enterprise platform with an ecosystem of hundreds of partners, we will say so honestly - that is a different shelf and a different budget. Our edge is fit, pace and direct access to the team that knows every line of the code.
What the two have in common
Both run alongside the existing landscape instead of replacing it, and both are neutral about the identity ecosystem - Microsoft 365, Google Workspace or local accounts, with no requirement to standardise on one stack first. Both can run inside your own infrastructure where security policy requires it; SNOK MDM additionally ships with source code in escrow.
Both are proven in real operational use rather than in a slide deck. SNOK MDM has been in production since 2022 and handles around 100,000 master data record events a year in an international environment spanning 18 countries and 9 source systems. SNOK.me runs our own organisation day to day - employee matters, projects, working time, profitability and billing all sit in it.
Support after go-live
Support runs 24/7 under an SLA. The commitment is held by the team that wrote the code, not by a help desk sitting between you and a vendor - so an incident does not travel between companies before anyone looks at it.
Versions and the roadmap stay on our side. Keeping the core current is not billed to you as change requests and is not something you have to plan around. Where policy requires the platform to run inside your environment, support works there on the same terms.
How evaluation starts
There is no public sandbox and no self-service trial, and that is deliberate. A generic demonstration of a master data platform tells you nothing about your own records - the interesting question is always what happens to your duplicates, your domains, your source systems.
Evaluation starts with a conversation about the data and the processes. A demonstration follows once we know what is worth showing.