Skip to content
IT Request a demo

Platform

We are not your operations backbone, and we do not want to be

This is a commitment, not a gap in the roadmap. Every quarter there is a reason to add invoicing, or HR, or a CRM, and every quarter the answer is no.

What we deliberately do not build

  • Accounting and invoicing. You have a system, it works, and it is bound to obligations we have no business touching.
  • CRM and sales. Not our domain and not our expertise.
  • HR and payroll. We hold competence and qualification records because welding codes require them. That is not HR, and the line is worth keeping sharp.
  • General document management. We control engineering documents in a project. We are not a company-wide file system.
  • Production planning at plant level. Project execution, yes. Shop scheduling and capacity, no.

Why the refusal is the strategy

Building HR, CRM and accounting properly takes a large team, and a small team that tries ends up with three mediocre modules and a welding engine it stopped improving. The depth in welding, NDT and inspection is the entire reason to choose this over a horizontal quality platform. Diluting it would remove the reason to buy it.

There is also a plainer argument: you already have those systems, they work, and replacing them is a project nobody asked for.

What we send outward

  • Progress and completion against project structure, for planning and for billing milestones
  • Hours and activity recorded against work, where you want it in another system
  • Material consumption and stock movements
  • Nonconformance costs, where you attribute them
  • Documents and dossiers, as files, wherever your archive lives

What we expect inward

  • Customers and projects, if they are created elsewhere
  • People, if identity is managed centrally
  • Purchase and delivery data, to save typing material in twice

How

A REST API over the whole data model, with authentication and permissions that match what a user would see in the interface. Webhooks for events worth reacting to. No proprietary connector you have to buy, and no integration partner you have to hire.

If an integration you need is not possible, that is a defect and we would like to hear about it — the API existing is part of the promise that your data remains yours.