OMR 2026 wrapped. On the way home now.
We caught Tom Brady's talk. Exactly what you'd expect: a classic American motivational speech, lot of "don't be a bitch", but very entertaining. π
Heading home with a long list of ideas we want to work through, a handful of leads, and some potential new projects on the horizon. I am very happy!! π₯°
It was really great to meet the people you work with or have been in touch with for a while, in person. Makes everything a bit more human & real :)
OMR Day 1 and I barely stepped inside a stage. No regrets, though. π
I only visited the talk from our client SnipKI (which was great btw)!
I mostly spend my time meeting cool people!
Met friends I've known from X and LinkedIn for years. Some for the first time IRL. Those conversations > any keynote.
One observation: AI for WhatsApp and chat commerce + GEO stuff was at every other booth. Wow, the market is saturated.
Excited for day 2!! π
Last night, a client thanked and recommended us in front of a room full of people. π€―
They hosted their ORM warm-up event and announced the MVP of an AI product we're building together, and completely surprised us with a shoutout in front of everyone. π±
Afterwards, several (some big) businesses came up to us because of it. A few might turn into clients. π₯°
What a start!!
Now two days of ORM. Let's see what else comes out of it. π
Looking forward to meeting a bunch of people (like @robin_faraj and some others).
We're heading to Hamburg for the OMR Festival (70k visitors) π₯°
But before that, @AamirBuilds and I are making a quick stop today at a small private event from one of our clients. Fun fact: it's the FIRST time in FeatherFlow's history that we're meeting a client in real life. Crazy. π
Wish us luck!
A potential client wrote us last week:
"I'll vibe-code the app myself first to get quick user feedback. Let's talk again in 3 months."
As a product studio, the easy answer would have been: "Sure, hit us up when you're ready."
Instead, we wrote back: Don't build anything yet.
The process we recommend:
User interviews β extract insights β understand the problem β product concept β THEN vibe-coding.
Why that order? Because users react to what they see, not to what they actually need. With a prototype, you get feedback on the prototype, not on the problem.
He didn't cancel the call. We talked.
Within 40 minutes, something became clear that he hadn't seen so sharply himself: his idea was trying to solve three problems at once. The actual core problem was just one.
He's going out now to talk to his target audience. No prototype. We'll talk again after that.
Sometimes the best sales move is to say: don't buy anything yet.
Had a call with a potential client yesterday.
He's a vibe coder, building a real estate product, no idea where his code lives, never used GitHub etc.
How did he find us?
I asked him and...
ChatGPT recommended us. π€―
People often ask me what we're currently working on. So here's a peek π
β A mobile app in the mental health space. Product & development.
β A client & internal hub for a luxury travel agency. Product, design & development.
β An AI platform for an AI consultancy. Product, design & development.
β An invoicing layer and new functionalities on top of a healthcare document processing AI product we built.
β A B2B Buyer Engagement Platform. UX.
β A full product design for an AI tool in the mechanical engineering space.
And if all goes well, we'll soon be adding:
β A platform in the real estate space
β An AI agent project
β Some other smaller projects
I am INSANELY thankful!! πππ
A client we are working with just secured their first round of investment. π₯³π₯³
When they (very experienced team!) first came to us, the product had potential, but it wasn't investor-ready.
So we went deep with them:
β’ Rethought the entire product UX
β’ Redesigned the core platform experience
β’ Built a new public website
β’ Created a dedicated investor website
The goal was simple:
Make the product instantly understandable, credible, and compelling.
Ideas are important for investors.
But investors fund clarity, vision, and execution.
Seeing the round close after that work is the best validation.
Now that the round is secured, we'll continue working with them expanding and refining other parts of the platform. LFG! πͺ
built an EdTech platform that cut manual work by 30% with AI.
here's the biggest mistake i see in B2B AI right now:
most teams add AI as a feature.
thatβs the wrong move β
in 2026, the winners will build context-first AI.
why?
AI without full context is guessing.
if itβs not connected to:
β historical user data
β real workflows
β every step users take
it might respond faster,
but it'll often be wrong.
we saw this firsthand.
a teacher asks:
"what should this student improve next?"
without context β
"they're strong in all areas."
with full context β
specific weaknesses, clear next steps, real insight.
that's how we achieved:
β 30% less manual prep
β better decisions, not just faster ones
AI shouldn't sit on top of your product.
it should understand it.
that's the difference between a gimmick
and a real competitive edge.
4 months ago, I brought Aamir on at FeatherFlow as a Technical Project Manager.
Best decision I made last year!
@AamirBuilds took ownership of projects from start to finish.
β Technical planning
β Managing the devs and timelines
β Handling client communication
That alone took a massive amount of stress off my shoulders.
It freed me up to focus on strategy, partnerships, and where FeatherFlow is going next instead of being deep in day to day project management (managing 5+ projects the same time before).
Ownership matters a lot to me.
Aamir does not just help out on projects. He fully owns them.
This is how we want to build FeatherFlow.
Designing and building real AI products that are well thought through and ready to scale.
Grateful to be building with people like this.
And we're just getting started.
Please go and follow @AamirBuilds !!