BELA
Home › Use cases › A workflow or approval system
Use case

A workflow or approval system, engineered from how you describe it

Requests that move between people and states, with the rules about who may move them.

What this is, and what it is not

This page describes what BELA can be used to build. It is not a customer story and it does not claim a result — it sets out the entities, the rules and the engineering BELA produces when you describe a business of this shape.

What BELA models first

Requests and their current state

Steps, assignees and due dates

Approvals, rejections and the reason given

The full history of who did what, when

The rules that decide whether it is right

Business rules are where generic software stops fitting. These are the kind BELA captures from your description before anything is built.

A step can only be completed by someone entitled to complete it
A rejection returns the request to a state your process defines
Nothing moves without leaving a record

What you get

A working application with its backend, database schema and interface, the model of your business it was engineered from, and the evidence produced along the way. The source is yours to download and run.

Business impact

What this is worth to you

We will not guess. What BELA saves you depends on what you are building, and that can be measured the moment you describe it.

  1. Describe your business in a sentence — BELA engineers a working application from it.
  2. The Engineering Estimator reads that real project: its entities, workflows and integrations.
  3. The Commercial Resolver prices the result in your region, with your tax rules applied.

Work it out with your own numbers

Enter what this project would cost you to build the usual way, and pick the BELA plan you would be on. Nothing here is sent anywhere, and nothing is saved.

How this is worked out
  • Your current cost = (team size × months × cost per developer per month) + (QA per month × months) + (maintenance per month × 12).
  • BELA plan cost = the plan’s own price, from BELA’s commercial configuration, multiplied by the months you entered — or by whole years where a plan is billed annually.
  • Difference = your current cost − the BELA plan cost. The percentage is that difference as a share of your current cost.
  • Nothing else is applied. No productivity multiplier, no assumed team reduction, no benchmark.

This is a scenario calculation based on the figures you entered and the plan you selected. It is not a quotation, a prediction or a guarantee, and it is not a promise that your engineering cost becomes the plan price — your own costs do not disappear on the day you adopt a tool. BELA has not assessed your project. A figure BELA stands behind comes from the Engineering Estimator reading a real project.

Describe your business

No assumed salaries, no invented multipliers, no percentage on this page. A figure appears only when it can be computed from your project.

Describe your business and see what BELA understands

Start with your own operation rather than a sample project.

← All use cases