Takhleeqat.pk — Wireframe v2
UX Wireframe · v2

Takhleeqat.pk — Wireframe & Navigation, Modernized

Updated on your two notes: the nav is redesigned as a mega-menu that ends the "We Help / We Do" confusion for good, AI Automation now has its own homepage spotlight sized like the flagship it is, and every service page is rebuilt as a single-purpose conversion landing page instead of a generic content template. Rationale is deeper throughout — where a decision follows a known UX principle, it's named.

★ New in v2: AI Automation homepage spotlight · mega-menu nav · landing-page service template · sticky CTA bar
Design rationale
Navigation concept — mega-menu, live preview

Core Services

Website Design & DevelopmentConversion-focused sites & maintenance
SEO & Local VisibilityOrganic search & local discovery
Paid AdvertisingGoogle & Meta acquisition
Social Content & ManagementContent, publishing, community
FLAGSHIP

AI Automation

AI Chatbot Development
LLM Solutions
Workflow Automation
Customer Service Automation
AI Content Generation
Strategic Funnel Building

Start Here

preview
Take the 2-min fit quiz →
Jakob's Law + Hick's Law
Why a mega-menu, not three separate dropdowns: visitors already know mega-menus from every SaaS and agency site they use — Jakob's Law says they'll expect this one to behave the same way, so it needs no learning curve. Putting Services and AI Automation side by side in one panel (instead of two menus a visitor has to open separately) also respects Hick's Law: decision time rises with the number of separate choices presented, so merging two menus into one glance is measurably faster to scan than forcing a visitor to open "We Do," close it, then open "AI Automation" to compare.

Von Restorff effect
Why the AI Automation column looks different: a dark, gold-accented column inside an otherwise white menu is the isolation effect at work — the one element that visually breaks the pattern is the one the eye lands on first and remembers afterward. That's deliberate: this is the flagship, so it should look like one at the exact moment a visitor is scanning "what do they actually do."

Why "Industries" stays a standalone top-level link instead of living inside the mega-menu: someone who searches "digital agency for franchises" is looking for themselves, not a service — folding that into a services menu buries a different search intent under the wrong mental model. It stays one click away, on equal footing with Work and About.

Why the third mega-menu column is a fit-quiz card, not another list: a menu that's all links asks the visitor to already know what they want. A 2-minute fit quiz gives the undecided majority a next step that isn't "pick blindly from 10 items," and it's a natural place to capture service_interest for the analytics event map before they ever reach a form.
Primary navigation — 5 links + 1 CTA
What We DoMega-menu: Core Services + AI Automation + fit quiz
IndustriesStandalone — different search intent, own landing pages
Work / Case StudiesEvidence index, not an image gallery
AboutStory, leadership, process, promise
InsightsBuyer-question articles, author + date shown
Get a Free Digital Audit CTA button — also the Contact path
Inside "What We Do" → Core Services
Website Design & Development
SEO & Local Visibility
Paid Advertising
Social Content & Management
Inside "What We Do" → AI Automation (flagship)
AI Chatbot Development
LLM Solutions
Workflow Automation
Customer Service Automation
AI Content Generation
Strategic Funnel Building
Industries (standalone nav item)
B2B
B2C
E-Commerce Marketing
Franchise Marketing
Non-Profit
Retail Marketing
Supporting / conversion utility
Case Study DetailClient context → challenge → approach → verified result
Packages / Pricing GuidanceCurrency, tax, scope, revision limits stated
Thank-You / ConfirmationFires generate_lead once, states next step
Legal (Privacy / Terms / Cookies)
Miller's Law
Why 5 links, not 6: the brief's own ceiling is six primary items; this nav uses five because merging Services and AI Automation into one mega-menu freed a slot rather than needing it. Fewer top-level choices means less working-memory load the moment a first-time visitor lands — Miller's Law is the reason "7 ± 2 items" became a rule of thumb, and five sits comfortably under it even before the CTA is counted.

