Before you brief a web agency, have your goals, content, brand assets, access credentials and a named decision-maker ready — missing any one of these is the most common reason a website project stalls.
What do you actually need to prepare before briefing a web agency?
You need five things ready: a clear goal for the site, your brand assets and content, access to your domain and hosting, a named decision-maker, and a realistic budget range. Having these in hand before the first conversation is what keeps a project moving.
Most first-time buyers assume the agency will tell them what to prepare once the project starts. That is partly true — a good agency runs a discovery process — but the things only you can supply are the things that hold everything else up. An agency can design a beautiful page in a week; it cannot write your About page for you from nothing, and it cannot log into a domain registrar you have lost the password to.
Since 2016 we have built sites on both WordPress and Shopify for clients ranging from Lahore startups to brands in Dubai and the USA, and the pattern is consistent: the projects that finish on time are the ones where the client arrived with their content and access organised. The design and development rarely cause delays. The waiting does.
Think of your preparation in three buckets: decisions (what the site is for and who it’s for), materials (words, images, logos, product data), and access (the logins that let an agency actually publish). If you walk into a briefing with all three, you remove the three most common reasons projects stall.
You do not need all of it polished. Rough notes on your goals and a folder of draft content are far more useful than nothing, because they give the agency something to react to and refine rather than a blank page to chase you about for a month.
1DecisionsGoal, audience, scope2MaterialsCopy, images, brand,product data3AccessDomain, hosting,analytics logins4A decision-makerOne person who canapprove
What makes a website project stall after it starts?
Projects stall most often because the client hasn’t supplied content, can’t be reached for approvals, or has lost access to their domain or hosting — rarely because of the design or development itself.
The uncomfortable truth is that the agency is usually ready before the client is. A build can be scaffolded, a design approved, and development completed, and then the whole thing sits waiting for the home page copy, the team photos, or the product descriptions that were due three weeks ago. Every agency that has been around a while has a drawer full of near-finished sites waiting on content.
The second stall is approvals. When nobody on the client side has the authority to say yes, feedback comes in rounds from different people who contradict each other, and each round adds a week. A project with five stakeholders and no final decision-maker takes far longer than one with a single empowered contact.
The third is access. We have had launches held up not by anything technical but by a client trying to recover the login to a domain registered years ago by a former employee or a web designer they no longer speak to. Sorting this out can involve identity verification with the registrar and genuinely take weeks, so it is worth checking you can log in before the project starts, not on launch day.
None of these are design problems, which is why spending all your preparation energy on choosing colours and fonts misses the point. The boring logistics are what determine whether you launch on time.
What content do you need to have ready?
You need the words for every page, high-resolution images, your logo in editable formats, and — for an online store — complete product data including titles, descriptions, prices and photos. Content is the thing clients most often underestimate.
Website copy is the single most underestimated task. Writing clear text for a home page, services pages, an About page and contact details is harder and slower than people expect, and it is almost always the client who knows the business well enough to get it right or at least draft it. Decide early whether you are writing it, the agency is writing it, or you are splitting the work — and if the agency is writing, they will need interview time and reference material from you anyway.
Images matter more than most first-time buyers realise. Low-resolution logos pulled off an old website, photos taken on a phone in bad light, or stock images that look like stock images all drag down an otherwise good design. If you have a budget for photography or professional brand assets, this is where it pays off. If you don’t, be honest with the agency so they can plan around it.
For an e-commerce store the content burden is much heavier. Every product needs a name, a description, a price, variants such as size or colour, stock information, and at least one clean photo. A store with two hundred products is two hundred small content tasks, and they cannot be skipped. We usually ask clients to supply this as a structured spreadsheet so it can be imported rather than typed in by hand.
Gather your legal and trust content too: privacy policy, terms, returns and shipping policies for a store, and any certifications or affiliations you want shown. These are easy to forget until the agency asks, and they often require input from someone other than you.
- Page copy for every planned page, even in draft form
- Logo in vector or high-resolution format, plus brand colours and fonts if you have them
- High-quality photography of your product, team, premises or work
- For stores: a product spreadsheet with names, descriptions, prices, variants and images
- Policies: privacy, terms, shipping and returns where relevant
What access and logins will the agency need from you?
At minimum, access to your domain registrar, your hosting account, your existing website’s admin if you have one, and your analytics and advertising accounts. Confirm you can actually log in to all of these before the project starts.
Your domain name — the web address itself — is registered with a registrar, and whoever controls that account controls where your site points. This is the access most often missing, because domains are frequently bought years earlier by someone who has since left or by a vendor you no longer work with. Check today that you can log in. Recovering a lost domain account can take weeks of back-and-forth with the registrar.
Hosting is where the site’s files live. If you have an existing site, the agency needs access to migrate or replace it cleanly. If you’re starting fresh, you’ll decide together whether you buy hosting or the agency arranges it. Either way, knowing who currently holds what avoids duplicate purchases and surprises.
If you already run Google Analytics, Google Ads, Meta advertising or a Search Console property, the agency will want access so your history isn’t lost and your tracking carries over. Losing years of analytics data because a new site was launched without migrating the property is a avoidable and common mistake.
A practical tip: rather than emailing passwords around, most of these platforms let you add a user by email address with specific permissions. That keeps your accounts secure and means you can revoke access cleanly later. A good agency will tell you exactly which role to grant rather than asking for your actual password.
What decisions should you make before the first meeting?
Decide what the website is primarily for, who it is for, and roughly what you can spend. These three decisions shape the platform, the structure and the scope more than any design preference will.
The most important decision is purpose. A site built to generate leads for a service business is structured completely differently from one built to sell products, take bookings, or simply establish credibility. If you can’t say in one sentence what you most want a visitor to do, the agency is designing in the dark. Pick the single most important action, even if the site does several things.
Know your audience in practical terms: are they local or international, on mobile or desktop, price-sensitive or premium, searching on Google or arriving from social media? We serve clients targeting customers in Pakistan and others selling to the US, Dubai and Australia, and the right choices differ sharply depending on who is actually visiting.
Have a budget range in mind, even a rough one, and be willing to share it. First-time buyers often hide their budget hoping for a lower quote, but it has the opposite effect: without a number, the agency can’t tell you what’s realistic, and you waste time on proposals that are either gold-plated or too thin. A range lets the agency design to fit.
Decide what success looks like and how you’ll measure it — more enquiries, more online sales, a lower cost per lead. Agreeing this upfront means everyone knows what the site is being judged on, which keeps later conversations about results grounded in something you agreed rather than a vague sense of disappointment.
Should you build on WordPress or Shopify?
Choose WordPress when the site is primarily about content, services and flexibility; choose Shopify when selling products is the core of the business. The decision depends mainly on whether you’re publishing or selling.
This is one of the first real decisions, and it’s worth getting right because moving from one to the other later means rebuilding. We develop on both, so the honest answer is that it depends on what the site mostly does rather than which platform is ‘better’.
WordPress is the more flexible foundation. It suits service businesses, content-heavy sites, blogs, and situations where you want custom functionality or full control over structure. It can run a store too, via WooCommerce, but it asks more of you in terms of maintenance and updates.
Shopify is purpose-built for selling. It handles payments, inventory, shipping and checkout out of the box, and it takes care of hosting and security for you. The trade-off is less flexibility outside of commerce and ongoing platform fees. For a business whose main goal is selling products online, that trade-off is usually worth it.
If you’re genuinely unsure, describe your business and your goal to the agency and let the recommendation follow from that, rather than deciding on the platform first and forcing the project to fit it.
| Factor | WordPress | Shopify |
|---|---|---|
| Best for | Content, services, flexibility | Selling products online |
| Selling products | Possible via WooCommerce | Built in |
| Hosting & security | You or your agency manage it | Handled by the platform |
| Flexibility | High, highly customisable | Focused on commerce |
| Ongoing cost shape | Hosting plus maintenance | Monthly platform fee plus transaction costs |
| Maintenance burden | Higher — updates and plugins | Lower — platform-managed |
Who needs to be involved on your side?
You need one empowered decision-maker who can approve work quickly, plus whoever holds your content, brand assets and account access. Keeping the approval chain short is what keeps the project fast.
The most valuable person on a web project is a single contact who can make decisions and make them quickly. This doesn’t mean one person does all the work — it means one person owns the relationship with the agency and has the authority to approve designs, content and scope without escalating every choice to a committee.
Problems appear when feedback arrives from several people who haven’t coordinated. One wants the header blue, another wants it green, a third wasn’t consulted and objects after sign-off. Every contradictory round costs time. Gather internal feedback, resolve it among yourselves, and send the agency one consolidated response.
Identify early who physically holds what: who has the logo files, who knows the domain login, who manages the current site, who can write or approve the copy. These may be different people, and chasing them one by one mid-project is a common source of delay. We provide a dedicated account manager precisely so there’s a single point of contact on our side too — the relationship works best when both sides are clear about who is responsible for what.
How do you write a brief the agency can actually use?
A useful brief states your goal, your audience, the pages you need, two or three sites you like and why, your rough budget, and your deadline. It can be one page — clarity matters more than length.
A brief is not a specification document and it doesn’t need to be long. Its job is to give the agency enough to ask good questions and propose a sensible approach. The most useful briefs we receive are short and specific rather than long and vague.
Include examples. Two or three websites you admire — and a sentence on what you like about each — communicate more about your taste in a minute than paragraphs of adjectives. Include a couple you dislike too; knowing what to avoid is just as useful.
Be explicit about must-haves versus nice-to-haves. A booking system, a multi-language option, or a specific payment method might be essential or optional, and the agency can only prioritise and price correctly if it knows which. Flagging the non-negotiables early stops them being discovered late when they’re expensive to add.
State your deadline and the reason behind it. ‘We’d like it done soon’ is different from ‘we’re launching a product in eight weeks and need the site live first’. A real deadline with a real reason lets the agency tell you honestly whether it’s achievable and what would need to be true to hit it.
Common questions
How long should it take me to prepare before contacting an agency?
You don’t need everything finished before you make contact — a good agency will help you shape the brief. Have your goal and rough budget clear enough to start the conversation, and use the project’s early weeks to pull together content and access in parallel rather than waiting until it’s all perfect.
What if I don’t have any content or brand assets yet?
That’s common and manageable, but say so upfront. Copywriting, photography and brand identity are services an agency can provide, but they add time and cost that need to be scoped in from the start rather than discovered halfway through when the design is waiting on words.
Can I give the agency my passwords, or is there a safer way?
Avoid sharing actual passwords. Most platforms — Google Analytics, Google Ads, your domain registrar, hosting panels — let you add a user by email with specific permissions. This keeps your accounts secure, lets you see who has access, and means you can revoke it cleanly when the project ends.
What happens if my content isn’t ready when the build is finished?
The site sits unfinished and the launch slips, which is the single most common cause of delay. If you can see content will be late, tell the agency early so the schedule can be adjusted, and consider launching with placeholder or phased content rather than holding the whole site hostage to one outstanding page.
Should I choose my platform before or after talking to the agency?
After. Describe your business and your main goal, and let the platform recommendation follow from that. Deciding on WordPress or Shopify before you’ve explained what the site needs to do risks forcing the project to fit a choice made for the wrong reasons.
Do I need to know exactly how many pages I want?
Not exactly, but a rough list of must-have pages helps enormously. Home, about, services or products, and contact are a typical core; from there you can discuss what else earns its place. The agency can refine the structure, but your list of essentials anchors the conversation.
How do I avoid paying for things I don’t need?
Share your budget range and separate must-haves from nice-to-haves in your brief. When the agency knows your constraints and your priorities, it can propose a scope that fits rather than quoting for features you’ll never use — and you can make informed trade-offs instead of guessing.
