Plate VII · Live

BuzIntel

Built to be cited, not just indexed.

The data layer for doing business in Pakistan — ~191 sourced, dated, citable pages built so people and AI assistants both trust and cite the answer.

Next.js (static export) · ~191 programmatic pages · JSON-LD @graph · llms.txt

~191
Pages
14 × 12
Sectors × cities
27 + 42
Guides + FAQs
20
Templates
Overview

Search is splitting in two: half your audience clicks a blue link, the other half asks an assistant and reads a synthesized answer — and only visits if it's cited. BuzIntel is built for both halves at once.

It's a data-driven knowledge engine for Pakistani SMEs — roughly 191 statically pre-rendered pages generated from a handful of typed data arrays, with answer-engine machinery on every page. It's live, served inside this space, and it's the emerald sub-brand.

The system in motion

Animated architecture breakdown — nodes and data paths resolve in sequence.

Full architecture blueprint
BuzIntel detailed architecture blueprint
Content pipeline — a handful of typed data arrays generate every page, its JSON-LD, the sitemap and llms.txt on each build. · open full-size ↗
The stack — and what each part does
Next.js (static export)191 pre-rendered pages, served at /buzintel
Typed data arrays (TS)Sectors, cities, guides, FAQs, templates, tools — the content spine
JSON-LD @graphOrganization, Article, FAQPage, QAPage, HowTo per page
llms.txt + llms-full.txtA machine-readable map + full corpus for AI assistants
Sourced figuresTax/fee data with source URLs and a verification date — the data moat
Under the hood

Data-driven, end to end

There's no CMS and no scraping — every page is generated from typed TypeScript arrays plus long-form JSON: 14 sectors, 12 cities, 27 how-to guides, 42 single-question FAQ pages, 20 downloadable document templates, and a sector×city matrix. Add a row, rebuild, and new pages, sitemap entries, JSON-LD and llms.txt lines generate themselves. That's how ~191 pages stay consistent and current without hand-maintenance.

AEO / GEO machinery

Every detail page follows one answer-first skeleton: a quick-answer block, a sourced key-fact table with a 'verified' date, the body, a crawlable FAQ, and typed knowledge-graph links. Under the hood, a JSON-LD @graph (Organization, Article, FAQPage/QAPage, HowTo) is emitted per page, and robots.txt explicitly allow-lists the AI crawlers.

The knowledge graph

Pages aren't islands — a related-links layer connects sectors to their cities, guides to their sectors, and FAQs to their guides, plus an interactive explorer. Internal linking that a machine can traverse is a ranking and grounding signal in its own right.

The data moat

Behind the calculators sits a spine of sourced, dated figures — tax brackets, SECP fees, official source URLs and a last-verified date. A dated, sourced number is one an assistant can cite without hedging; that's what turns content into a citable source.

Proof. Live and served inside this space at /buzintel — built to be cited by ChatGPT, Perplexity, Gemini and Google AI.