Product videos

EnviroCert

Short demos of the modules – see how the platform works in practice.

Overview

Watch this one first: what every film can tell you about you

Every card here has a «more» link, and it is easy to miss. Open it, and the film stops being a demo and starts talking about you: which company you are signed in to, whether the module is switched on there, and a button straight into it when there is somewhere to go. A green check means the module is on for your company. No check means the film shows you what you would get, and how to switch it on. The search field at the top looks in the words: type what you work with, and if nothing matches, let the AI pick the films that fit what you described. Nothing here changes your access — it only reads what already applies.

Everything in one place

HSE in a binder, environment in a spreadsheet, GDPR in a folder — and one login instead.

Tenders: pay only if you win

The tender that fit you closed before you saw it. Doffin watched for you — pay only if you win.

Benefit realisation

The CFO asks what quality work saved, and you have a feeling. Here's the number.

Everything in one place (30s)

Thirty seconds: three systems, one login.

Pay only if you win (30s)

Thirty seconds: pay only if you win.

Benefit realisation (30s)

Thirty seconds: what the quality work saved.

Deviations

Deviation management

A report nobody followed up is worse than none — people stop reporting. From report to closed, on record.

The report that did not get lost: from the QR code on the wall to the case that closes

A plumbing firm with a report point on the loading bay. Someone scans the QR code and reports a deviation with no account and no login, and gets their own link to add photos later. The report becomes both a deviation and a case, so it can be assigned and given a deadline. The follow-up is a checklist, and when an item is set to deviation the new deviation lands on the same case. The road runs both ways, as a relation and not a line of text somebody wrote.

Internal control

Internal control that gets used

Internal control as a binder on a shelf: routines nobody reads, inspections from memory. The version people use.

Risk and preparedness

A risk nobody wrote down is a risk nobody prepared for.

Annual cycle

The annual cycle

An audit is due, a review is next month, someone wants last year's numbers — running on live data.

Whistleblowing and GDPR

Someone sees something wrong and says nothing. A safe channel, and control of the data you hold.

People, training and HR

People, certificates and training

An HSE card ran out, and nobody noticed until the inspector did.

HR and timesheets

Holiday requests by email, hours in a spreadsheet, approvals over the shoulder.

Chemical inventory

The inspector asks for the data sheet, and someone goes looking for the binder. One scan away instead.

Suppliers

Suppliers and the Transparency Act

Anyone can ask how your suppliers treat their people — and the law says you must answer.

Projects

A rebuild brings its own deviations, risks and outside people. Walls around each job.

Climate accounting

A tender asks for your climate accounts, and you have power bills. An afternoon, done yourself.

The reporting that's coming

The reporting that hit the big companies rolls down to their suppliers — and stops at you.

VSME

VSME reporting

Basic module B1–B11 and comprehensive module C1–C9, per location with consolidation, filled from climate data and HR, one report as PDF.

Tenders

Find the right tenders

The tender that fit you closed last week, because nobody reads Doffin every day.

From requirements to response

Finding the tender is the easy part. Then come the evenings of requirements and answers.

Public tenders: find one, share it, answer it

Let the system pick your procurement codes, see the open Norwegian tenders that fit ranked with days left, start a bid from one, pull the requirements out of the documents and draft the answers, then set who gets the alerts and let new tenders be shared between colleagues in turn. English narration, 6 min 34 s.

CRM and cases

From lead to signed quote

A lead comes in — and six weeks later it's signed, or lost between inbox and spreadsheet.

Cases that run themselves

Four on a Friday, a case comes in — and who takes it shouldn't depend on who's around.

Field work without paper

The job is done on site; the paperwork at a desk, hours later, from memory.

Plan the week by dragging: technician, day and time in one movement

Drag a job from the unassigned list straight onto a technician’s hours. The card hangs from the pointer all the way, and technician, day and time are set by the same drop. Move it on, lay out the rest of the week in the week view, and see the system speak up – with the reason, not just a question – when you are about to schedule a job waiting for a part.

From text to checklist: workstations, AI-made checklists and bikes that take their own route

A bike workshop with four stations. The job is written as plain text on each work step, and the checklist is created from the text, with a preview before anything is saved. One flag decides whether the repair is included: one bike just needs a wash, one needs repairs. On the board the checklist follows the card from station to station, every answer is saved at once and remembers who and when, and the overview shows where the checklist was used and which bikes raised a deviation.

The customer calls, you answer with a date: catalogue, promised delivery, production and purchasing

