Why SumaFlow
Twenty years inside enterprise data systems showed me what was broken. SumaFlow is what I'm building in response.
For most of my career, I worked inside systems most people never see.
Banks, fintech platforms, healthcare networks, manufacturers. Data flowing through pipelines, dashboards, settlement systems, audit trails. The infrastructure underneath everyday life.
It taught me a lot. About scale. About reliability. About what happens when systems fail at 3 a.m. and someone has to be paged.
It also taught me something quieter, that took longer to admit: most of the work was compensating for software that should have been better.
I lost count of how many times I watched smart people maintain shadow spreadsheets — careful, fragile, deeply personal Excel files — because the official tool couldn’t filter what they actually needed.
Analysts stitching reports together by hand. Senior people scribbling notes on legal pads because no digital option felt safe.
Nobody complained loudly. There wasn’t time. The work had to get done.
So we adapted. We built workflows around the tools instead of through them. We patched friction with our own time. We moved on.
It only struck me later how much of my career was that — humans doing the work the software couldn’t.
That gap — between the system that gets bought and the system you actually need — is what SumaFlow is for.
The name isn’t accidental. It carries my own DNA: SUMA from Sumawang, my family name — meaning summit, the highest point. And FLOW for what good systems should feel like — smooth, quiet, out of your way.
Standards from the summit. Work that flows.
That’s the whole idea.