Test v3 · EN default · system fonts · Lighthouse path · not production

FehrWatch The Other ERP

Platform · not a rigid catalogue

Your process. Your dashboard. FehrWatch underneath.

The platform is ready. The workflow is built around the customer. FehrWatch is the technical foundation — not a finished industry pack for every vertical.

  • Not a rigid standard product — one gearbox, customer-specific process on top
  • Requirements in, dashboard out — fields, workflows, reports, interfaces as specified
  • ITAD as working proof — already running on this foundation, including data erasure
Send a process brief See the four steps

No claim that every industry is pre-built. The stack exists. The process is specified, then fitted.

Platform

Gearbox

The technical foundation. Same chassis for every process. Hosting, updates and technical support sit here. The customer workflow does not.

auth

Accounts, sessions, access control. Not a billed headcount.

rows

The record layer. Volume is counted here: rows, intake events, devices.

rules

The engine that can run thresholds and routing. The rule set itself is the ratio.

APIs

Inbound and outbound capability. Each connection is named in the brief.

views

Screens can be fitted. Which masks exist is specified per process.

reports

Export and audit capability. Which reports ship is part of the ratio.

Process

Ratio

Fitted from the brief. Not a catalogue. Further processes use the same gearbox. Only this layer changes.

Fields & masks

Which columns exist. Which form that station sees. Extra fields stay out of the way.

Rules & logic

Thresholds, flags, routing. Signal — not an unsupervised auto-decision.

Views & roles

Who sees which mask. Pack table, buying, admin — same foundation, separate views.

Interfaces

ERP, CRM, backend. Existing systems stay. FehrWatch sits between them and the bench.

External data sources

Market feeds, device recognition, lists — if the process names them.

Audit trail

Who ran which step, on which unit, with which result. Documentation on the row.

How it works

Four steps

The customer describes the process. FehrWatch is fitted to that process. The dashboard matches the operation.

Process

The operation and the requirements. Sites, roles, hand-offs. What stays in the existing ERP.

Brief

A specification, a requirement list, or a workflow description. A requirements document or a walkthrough at the bench.

Fit

Masks, fields, rules, views, interfaces. The gearbox stays. The ratio is built on top.

Dashboard

The functions, fields, evaluations and interfaces that were specified. Not a generic all-in-one screen.

Working proof

ITAD

One live instance of the same principle: gearbox underneath, process on top. Not a vertical pack. Not the identity of the platform.

Intake & serials

Rows at the bench. Capture and lists as specified for that flow.

Risk & market range

Signals on the unit. Decision aid. Not a price guarantee. Not auto-buy.

Erasure & device file

Protocol and certificate in the ITAD path. Device file on the row. Included.

„Bei modernen Massenspeichern wie SSDs oder USB-Sticks ist ein sicheres und vollständiges Löschen technisch bedingt nicht möglich. Daher sprechen wir keine Zulassung für ein Produkt dieses Produkttyps ‚Datenlösch-Software‘ aus.“ — BSI

FehrWatch respects that statement. The platform records what ran. It does not claim a wipe the medium cannot support. For VS-NfD and classified drives, physical destruction according to TL-M50 is required. Software wipe is not that path. Commercial remarketing uses the device file as documentation.

ITAD intake & risk

Price

Gearbox and ratio, in text

No catalogue. No per-seat price. No industry surcharge. The same logic applies to further processes.

Platform = fix + volume band. The gearbox is priced once. Volume is rows, intake events, or devices. On the live ITAD instance the published bands are 1,500 and 6,000 valuations per month; above that, by volume, sites and signal load.

Process = effort + volume + ratio. Fields, masks, rules, views, interfaces and external sources are quoted from the brief. Another process is not a discount off ITAD. It is another ratio on the same gearbox.

Erasure = included. Native to the platform. In every volume band. No extra licence line. Protocol and certificate sit in the device file for that path.

Monthly total = platform + process layer + signals where used. Illustrative, not a quote. We price the ratio — the gearbox is ready.

Next step

Send a process brief

A requirements specification, a requirement list, or a workflow description is enough to start.

Send a process brief