Taking on new projects
Client portals, dashboards and internal systems for small businesses — and for the agencies whose clients ask for more than a website.
Who you get
12
Production apps shipped
10
Clients delivered for
4
Years, longest single client
5+
Years building professionally
What we build
Three systems we built, and use every day.
Client projects sit under their own agreements. We can talk through those on a call.
How we work
The failure mode in this industry is silence between the quote and the launch. Every step below exists to remove it.
One call, then a written scope. What it does, what it does not do, what it costs, and the date it lands.
A weekly demo on a real URL. You use it while it is being built, not the week after it is finished.
Repo, environment variables, deployment steps and a walkthrough recording. You could hire someone else tomorrow and they would not be stuck.
A support window after launch. After that, an hourly rate — not a retainer you cannot leave.
The difference
Who you get
Led by Munib
Led by Munib
Led by Munib
Specialist — brought in per project
Specialist — brought in per project
Specialist — brought in per project
I lead delivery, and I bring in specialists when a project needs them. No account manager between you and the work.
Anatomy of a build
Multi-tenant workspaces with role-based access and page-level grants. Every team sees exactly what it should — and nothing else.
Invite flows and approval requests, so new people join with the right access from day one instead of a shared login.
Orders live next to the pipeline, and when a deal dies the reason is recorded where the next decision can actually use it.
Revenue analytics on top, and cron-driven reminder emails underneath — the system chases the follow-up so nobody has to remember to.
For agencies
Your client asked for a portal, a dashboard or an integration. You do not have to say no, and you do not have to hand them to someone who might keep them.
Your name on the work. Ours nowhere — not in the repo, not in the footer, not in an email to your client.
Unless you put us in the room, and then we are your team. We do not pitch, we do not swap contact details, we do not follow up afterwards.
Fixed scope and dated milestones before anything is built, so you can put a number in front of your client and stand behind it.
Repo, environment variables, deploy steps and a walkthrough recording — written down, so the next developer is never stuck.
“We got the repo, the deploy steps and a walkthrough recording. Our own developer picked it up without a single call back.”
“I was clicking through the portal while it was still being built. No silence, no big reveal at the end — just steady progress I could see.”
“The scope we agreed on the first call is the scope that shipped. The date did not move and neither did the price.”
“Our client still thinks our in-house team built their dashboard. That is exactly what we paid for.”
“No jargon, no upsell. He asked what was broken in the business, then built the thing that fixed it.”
“Months in daily use and the reminders, reports and approvals still do their job without anyone touching the code.”
“He told us half our wishlist was not worth building yet, and quoted only the half that was. You do not forget that.”
“We resold the build under our own name, at our own price, and every email went through us. No leaks, no follow-ups behind our back.”
“A fix window after launch, then hourly when we need it. No retainer holding us hostage — which made us trust him more, not less.”
“Every call was with the person actually writing the code. Questions got answers on the spot, not "let me check with the team".”
Pricing
Small businesses that need one system built properly.
Fixed quote/ after the scope call
Book the scope callAgencies whose clients ask for more than a website.
Per project/ quoted so you can re-quote it
Talk it throughQuestions
Based
Pakistan
PKT (UTC+5) — full overlap with UK and EU hours, mornings with US East
Full UK & EU overlap, mornings US East
