The Lobbi Delivery Team
Operational Systems Engineering
Every automation project arrives at the same fork: configure an existing platform, or build something purpose-fit. The wrong choice in either direction is expensive. Configure when you should build, and you accumulate a fragile stack of workarounds. Build when you should configure, and you own a maintenance liability that grows with your team.
The Configuration Ceiling
Low-code and no-code platforms are excellent tools for standard workflows. They shine when the problem is common, the data model is shallow, and the trigger logic is simple. Power Automate handling a SharePoint-to-Teams notification? Ideal. The same tool trying to orchestrate conditional approvals across five business units with exception handling and audit trails? That's where ceilings appear. not as hard walls but as compounding friction.
Four Questions That Decide
1. Does the workflow have more than three conditional branches that depend on external data? Configuration tools handle branching, but not conditional branching that requires real-time lookups. If yes, lean toward custom. 2. Is the data model owned by a platform you can't control? If the source system has a rigid or undocumented API, a thin custom layer gives you durability. 3. Will this workflow need to scale by 10x within 18 months? Configuration tools have per-run pricing that can invert ROI at scale. 4. Do you need end-to-end auditability at the field level? Most low-code tools log at the workflow level, not the data level. Custom builds can capture exactly what changed, when, and why.
When all four answers point to custom, the decision is clear. When two or more point to configuration, start there and track the ceiling indicators. The goal is to use the simplest tool that will still be the right tool in three years.
Topic clusters