Why every AI Automation sub-item still gets its own indexable URL even though it's grouped visually under "What We Do": grouping is a navigation decision, not an information-architecture one. Each still needs its own landing page, title tag and schema per the SEO requirements — the mega-menu changes how a human finds it, not how many pages exist underneath.
1
Sticky header
Serial Position Effect
Why: what sits first and last in a list is remembered best — that's why the CTA is the last thing the eye crosses before leaving the header, not buried mid-row. The mega-menu (see Nav & IA tab) replaces three separate dropdowns with one, so the header now reads as five decisions instead of seven.
2
Hero — above the fold
Get a Free Digital Audit
View Client Results
[N] PROJECTS DELIVERED[RATING] · [SOURCE]BASED IN PAKISTANSERVING CLIENTS REMOTELY
work sample / product screenshot
F-pattern scanning
Why: eyes move in a rough F across a page — headline top-left, then a horizontal sweep, then down the left edge. The H1 sits where that first sweep starts, the CTAs sit where the sweep naturally ends, and the proof strip is the first thing hit on the way down — it answers "is this legit" before the visitor has scrolled at all, not after.
3
Problem recognition
icon
icon
icon
icon
Weak credibility · Low-quality leads · Unclear services · Poor search visibility
Why: a visitor who sees their own problem named specifically trusts the next section more than one shown a solution first — self-recognition builds more credibility than a claim does. It also primes the AI Automation spotlight immediately below: "poor visibility / manual overload" sets up "here's the modern answer" as a direct response, not an unrelated pitch.
4
Flagship service — full-width spotlight
AI AUTOMATION
Explore AI Automation
→ dedicated landing page
AI Chatbot Development
LLM Solutions
Workflow Automation
Customer Service Automation
AI Content Generation
Strategic Funnel Building
Von Restorff Effect + Peak–End Rule
Why this exists as its own full-width block, not a 5th card in the offers grid below: you told me AI Automation is the main service — a card the same size as four others structurally tells a visitor it's one of five equal options, which contradicts that positioning regardless of what the copy says. Layout communicates hierarchy faster than words do. Giving it a distinct dark, high-contrast treatment against the surrounding light sections is the isolation effect in practice: the one section that looks different is the one visitors remember and describe to others afterward.

Why it sits here — after Problem Recognition, before the generic offers grid: this is the "peak" moment of the homepage narrative (peak–end rule: people judge an experience heavily by its high point and its ending). Placing the flagship differentiator right after the visitor recognizes their own problem — and before the breadth-of-services list — means the strongest, most memorable idea lands while attention is highest, not diluted among four other offers.

Why 6 icon+label chips instead of full descriptions: the job of this block is recognition, not explanation — depth belongs on the dedicated AI Automation landing page (see Service Landing Page tab). A dense wall of six paragraphs here would slow the homepage down and hurt the very Core Web Vitals budget the brief sets.

