Philosophy
Every Rengised product started as a problem I had.
Rengised wasn't built to ship software. It was built because I kept needing simple answers and couldn't find them.
I never wanted to just make a digital product. I wanted to fix things that had actually got in my way.
Complicated is easy. Simple takes thought.
Over the years I kept running into the same kind of problem: something I needed to do, and every option out there was either too complicated to bother with, or clearly designed by someone who had never stood in my shoes.
So I started writing the needs down and building the simplest answer to each one. Rengised is what that list became.
Everything we make has to pass one test: does it make sense from the customer's side of the screen? If it doesn't, it doesn't ship.
— Femi
Four needs · four answers
What I needed, and what I built.
-
“I needed a designer who understood the product, not just the pixels.”
-
“I needed to see what I was paying for before the next renewal.”
-
“I needed to find a video I only half remembered.”
-
“I needed to know where the things I buy actually come from.”
How we decide what to build.
-
01
Simple to design
If it needs a manual, the design isn't finished.
-
02
Simple to build
Fewer parts means fewer failures and faster fixes.
-
03
Simple to use
Built from the customer's side of the screen, not ours.