Your finished process first.
Then we talk.

For medium-sized and large companies and organisations, for public administration and universities – and for BPM consultants and integrators who build processes for their clients. What they have in common: many workflows with roles, deadlines and approvals, often across departments. For a single small workflow in a small business we are not the right tool.

It logs in as every role, works through the process, lets deadlines actually run out and then reads the stored state and the send log. It checks the flow, not whether a decision was professionally right. It checks what your material said – what was not in there, it cannot find. Whatever the material does not settle is marked in the process as an assumption, visibly. A person decides on every assumption before anything goes live.

A running process with forms, roles, group inboxes, deadlines, escalations and mail templates, test accounts for every role and the test report from the play-through. Not included: interfaces to your systems. It is a test environment, not production; deadlines run on test values – minutes instead of days. One process per challenge.

Nothing. There is no charge for the test process – one process, in our test environment, with test accounts for every role. We only talk about licence and installation once you have played it through.

No. An invented one, a publicly documented one or one from an old manual will do – as long as it has roles, deadlines and approvals. Send material to info@flyingdog.de; the form deliberately has no upload.

The test process runs in our test environment. With a licence, the platform runs on your servers – AI operation included – with the source code shipped. If you run a modelling environment in-house, the process goes back there as BPMN 2.0.

You play the process through with your people. Then we talk – about licence and installation. You can still buy afterwards.