Kissflow middle-office workflow platform

The key to Kissflow is that it sells into the messy handoff layer between core systems, where companies still run important work through email, spreadsheets, and ad hoc approvals. CRM and ERP systems hold the main records for customers, orders, and finance, but teams still need small internal apps for exceptions, reviews, intake forms, and cross functional routing. Kissflow turns those loose processes into structured apps without asking IT to build each one from scratch.

• This is middle office in practice, not a back office replacement. A sales or finance team may keep the official account or invoice in Salesforce or SAP, then use Kissflow for the extra steps around it, like collecting documents, routing approvals, notifying managers, and logging who signed off.
  1 sacra 4 salesforce 5 sap
• The closest comparison is not a full suite like Salesforce or SAP, but workflow and low code tools that sit beside systems of record. Onit does this inside legal and compliance, while Microsoft Power Apps extends existing line of business systems with low code apps. Kissflow is broader by aiming at many departmental processes across the enterprise.
  2 sacra 3 microsoft 6 sacra
• That positioning matters commercially because these projects are easier to start. A company can buy Kissflow for one broken process, then expand as more teams want their own request forms, approval chains, and dashboards. Pricing also rises with app complexity and enterprise requirements like external users, private clusters, HIPAA, and GDPR support.
  1 sacra 2 sacra

This category is moving toward becoming the default layer for company specific work that big suites do not cover cleanly. As more enterprises keep their CRM and ERP as the source of truth, the winners in low code will be the products that most easily wrap those systems with fast, usable workflows for all the exceptions and approvals around them.