ZAKA ULLAH WAHEED · OPEN FOR REMOTE WORK · ISLAMABAD
Fixed-scopework.
Five defined pieces of work. Each one has a clear list of what you get, what I need from you, and what is not included, so you know where you stand before anything starts. No price on this page: you get it in writing, with the scope and the timeline, before you decide.
01 Website health audit02 Automated tests for your web app03 A fast marketing website in Next.js04 Automate one repetitive workflow05 Quality checks for your AI feature
01
Website health audit
For: Anyone with a live website who suspects it is slower, less secure or harder to find than it should be.
I run your site through the same checks as the free site-health tool, go through it by hand, and give you a written, ranked list of what to fix and how.
TYPICAL TIME3 to 8 working days
Ask about thisWhat you get
- A written report on security headers, search basics, speed hints, accessibility basics and broken links
- Every finding ranked by how much it matters, each with the exact fix
- A walkthrough call to go through the report together
- Optionally, the fixes themselves as a follow-on piece of work
What I need from you
- The address of the site, and a staging copy if there is one
- Anything you already know is broken or slow
Not included
- Making the fixes (quoted separately)
- Penetration testing or a legal accessibility certificate
SEE SIMILAR WORKTry the free checkZong Health Scanner (case study)
02
Automated tests for your web app
For: Teams that ship often and are tired of finding bugs after release.
A Playwright test suite for the journeys that matter most, running automatically on every push, with reports your whole team can read.
TYPICAL TIME2 to 4 weeks
Ask about thisWhat you get
- Automated tests for the critical journeys we agree on (sign-up, login, checkout...)
- The tests run in your CI on every push, with a clear pass or fail result
- A readable structure, so your team can add tests later without starting over
- A short guide to running and extending them
What I need from you
- Access to a test or staging environment
- The list of journeys that matter most
- Test accounts or test data
Not included
- Load and performance testing
- Fixing the bugs the tests find (quoted separately)
- Native mobile apps (web apps only)
SEE SIMILAR WORKZong Health Scanner (case study)QA with Zaka (case study)
03
A fast marketing website in Next.js
For: A business, product or person who needs a site that loads quickly, looks good and can actually be found.
A responsive site of up to five pages built in Next.js and React, with the search basics done properly and the speed and accessibility checked before launch.
TYPICAL TIME1.5 to 3 weeks
Ask about thisWhat you get
- Up to five pages, responsive from phone to wide desktop
- Titles, descriptions, sitemap and structured data set up for search engines
- Speed and accessibility checked before it goes live
- A contact form that works, deployed to your own hosting account
What I need from you
- Your text and images, or a short call to shape them
- Designs or a clear reference to follow (design help is possible and adds time)
Not included
- Writing all of your copy
- Ongoing SEO campaigns or advertising
- Online payments or user accounts (bigger pieces, ask me)
SEE SIMILAR WORKThis portfolio (case study)GlamourHub (case study)
04
Automate one repetitive workflow
For: Anyone who copies things between tools every day: leads, reports, notifications, data entry.
One workflow built end to end with n8n, with an AI step where it helps, connected to the tools you already use.
TYPICAL TIME1.5 to 3.5 weeks
Ask about thisWhat you get
- One workflow, built and tested from trigger to result
- Connected to your tools through their APIs
- Error handling and alerts, so it does not fail silently
- A one-page description of how it works and how to change it
What I need from you
- A clear description of how the process works by hand today
- Access to the tools involved (accounts or API keys, shared safely)
Not included
- Several workflows at once (each is its own piece)
- Tools that offer no API or export
SEE SIMILAR WORKZong Health Scanner (n8n alerts, case study)
05
Quality checks for your AI feature
For: Teams shipping a chatbot, an assistant or any feature built on a language model, with no way to tell whether it got worse.
A test suite for your AI feature, built with llmcheck, the open-source tool I wrote for this: the facts it must get right, the things it must never say, run repeatedly so a flaky answer shows up, and wired into CI.
TYPICAL TIME1.5 to 3.5 weeks
Ask about thisWhat you get
- Test cases written from your real prompts, policies and past mistakes
- Checks for facts, format, refusals, prompt leaks and injection attempts
- Repeated runs with a pass rate, so one lucky answer does not hide a flaky one
- A CI job and a readable report (JUnit and Markdown) on every pull request
What I need from you
- Access to the feature or its endpoint (a test key with a spending limit)
- Your system prompt and policies, and examples of answers that were wrong
- Someone who can say what a correct answer looks like
Not included
- Improving the model or rewriting your prompts (quoted separately)
- A guarantee that the feature never fails: tests find what you thought to test
- Legal, safety or compliance sign-off
SEE SIMILAR WORKllmcheck, the tool behind itQA with Zaka (has an AI assistant, case study)
HOW IT WORKS
Four steps, nothing hidden.
- 01
A short call or a written brief
You tell me what you need. If it fits one of the pieces above, we start from that; if not, we shape it together.
- 02
A written scope, timeline and price
Before any work starts you get all three in writing, and you approve them. Anything outside the scope is agreed separately instead of quietly growing.
- 03
Building, with regular demos
You see the work as it takes shape, so there are no surprises at the end.
- 04
Handover
The code goes in your repository, deployed where you want it, with short notes on how it works.
QUESTIONS
Before you write.
Is the price really fixed?
Every piece starts with a written scope, timeline and price that you approve before any work begins. If something outside the scope comes up, we agree on it separately instead of it quietly growing.
Where are you, and does the time difference matter?
I am in Islamabad, Pakistan (UTC+5), working Monday to Friday, 10:00 to 18:00. Most work is done by message and short calls, and the call helper on the hire page shows the overlap with your own time zone.
How long will it really take?
The timelines on this page come from the same estimator as the hire page: typical for one developer on a job of that size. I confirm or adjust them once I have read your real brief.
Can I see work like this?
Each piece above links to a project I built that is closest to it, with a case study of what was made and how.
My project does not fit any of these.
Most real projects do not fit neatly. Send a brief, or use the estimator on the hire page to get a rough timeline first.
Not sure which one fits?
Paste a job description or a rough idea into the estimator, or just send a brief. Either way you get a real answer, not a sales call.