Skip to content
Toronto · Replies in 24 hours
Bilal Khan
Bilal Khan I write—and stand behind—every reply.

For technical B2B teams with a growth bottleneck

Pick the bottleneck. I'll send you the first moves.

If Google is swallowing clicks, content is moving too slowly, or your stack cannot support the next move, choose the constraints costing you most. Within 24 hours, I’ll send the sequence I would use, the tooling I would reach for, and what I would do first. Useful before you hire anyone. No call. No deck. No follow-up sequence.

  1. You get judgment, not a template

    I read the constraints, choose a point of view, and give you the sequence I would use.

  2. Your URL turns direction into diagnosis

    Reply with it and I’ll identify what to change first, what can wait, and what not to waste money on.

  3. The advice stays useful without a sale

    No nurture sequence. No SDR. If your team can do it internally, I’ll tell you instead of forcing a pitch.

The person diagnosing the problem is the person who would build the solution. One person, full stack, no relay race.

Get the first moves

Choose the constraints. I’ll reply with where I would start and why.

Where do you need leverage?

One useful reply, written by me. No SDR, calendar gate, or follow-up sequence.

540K+

Annual readers without a media budget

Built Quwa Defence Journal from zero to 540K+ annual visitors and 50K+ monthly readers—solo, organic, and cited by CNN and AFP.

15+

Live-data AI systems shipped

Built custom MCP servers on GCP Cloud Run that connect AI to GA4, Search Console, WordPress, BigQuery, and CRMs—so decisions run on evidence, not assumptions.

3 hrs

From blank repo to this site

Built and deployed this site on Cloudflare in three hours, with a 90+ performance score. The workflows offered here are the ones that built it.

Quwa / 2026 field data

Google put answers between the query and the click. Quwa grew anyway.

From 1 January through 27 July 2026, Quwa earned 916,469 clicks across Google Search and Discover, plus 2,826 attributable sessions from named AI assistants. The lesson is not “SEO still works.” Visibility compounds when you build for search, feeds, and answer engines together.

Finalized window
01 Jan — 27 Jul 2026
Sources
GSC + GA4
Comparison
Same 2025 period
01 Google Discover
833,988 clicks
+285% YoY
19.94M impressions · 4.18% CTR A second discovery surface became the primary acquisition engine.
02 Google Web Search
82,481 clicks
−7% YoY
7.29M impressions · average position 6.7 Fewer clicks, stronger rankings: the channel got harder, not irrelevant.
03 AI assistants
2,826 sessions
+57% YoY
ChatGPT 1,932 · Gemini 335 · Claude 260 Named assistant referrals grew as discovery fragmented.
04 AI-referred outcomes
40 key events
1,291 engaged
4,188 page views from AI-assistant sessions Not vanity visibility: 40 tracked actions after assistant referrals.

The operating advantage

One body of expertise. Three paths to the buyer.

Quwa compounds the same expertise across the surfaces buyers now use. The mechanics change; the requirement does not: become the clearest, most credible source the system can retrieve.

  1. 01

    Be retrievable before you try to be quotable

    Quwa keeps public analysis indexable and leaves OAI-SearchBot unblocked. Access is only the floor, but no answer engine can cite evidence it cannot retrieve.

  2. 02

    Give the model something only you can say

    Original reporting, specific claims, named entities, and a visible evidence trail give search and answer systems a defensible reason to surface you.

  3. 03

    Package the same expertise for every surface

    Query-complete headings support retrieval. Entity and topic clarity support Search. Timely framing and strong imagery give Discover a reason to distribute the work.

  4. 04

    Tie visibility to behavior you can prove

    GSC measures Google surfaces. GA4 identifies clicked assistant referrals and key events. Citation-only visibility stays separate instead of being dressed up as attributable traffic.

Choose the leverage point

Five bottlenecks. Each with a shipped answer.

Start where the delay costs the most. Each path pairs the outcome with the mechanism and a receipt—not a capability claim.

01

Google Discover visibility

Reach qualified readers before they know to search for you.

AI Overviews compete for demand that already exists. Discover creates reach before the query. Winning it takes entity clarity, image eligibility, freshness, and engagement signals—not another keyword calendar.

Receipt

In 2026 YTD, Quwa earned 833,988 Discover clicks—10.1× its Web Search clicks and 285% more than the same 2025 period.

02

Brand-adjacent publication creation

Build an audience, authority, and acquisition channel you control.

A brand-adjacent publication turns expertise into a channel you own: its own search demand, audience habit, citations, and direct line to buyers. Platform reach becomes an input, not the business model.

Receipt

I built one from nothing to 50K+ monthly readers and 37+ enterprise buyers: defence OEMs, think tanks, and government departments.

03

AI workflows for building & managing custom websites

Launch faster, stay fast, and cut long-term development overhead.

Your site should accelerate the work, not turn every change into a ticket. I use AI-assisted development to ship custom, maintainable code—and the operating system that keeps it fast after launch.

Receipt

Quwa runs a custom theme with a ~30KB frontend footprint and Bloomberg-style paywall logic. This page loads on infrastructure I built and maintain myself.

04

AI workflows for creating custom WordPress plugins

Turn workflow gaps into owned tools that ship in days, not quarters.

The expensive gap is usually the workflow unique to your business. AI makes custom software economical enough to solve it instead of stacking another compromise onto WordPress.

Receipt

Gated podcast delivery with per-user RSS feeds and signed AWS enclosures. Rule-based paywalls with subscriber-tier logic. Exit-intent capture wired into the email platform. All custom, all shipped.

05

AI workflows for high-quality, high-velocity content creation

Multiply expert output without diluting judgment, quality, or trust.

More output only matters if the buyer still trusts it. I use AI to compress research, competitive analysis, and first drafts—then keep the thesis, evidence, and final judgment human.

The test

Would your CTO publish this under their own name? If the answer is no, it doesn't ship. That single rule is what separates a content engine from an AI content dump.

The risk reversal

Judge the thinking before the pitch.

You should be able to test my judgment before you spend time on a call or money on a proposal. The useful part comes first.

  • No gate around the answer

    You get the first moves whether or not we work together. If your team can execute them in-house, I'll tell you that plainly.

  • No calendar tax

    You should not owe someone 45 minutes just to learn whether they can help. There is no calendar link here on purpose.

  • No handoff chain

    No account manager translating your problem. No junior learning your product on your budget. The person who diagnoses the work does the work.

  • No borrowed judgment

    AI provides research leverage and speed. The point of view, evidence standard, and final call stay mine—and carry my name.

Make the constraint useful

Make the next move obvious.

Choose one bottleneck or several. Within 24 hours—usually the same day—I’ll send back where I would start and why.

  • A concrete sequence you can act on.
  • A point of view tied to what you selected.
  • No obligation to turn the answer into a sales call.

Get the first moves

Choose the constraints. I’ll reply with where I would start and why.

Where do you need leverage?

One useful reply, written by me. No SDR, calendar gate, or follow-up sequence.