Approvals, statuses and business rules inside the system
We take your process rules out of spreadsheets and conversations, such as approvals, sign-off limits, deadlines and statuses, and put them into the system, with a history of every decision.
Who it's for
For companies where orders, approvals and exceptions travel through spreadsheets, email and WhatsApp.
What it solves
- A request sits waiting because the approver is on holiday and nobody noticed.
- The discount rule exists only in the heads of two people.
- The same order is processed twice when someone clicks again.
- Nobody can say who approved it, when, or on what basis.
What we do
- Status model
- The states of each process and the allowed transitions between them, designed with your team.
- Sign-off limits and approvals
- Who approves what, up to which amount, and what happens when that person does not respond.
- Deadlines and escalation
- A task stuck past its deadline moves to the next person in charge, with a notice.
- Rules outside the code
- Rules held in tables that the business side reads and reviews, kept apart from the rest of the code.
- No double execution
- A repeated click or a resent message never runs the same action twice.
- Decision history
- Who made each transition, when and with what data, available to consult later.
What you get
- A map of statuses and rules, approved by your team before any code
- Workflows running in the system, with deadlines and escalation
- Tests that walk through every rule and every status transition
- A decision history that can be consulted per process
- A documented rule table for the business side
How we do it
Discovery
We talk to the people who run the process and gather spreadsheets, emails and real exceptions.
Design
Statuses, rules and sign-off limits designed and validated with the team responsible.
Development
Workflows, deadlines and history, with tests for every rule.
Coexistence
Processes already under way finish the old way; new ones start in the system.
Adjustments
Rules reviewed with the people using them during the first weeks.
Technology examples
- Temporal
- Camunda
- BPMN
- PostgreSQL
- RabbitMQ
Related services
FAQ
Who validates the business rules?
Your company. We implement and test what your team has defined; rules with tax or employment consequences are checked by your specialist, not by us.
Do we need a workflow engine?
Not always. Short processes fit a status model in the database itself; long workflows, with waiting and deadlines, call for a tool such as Temporal or Camunda. We decide this during design.
What happens when a rule changes?
The change goes into the rule table and through the tests before production. Processes already under way keep the rule they started with, unless your team decides otherwise.
Can approval notices go out on WhatsApp?
Yes. The workflow raises the event, and sending is handled by the notifications and WhatsApp service.
Write to Balkan
Talk to us about your project