Scalepact logoScalepact logo
The team · Scalepact

The Team

The same team works on every destination site we publish, which is why the research reads the same way whether you are looking at Belize or Sydney. None of us came to this from travel writing. We came from marketing work for tour operators, and that is the lens we read a booking page through.

Everybody below is named in full, photographed, and linked to profiles you can check. If a page on one of our sites credits a researcher, that person has a card here, and the card says what they did.

Research

  • Hamza Liaqat, founder of ScalePact

    Hamza Liaqat

    Founder, and lead of the research desk

    Faisalabad, Pakistan

    Sets the ordering rules for every tour grid we publish and signs the judgement at the foot of each experience page. Spent the last several years inside tour operator websites, booking flows and paid acquisition, including building an operator's entire booking site from nothing for a business that until then sold only through marketplaces.

  • Mazhar Siddiqi, Delivery and project management, ScalePact

    Mazhar Siddiqi

    Delivery and project management

    Faisalabad, Pakistan

    Manages delivery of the destination booking sites: scheduling each build, running the pre-launch checks and making sure a page clears its verification list before it goes live. Project manager at AryzeTech, previously a full-stack engineer there in React, Next.js and NestJS.

  • Zunira Amir

    Tour research and SEO

    Faisalabad, Pakistan

    Researches the tours behind the destination booking sites and handles their SEO, along with the automation that keeps listings and enquiries moving. Tour research analyst, SEO and automation specialist at AryzeTech since 2023, working in GoHighLevel, WordPress and Shopify.

Design and build

  • Mubashar Shafique

    Web development

    Faisalabad, Pakistan

    Builds and maintains the destination booking sites: the Astro templates, the tour grids and the booking cards that pull live prices from Viator. Website developer at AryzeTech since 2024, working in WordPress, Next.js and Framer.

  • Hassan Mujahid

    Software engineering

    Faisalabad, Pakistan

    Builds and maintains the Astro-based destination booking sites, with a focus on fast load times and a smooth path from tour grid to booking. Software engineer at AryzeTech since 2025, working in Next.js, NestJS and PostgreSQL.

  • Asad Atiq

    Booking automation

    Faisalabad, Pakistan

    Builds the follow-up and reactivation flows behind the destination booking sites: the GoHighLevel CRM setups, funnels and booking automation that run after a traveller enquires. Automation specialist at AryzeTech.

  • Harmain Atiq

    Front-end development

    Faisalabad, Pakistan

    Builds the page templates and landing pages for the destination booking sites in React and Next.js, with the tracking and booking flows wired in. Developer at AryzeTech.

  • Zainab Imtiaz

    Front-end and funnels

    Faisalabad, Pakistan

    Builds the landing pages for the destination booking sites in Next.js and Tailwind, and the enquiry-to-booking funnels behind them on GoHighLevel. Front-end developer and funnel strategist at AryzeTech since 2022.

  • Amina Bashir

    Front-end and funnels

    Faisalabad, Pakistan

    Builds responsive pages for the destination booking sites in Next.js and Tailwind, and the booking and sales funnels behind them on GoHighLevel, Kajabi and Systeme.io. Front-end developer and funnel strategist at AryzeTech since 2023.

How to check a card

  1. Open the LinkedIn link. It should resolve to an account with history, showing the same full name as the card.
  2. Compare the photograph with the one on their profile and on any destination page that credits them. It is the same photograph everywhere a person appears.
  3. A card with a field missing does not go on this page. If someone is credited on one of our sites and has no card here, that is an error, and we want to hear about it.

A card is not a byline

Adding people to this page adds real human beings to the organisation. It does not add authors. The signature at the foot of every experience page we publish stays one person, Hamza Liaqat, and the author in every tour page's schema stays one identifier.

Where another researcher worked on a page, they are credited by name on that page, separately from the signature, and only on pages they actually worked on. The credit links back to their card here.