Built by an architect who got tired of copying specs by hand.

Why it exists

A lighting schedule for one apartment, forty products with eleven values each, took the better part of an afternoon. Not the choosing, that was already done. The afternoon was opening each supplier page, finding the dimensions, the finish, the price, typing them into a row, saving the image, and moving to the next tab. The values were already there. The work was just moving them.

Intspec does the moving. Paste the links and it reads the pages, fills eleven fields per row, and marks every value it extracted so you can see what to check. On a real project, 216 links took four minutes and twenty-two seconds. You still check every value. You just stop typing them.

It runs in the EU, is backed up nightly and restore-tested, and only reads a supplier page when you press Extract, only for the rows you chose. Your data is never used to train a model. There are no customer quotes on this page because there are no customers yet. How it works for architects and for interior designers is on their own pages.

What it is not

Not a chatbot

The model is an extraction engine behind the table. It reads product pages and writes structured fields. It does not generate text or invent products.

Not a generic scraper

It reads product pages for product data, eleven fields with units normalised, not whole sites into text.

Not a procurement suite

No purchase orders, no invoicing, no client portal. The spec sheet, done well, is the whole job.