A
Audit
Diagnose + map
We sit with the people doing the work and map the current scenario: what runs where, who decides, and where the process stalls. The result is a written picture of the operation as it actually is.
Us, with your process owners
The work your operation runs on, built into one system.
Procedo is a dedicated instance, adapted to how your company actually works. It can connect to ERP data, and some processes need no integration at all.
Application coreStandard
SecurityStandard
User interfaceStandard
Business rulesTailored
ConnectorsTailored
AI assistTailored
- AI assist Tailored
- Connectors Tailored
- Business rules Tailored
- User interface Standard
- Security Standard
- Application core Standard
- Records, users, permissions and the audit trail. The same engine runs for every client, so it is already proven before your project starts.
- Authentication, roles and access boundaries. Your deployment is dedicated and your data stays isolated.
- The screens, task lists and reports your team works in every day. Consistent across implementations.
- Your approval limits, deadlines, exceptions and who answers for each step. Written to match how your operation actually decides.
- Reads from and writes to your ERP and the systems around it. Nothing is replaced and no data is duplicated by hand.
- Reads documents, drafts entries and flags what looks wrong before it reaches a person. Someone still approves.
Built on a proven foundation
Your implementation starts from a platform that already runs other operations, and is shaped to fit the way your company works.
Hover a layer
Six layers, three of them yours
The bottom three run the same way for every client. The top three are written for your operation.
ATOM — how we work
Four stages, then it starts again
Every process we take on runs through the same four stages. When the next one comes up, it enters at the beginning and the cycle repeats.
T
Transform
Build + change
We build the tool around the processes we found. Rules, screens and connections to your existing systems are written for your operation, then rolled out with the team that will use them.
Us building, your team validating
O
Optimize
Tune + adopt
With the process running, we follow real usage and adjust: rules that were too strict, steps nobody needed, numbers that were missing. Fine tuning continues until the process holds on its own.
Us watching, your team using
M
Maintain
Run + evolve
We keep your instance running, supported and current, so the gain does not fade after go-live. When the next process needs to come in, it enters at Audit and the cycle starts over.
Us, continuously
Each new process re-enters at Audit
ERP and Procedo
What stays in the ERP.
What runs outside it.
The ERP keeps the records: the ledger, the invoice, the stock balance. Procedo runs the work that happens before and after those records, the orders, approvals, credit checks and follow-up that cross people and systems. The two talk to each other, so nobody types the same thing twice.
Your implementation starts from a platform base that already runs other operations, and is adapted to the way your company works. Reuse is what makes implementation cost thousands instead of tens of thousands, and it is why your instance keeps changing after it goes live.
The system can answer questions, read messages, query documents, prepare an analysis, trigger a task, or make a decision inside customer-defined limits. You decide, process by process, what the system can decide and what still requires a person.
No, and it is better to read that here than to find it in the proposal. The standard model delivers a dedicated deployment and a continuing relationship: we build on our proprietary codebase, run your instance, and keep it evolving. The code is not transferred. Your data is, in an open format, whenever you ask.
Where the line sits
One example
System of record
ERP
Holds the truth once it is final.
- Ledger and entries
- Invoices and tax documents
- Stock balance
- Payables and receivables
- Master data
System of work
Procedo
Runs everything before and after it.
- Order intake
- Approvals
- Credit checks
- Follow-up across teams
- Exceptions and handoffs
One common split, not a fixed rule. Where the line falls is decided process by process, with you, during the audit.
Operations already running this way
What the operation does today that it could not do before.
Procedo helped us build a whitelabel platform with AI-powered behavior analysis for hospitals. It turns camera and sensor data into predictive insights, enabling better decisions, cost reduction, and smarter space use.Rodrigo Trentin
CEO @ Observa
Bring the process that is hardest to control.
How we charge
We keep things transparent, flexible, and fair - no hidden fees, no surprises. Explore the questions to understand exactly how we estimate, bill, and adapt to your project needs.
Implementation is priced according to the processes involved, integrations, complexity, and the customer-specific development your operation needs. It is quoted before anything begins.
30% when the signed detailed scope is approved. 70% remaining implementation amount on delivery.
Then the fixed monthly relationship begins. Larger implementations may be divided into packages.
Platform improvements are developed for the platform as a whole and become available to customers without an additional charge.
Customer-specific requests are new behavior developed specifically for one customer. They are estimated and approved before development.
Personalization is changing parameters, rules, triggers, messages, or criteria yourself. It does not create a development charge.