The full 9-week method behind Ijjad's first-party 3x lead report for an anonymized Riyadh SME, including the audit, rebuild, CRO, measurement window, and evidence limits.
How We 3x’d Leads for a Riyadh SME in 9 Weeks (Anonymised Playbook)
Ijjad is the team behind this anonymised Riyadh SME playbook: sharper messaging, faster performance, mobile-first UX, and SEO structure turned a slow website into a stronger lead engine. The useful lesson is the rebuild sequence behind the 3x qualified-lead result.
- Ijjad serves Amman, Riyadh, Jeddah, Iraq, and the GCC.
- Every recommendation is framed around scope, conversion, and search visibility.
- Use the guide to clarify decisions before speaking with an agency.
- Talk to Ijjad when you need senior delivery, not generic templates.
How did Ijjad triple leads for a Riyadh SME?
Ijjad rebuilt an anonymised Riyadh professional services SME's website in nine weeks on Next.js, then measured and iterated after launch. Ijjad's private first-party records show qualified leads moved from about 3 to about 9 per month over six months, PageSpeed moved from 42 to 94, and bounce rate moved from 71% to 39%. These are case-specific results, not a forecast.
TL;DR
- Client: anonymised Riyadh professional-services SME with a B2B lead-generation goal.
- Problem: the old site was slow, the contact path was difficult to find, and commercial search visibility was weak.
- Engagement: nine-week rebuild followed by post-launch measurement and CRO iteration.
- Result: qualified leads about 3 to about 9 per month; PageSpeed 42 to 94; organic sessions about 1,800 to about 6,300 per month; bounce rate 71% to 39%.
- Priority decision: remove friction from the primary contact path while improving performance and search visibility.
In this playbook
Let me tell you about the Riyadh project that taught us more about conversion than any brand-new build ever could.
In late 2024, a professional services SME in Riyadh came to us with a familiar problem. The business had a solid repeat-client base, but its slow, content-heavy WordPress site had weak commercial-search visibility and a difficult contact path. The reported baseline was about three qualified website leads per month.
Nine weeks later they had a new site. Six months after launch, Ijjad's analysis showed qualified leads had tripled. This is the full playbook behind that - the diagnostic, the rebuild, the post-launch work, and what we'd do differently if we were starting again. The client stays anonymous under NDA. The figures are Ijjad's first-party analysis of Google Search Console, GA4, and HubSpot data; the underlying accounts are not public. You can see the one-page summary on our Riyadh case study page if you want the shortest version first.
Where the site started - the diagnostic
Before anyone touches a design file, we run a full diagnostic. Three tools, one week.
- PageSpeed + Core Web Vitals. The old site's reported mobile PageSpeed score was 42. That established a performance problem; it did not by itself prove why any query ranked where it did.
- GA4 funnel analysis. The reported homepage bounce-rate baseline was 71%, which supported a closer review of page intent and conversion paths.
- Hotjar recordings + heatmaps. Qualitative recordings showed users looking for a contact path and abandoning the page when they did not find one quickly.
On the Google side, query-to-page evidence from Google Search Console showed weak visibility for relevant Riyadh commercial searches. Competitor research helped prioritise the initial target list, but third-party tool estimates were treated as directional rather than proof of live Google positions.
Diagnostic verdict: the site was functioning. It just wasn't working. Small distinction, massive difference.
The 12 hypotheses we prioritised
Every Ijjad project starts with a ranked list of hypotheses - ways we think we can move the needle, scored by expected impact x effort. This keeps us disciplined. You can't optimise everything at once. Here's what we wrote on the whiteboard that first week.
- Make the primary CTA unmissable and one-click (WhatsApp + form).
- Reduce form fields from 6 to 3.
- Rebuild on Next.js with a project-specific performance budget and representative-device testing.
- Add a sticky WhatsApp button visible on every page.
- Rewrite H1s and meta descriptions for Riyadh commercial intent.
- Create 4 new location + service landing pages targeting the top-SERP gap.
- Add visible, genuinely useful FAQs where the page needs them, with matching structured data for eligibility.
- Restructure the homepage around a single conversion path, not five.
- Publish 3 anonymised client-results stories (trust signals).
- Integrate HubSpot so every form submission triggers a same-day founder reply.
- Add a "why us" block tied to specific outcomes, not platitudes.
- Set up weekly GA4 conversion-event tracking for every CTA.
We ranked the hypotheses qualitatively by expected impact, confidence, and effort, then built the sprint around the strongest evidence. The list was a decision tool, not a promise that any one item would produce a fixed share of the result.
The 9-week timeline
This case used one week of diagnostic, six weeks of design and build, two weeks of launch preparation, and a post-launch measurement and iteration period.
| Week | Phase | Key deliverables |
|---|---|---|
| Week 0 | Audit + diagnostic | PageSpeed report, GA4 funnel analysis, Hotjar recordings, competitor SERP audit, 12 hypothesis-based fixes ranked by impact/effort. |
| Weeks 1-2 | Strategy + IA | New sitemap, primary conversion paths, messaging hierarchy, bilingual content brief, CRM integration plan. |
| Weeks 3-6 | Design + build | Figma designs signed off, Next.js build, CMS wiring, HubSpot CRM integration, bilingual Arabic + English copy. |
| Week 7 | QA + staging | Cross-browser tests, rendered performance budget and representative-device checks, schema validation, GA4 events, and a final 301 redirect map. |
| Week 8 | Launch + migration | Zero-downtime cutover, sitemap submitted, GSC monitoring, first weekly CRO review scheduled. |
| Weeks 9-12 | Post-launch CRO + SEO | CRO experiments, query-to-page monitoring, and qualified WhatsApp + form lead tracking. |
This was the phase split for this case. Another timeline depends on content readiness, integrations, approvals, migration risk, and testing scope.
Why contact friction was prioritised
The funnel review identified the old contact path as a major source of friction, so it became an early priority. The available data cannot isolate a precise share of the final result to this one change.
Not removed it. Killed it as the primary conversion target. The new site put a 3-field inline form + a WhatsApp deep-link into a sticky footer visible on every page, plus inline CTAs mid-scroll on every service page. The old 6-field contact-page form stayed as a secondary option - but it was no longer the default.
The new path let visitors choose between WhatsApp and a short form and included enough context for the team to qualify the inquiry. Both channels were measured as qualified contact actions. The case data supports the combined lead result, but it does not establish that one channel caused a specific share of the lift.
Lesson: before you spend heavily on a redesign, look at your primary conversion path and ask whether it works the way your customers actually want to contact you.
Want a quick evidence check before planning a rebuild? Our free live SEO analyzer inspects accessible HTML and delivery signals, then separates observed findings from items that still require Search Console, analytics, or a real-user performance test. No email required.
Post-launch CRO + SEO iteration
Launch was followed by structured measurement and iteration. The team used observed behaviour and search data to decide what to retain, revise, or revert.
Week 9 - CRO experiment 1: homepage hero rewrite. The team compared a generic headline with a clearer, benefit-led alternative and kept or revised the treatment using observed contact behaviour.
Week 10 - CRO experiment 2: requirements and fit. Service pages received a clearer requirements-and-fit block so visitors could understand the likely engagement before contacting the team. The experiment was evaluated on qualified actions, not raw form volume.
Week 11 - CRO experiment 3: trust signals. The team added anonymised, first-party project evidence below the fold and reviewed whether it helped visitors reach a qualified decision. Client identity remained private under NDA.
Weeks 9-12 - search monitoring. We submitted the new sitemap in Google Search Console, checked redirects and canonical pages, reviewed query-to-page movement, and improved internal links where the evidence supported it. The public result table below reports the approved six-month checkpoint rather than unverified keyword-count snapshots.
We documented the whole CRO playbook as a reusable process, which is what eventually became our 3S Framework for choosing and working with an agency.
Want this playbook run on your own site?
Send us a paragraph on your current site and lead goal. We'll review whether the evidence points to a rebuild, focused CRO work, or a smaller technical repair before proposing scope.
Get Started →Reported baseline and six-month checkpoint
The figures below are the approved baseline and six-month endpoints from Ijjad's private first-party records. Intermediate snapshots are not published because they are not part of the evidence ledger.
| Metric | Baseline | Six-month checkpoint |
|---|---|---|
| Mobile PageSpeed | 42 | 94 |
| Bounce rate | 71% | 39% |
| Organic sessions / month | ~1,800 | ~6,300 |
| Qualified leads / month | ~3 | ~9 (3x) |
First-party sources used by Ijjad: client GA4, Google Search Console, and HubSpot CRM. Comparable 3-month windows were used on both sides; the underlying accounts and exports are private under NDA, so this page discloses the method rather than independent verification.
The six-month checkpoint is case-specific, not a universal SEO or conversion timetable.
How to apply this playbook to your own SME
If you run a services SME in Riyadh, Jeddah, or elsewhere in the GCC, this method can be adapted after a real diagnostic. Five principles are useful starting points.
- Run the diagnostic first. Review performance, the analytics funnel, and qualitative user behaviour before deciding what to redesign.
- Rank hypotheses by impact, confidence, and effort. Start with the strongest evidence, ship a coherent change, and measure it.
- Build on a suitable modern stack. Next.js or a comparable approach can make performance work easier, but the stack alone does not guarantee rankings or conversion gains.
- Remove friction from the primary conversion path. WhatsApp, short forms, visible CTAs. If it takes two clicks to contact you, fix that first.
- Treat launch as the start of measurement. Reserve time for post-launch CRO and search monitoring, with duration based on traffic and decision risk.
If you'd like to see what this looks like on the scope side before you commit, run the scope through our contact form or read the full Saudi website scope planning guide.
Frequently asked questions
Why is the client anonymised in this case study?
The engagement is covered by an NDA, so Ijjad does not publish the client name, logo, or source-account access. The figures below are Ijjad’s first-party analysis of the client’s GA4, Google Search Console, and CRM data. The measurement method is disclosed, but the underlying accounts are private and the results are not independently auditable from this page.
What sector was the Riyadh SME in, and why does it matter?
The client was a professional-services SME, where the website’s primary job was producing qualified inquiries. Both acquisition and conversion changed during the project: organic sessions increased while the contact path became shorter. The method can inform another services project, but the 3x outcome is not a forecast or guarantee.
How long does a project like this typically take?
This case used a nine-week rebuild schedule followed by post-launch measurement and iteration. Another project can take more or less time depending on content, integrations, approvals, migration risk, and the evidence needed after launch. Ijjad scopes the schedule after diagnosis rather than treating this case as a universal timetable.
How is a rebuild like this scoped in Saudi Arabia?
For a professional services SME in Riyadh or Jeddah, the relevant scope can include a custom Next.js build, bilingual Arabic and English copy, CRM integration, CRO setup, and an evidence-based post-launch iteration period. Our full planning checklist is in the Saudi website scope planning guide.
Can this playbook be applied to an e-commerce store or a founder MVP?
Partially. The audit, CRO, and measurement layers transfer directly - you always want to diagnose before redesigning. The UX and page architecture are different because e-commerce optimises for cart completion rather than lead capture, and MVPs optimise for activation instead of inquiry volume. Ijjad adapts the method and schedule to each project type.
What single change moved the needle the most?
Ijjad’s funnel review identified the contact path as a major source of friction: the old site had a six-field form hidden two clicks deep. The rebuild used a three-field WhatsApp-or-form path visible on every page, alongside performance and search improvements. The available first-party data does not isolate one change as a precise share of the total lift.
What tools did you use to measure the result?
Ijjad used Google Analytics 4, Google Search Console, Hotjar, and the client’s HubSpot CRM. The 3x figure compares qualified form submissions and WhatsApp conversations in months 4-6 post-launch with a comparable 3-month pre-launch window. This is Ijjad’s first-party analysis; the client accounts remain private under NDA.
Ready to run this playbook on your site?
Three fastest entry points:
Run the live SEO analyzer → | Get Started | Meet the founder behind Ijjad
Source note
Market context: Saudi Arabia's digital economy reached 16.0% of GDP in 2024, according to the General Authority for Statistics, published December 31, 2025. This is why Ijjad treats modern websites, SEO, e-commerce, AI MVPs, and mobile experiences as business infrastructure across Saudi Arabia, Jordan, Iraq, and the GCC.
