Creato - No code link-in-bio platform

Product Type

link-in-bio platform with
calendar management integration

Our Aim

a platform for creators to monetize their services


6 months

Tech Stack

Flutter Flow, Firebase, GCP


iOs, Android

Key Results

▫️ Ceator Signups: 214
▫️ Fan Signups: 102
▫️ Total Transactions: 170

As someone who always wanted to be a creator, Uzair recognized the gaps in the creator economy of Pakistan. On his journey to becoming a creator himself, he realised how little resources were available in the market, to help one get there.
More than just purely becoming a creator, he discovered an even larger gap in the market when it came to these creators monetizing themselves. Creators had to sign tough brand deals, with little to no room for creativity, to be able to earn a living.

“Any time I looked outside of Pakistan, I saw how good creators were doing, how they were monetizing their content, their services, with so much ease. I wondered why people didn’t use the same products here, and I soon realised that the platforms were either priced in USD, or there was a language barrier, or the payment method was unavailable, or simply, some products were just not available for Pakistan. This pushed me to dream of a product, that was localized for our audience, with local payment integrations, and in a language we all understood.’ -Uzair, founder of Creato

Uzair soon turned to his friends, discussing the product he had in mind, and through a mutual, stumbled upon Muhammad and alt sprints. From the website, he learned about no-code and low-code tools. He first took the decision of making the app himself after watching a couple of YouTube videos, however after realizing the complexity of the tool, he reached out to alt sprints.


Uzair wished to create a tool that had two sides to it, a creator side, and a fan side.

The creator side had two primary functions: i) calendar management system, ii) selling services/digital products.

For the calendar management system, he wanted to connect the the app to a person’s already existing calendar, so it can sync. He also wanted the individual to be able to set their availbility inside the app, and price their calls at whatever value they pleased. He then wanted the fan side to be able to view the available times, and book a slot after paying the set fees.

The second part of the creator app was the selling of digital services and products. In this part, people could enlist their services or digital products, and the fan side would be able to access this easily behind a url after paying the amount set by the creator. The trick here was to ensure URLS were single-use.


We got on a call with Uzair to determine if he was a right fit for alt sprints. Soon after, we assigned a designated product manager to the project, who helped scope out the entire project for 1 month. This scope included figma designs, protyping, user analysis, a structured database, app tear downs, competitor analysis, and more. During the scoping phase, we also worked closely with two engineers and one growth head who helped us set realistic deadlines for the deliverables. Once everything was locked, we began development.

What followed were weeks after week of releases. As we gave Uzair a designated team, we decided to organize our sprints to a one-week release format, as opposed to our usual two-weeks. We released build after build, pushing features live, testing them out, iterations and reiterations, until it was perfect.

Number of releases: 74 builds.

While our engineers were set out to ensure the product was worth using, our growth team of, not more than two people were ensuring the product was distributed aptly. We are of the firm belief, that while the product can be amazing, if not distributed properly, the best of the best products can fail. So after an initial month of cold calling and emailing, essentially using the push methodology, our growth team decided to create a pull for the product.

Reached out to 700 individuals, spoke to over 400 of them.

The pull methodology worked. But what did this methodology entail? They began building in public. Wasn’t so hard for them as our engineers were already giving their blood, sweat, a tears (sometimes literally) to ensure there was a release every week. All the growth team had to do there was ensure the world knew of the product this team was cooking. The team activated their socials, put out content, they posted an update about their releases every week, and to no surprise, landed their first, second, third customer.

The Results

book a demo