Business processes, as working software

Turn the way your business works into a working business application.

Describe what your business keeps track of, how it connects, what it decides and how work moves. Tavuni turns that description into the application your people operate — no code, and nothing to keep in step by hand.

  • Model what your business keeps track of.
  • Define how those things connect.
  • Configure the rules that decide things.
  • Build the workflows and approvals work moves through.
  • Operate all of it from one application.

An illustration of the interface. The running demonstration, with its real records, is behind the sign-in.

How Tavuni works

Three of these four are things somebody describes. The fourth is what everybody else then uses.

  1. Business model

    What the business keeps track of, and what it records about each thing.

  2. Business graph

    How those things connect, so a rule or a report can reach across them.

  3. Rules and workflow

    What is calculated, what happens by itself, and who has to agree.

  4. Working application

    People operate the result every day. Not a diagram, and not a spreadsheet.

The demonstration business

A small vehicle-testing company. One piece of work goes the whole way through, and every step of it is configuration rather than code.

  1. Customer

    asks for testing

  2. Request

    is raised, and broken into lines

  3. Testing

    is carried out against a stamped procedure version

  4. Calculation

    turns each reading into a verdict

  5. Approval

    two departments sign off, at the same time

  6. Certificate

    is produced, and attached to the test

What is real, and what is illustrative. The business objects come from a real test-management schema, which is why they hang together. The limits, formulas and approval groups are illustrative: that schema describes tables and relationships and states no tolerance and no approval chain. Do not read them as anybody’s process.
Tavuni