Guided processesNEW
Turn business rules into a visual process that any record follows to the letter. You design the stage transitions, where each state can move from and to, set the conditions that unlock the passage, the required fields for each transition, the automatic actions that fire afterward and even an optional approval. What used to exist only in the sales pipeline now applies to any object, and nobody skips a stage without filling in what the process demands.
- From → to stage transitions with conditions: only those who meet the rule advance.
- Required fields per transition: the record won’t pass without the right data.
- Automatic post-transition actions and optional approval at each passage.
Free in Sellio, you only pay for the machine
A process engine with transitions, required fields and approvals is usually an advanced-tier feature. On Sellio it’s part of the free plan: you only pay for the machine.
Nobody skips a stage without a basis
Required fields and conditions per transition ensure every advance carries the right data, raising the quality of the whole process.
A consistent process for every object
Contracts, tickets, projects or objects you created follow the same rigor as the sales pipeline, no exceptions.
Less error, less rework
Automatic post-transition actions handle what comes next, cutting forgotten manual steps and corrections.
Governance without slowing the team
Optional approval steps in only where it matters, giving control without turning every move into bureaucracy.
Rules easy to maintain
Because the process lives in a visual editor, changing a transition is a configuration task, not a development request.
Works for any object, not just the sales pipeline: the same engine governs contracts, tickets, projects or whatever you model.
Visual process editor: you draw the map of stages instead of hiding rules in code.
Quality gating by design: required fields and conditions stop anyone from jumping stages without a basis.
A per-object process engine is usually an enterprise-tier feature; on Sellio it’s already included.
The pipeline’s gating, now everywhere
The lock that guaranteed quality across opportunity stages has been generalized. Any object with a state field can get a process: you define which transitions are possible, what must be filled in for each one and what happens afterward. The result is a consistent flow where the system itself guides the person down the right path.
Rules everyone can see
In the visual editor, the process becomes a map of stages and transitions instead of a hidden list of rules. That makes it simple to review, adjust and explain how work should flow, without depending on whoever wrote the configuration. When the rule changes, you move a transition, not request a new version of the system.
- 1
Pick the object and the state field the process will govern.
- 2
Draw the from → to transitions in the visual process editor.
- 3
Set conditions, required fields, automatic actions and approval per transition.
- 4
Publish and the system starts guiding each record down the right path.
A contract that can’t be signed without review
The transition to the signed state requires the legal-review field filled in and fires the approval, so no contract advances without the right sign-off.
A ticket that needs diagnosis before resolving
The process only unlocks the passage to resolved once the root cause is recorded, ensuring support doesn’t close without understanding the problem.
A custom object with its own flow
You model a new object, define its state field and draw the transitions in the editor; the gating applies immediately, just like in the pipeline.
Does the process only work for the sales pipeline?
No, the same engine works for any object with a state field, contracts, tickets, projects or whatever you model.
Do I need to code to build the process?
No, you design it in a visual editor, drawing the map of stages instead of writing code.
How do I define which stage transitions are allowed?
You draw the from-to transitions and set the conditions that must be met for a record to advance.
Can I require certain fields before a record moves forward?
Yes, you set required fields per transition so a record can't pass without the right data filled in.
Can something happen automatically after a transition?
Yes, automatic actions can fire right after a transition completes.
Can I add an approval step to a transition?
Yes, an optional approval can be added to any transition where it matters.
Is this included in the free plan?
Yes, a per-object process engine like this is usually an enterprise-tier feature elsewhere, here it's already included.
Can I apply this to a custom object I created?
Yes, you define the state field on your object and draw its transitions, the gating applies right away.
Is it easy to change the rules later?
Yes, since the process lives in a visual editor, changing a rule is a configuration change, not a development request.