The process you drew is the one that runs tomorrow.
KulturPro is a complete BPMS: model in BPMN 2.0, give every task its form, let deadlines run on the company’s business calendar, and measure everything that happens. No code, no waiting for a deployment.
- BPMN 2.0
- No-code forms
- Calendar-aware SLAs
- Multi-company
- Spanish and English
- On your own servers
- REV
Requesting area reviewClosed by C. Ramírez · yesterday 16:20
On time - BUD
Budget verificationClosed by Finance · today 08:05
On time - APR
Manager approvalAssigned to M. Duarte · due today 17:00
Due in 3 h - SUP
Supplier quotationEmailed to three suppliers
External - ORD
Order issueEnabled once approved
Pending
What it won’t let through
A process engine is judged by what it prevents.
Not by how many screens it has. These four rules are in the product, not in a statement of good intentions.
A design version never serves users
While the process is in Design only test instances run, and publishing deletes them. What people see is always a version published on purpose.
Deadlines skip non-working time
The clock runs on each company’s schedule and holidays. Outside working hours it stops, and the alert can notify or reassign.
Fixing something means saying why
Editing instance data, bulk-reassigning tasks, cancelling a process or retouching a published form all require a justification, and all are recorded.
A session without a company reads nothing
Separation between companies lives in data access: if the session carries no company, the query returns no rows and writes are rejected.
Capabilities
The whole cycle, in one tool.
Nine parts that share the same sign-in, the same company and the same permissions. Roll them out in whatever order your operation can take.
Design
What the analyst does
Run
What the user lives
Build
When it isn’t a flow
Deadlines and workload
The deadline stops being a promise.
The SLA dashboard separates what is on time, what is at risk and what is already overdue, task by task and process by process. The clock uses the company calendar, so the number survives a meeting.
- Projected duration per process element, in minutes
- Alerts that notify or reassign, to the assignee or their manager
- Workload per user and bottlenecks per task
- Instance duration and operating time spent on forms
Traceability
What gets written down.
Without this, a digital process is just an email with better typography. Everything below is in the product and can be read from the screen.
- Sign-in attempts
- User, address, browser, result and failure reason; plus an email to the account holder when an attempt fails.
- Each instance’s path
- An execution log element by element, with the state of each task and the diagram that shows it.
- Data corrections
- Which field changed, who changed it, when, and with what justification, nested tables included.
- Reassignments and cancellations
- Preview before applying, mandatory reason and a record of what was applied; cancelled work stays in a readable archive.
- Form revisions
- Every minor edit produces a numbered revision, with its justification and a history you can restore from.
- Asset permissions
- Every permission change on the facilities hierarchy keeps its own audit trail.
It connects
It doesn’t live in isolation.
A versioned API, a webhook so an outside system can write into the right task, and outbound calls from the form itself.
Versioned REST API
Everything the application does goes through the same API under /v1, documented with Swagger and with a uniform response.
Inbound webhook
An external system writes into a field of one specific task with an encrypted, single-use, expiring token.
Calls from the form
When the form opens, a field changes or a button is pressed, it can call your service and bring the value back.
SendGrid or your own SMTP server, with templates and in each recipient’s language.
Your own microservice
A service of yours can share the same database and the same session, and return its result through the webhook.
Inside another suite
KulturPro can run hosted under an ERP, taking its session and its permissions, switched on per company.
Do we need to program to build a process?
Not for the normal case: the diagram, the form, the rules and the deadlines are configured on screen. You can write your own JavaScript inside a form for special cases, but it is optional.
Where does the data live?
In your SQL Server. KulturPro is installed on your Windows server with IIS, or on the cloud you choose. It is not a shared service.
Does it work with a process that already runs elsewhere?
Yes, if that system can call an API or receive a call. There is an inbound webhook and outbound calls from the form; packaged ERP connectors there are not.
Can suppliers or customers who aren’t users take part?
Yes. A task can be assigned to an email address: the person gets a link, confirms a code sent to that same address and fills in only that form. The link expires and can be revoked.
Does it handle several companies?
Yes. One installation serves several companies with separated data, each with its own users, groups and calendar. The company is chosen at sign-in.
Does it include electronic signatures or validation for regulated industry?
No. KulturPro records who did what and why, but it does not sign records. For password-plus-second-factor signatures, a GxP audit trail and a validation package, that is what the InduBatch suite, from the same maker, covers.
Which languages does it speak?
Spanish and English, including the emails and the form labels, which are stored in both languages.
How is it rolled out?
By processes, not by modules: pick one that hurts, put it into production, move to the next. The first one is usually live in weeks.
Demo with a process of yours
See it with a request you already know.
Tell us which process is costing you today. We prepare the demo around that case, not around a generic example.
- Rollout process by process, with support
- Installed on your server or your cloud
- Training for analysts, users and administrators