
Flows
Killing paper with flows
Earlier this year we launched Flows for the first time.
Our idea was simple, we wanted to build a no-code system like Notion but for non-desk workers. (workers without access to computers)
We launched our MVP together with a couple of companies all in different verticals. (Transportation, Construction and Food).
The companies all had the same job to be done, or so we thought: Replacing paper documentation with digital workflows.
It didn't take us long to realize that we couldn't have been more wrong.
Despite the overall similarities of using paper, the underlying pains were completely different.
Transportation: wanted to save time on gathering supplier documentation
Construction: wanted a better process for managing on-site quality documentation
Food Manufacturing: Highly regulated, wanted to save time & money on compliance.
As we are only two men, with limited resources, we knew that we would never win by building a solution for all three verticals at the same time.
We decided to build for the vertical with the strongest pain: Food manufacturers.
In a couple of weeks, we'll be launching our alpha on www.itflows.co.
The question remains: Did we make the right decision?
I guess time will show 🤞
About
We help companies get tasks done with powerful flows designed to be completed, anytime and anywhere.

Comment