A bike workshop that builds bikes. The seller finds the bike in the catalogue, picks the tyre size the customer wants, and gets a delivery date calculated from free stock, supplier lead times and station capacity, with the bottleneck named. The order becomes a sales order, production orders with sub-orders for the wheels made in house, and draft purchase orders per supplier, all sharing one reference. The second half shows the setup: bill of materials with minutes and setup time, choice groups, the internal cost breakdown, supplier lead times and pack sizes, and the station calendar with closed days.

The customer calls: one search box, and the whole customer on one page

The support desk. The customer gives an e-mail, a phone number or her own order number, and you get cases, sales orders, the production behind them and deviations on one page — including the deviations the customer reported herself. Phone numbers are found whatever the spacing and country code, and a single unambiguous hit opens straight away. If she says something that is written down nowhere, it is written down there and then as a deviation and a case that are linked. The case opens straight from her card, and the rest becomes one log: the comment with the photo and the report she sends in the same entry, a checklist for what the plumber should go through, and who takes it and by when.

Record how you do it, and hand it to a colleague

Press Record in the Quick actions panel, do the job the way you normally do, and press Stop. The server cuts that span out of the usage measurement that already runs on every page, so nothing new is collected and nothing you type is ever stored — only how many characters it was. Then the AI writes a work instruction using the real button and field names, and says what took time: a form sent five times, a field you kept pasting into, a search that never hit. One click turns it into a routine with a version and an approval. And the last part is the point: a colleague opens the same recording and gets pointed through it, one step at a time. It points — you click. Nothing happens by itself. For systems that are not ours, a trade system or Altinn, there is a browser extension that does the same thing. English narration.

One command, and you can record in any system

The browser extension installs with one command. It downloads nothing: it writes a single policy file, and the browser fetches the extension itself, and every update after it. Connect it to your account with a key that can only deliver a recording and reads nothing back. Then open it on a supplier system, give access to that one site, and record the task the way you always do it. It stores which buttons and fields you used, never what you typed into them. Chrome, Edge and Brave.

Ordering and booking

Customers order themselves

Orders by phone, email and a sticky note by the till — each one typed up, each one missing something.

Booking and rooms

Someone calls to book the room; you check, call back, and hope nobody double-books.

Stock and purchasing

Purchase orders: find products by searching

Type a name, article number or barcode. A scanned code selects the product instantly.

Sales orders: the same search for order lines

Category matches too, and free-text lines still work next to product lines.

Quick goods receipt and stock search

Search the product, enter the quantity, done. Filter the stock overview by product, SKU, barcode or location.

Product images

One picture per product, shown in the product list, the stock overview and search results.

Purchase order letterhead and e-mail templates

Your logo and address on the PDF, and saved e-mail texts to choose from when sending.

Returns and bill of materials

The same product search on returns to the supplier and in the bill of materials.

From sales order to restock

The whole chain: setup, sales order with reservation, production with picking, assembly, quality check and packing, delivery and restock from shortfalls.

Scan in and out with your phone

Barcode and QR labels, scanning with the phone camera or a reader, in and out with quantity and note, stock updated at once.

A faster day: search, rows and scanning

Search that forgives typos and spacing, clickable rows, barcodes with a check digit, several order lines in a row and scanning at goods receipt.

The order arrives as a PDF. Read it in.

For the supplier: the customer’s order is read from PDF into a sales order, with product matching, stock before and after, a count, confirmation and shipping.

The packing slip arrives as a PDF. Receive it.

For the customer: the supplier’s packing slip is read against the order, lines are tied, goods are counted and the receipt is registered.

The warehouse in your pocket: shelves, counting and moving

On the phone: scan the shelf, quick in, count the shelf against the list, move to the service van as one action, and the overview grouped by warehouse with minimum right in the table.

Receiving with lot and expiry, labels and an unknown code

One GS1 scan gives product, lot and expiry on receipt; the lot follows the product card and overview; labels on sheets or rolls; an unknown barcode becomes a product with one tap.

Is the box packed correctly? Weight check when packing

Small items without barcodes are checked by weight: weigh a handful to get the weight per unit, weigh the packed box against the order, and get suggestions for what a deviation could be. Optional per company.

Product passport

Product passports: one per unit you build

Mark a product for passports, and every finished unit freezes its own: what it is made of by mass, a calculated carbon figure, the documents, and a logbook. The QR opens a public page with no login, the customer gets an owner link that shows more, and life cycles record how many times the element has been installed and what state it came down in. Ends on the machine-readable passport, with its hash and signature. Preparation for the EU construction product rules, not an approved passport; the figures are calculated, not verified. English narration, 8 min 00 s.

Building documentation

Supplier documentation: one link per supplier, one register per building