Why the CTA says "Explore AI Automation," not the sitewide "Get a Free Digital Audit": a visitor drawn in by this specific spotlight is signaling specific intent — sending that intent to a purpose-built AI Automation landing page (with its own case studies and FAQ) converts better than routing everyone back to one generic audit form.
5
Core services — 3 shown
icon
Website Design & Development →
icon
SEO & Local Visibility →
icon
Paid Advertising →
Why only 3, and why they follow the flagship instead of leading: the brief caps homepage offers to keep the page from reading as "broad full-service" again. Sequencing them after AI Automation, in a visually quieter light section, is intentional contrast — a calmer, uniform grid right after a bold spotlight lets the eye rest, a basic principle of pacing a long page so nothing after the peak feels like a letdown.
6
Featured case study
before / after visual
Read the full case study →
Why: one specific, verified story outweighs a logo wall — it's the first hard evidence a skeptical visitor hits after two sections of claims (spotlight + offers). Links to a full case-study page rather than expanding inline, keeping the homepage scannable while giving the proof page its own SEO-indexable depth.
7
Process
1
2
3
4
5
Discover → Strategy → Design/Build → Launch → Measure/Improve
Why numbers only appear here: this is the one section on the page where sequence is literally true information — a real, ordered process — so a numbered track earns its place. Every other "01/02/03" pattern elsewhere on the site would be decorative, which is why you won't see numbering reused on the offer cards or testimonials.
8
Why Takhleeqat
Named expertise · Response-time standard · Delivery ownership · Verified guarantee
Why here: sits between "how we work" and "what others say" — differentiation claims land better once the visitor understands the engagement, and they prime credibility right before testimonials have to carry the final weight of proof.
9
Testimonials
Each card: name · role · company · date · service used
Why: three fully attributable quotes, not a carousel — carousels hide content from scroll-based readers and crawlers alike. Full attribution turns each quote into a checkable claim, directly answering the audit's "weak review attribution" finding.
10
Service / industry fit
Website
AI Automation
SEO
Paid Ads
Social
See fit details →
Why: a self-select toggle instead of a static "we also do..." list — it routes each visitor segment (including AI-curious ones who scrolled past the spotlight without clicking) to the right page without repeating content already shown above.
11
FAQ
+
+
+
Timeline · pricing approach · ownership · revisions · support · hosting · reporting · ad spend
Why here, not near the top: its job is removing the last practical objections at the exact moment a visitor is deciding whether to submit the form — answering them before the offer's even been seen would just introduce doubt early.
12
Final CTA
Get a Free Digital Audit
Response-time expectation stated: e.g. "We reply within [X] business hours."
Peak–End Rule
Why a full-width color break: people judge a whole experience largely by its ending — the final section a visitor scrolls past matters almost as much as the hero for what they remember. A distinct color break signals "decision point" and repeats the identical CTA label used in the header, so a visitor who scrolled the whole page gets the same promise as one who clicked immediately.
13
Footer
Address · phone · email · WhatsApp · social icons · sitemap link (incl. AI Automation) · © [dynamic year]
Why: a full navigation surface for visitors who scroll straight to the bottom looking for contact details — and the sitemap link here is the safety net that keeps every AI Automation sub-page crawlable even for visitors who never opened the mega-menu.
Desktop reference width: 1180–1440px. Sections re-flow to single-column stacks at the 768px and 320px checkpoints.
0
Reduced nav — landing-page mode
Distraction-free ratio
Why the nav shrinks here: this is the one part of the site built with a single goal — get a qualified AI Automation lead — not to route traffic elsewhere. High-converting landing pages deliberately cut the number of exit paths (a full site nav gives a visitor eleven ways to leave before deciding); this page keeps only a single collapsed "Other Services" escape hatch plus the logo as a way home, so wayfinding isn't fully lost, but it's no longer competing with the CTA for attention.
AI Automation — Book an AI Readiness Call PINNED ON SCROLL ↕
1
AI AUTOMATION
Book an AI Readiness Call
[N] AUTOMATIONS DEPLOYEDRESPONSE WITHIN [X] HRSSAME TEAM DESIGN → BUILD → SUPPORT
Why one CTA, repeated, not "primary + secondary" like the homepage: the homepage hero splits traffic between "ready now" and "still deciding" because it serves every visitor type at once. A landing page already has a pre-qualified visitor — someone who clicked "Explore AI Automation" specifically — so a second, softer CTA here would only dilute the single action this page exists to drive.
2
Built for
Growing service businesses
High enquiry volume
Repetitive support load
Why chips, not paragraph cards: this section's only job is a fast yes/no self-check — a visitor should confirm "that's me" in under two seconds, not read three sentences to find out.
3
What you get
demo
Aesthetic-Usability Effect
Why a bento grid instead of uniform 3-column cards: a page built entirely of identical-size cards starts to feel like a template, and an uneven, considered layout reads as more crafted — the aesthetic-usability effect means visitors perceive genuinely more-usable design as more trustworthy, which matters most on the page selling your most technical, hardest-to-visualize service.
4
How it works
1
2
3
4
Why a service-specific version, not a repeat of the homepage process: AI Automation projects genuinely involve different early steps (e.g. auditing existing workflows before design starts) — reusing the generic 5-stage homepage process here would either be inaccurate or force-fit, and a landing page's whole premise is specificity.
5
Proof — service-specific
automation dashboard / before-after
Why: proof shown here must be an AI Automation project specifically — a generic web-design case study reused on this page would undercut the exact claim ("we're an AI automation partner") this page is trying to prove.
6
Is this the right fit?
Good fit if
Better suited to a simpler start
Anti-persona transparency
Why include a "not for everyone" column at all: a page that only ever says yes reads as a sales pitch; naming who this isn't for costs almost nothing and makes the "good fit" column far more credible by contrast — it also pre-qualifies leads before they book a call, protecting the response-time promise stated in the hero.
7
Pricing guidance
Currency · setup fee · scope boundaries · revision limits · minimum term
Why stated ranges, not "contact for pricing": unqualified visitors self-filter before booking a call instead of after, which is what actually protects the response-time SLA stated at the top of this page.
8
FAQ — AI Automation specific
+
+
Data privacy · which LLM/vendor · human handoff · integration with existing tools
Why these specific questions: AI Automation buyers' actual blockers are data handling and vendor lock-in, not "how many revisions" — copying the generic homepage FAQ here would answer the wrong objections for this specific, more technical audience.
9
Final CTA
Book an AI Readiness Call
Why the label differs from the sitewide "Get a Free Digital Audit": the audit offer is a general-purpose entry point; "AI Readiness Call" tells a warm, pre-qualified visitor exactly what happens next in language specific to what they came here for — consistency matters within a funnel, not across every unrelated one.
This structure — reduced nav, sticky CTA bar, bento deliverables, fit-check, service-specific FAQ — is the template for every service page (Website Design, SEO, Paid Ads, Social, and each AI Automation sub-service), not just this one. Only the problem statement, deliverables, proof and FAQ content change per page.
1
Hero
Get a Free Digital Audit
View Client Results
work sample
Why: both CTAs stack full-width — side-by-side buttons under 375px shrink tap targets below the accessible minimum (Fitts's Law: smaller, harder-to-hit targets take measurably longer to tap accurately, which costs conversions on a screen this size).
2
Problem recognition
Why: the 4-item grid collapses to 2 columns so each symptom stays readable at arm's length instead of shrinking into unreadable micro-text.
3
AI AUTOMATION
Explore AI Automation
Chatbots
LLM Solutions
Workflow Automation
Support Automation
Why it keeps its full-width dark treatment on mobile too, not a scaled-down card: shrinking the flagship section down to match generic mobile card sizing would erase the exact visual hierarchy that makes it read as "the main service" on desktop — the contrast has to survive the breakpoint, or the section's whole purpose is lost the moment most traffic (mobile) sees it.
4
Core services
icon
icon
Why: stacked vertically in priority order, not a swipeable carousel — carousels hide content from users who don't realize they can swipe, a common mobile accessibility failure.
5
Process
1
2
3
Why: the horizontal timeline becomes a vertical list with the connecting line removed — compressed into 375px, a horizontal track either truncates labels or forces sideways scrolling.
6
Testimonials
Why: one testimonial visible at a time with a next control — three full attribution blocks stacked would push the FAQ and final CTA an extra screen-length down.
7
FAQ
+
Why: accordions matter more on mobile than desktop — collapsed by default, a necessary objection-handling section doesn't add to scroll fatigue for visitors who don't need every answer.
8
Final CTA
Get a Free Digital Audit
Why: generously oversized tap target, past the WCAG 2.2 minimum — this is very likely the last thing a scrolling thumb taps, so it's sized for certainty, not just compliance.
9
Footer
Tap-to-call · WhatsApp · email · address · legal links
Why: phone and WhatsApp become true tap-to-act controls on mobile, since a mobile visitor reaching the footer is often trying to skip the form and contact a human directly.
Reference width: 375px. Same section order as desktop — the AI Automation spotlight deliberately keeps its full-bleed dark treatment rather than shrinking to match surrounding cards, since most of this site's traffic will see the mobile version first.