An idea. A product that already works. A process held together by spreadsheets. Whichever one you have, I turn it into something that runs.
For eight years I've been building SaaS products for founders and teams who needed one and didn't have the hands to build it. I also automate the work that shouldn't be done by hand anymore.
Get in touch→
A bit about me
I noticed a pattern early on: the products with the best ideas weren't always the ones that shipped fastest. Speed came from somewhere else — from someone close enough to the problem to just decide and build, instead of routing every choice through a process.
So that's what I became for the people I work with. Fourteen builds later, that's the whole method: small scope, real users early, and someone who can decide and write the code the same afternoon.
I work from Bordeaux, mostly remote, and I read every email myself.
Half of what slows a company down isn't a missing product. It's four people repeating the same steps every week because nobody has had the time to stop and remove them. why automation is half of what I do
Where you might be starting
Not a spec, not a deck. An idea. I build the first working version, fast enough to test it against real users before you've spent a year on it.
It's live, and it needs to move faster than one founder can code. I plug in as the technical hand that doesn't slow the ship down.
Something held together by tabs, copy-paste and good luck. I replace it with something that doesn't need babysitting.
The report someone rebuilds every Monday, the data moved between two tools that don't talk. I automate it and hand you back the hours.
What I've built
Three of the products I've built for clients. They own them, they run them, and they're all still live.
See all case studies→01 / 03
Stack and scale
Eight years and fourteen products in, I've got no favourite stack left — every need has a solution that fits it, and it's rarely the one I used last time. Some products want a boring database and nothing else. Others need queues, workers and a cache from day one or they fall over at the first real week of traffic. I pick what your problem asks for, and I plan for the growth that always arrives faster than expected.
Automation
A task that eats four hours a week costs more in a year than the build that removes it. I find those tasks, and I take them off your team. The work still gets done, it just stops needing a person.
Sometimes it's the whole engagement: no product to build, just a process that got stuck two years ago and has been costing you since. Sometimes it's the layer underneath a product I'm already building, so the thing scales without adding headcount.
How working with me goes
No account manager, no ticket queue, nothing lost between you and the build. And I'm still there after launch. That's the part most people find out too late elsewhere.
Tell me where it stands, in as few words as you like. I'll tell you straight whether I'm the right fit, and I'd rather say no than waste your time.
hello@nekena.comUsually replies the same day.