Skip to content
Zapp Studios

HAMZA ZULQUERNAIN · FRACTIONAL CTO · HOUSTON

I build the software your business runs on. Then I hand your team the keys.

Your website, your ads, and the back-office system your staff use every day, built alongside your team in about three months. After that, your people make the small changes themselves with Claude, and I stay on call for anything that breaks.

  • 55 changes

    shipped in-house by a client's owner, with Claude, in the first month after handoff (Aug 18 – Sep 11, 2026). I made one.

  • 2

    back-office systems built with owner-run businesses and handed over in 2026.

  • 12×

    monthly revenue by month six at Royal Pawz, where I'm an equity partner.

  • 7-figure exit

    founding engineer, DietAI.

Recent work

Production software, not a slide deck.

a Houston-area wholesale distributor

Website and back office · handed over in August 2026

I built it with the owner. Then he took over the changes.

I built a new website. Then the owner and I built a back office for reorders, purchasing, pricing, delivery and sales. He started building alongside me in June. At handoff in August, the owner had the code, a How-To Guide built into the app, and Claude set up so he could change it himself. I am still on call.

55 of 56
changes after handoff, made by the owner
59
back-office screens
24
chapters in the staff guide built into the app
Changes to the software, by who made them

From April to July I made most of the changes, and the owner joined in from June. After handoff on August 17 that flipped. From September 1 to 11 the owner made 52 changes and I made 1.

Changes to the software, by who made them
MonthThe ownerMe
Apr016
May031
Jun638
Jul945
Aug324
Sep 1–11521

Each bar is a month of changes. The software is the website and back office of a Houston-area wholesale distributor. The last bar is September 1 to 11.

a Houston meal-prep brand

Ads, online store and back office · 2026

Ads, a faster storefront, and a back office for the kitchen.

I rebuilt their storefront. I also built the order messages that made a second weekly delivery day possible. Then I built a back office for cook plans, kitchen sheets, stock, purchasing and costing. I handed it over in September, and the team is early in using it day to day.

55 / 55
kitchen-sheet checks that matched the owner's own records
98.8 / 100
score reading 12 real supplier invoices
16 → 5
screens, after we simplified the back office
2,430
automated tests

We still work together: I run their Google Ads and I'm building what's next.

Royal Pawz USA

Houston · Mobile dog grooming

12× monthly revenue by month six.

Google Ads, a landing page, online booking and text follow-ups. I built it and run it as one system.

16 → 136
grooms per month, December to the May peak
30.8%
booking conversion, up from 7.1% (A/B tested)
52%
of revenue from repeat customers by June, up from 13%

Working with Zapp Studios completely transformed our business. The booking system they built and the way they optimized our funnel - we went from barely getting customers online to having a system that just works.

Owner, Royal Pawz USA. I'm an equity partner there.

Sound familiar?

  • Orders arrive in five places.

    Your site, email, phone calls, texts and a web form. Someone copies them all into one list by hand.

  • The same sheets get rebuilt every week.

    Order sheets, price lists, the weekly plan. Someone rebuilds them by hand, and one typo costs you.

  • You pay for a tool nobody uses.

    It was meant to fix the mess. It never fit how your team works, so the spreadsheets stayed.

  • Your developer went quiet.

    A freelancer built part of it, then stopped replying. Nobody knows how it works or who has the logins.

How it works

Built with your team, not handed over the wall.

  1. Scoping Sprint

    7–10 business days

    We map how your business runs today and decide what to build. You get a written plan and a fixed price for the Build.

    Fixed price. Credited in full toward the Build if it starts within 30 days.

  2. Build

    About 3 months

    I build your website, ads and back office alongside your team. Your staff use each part as it ships, so nothing lands as a surprise.

    Fixed scope, agreed in writing after the Sprint.

  3. Handoff

    End of the Build

    Before I step back, your team gets the keys and the guardrails. Every handoff includes the same things.

    Part of every Build.

  4. After handoff

    Your choice

    You pick how much of me you need. The standing warranty on my work stays in place whatever you pick.

    • Self-serve with on-call supportYour team makes the changes. When something breaks, you text me and I pick it up.
    • Self-serve, pay per fixYour team makes the changes. When you need me, you pay for that fix and nothing more.
    • Monthly fractional CTOI stay on as your part-time CTO. Each month we plan, build and review the work together.

Owned, not rented.

Every handoff includes:

  • Your code and accounts in your company's name
  • Claude set up for your team
  • Checks that run on every change before it goes live
  • A preview link for every change
  • A runbook
  • A staff guide

Changes that touch payments, security or your database come to me before they go live.

Standing warranty: if something I built doesn't work the way we agreed, I fix it. No invoice, no end date.

How this compares

Each option is right for some businesses. Here is how they differ.

How this compares
Zapp (fractional CTO)AgencyFreelancerFull-time hireDIY with AI
Who owns the codeYou do, with the accounts in your company's name.Depends on the contract.Depends on the contract.You do.You do.
Who can change itYour team, with Claude. Payments, security and database changes come to me before they go live.Mostly the agency.Mostly the freelancer.Your hire.You.
Hands-onYes. I build it with your team.Through a team, often led by an account manager.Yes, on the task you hire them for.Yes, every day.Yes. It's you.
When it breaksYou text me and I pick it up. Fixes to my own work carry no invoice.A support plan or a new ticket.Depends on their schedule.They fix it, while they work for you.You fix it, or find someone who can.
CommitmentA fixed-price Sprint, a fixed-scope Build, then your pick.A project contract, often with a support plan.Per task or per project.A salary, benefits and the time it takes to hire.Your own time.

Zapp (fractional CTO)

