Building at AI Speed: What Our AI-Driven Engine Means for Your Product
We are implementing a number of ideas that we have had for many years. All at once. That is neither a stretch goal nor a five-year plan. This is what Blink22's year looks like: our own products being built alongside our usual client work. We aren't starting from scratch here. Millions of people have used our products for many years. What's new is the pace, and how we got there reveals something about how software is built today.
Two Tracks, One Company
Blink22 has always done two things simultaneously.
We create products for our clients, turning their ideas into reality. That is work we love.
We also create our own products. It is important to consider both tracks. Both are Blink22.
Where the Services Track Took Us
Fifteen years of building software for other people makes you an industry leader.
Large companies trust us with the products their business runs on. We have built and shipped for major enterprises and government entities across the Gulf. Products with real users, real revenue, real consequences when something breaks. Some have been in our hands for years, through multiple platform migrations and complete rebuilds. We became the team a company calls when the product really matters.
Hundreds of projects made us one of the leaders in our space. It allowed us to build a team of engineers who have seen what works, what matters, and what it takes to turn an idea into a product people actually use.
It also kept us busy. Genuinely, continuously busy. That is what happens when you do outstanding work: clients stay, they come back with more, and they recommend you to others. Almost all of our growth has come through word of mouth, and the demand has never let up.
We’ve been so busy with client projects to focus on our own products. The product's track never stopped, though; it just did not get enough room to expand. We didn’t have capacity for building more of our products.
What Changed the Math
AI changed the math.
That sounds like every other post on LinkedIn right now, so let me be specific about what I mean.
Before, building a product meant assembling a team. Developers, designers, someone on market research, someone on go-to market. Every product carried the weight of a full team, which meant you built them one at a time and waited.
AI collapsed that. A single capable engineer with the right tooling now covers ground that used to need a full team before…. and covers it properly. Not because AI does the work for them, but because it removes enough friction that one person can operate across far more of the product than before.
We saw it first in our client work. We started noticing single engineers doing in a week what used to take a small team a month. People have argued about the 10x engineer for years, mostly as a myth. With the right tools in the right hands, it stopped being a myth.
Now a product carries the weight of a person, supported by everything the company already has. That difference is what makes building several products at once not just possible but the more logical path to take. Ten ideas that would have taken a decade sequentially can run together and find their markets in parallel.
What Sits Behind the Owner
A 10x engineer gets to be a 10x engineer because everything around them is already solved.
Design runs centrally and serves every product. So does market and user research. On the technical side there is security, QA, release and store operations, and infrastructure that every product plugs into rather than rebuilds.
On the business side there is pricing and monetization work, analytics, and the finance and admin machinery behind app store agreements and payouts. In marketing, there is positioning, store listings, creative, and growth work that spans several products rather than belonging to any one of them.
Each product owner also has a technical architect to work through the harder design calls with. Not oversight, just someone to think with when a decision is expensive to reverse.
Sitting under all of it is the accumulated judgment of building hundreds of projects for clients across the region over many years. That matters more than the tooling. We know what breaks. We know which shortcuts cost you later.
We know what a store listing needs to do, what onboarding failure looks like, and how a product behaves in the Gulf market specifically. You do not get that from an AI tool. You get it from having done it a few hundred times.
The Team of One
So we asked the obvious question: if one person can carry a product on top of that shared base, what happens when we point a team at ten different products?
That is roughly what we are doing.
It is not a clean one-to-one. Some people overlap across two projects. Some own a single product across multiple platforms: Android, iOS, and web. But the shape of it is that each product has one person who owns it.
We call it the team of one, and the phrase undersells it. Nobody is working in isolation. The one person is the owner. The company is the engine underneath them.
Why Multiple Products Simultaneously
Every product needs time to find its market. Time to be discovered. Time to pivot until what you built matches what people want. You cannot compress that. It is calendar time, not effort time.
When you launch them one by one, you restart that clock each time. Launch them together, and every clock starts simultaneously. You learn multiple markets in parallel, and the lessons cross over, because the person solving retention on one product sits next to the person solving it on another.
We are not guessing. Everything in the pipeline has been through research and validation. We have been collecting ideas for years. We are working through that pool and seeing which ones find their audience.
What We Are Building
Running this strategy for years has taught us enough to keep going with grounded confidence. The products we have live now are:
Fajr Calendar: a web app and iOS app (Android coming soon) that syncs prayer times directly into your calendar (Google, Outlook, etc.), helping Muslims build daily prayers into their existing work and personal schedules. It’s got a task manager and habit tracker as well.
Fajr App: A prayer companion iOS and Android app that was originally centered on waking users for Fajr through wake-up challenges, alongside prayer times, Qibla direction, Athkar, and a full Quran experience with recitation and tafsir.
Blink Alarm: An AI-powered smart alarm on both iOS and Android that helps you plan your whole day, with flexible snooze controls, offline reliability, and calming sleep sounds.
Rehla: A parental control iOS and Android app that helps parents manage and safeguard their kids' device use.
Hoya: A team recognition and work-performance tool that helps companies celebrate wins and keep culture strong as they scale.
Coming soon:
RM: An SME tool for resource management and running day-to-day processes
Blink Calendar: A complete productivity and tracking app
Friends Bell: A social/connection app, centered on staying in touch with friends and family
Fajr for Kids: A kid-friendly version of the Fajr experience
Qurany: A tool that allows you to learn Quran with tutors you choose for Tajweed, recitation, Hifz, and Arabic lessons on your own time and at your own pace.
Most of these are built for our region, in Arabic and English, by people who use them. And we are not stopping at this list. The pool of ideas is deeper than what is in it.
We Treat Your Product Like Ours
Building our own products does not pull from what we do for you.
We have never seen client work as taking a specification and implementing it. When a decision looks wrong to us, we say so. When there is a simpler path to what you actually want, we point at it. We argue about pricing, about onboarding, and about which feature can wait until version two. That is what it means to treat your product as ours, and it is the part clients tend to value most.
Running our own products sharpens that. We live with our own decisions on retention, pricing, onboarding, store performance, and everything we learn there goes straight back into the advice we give you.
If You Are Building Something
Some of the best work we do starts with a founder and an idea. Someone who has been carrying a product in their head for a year and needs a development team that will take it as seriously as they do.
We love that work, and a lot of what we have learned about building our own products came from it.
We also work with enterprises and established businesses. A new initiative to launch, a product that needs additional hands, systems that have been running on paper and spreadsheets for too long and need to be digitized properly.
Different starting points, same work. And in every case the useful question is not who can build it. Plenty of people can build it.
The question is who will tell you when it needs to change, who has watched enough products meet their market’s expectations to know which parts of the plan will survive contact with real users, and who will still be thinking about it after launch.
That is the work we do at Blink22, and we would be glad to work on your products with you.