The building owner sets out what the building needs, and invites every supplier with a link. No account: the supplier sees only their own lines, uploads declarations of performance, environmental declarations and operating manuals, pastes links, adds the figures, and marks the line done. The owner approves or sends back with a comment, reads a material register that only adds up the lines whose unit matches, and pulls a handover package. Where a product has a passport from the passport module, the owner marks it installed and the unit public page shows the new life cycle. A documentation register, not a certificate of conformity; supplier figures, not verified. English narration, 9 min 46 s.

AI assistant

The AI assistant

Every answer is in the system — five clicks away. Ask instead, on your own data.

Documentation requirements

CE marking: what the machine can show, and who signs for it

A declaration of conformity is signed for one machine, not for a product type – so the documentation hangs on the serial number. Open a produced unit and you see what it is built from, what was logged during production, and which requirements are confirmed, by whom and when. Before anyone signs, the page lists what is ‘not confirmed’: you sign with your eyes open, and the gaps become part of the declaration exactly as they stood that day. The name and the authority are entered by hand, because it is the manufacturer who declares conformity – not the system, which only records what the documentation showed. A declaration that turns out to be wrong is withdrawn with a reason, never deleted. Nothing new is asked of the people building the machine: the serial number, the bill of materials and the production log are already there.

More modules

Shortcuts and recipes: your key on your field

Quick actions is off until you switch it on. Bind a key to a field, build a recipe of seven steps as you work, give it a key, and read the run log afterwards. The pages are unchanged.

From habit to script, and a whole sheet on one approval

Mark your own activity and get a draft recipe. Paste a sheet from Excel, map the columns, run every row as a draft, and see each change before you approve. If a row was changed by someone else, nothing is written.

Advanced 5

Scripting, bulk updates and shortcuts. Not needed to get started.

CRM and cases

Many rows at once: CSV in and out, with a preview and a full trail

The supplier sends a new price list. You download what is in the system, correct it in a spreadsheet, and upload it again. Before anything is written the system shows what will be new, what changes with the old and new value field by field, what is unchanged, and which rows have errors. Afterwards the whole run sits in a log with who, when and row by row, and the same changes appear on the product itself. Stock goes the same way, but is booked as a count in the movement log. Finally: products with an end date that leave the search without leaving the history, barcodes that several products may share, documentation on the product, and the build record showing everything that actually went into a production order.

Product passport

Answer once, and let it follow the product

For manufacturers. Every project that buys your product asks the same questions — fire class, recycled content, the carbon figure, substances on the candidate list — in a different spreadsheet every time. Answer them once, on the product, and the answers are frozen into the passport of every unit you build and arrive as suggestions on the building owner's requirements. They still confirm them; you are no longer sending them. The film also takes head on the claim that the digital product passport replaces the environmental declaration — it does not, and the declarations you have already paid for are not wasted. English, 4 min.

Building documentation

Who sees which project — and how the next one starts

Two windows, side by side: the administrator on the left, a colleague in the office on the right. She ticks a project on an access group — and in the same moment it disappears from his list, counts and all, and the address he types answers 'not found' rather than 'no access'. Then the company-wide switch that reverses the default, so a project with no groups is seen only by administrators. Access lives in one place here: one group, one list, granting modules — production, HR, customers, building documentation — and now projects too. The last part is starting the next project: any ordinary project can be the one you copy from. Specification is inherited; the answers never are. English.

Documentation requirements

Requirements in the documentation, not in a folder of PDFs

Ask a building owner what they require of a product today and the answer is usually one thing: is there an environmental declaration, yes or no. But a municipal climate requirement is a number under a limit, a fire requirement is a class from a list, and a chemicals requirement is a declaration about a named substance — none of which fits in yes or no, so it ends up as PDFs nobody can answer from. This film shows the requirement library, the matrix of every delivery line against every requirement, suppliers answering through the link they already have, and exceptions recorded with a reason and a date. It also says plainly that the product passport does not replace the environmental declaration. This is the building owner's own assessment, not a certificate of conformity. English, 6 min.

EPD register

The EPD register: filled by your own supply chain

An environmental product declaration usually arrives as a PDF and ends up in a folder. This film shows what happens instead: when a supplier states the EPD number and the carbon figure on a delivery line, or uploads the declaration itself, it lands in a register you can search across every project. No programme operator involved, nothing downloaded. Every row says where it came from — stated by hand, read from a PDF, or a full dataset — so one figure never passes for thirty-one. The film also shows two limits we keep on purpose: units are never converted, and where we have not established the right to reproduce a source's figures, no figures are shown. We verify no EPD. English, 5 min.