One person owns your build.
A senior team ships it.

I’m Shahzad. I’ve been building apps for seven years and I run a small senior team. When you work with us, you talk to me. I decide how your product is built and I review the important parts myself. If something goes wrong, I’m the one who tells you. We mostly build mobile applications with Node backends, and we also do Stripe payments, AI features and Bluetooth hardware.

The Blocship teamShahzad, founder & principal engineerSets the architecture on every build.
6,000
drivers on one platform we built
30+
products shipped and live
7 yrs
building apps for clients
6
regions we work with: UK, Australia & NZ, Hong Kong, MENA, Palestine, Europe

Four products, and what broke on each.

Things break once people start using an app. I’d like to show you what broke on these four and what we did about it, so you know what working with us is like when it gets difficult.

See all work →
The Courier App screen 1
The Courier App screen 2
The Courier App screen 3

The Courier App

Logistics · Full-stack

10K+ downloads

Did

A delivery company’s app for its drivers. They sign up, get onboarded and run their daily deliveries on it.


Built

The app we were given was slow, and the code couldn’t handle more drivers, so we rebuilt it. It now runs for 6,000 drivers.

Broke

Someone hit the sign-up endpoint with a DDoS attack while new drivers were trying to join.


Fix

We put Turnstile in front of sign-up. The attack stopped and the app never went down. Sign-up got faster afterwards, and the client’s hiring data got cleaner.

“If I could relocate Shaz to the UK, I wouldn’t let him out of our reach. That probably says enough on its own.”

Chris Hamilton, CEO · The Courier App

Balsam screen 1
Balsam screen 2
Balsam screen 3

Balsam

Social · Full-stack

3 apps, one platform

Did

An app where people talk to trained listeners by chat, audio or video call when they need someone to hear them out.


Built

We built all three parts: the user app, the listener app and the admin panel. Users pay with coins bought through Stripe, in Arabic or English.

Broke

Calls didn’t come through when the app was in the background. If the app was closed or the phone was locked, a user could call a listener and it would never ring.


Fix

We built native background calling with a wake-up, so the phone rings like a normal call even when the app is closed.

“I trust you, my friend, and I sincerely hope we continue maintaining and strengthening this trust throughout our long-term partnership.”

Dr. Ali, Founder · Balsam

United Arab EmiratesRead the full case study →
YDigest screen 1
YDigest screen 2
YDigest screen 3

YDigest

AI · LLM pipeline

500K → 10K API calls

Did

An app that turns YouTube videos into transcripts and summaries. You follow the channels you like and new summaries show up in your feed, in the format you choose.


Built

It came to us as a vibe-coded prototype. We rebuilt the data layer under it so it could handle many more users.

Broke

Supabase was logging 500,000 REST calls. Requests were running away and there were a couple of memory leaks, so the bill kept going up and the app kept getting less stable.


Fix

We added caching, found the leaks and fixed them. The same product now makes 10,000 calls, which is 98% less.


Calcount Australia screen 1
Calcount Australia screen 2
Calcount Australia screen 3

Calcount Australia

Mobile · Nutrition

70K+ users a year

Did

A free calorie-tracking app for Australia and New Zealand. The client already had a web product with over 70,000 users a year. The app covers local foods and has a barcode scanner.


Built

We turned their web product into a mobile app and connected the barcode scanner to a nutrient database made for the region. We also added AI meal logging, using Gemini to read photos and voice notes.

Hard part

Nutrition numbers have to be correct. If someone is counting calories, a wrong barcode match or a US figure is worse than showing them nothing.


Fix

We check every scan against an AU/NZ food database, so people get the local number for what they’re eating.


The hard parts we’ve done before.

Some parts of a build can delay a launch by weeks if the team is doing them for the first time. These are the ones we have already shipped, so we know where they go wrong.

SEPA

SEPA & virtual IBANs

Direct-debit mandates, credit-transfer reconciliation, and the webhook lifecycles that SEPA requires.

PAY

Stripe Connect split-fee

Marketplace payouts to connected accounts, convenience + management fees, subscription paywalls.

RTC

Real-time video (Agora / WebRTC)

Stable join → live → reconnect lifecycle, secure token handling, cross-device reliability.

BLE

BLE & device sensors

Barometric floor detection, hardware pairing, and dealing with noisy sensor signals.

SaaS

Multi-tenant + AI agents

Platform plus client instances, with LLM workflows that keep working once customers use them.

SHIP

App Store & Play submission

Metadata, permissions and compliance handled so your build passes review without technical rejections.

How I’d run your project.

This is how I work through a project, so you can see how I think before you decide anything.

01

I check what you already have

Before we write any code, I look at what’s worth building and what isn’t. If you already have a half-built app, I go through the code myself and tell you what to keep and what to rewrite, and why.

02

The risky parts go first

Payments, integrations and hardware are where projects usually get stuck. We build those first, so if there’s a problem we find it early and you still have time and budget to deal with it.

03

You see working software early

You get something you can install and use within weeks. My team uses Claude every day, which is a big part of why we’re fast. I still review every important part before it goes live.

04

I keep you updated in writing

You’ll know what’s done, what’s next and what might be a problem, without having to ask. After launch we stay on, because your product will keep changing and it helps to have the team that built it.

Three ways we can start.

Some things are in my control and some aren’t. Apple and Google review times are one example. I’ll give you dates I believe we can hit, and if something puts a date at risk I’ll tell you as soon as I see it.

Full build

From $3,200 · 4–6 weeks

You bring the scope, and I work closely with you on which features are worth building for the business. Then we design the architecture, build it and get it through App Store and Play review.

You get

The full codebase with complete documentation, plus every important file that goes with the project.

Maintain & scale

$800 / month · 10 hours a week

We stay on after launch for fixes, new features and scaling. You keep the team that already knows your product.

You get

Work happens on weekdays, and you get quick replies from me then. On weekends I still reply, just slower. Every week you get a report of the bugs we fixed and any new features we shipped.

When we’re not the right fit

If you need fifty developers, or someone who agrees with everything you say, we’re the wrong choice. We’re a small team. If I think we can’t help, I’ll tell you on the first call, so you don’t spend money finding out. We do sometimes place one of our developers in a client’s team. When we do, I stay on as lead and review their work.

Who you’ll be working with.

You talk to me about the plan, the architecture and the difficult decisions. The building is done by me and a small senior team, so your project doesn’t depend on one person. If one of us is off for a day, the work keeps moving.

  • Shahzad Umar BaigFounder & principal engineer · architecture and the difficult decisions
  • Abdullah AhmedSenior mobile app developer · builds the apps, Android & iOS
  • Affan MinhasSenior mobile app developer · builds the apps, Android & iOS
  • Anwar SiddiqiSenior mobile app developer · builds the apps, Android & iOS
  • Tanzeel BhattiProject manager · timelines, weekly updates and keeping the build on track

Tell me what you’re trying to build.

Send me your PRD, your half-built app, or just the idea as it is now. I read everything myself and reply within 24 hours with what I think, including if we’re not the right team.

Rather not fill anything in?

Fifteen minutes with me.

Pick a time that suits you. The times show in your own timezone, and I’ll have read whatever you sent before we talk.

  • You’ll be talking to me, the person who builds it.
  • Bring a PRD, a half-built app, or just the rough idea.
  • By the end you’ll know the rough scope, the likely cost and whether I can help.
See available times →