Who owns the code
You do, with the accounts in your company's name.
Who can change it
Your team, with Claude. Payments, security and database changes come to me before they go live.
Hands-on
Yes. I build it with your team.
When it breaks
You text me and I pick it up. Fixes to my own work carry no invoice.
Commitment
A fixed-price Sprint, a fixed-scope Build, then your pick.

The other options

Agency
Who owns the code
Depends on the contract.
Who can change it
Mostly the agency.
Hands-on
Through a team, often led by an account manager.
When it breaks
A support plan or a new ticket.
Commitment
A project contract, often with a support plan.
Freelancer
Who owns the code
Depends on the contract.
Who can change it
Mostly the freelancer.
Hands-on
Yes, on the task you hire them for.
When it breaks
Depends on their schedule.
Commitment
Per task or per project.
Full-time hire
Who owns the code
You do.
Who can change it
Your hire.
Hands-on
Yes, every day.
When it breaks
They fix it, while they work for you.
Commitment
A salary, benefits and the time it takes to hire.
DIY with AI
Who owns the code
You do.
Who can change it
You.
Hands-on
Yes. It's you.
When it breaks
You fix it, or find someone who can.
Commitment
Your own time.

What it costs

Every phase is priced before it starts.

  1. Scoping Sprint

    A fixed price, set up front. Credited in full toward the Build if it starts within 30 days.

  2. Build

    A fixed scope, priced in writing after the Sprint.

  3. After handoff

    You pick how much of me you need: on-call support, pay per fix, or a monthly fractional CTO.

Who you work with

Hamza Zulquernain

Fractional CTO · Zapp Studios · Houston

Based in Houston, working with owners here and remotely.

I take pride in this work, and I stay with it after it ships. The job is done when your business gets real value from it and your team can run it.

  • Founding engineer, DietAIBuilt the product, the funnel and the growth systems through a 7-figure exit.
  • Equity partner, Royal Pawz USA12× monthly revenue by month six.
  • Two back-office systemsBuilt with the owners and their teams, and handed over in 2026.

Other ways to work with me

  • Founders

    Fractional CTO for founders. The same phases, starting with a free 30-minute call.

    For founders →

  • Vibe-Code Rescue

    You built an app with an AI tool and it has stopped holding up. I audit it, fix what matters, or rebuild it.

    Rescue an app →

  • Equity Partnership

    Less cash up front and a real stake in how your business does. It starts with a paid two-week pilot.

    Partnerships →

Questions owners ask

What's a fractional CTO?

A part-time head of technology. I decide with you what to build, build it with your team and look after it, without you hiring a full-time executive. For an owner-run business, that usually means your website, your ads and the back office your staff use every day.

Do we own the code and accounts?

Yes. Your code, your data and every account sit in your company's name, not mine. That is part of every handoff. If you ever want a different developer, you hand them the keys and they pick up where I left off.

Can a non-technical team really make changes with Claude?

Yes, for the small changes that come up every week, like a new field, a new report or a tweak to a screen. During the Build, the person who will make changes works next to me. That way they learn the system as it grows. At a Houston-area wholesale distributor, the owner made 55 of the 56 changes in the month after handoff, using Claude.

Is it safe to let staff change our software with AI?

It is when the guardrails are in place, and every handoff includes them. Checks run on every change before it goes live. Every change gets a preview link your team can click through. Changes that touch payments, security or your database come to me before they go live. And every change is on record, with who made it and when.

What happens when something breaks?

When something breaks, you text me and I pick it up. If the cause is in my work, there's no invoice. That's the standing warranty, and it has no end date. If the cause is a later change, an outside service or a new feature, it falls under the support option you picked at handoff.

What if you disappear?

Your software keeps working. The code and accounts are in your name, the runbook and staff guide explain how it fits together, and your team already makes the everyday changes. Any good developer can pick it up from there.

How is this different from an agency, a freelancer or a full-time hire?

An agency builds for you and usually stays the one who can change it. A freelancer builds the piece you ask for. A full-time hire makes sense once there's a full week of work every week. I sit in between: I plan and build the whole system with your team, then hand it over so you don't need me for the small things.

Wouldn't a developer on payroll cost less over time?

Sometimes, once there's steady work for one every week. Many owner-run businesses aren't there yet. They need a burst of building, then small changes. So I build the system in about three months, your team takes over the small changes, and you keep as much of me as you need. If a hire makes sense later, I'll help you make it and hand over to them.

How much of your time do we get?

During the Build, I work on your system every week and you see progress every week. After handoff, it depends on the path you pick: on call when something breaks, pay per fix, or a set share of each month as your fractional CTO. We agree the time in writing before it starts.

What size business is this for?

Owner-run businesses with a team. The daily work lives in spreadsheets, inboxes and tools that don't talk to each other. In 2026 I handed over systems to two of them. One is a Houston meal-prep brand. The other is a Houston-area wholesale distributor. If you're a founder still building a product, see the founders page.

What does Claude cost us after handoff?

Your team pays for Claude directly, at Anthropic's published price. It's a monthly plan for each person who makes changes, and the bill goes to you, not through me. I help you pick the right plan during handoff.

What if Claude changes or goes away?

Your software runs without Claude; Claude is how your team edits it. The code is standard and lives in your accounts, so any developer or another AI tool can work on it. If the tools change, I will help your team switch.

Can we start small?

Yes. Every engagement starts with the Scoping Sprint: a fixed price, about two weeks, and a written plan you keep whether or not we build. If the Build starts within 30 days, the Sprint is credited in full.

Let's see if this fits your business.

Answer a few questions, then book a 30-minute call. We'll talk through how your business runs today, what's worth building and what isn't. You'll leave with a clear next step, whether or not it's me.