About RKade
RKade comes from arcade, and arcade comes from the Latin for arch.
An arcade is a run of arches that holds a building up while making a way through it. That is the whole idea behind this site, and behind how we build: not a feature bolted on top, but the structure that carries the weight so your team can move through it faster.
Look again at the first two letters: RK is Raffay and Kushan, the two founders whose initials sit inside a real word.
Who's behind it
Raffay and Kushan. That's the whole team.
We both build. We both sit with clients. These are just where each of us spends more time.
The build side
Raffay Ali
Lives in the tools, the APIs and the edge cases. Turns a scoped process into a working system.
Operations
Kushan Naresh
Deals and operations background: sourcing and closing acquisitions, standardising diligence process at a private equity firm. Leans into client conversations and scoping, turning a messy process into something worth automating.
How the work gets done
Small phases. Checked before the next one starts.
This is true of every RKade project, including the site you are reading this on right now.
- One phase at a time
- Every project breaks into small phases, each one scoped before it starts.
- Checked before it moves on
- Each phase gets verified against what it was meant to do before the next one begins.
- Loaded in a real browser
- Nothing ships on the assumption that it works. It gets opened, clicked through and confirmed.
- You see it first
- A preview goes to you before anything reaches your live site or system.
Stop losing hours to work a system should be doing.
Start with the audit. We map exactly where automation pays off, and tell you the order to do it in. It costs nothing and there is no pitch.