Solution

Not a product you buy.
One that gets fitted onto your data model.

There is no standard installation of ProcessForge. Component system and blueprint are fitted onto your structures — your vocabulary, your sources, your artifacts. And yes: that takes a project. The difference to a consultant is what happens afterwards.

Your data model — your ProcessForge. No two installations are alike.

Why a project at all

The project is the fitting. Not the artifact.

With a consultant

The project is the product.

Once it’s done, they leave. What stays is a document with a date on it — and it ages from the day they walk out. The next trigger is the next cycle. The next proposal.

With us

The project is the fitting.

Afterwards the system stays — and keeps delivering. When the next trigger comes, it forges the next artifact from the same context. No new project, no new cycle.

What stays with you isn’t the single artifact — it’s the ability to forge the next one.

What gets fitted

The forge is ours. The model is yours.

ProcessForge is a component system. We bring the parts and the blueprint — and fit both onto your structures, instead of forcing you into someone else’s schema.

What you already have

Wikis & docsConfluence · SharePoint

Process inventoryBPMN · process maps

Tickets & work itemsJira · ServiceNow

Core systemsSAP · CRM · DBs

People & workshopsInterviews · Miro

Your sourcewhatever else you have

ProcessForge

What you get from it

Process modelBPMN

Automation draftn8n · Zapier · Make

Podcast & learningin your language

Audit docsDORA · NIS2 · ISO

Operating modelVersions · scenarios

Your artifactwhatever else you need

Stays oursThe engine

The components and the blueprint
The forging logic
The artifact forms as a build method

Becomes yoursThe fitting

The layer on your data model
Your vocabulary and your structures
Your sources, your rules, your controls
The artifacts you actually need

And if our documentation is a mess?

Then you’re in exactly the right place. ProcessForge needs a verified data model as substrate — but not as homework for you: it emerges during the fitting. What counts is not how tidy your material is, but how much of it there is. Outdated manuals, scattered SOPs, a BPMN library grown over ten years, wikis, workshop notes — that isn’t an obstacle, it’s the raw material. One of our customers moved around 5,000 processes out of outdated written documentation. What this does not mean is where your data lives: it stays where it is. There’s no data lake for you to fill first, and ProcessCollector is one route to that model — not the only one.

How it runs

How your ProcessForge comes to be.

Five stations. The first costs you a conversation, the second a bit of data — and after that you know whether it holds, before anyone mentions a project.

01

You get in touch

One conversation, one demo. We settle two things, in this order: do you genuinely want to change something — and does your trigger fit what ProcessForge does.

What we need from you
A concrete trigger. The people who decide.

What exists afterwards
An honest read on whether it fits.
02

We build a first example

You give us access to data once and tell us what you want out of it. We generate a first real artifact from it — from your real data, not from a demo organization.

What we need from you
Access to data. The artifact you want. An NDA if you need one.

What exists afterwards
An artifact you can hold against your expectation.
The moment of truth

Does the example match what you expected? If not, it ends here — no project, no proposal on the table. We consider you too expensive to sell something that won’t hold.

What we need from you
An honest answer.

What exists afterwards
A decision — with proof instead of goodwill.
03

The POC

Now the fitting happens: blueprint and components go onto your data model. How big that gets depends on you — how many systems, how complex the model, how much goes in and how much comes out. Which is why we won’t quote a number of weeks we don’t have.

What we need from you
Access to your systems. A counterpart on your side.

What exists afterwards
Your fitted system.
04

Your system — and us alongside

You get the finished system and keep working with it. When something new comes up, we adapt it together. That isn’t a courtesy: it’s part of what you pay for.

What we need from you
A call when something’s up.

What exists afterwards
A system that’s yours. And us, when you need us.

Before any data moves: we are ISO/IEC 27001 certified, host in the EU, and the DPA, TOMs and the list of subprocessors are openly available. See security and documents →

The scope

There is no list price. But there are three variables.

Because no two installations are alike, the scope can’t be written into a number up front. What it depends on, however, is always the same — and you can judge it better than we can.

How many systems

Every source that comes in is work of its own: access, structure, quirks. Six systems aren’t three times two.

How complex your model is

An organization where everyone runs the same process the same way carries a leaner model than one where twenty units maintain their own variant.

How much goes in and out

One artifact for one trigger is the small cut. Several artifact forms across the whole process landscape is the large one.

We settle these three in the first conversation — before anyone names a number. Naming one earlier would be guessing.

Do you fit?

We work with few. So we say up front with whom.

Every installation gets fitted, and that takes attention. This honesty saves us both the third meeting:

ProcessForge is for you if

you genuinely want or need to change something. That’s the one condition we can’t negotiate.
your process landscape follows its own rules — multiple sites, many regulated processes, legacy systems grown over years. This is not a question of headcount: a regulated mid-sized company with a few hundred people can be more tangled than a large group.
your organizational context can carry a solid model.
the triggers don’t stop — ERP migration, regulatory deadline, integration after an acquisition, a new site, a new certification. The next one arrives while the last is still running.

ProcessForge is not for you if

you’re a small team without structured organizational context — ProcessForge needs substrate.
you’re a sales or country branch without authority over your own processes. Then it isn’t the account that’s wrong, it’s the entity: we talk to the organization that owns its processes.
you’re a consultancy looking for an internal tool for client projects. ProcessForge is an end-customer tool, not white-label substrate.
you need one document and then quiet. A consultant is cheaper for that, and we’ll tell you so.
you want software that runs tomorrow without anyone looking at your model.

What stays

The consultant leaves. The system stays.

A consulting project costs a lot once and ages from day one. ProcessForge is built the other way round: the effort sits at the start — and from there every further trigger gets cheaper, not more expensive. The next artifact comes from the same context, in days.

It grows with you

Your process changes, the model changes. Not in the next documentation round — immediately.

The next trigger isn’t a new project

First BPMN, then the automation draft, then the audit docs. Same context, different form.

We stay — contractually

Further adaptations we make together with you. That sits inside what you pay annually, and it isn’t a favour.

Bring your trigger.
We’ll build the first example.

Show us a concrete plan in a call — then we’ll show you an artifact made from your own data.

How the first conversation runs →

Not a product you buy.One that gets fitted onto your data model.