Integrations & data
What is recorded on the shop floor should not be typed in a second time. Not in the ERP, not in Excel and not at the accountant.
In most organisations inspection data lives on an island. An inspector records something, and then someone else retypes it: into the maintenance system, into a spreadsheet for management, into an email to accounting. Every retyping step costs time and introduces mistakes.
PinPoint is built as a data product. Every finding is a completed questionnaire with photos, a status and a history, so structured data you can pass on. Through the API, an export or the MCP server it ends up where it is used, without anyone entering it again.
Why now?
Every integration you do not have today, you pay for every week in retyping. And the longer data stays on an island, the harder it becomes to do anything with it later.
As a business owner you do a lot of admin that has nothing to do with your trade. So we use PinPoint ourselves for our receipts. It is not an inspection, but the principle is the same: record it where it happens, and never touch it again.
A simple "Receipt" questionnaire in the app, on the smartphone, at the moment you pay.
The questionnaire briefly asks what the receipt was for. A few words are enough.
A photo of the receipt, or several for a long invoice.
A fixed integration through the API sends the photos and the description to Yuki, our accountant's bookkeeping software. Nobody has to forward anything any more.
The same setup works for anything that now arrives by email, WhatsApp or a loose photo: a damage claim to the insurer, a defect to the maintenance system, a work order to invoicing.
Some integrations come with every environment. Others we build as a separate project, with their own price, once there is a concrete need.
An integration is custom work, not a more expensive plan
Every feature of the core is in every environment. An integration with one of your systems is built as a separate project, with a price fixed before we start. This is how our offering works.
MCP (Model Context Protocol) is an open standard that lets an AI assistant such as Claude or ChatGPT query and update data in another system. PinPoint's MCP server gives such an assistant access to your assets, inspection rounds and findings, within the rights of the user. You simply ask a question about your inspections, and the assistant looks for the answer in your own data.
Yes. Through the API you read and write assets, inspection rounds, findings and photos from your own systems. It is the basis of every fixed integration, like the one that sends our own receipts to our bookkeeping software. Which data you need and how often, we work out together during the setup.
An assistant such as Claude or ChatGPT can query and update your assets, rounds and findings through the MCP server. You ask, for example, which items have been open for more than a month, or how often a particular defect comes back, and get the answer from your own inspection data, within your rights.
Yes, as a separate project. A finding can then become a work order or a ticket by itself in the system you already use, and the status can flow back to PinPoint. We first look together at which data has to go back and forth, and fix the price before we start.
Export, Power BI, the API and the MCP server are part of the platform. An integration with a specific system of yours, such as an ERP, bookkeeping software or your SSO, is custom work: a separate project with its own price, agreed together before you sign. So no integration is ever hidden in a more expensive plan.
We will be honest with you. If PinPoint is not the right fit, we will tell you. No hard sell, no obligations. Just a conversation between people who understand inspections.
Last updated on