A check before you quote, run by one person.

What you get

You upload the package, and you get back a report listing what is missing, what two files disagree about, which revision governs and which does not, what could not be read, and which wording can honestly be read two ways. Every value in it is quoted from the file it came from, and every finding opens to show that quote.

That is the whole product. It does not quote, it does not price, it does not decide whether to bid, and it does not read a CAD solid. Whether to quote, at what price, and whether to accept the customer's requirements stay with the estimator — that boundary is the reason the report shows its work instead of handing you an answer.

Who runs it

This service is run by an individual operator, under the trade name Scutiqo. Scutiqo is a brand name and not a registered company, and it is not presented as one.

Everything on this site was written and built by that one operator: the check rules, the extraction contract, the site itself, and the reply to every message that arrives at support@scutiqo.com. There is no support desk and no chatbot, because there is nobody to route a ticket to.

How it decides

A language model reads the documents and proposes values. Ordinary TypeScript decides what counts as a problem. A value reaches the report only if the segment it was read from exists, the quoted text appears verbatim in it, and the quote supports it — otherwise the field shows a dash, which means not established and never a guess.

Two files that disagree produce a finding and no winner. A conflict is reported, never resolved. The complete rule list is published on the features page, and the mechanism is written out on how it works.

What it refuses to do

These are boundaries, not missing features, and each one is deliberate:

• It does not quote, price or recommend. No cost, no margin, no bid/no-bid. Deciding what a job is worth is not a thing a document checker can do.
• It does not connect to your ERP or read a CAD solid. It reads the files you upload.
• It makes no accuracy claim. There is no published figure because no measurement baseline exists to publish. When there is one, it will be published with the method written down, not before.
• It keeps nothing. Uploaded files are deleted from storage as soon as the report is built, on failure as well as success. How files are handled has the detail.

What there is not

No customer logos, no testimonials, no case studies, no certification badges and no partner list. This deployment has no customers to point at, and a page that implied otherwise would be claiming something false.

What there is instead: five fictional sample packages you can open without an account, and the complete rule list, so you can judge the thing before you spend anything on it.