Muhammad Rashid Nawaz
Clients · SEO & GEO · Web
Your point of contact from first call to invoice. Leads the SEO and AI-search work this site practices on itself, and the web builds that carry it.
LinkedInAbout
One team for the whole route.
System Routes is an engineering team led by its partners, working with clients across the US, UK, Europe and the Gulf. We build with AI in the loop and sign every piece off by hand, and we take responsibility for the route end to end: from the search result that finds you, to the system that closes the sale, to the infrastructure that keeps it standing at 3am. We run businesses on the same systems, and the numbers from those are published on this site.
The name is the method. Our mark is a route with stops on it, because that's what a customer does with every business: they find you, they choose you, and they need you still working afterwards. Every service we sell is a stop on that route, and the value of one team owning all of it is that nothing gets lost at the handoffs.
The disciplines
Who owns each part of the work?
Work splits into three disciplines. Each is owned by a partner who does that thing all day, with specialists brought in as the scope requires. One route, one thread of communication.
The partners
The people on the route.
Partners who work US, UK, European and Gulf hours. You always know whose hands your work is in.
Abubakar Riaz
SaaS · CRM · AI agents
Builds the products: SaaS builds, custom CRMs, including the one our own operation runs on, and the lead-generation tooling and AI agents behind them.
Shazib Mustafa
Backend · Cloud · DevOps
Owns everything below the waterline: backend engineering, AWS and cloud infrastructure, deployments, and the uptime that keeps it all standing at 3am.
System Routes · hello@systemroutes.com
How we build
AI-native workflows. Human accountability.
24
products, roughly, in four months
7
days to ten tools taking payments
50.4%
of a store's sessions from AI assistants, Aug 2026
We build with multi-agent AI systems the way other teams use an IDE. It is why roughly two dozen products shipped in four months, including the ones we own and operate, and why a tool suite taking live payments went from nothing to live in seven days. The research is honest about the catch: Google's DORA study found AI raises output but breaks delivery where the foundations are weak, and a randomised trial found experienced developers slower with AI while believing they were faster. So every system here ships with the parts that make speed safe: guard rails before destructive operations, confirm-before-send policies, a partner signing off where a mistake would cost money, and a written post-mortem when something breaks anyway. The speed is AI. The accountability is people.
See what that producesNow
What we shipped lately.
Dated, newest first, so you can see how current it is. Some of it is client-facing, some of it runs our own operation.
- Sep 2026Monthly AI-traffic data, publishedFourteen months of first-party analytics on how much of a store's traffic comes from AI assistants, refreshed as each month closes.
- Aug 2026AI search visibility, as its own serviceMeasuring and fixing whether ChatGPT, Perplexity and Google's AI answers recommend a business, starting with a free check.
- Aug 2026An AI-crawler logger on our own siteEvery visit from the crawlers behind ChatGPT, Claude, Perplexity and Google's AI features, recorded as it happens.
- Aug 2026A search watchdog that runs itselfTracks search-engine and AI-crawler policy changes and our own rankings every day, and reports when something moves.
- Aug 2026Modern UI, publishedA Claude Code skill built from fifty-five well-made sites: thirteen written playbooks and seven agents that apply them.
Working rules
What we hold ourselves to.
Not values-page poetry. Working rules, each one already visible somewhere on this site.
Price fixed before work starts
Scope and number agreed in writing before anything begins. Changes get re-scoped in writing too, never discovered on an invoice.
Your repository from day one
Code, CMS, analytics and every credential live in accounts you own. If we part ways tomorrow, you lose nothing.
A working demo every Friday
Progress is something you click, not a status report. You watch the build grow week by week.
Thirty days of fixes after launch, free
Launch isn't a handoff cliff. What surfaces in the first month gets fixed as part of the job.
We publish our mistakes
Our case studies include an incident we caused ourselves, written up with the guard rail that made a repeat impossible. Judge us by how we handle being wrong.
No manufactured proof
No invented testimonials and no numbers we cannot show the working for. Everything we claim is clickable, and where a client's results are not ours to publish, we show our own instead.
Book a call
Pick a time that suits you
Thirty minutes, no pitch, and an honest answer at the end of it. The calendar is already showing your timezone.
Loading the live calendar…
Real availability, already in your timezone.
or send details first
Rather write first? Send an enquiry instead.