What you need before engaging with a web developer

Your website represents your business 24/7, which is precisely why proper planning matters. Finding the right web developer starts with understanding what you’re actually trying to achieve, not just aesthetically, but functionally and strategically.

Whether you’re developing a site from scratch or updating an existing one, typing “web developers near me” into Google is only the beginning. Successful website projects require clarity about your objectives, your audience, and what you need the site to accomplish.

This guide walks you through everything you should prepare before engaging a web developer, helping you avoid common pitfalls that cause delays, budget overruns, and disappointing outcomes.

Understanding your project scope

Before you can effectively communicate with a web developer, you need to understand what type of project you’re actually commissioning. Website projects fall into several broad categories, each with different requirements, timelines, and costs.

Brochure/Informational Websites present your business, services, and contact information. They’re typically 5-15 pages with straightforward functionality: contact forms, basic image galleries, perhaps a blog. These suit professional services, small businesses, and organisations needing an online presence without e-commerce or complex features.

E-commerce Platforms sell products or services online, requiring shopping carts, payment processing, inventory management, and customer accounts. Complexity varies enormously – a small catalogue of 20 products differs substantially from hundreds of SKUs with variants, subscriptions, or wholesale pricing.

Custom Web Applications provide specialised functionality: booking systems, member portals, project management tools, data visualisation, or industry-specific workflows. These require bespoke development rather than off-the-shelf solutions.

Website Redesigns update existing sites, which introduces additional complexity: content migration, SEO preservation, maintaining existing functionality whilst improving it, and managing the transition without downtime or broken links.

Platform considerations also matter. Most SME websites work well on WordPress, which offers flexibility, cost-effectiveness, and widespread developer support. However, high-traffic applications, complex integrations, or specialised requirements sometimes warrant custom development using frameworks like Laravel or React.

Mobile apps versus responsive websites serve different purposes. If your users need offline functionality, device features (camera, GPS, notifications), or frequent daily interaction, an app makes sense. If they need occasional access to information, a mobile-responsive website usually suffices and costs considerably less.

Understanding which category describes your project helps developers provide relevant advice and accurate quotes. If you’re uncertain, that’s perfectly fine – a good developer will help you determine the best approach during initial consultations.

Know your audience

Clarity about your target audience fundamentally shapes every development decision, from site structure to functionality choices to design aesthetic.

Start with a brief overview of your business sector. Are you B2B or B2C? Goods-based, service-based, or both? What problem do you solve for customers, and who are those customers?

Create basic audience profiles. You don’t need extensive personas, but you should articulate:

• Who visits your site: Job roles, demographics, technical confidence
• Why they visit: What specific problems or questions bring them to you
• What they need to accomplish: Information gathering, purchase decisions, booking services, accessing support
• How they access it: Predominantly mobile, desktop at work, tablets, mix of devices

B2B versus B2C audiences require different approaches. B2B sites typically need detailed service information, case studies, clear contact paths, and content that speaks to multiple stakeholders (end users, budget holders, technical evaluators). B2C sites often prioritise speed, simplicity, visual appeal, and streamlined purchase paths.

Accessibility requirements depend on your audience. If you serve education, healthcare, or government sectors, legal accessibility standards likely apply. Even when not legally required, accessible design benefits everyone – clear navigation, readable text, keyboard functionality, and proper heading structure improve usability for all visitors.

Mobile-first relevance varies by audience. If analytics show 70%+ of your traffic comes from mobile devices (common for consumer-facing businesses), mobile experience takes priority. Professional services seeing primarily desktop traffic can balance both equally.

Ask yourself these questions:

• What’s your visitors’ technical confidence level?
• What’s their patience threshold for finding information?
• What convinces them to trust your business?
• What objections or concerns must your site address?
• What would make them choose a competitor instead?

This audience clarity allows developers to structure information effectively, prioritise features appropriately, and create user journeys that actually convert visitors into customers.

Define specific requirements

“I need a website” tells a developer almost nothing useful. Specific requirements enable accurate quotes, prevent scope disputes, and ensure you get functionality that actually serves your needs.

Work through these categories to document your requirements:

Essential Functionality (must have for launch):

• Contact forms: How many? What information do they collect? Where do submissions go?
• Search functionality: Do visitors need to search your site?
• Booking/scheduling: Do you need appointment booking, event registration, or reservation systems?
• User accounts: Do visitors need to log in? What can they access when logged in?
• Payment processing: Do you need to accept payments? What payment methods? One-off or subscriptions?
• Content management: Which areas do you need to update yourself (blog, news, products, services)?

Integrations with Existing Systems:

• CRM systems (HubSpot, Salesforce, Zoho): Do you need contact submissions to flow into your CRM?
• Email marketing (Mailchimp, ActiveCampaign): Should newsletter signups integrate automatically?
• Accounting software (Xero, QuickBooks): Do orders need to create invoices?
• Booking systems (Calendly, Acuity): Should your site embed or integrate with existing booking tools?
• Analytics and tracking: Google Analytics, Facebook Pixel, other tracking requirements?

Multi-language or Multi-currency Requirements: If you serve international markets, specify:

• Which languages? (Each language typically doubles content creation work)
• Professional translation or machine translation?
• Currency conversion or multi-currency pricing?
• Region-specific content or universal content across languages?

User Experience Expectations:

• Specific features you’ve seen on competitor sites that you need
• Forms with particular validation requirements
• Interactive elements (calculators, configurators, filtering systems)
• Media galleries (images, videos, virtual tours)
• Download centres (PDFs, resources, case studies)

Be specific, not vague. Instead of “I need a shop,” specify: “I need to sell 50 products in 5 categories, accept credit cards and PayPal, offer discount codes, and charge different delivery rates for UK and international orders.”

The more detailed your requirements list, the more accurate the quote and the fewer mid-project surprises. If you’re unsure whether something is technically feasible or standard, list it anyway with a question mark – better to discuss early than discover problems mid-development.

Gather Brand Assets

Strong brand presence migrates to your website most effectively when you provide developers with proper brand assets from the start.

Essential Brand Materials:

Logo files in multiple formats:

• Vector formats (AI, EPS, or SVG) for scalability without quality loss
• High-resolution PNG with transparent background for flexibility
• Colour and white/reversed versions if your logo has variants
• Clear space requirements if your brand guidelines specify them

Brand guidelines (if they exist):

• Colour codes (hex values like #1a2b3c for web use)
• Typography choices (primary headings font, body text font, acceptable alternatives)
• Logo usage rules (minimum sizes, clear space, colour variations)
• Tone of voice guidelines
• Any brand dos and don’ts

Existing marketing materials:

• Brochures, flyers, business cards (for colour and style reference)
• Previous website (if redesigning) for brand continuity elements
• Social media graphics showing how brand applies digitally
• Any photography style that defines your brand aesthetic

Photography and imagery:

• Professional photos of your team, premises, products, or services
• Image rights confirmation (you own them or have licence to use them)
• Preferred photography style (bright and airy, dark and moody, corporate, casual)

If you don’t have established branding:

Be upfront about this during initial discussions. Some web developers offer brand development services or work with trusted designers. Others may suggest you engage a graphic designer before commencing website work.

Attempting to “figure out branding as we go” during website development typically creates delays and dissatisfaction. Better to invest in basic brand identity first (logo, colours, typography) then build the website on that foundation.

However, if budget constraints make separate brand development unrealistic, discuss this honestly. Some developers can create simple, clean websites with minimal branding requirements whilst you establish stronger brand identity over time.

Design direction & examples

Communicating design preferences effectively requires more than “make it look modern” or “I’ll know it when I see it.” Developers need concrete examples to understand your aesthetic preferences.

How to Collect Design Examples:

Create a collection of websites you admire using:

• Pinterest board for website screenshots
• Spreadsheet or Google Doc with links and notes
• Bookmarks folder with annotations

For each example, note specifically what appeals to you:

• Overall layout and structure?
• Colour scheme or typography?
• Navigation style?
• Specific component (hero section, team page, portfolio gallery)?
• Interactive elements (animations, transitions, hover effects)?
• Mobile design approach?

Be clear about inspiration versus copying. Developers can create designs influenced by examples whilst maintaining originality. They cannot and should not replicate another site’s exact design – that’s both unethical and potentially illegal.

Balance functionality and aesthetics. Beautiful design that doesn’t help users find information or complete tasks fails. When evaluating examples, consider:

• Can you easily find information on the site?
• Is the navigation intuitive?
• Does visual hierarchy guide you through content?
• Do design elements enhance or distract from the message?

Consider your audience, not just personal preference. You might love bold, experimental design, but if you’re a solicitor serving risk-averse corporate clients, safe and professional probably serves better. Your examples should reflect what appeals to your audience whilst aligning with your brand.

Mobile design matters as much as desktop. If your examples only show desktop designs, visit them on mobile devices too. Note which sites provide excellent mobile experiences – this guides developers toward appropriate approaches.

Common design pitfalls to avoid:

• Collecting 20 examples with completely different styles (developers can’t combine minimalist with ornate)
• Focusing solely on homepage designs (inner pages matter too)
• Ignoring functionality in favour of visual flash
• Comparing yourself to sites with 10× your budget
• Feature creep from seeing competitors’ functionality

Aim for 3-5 strong examples that represent a cohesive direction. Quality over quantity – one well-annotated example beats ten random links.

Content preparation

Content should inform design, not follow it. This isn’t debatable from a practical standpoint – design that serves lorem ipsum placeholder text rarely serves actual content well.

When developers design around real copy and genuine imagery, they create layouts that enhance your message. When they design first and force content into predetermined spaces later, they compromise either the design or the message. Neither outcome serves you well.

What “Content Ready” Actually Means:

You don’t need final polished copy before engaging a developer, but you do need substance to work with:

Copy and Messaging:

• Core messaging outlined (what each page communicates)
• Copy length approximated (paragraph-length content versus detailed explanations)
• Key messages and value propositions articulated
• Calls to action identified (what you want visitors to do)
• Tone established (formal, conversational, technical, friendly)

Visual Content:

• Photography selected or sourced (actual photos, not “we’ll find some later”)
• Image style established (professional studio shots, candid workplace, illustrations, icons)
• Video content scripted or produced if featuring heavily
• Graphics or diagrams outlined (flowcharts, processes, data visualisations)

Structured Information:

• Product or service details gathered
• Team biographies written
• Testimonials collected (with permission to publish)
• Case studies or portfolio pieces documented
• FAQs compiled from common customer questions

Stakeholder Approval:

• Key messaging approved by decision-makers before development
• Brand tone confirmed across stakeholders
• Controversial or sensitive content reviewed in advance

If Content Creation Feels Overwhelming:

Professional copywriters can help. We collaborate with experienced copywriters for clients needing content support, or can recommend trusted professionals if you prefer to manage separately. We can also guide you through the content creation process if you’re writing yourself but need structural direction.

Alternatively, create rough drafts for developers to work with, then refine copy during development. This works if you’re comfortable iterating, but expect some design adjustments as content evolves.

Realistic Timeline Consideration:

Content creation typically takes longer than clients expect. Allow:

• 4-8 weeks for comprehensive copy if writing yourself
• 2-4 weeks working with professional copywriters
• 1-2 weeks for internal stakeholder reviews and approvals

This happens before or parallel to design work, not after development starts. Starting development without content creates delays, budget overruns, and compromised design quality.

The Cost of “We’ll Sort Content Later”:

Projects starting without content ready experience:

• Design revisions when actual content doesn’t fit initial layouts
• Delayed launches waiting for content
• Developer downtime (you’re still paying for their time whilst waiting)
• Rushed content to meet launch deadlines (sacrificing quality)
• Frustrated developers working with inadequate information

Invest in content preparation. Your return on that investment appears in every visitor’s experience with your website.

Platform & technology decisions

Understanding platform options helps you make informed decisions about the foundation your website builds upon. Different platforms suit different needs, budgets, and long-term maintenance approaches.

WordPress: The Standard for Most SME Websites

WordPress powers over 40% of all websites globally, offering proven reliability, extensive plugin ecosystem, and widespread developer support. For most small to medium businesses, WordPress delivers:

• Cost-effectiveness: Mature platform with extensive pre-built functionality
• Flexibility: Thousands of plugins extending core features
• Control: You can update content, images, and basic site elements yourself
• Developer availability: Finding WordPress developers for future maintenance is straightforward
• Scalability: Grows from small brochure sites to large e-commerce platforms

WordPress suits: Professional services, small retailers, educational institutions, membership organisations, blogs, portfolios, and most SME websites.

Custom Development: When WordPress Isn’t Enough

Some projects require bespoke development using frameworks like Laravel, React, or Python:

• Complex, unique functionality: Specialised workflows that no plugin addresses
• Very high traffic: Sites expecting millions of visitors monthly
• Sophisticated integrations: Complex connections to enterprise systems
• Specific performance requirements: Millisecond-level speed requirements
• Proprietary systems: Protecting unique business logic or processes

Custom development costs significantly more (3-5× typical WordPress projects) and requires specialised developers for future maintenance. Only pursue if WordPress genuinely cannot meet your needs.

Mobile Apps: When Websites Aren’t Sufficient

Consider native mobile apps (iOS/Android) when you need:

• Offline functionality: Users need features without internet connection
• Device features: Camera, GPS, push notifications, or sensor access
• Frequent daily interaction: Users engage multiple times daily
• Complex user workflows: Multi-step processes benefiting from app structure
• Performance requirements: Intensive calculations or data processing

Apps cost substantially more than websites (£8,000-25,000+ for basic apps) and require separate iOS and Android development. For occasional user interaction, responsive websites typically suffice.

Hybrid Approaches:

Many successful projects combine approaches:

• WordPress website for public presence, custom application for specific functionality
• Progressive Web App (PWA) offering app-like experience without app store submission
• WordPress with headless architecture (custom frontend, WordPress backend)

Our Recommendation Approach:

At Arkay Digital, we specialise in WordPress and React Native development, which covers the vast majority of SME website and mobile app requirements cost-effectively. These technologies represent robust, proven foundations built on PHP and JavaScript – the web’s most widely-supported languages.

For projects requiring custom development beyond these platforms, we have the technical capability to deliver bespoke solutions using modern frameworks and languages. We’ll assess your specific requirements during consultation and recommend the approach that best serves your needs – whether that’s leveraging proven platforms or building custom functionality from the ground up.

We’re transparent about our strengths: if a project requires highly specialised technology outside our core expertise, we’ll recommend appropriate specialists rather than deliver suboptimal work. Your success matters more than winning every project.

The right platform balances functionality, budget, timeline, and long-term maintenance. We’ll guide you toward the approach that serves your business sustainably.

Budget & investment planning

Understanding budget parameters early allows developers to align scope with investment and propose solutions within your range. Website development costs vary significantly based on complexity.

Typical Investment Ranges:

Brochure/Informational Sites typically represent the most accessible investment, suitable for small businesses establishing online presence. Costs vary significantly based on:

• Design customisation (template-based versus bespoke design)
• Page count and content volume
• Features (contact forms, basic integrations, image galleries)
• Content complexity (straightforward services versus technical explanations)

E-commerce Platforms require greater investment due to payment processing, product management, and security requirements. Cost factors include:

• Catalogue size and complexity
• Custom payment workflows beyond standard checkout
• Inventory integrations with existing systems
• Product variations, wholesale pricing, or subscriptions

Custom Web Applications represent substantial investment reflecting bespoke development. Costs depend heavily on:

• Functionality complexity and custom features
• Integration requirements (connecting multiple systems)
• User account systems and permission structures
• Data handling, reporting, and visualisation needs

Mobile Applications (iOS/Android) require significant investment for both platforms, increasing based on:

• Feature complexity and interface sophistication
• Backend infrastructure and API requirements
• Integration with existing systems
• Ongoing maintenance across platform updates

Understanding Investment Ranges:

Project costs can range from low four figures for simple brochure sites to five or even six figures for sophisticated applications. However, identical-looking websites can have vastly different costs depending on:

• Technical complexity under the surface: A contact form collecting basic information costs far less than one with GDPR compliance automation, CRM integration, and sophisticated validation
• Quality and compliance standards: Basic security differs significantly from Cyber Essentials-certified hosting with comprehensive monitoring
• Content and support services: Developer-only projects cost less than full-service including professional copywriting, photography, and ongoing support
• Timeline and urgency: Rushed projects typically cost 30-50% more than those with realistic schedules
• Stakeholder complexity: Single decision-maker projects move faster than committee-approved initiatives

Rather than comparing quotes solely on headline price, evaluate:

• What’s included in the quote (design only, or design + development + content + hosting + support?)
• Ongoing costs (hosting, maintenance, updates, security)
• Developer credentials (insurance, certifications, portfolio quality)
• Project management approach (ad-hoc versus structured process)
• Post-launch support (bug fixes, training, handover documentation)

Development represents initial investment only. Factor in ongoing operational costs:

• Hosting: Monthly costs vary from basic shared hosting to dedicated infrastructure
• Maintenance: Security updates, plugin updates, technical support (consider monthly retainer)
• Content updates: Either manage yourself or retain developer support time
• Domain and SSL: Annual renewals and security certificates
• Email hosting: If using professional email addresses

Calculate total cost of ownership over 3-5 years (typical website lifespan before major refresh) to understand true investment.

If Budget Constraints Exist:

Discuss phased approaches. Many successful projects launch with core features first (Minimum Viable Product), then iterate based on user feedback and available investment:

Phase 1: Essential functionality only (information pages, contact form, basic branding)
Phase 2: Enhanced features (blog, case studies, basic e-commerce)
Phase 3: Advanced functionality (member areas, integrations, custom workflows)

This spreads investment whilst delivering value early.

Cost Versus Value Perspective:

A website functions 24/7 for years. Calculate cost across expected lifespan (typically 3-5 years before major refresh) to understand true value.

Example: A £6,000 website over 4 years costs £125/month – less than many marketing channels with far less reach. That same website might generate enquiries worth tens of thousands of pounds annually.

What Affects Cost:

Higher costs typically reflect:

• Custom design work versus template adaptation
• Bespoke functionality versus using proven plugins
• Complex integrations connecting multiple systems
• Content volume (50 pages costs more than 5 pages)
• Technical complexity (sophisticated calculations, user workflows, data processing)
• Project management overhead (multiple stakeholders, approval processes, revisions)

Lower costs typically involve:

• Template-based design with customisation
• Standard features using existing plugins
• Client-provided content ready to use
• Straightforward structure (brochure sites, portfolios)
• Single point of contact (streamlined decision-making)

Budget as Planning Tool, Not Secret:

Sharing budget parameters helps developers:

• Propose solutions within your investment range
• Flag when expectations exceed available resources
• Suggest phased approaches if needed
• Prioritise features appropriately
• Avoid wasting your time on inappropriate quotes

“What can I get for £X?” is a perfectly reasonable question. Professional developers will outline realistic scope within that budget rather than inflate quotes or overpromise.

Timeline & project phases

Realistic timeline expectations prevent disappointment and allow proper planning. Website projects involve multiple phases, each requiring specific time allocation.

Typical Project Duration by Complexity:

• Simple brochure sites (5-10 pages, template-based design): 1-2 months
• Custom SME websites (bespoke design, 10-20 pages, standard features): 2-3 months
• E-commerce platforms (custom design, moderate catalogue): 3-4 months
• Complex web applications (custom functionality, integrations): 4-6+ months
• Mobile applications: 3-6+ months depending on complexity

These timelines assume content is ready and decisions made promptly. Delays in either extend projects significantly.

What Happens in Each Phase:

Professional web development projects typically flow through several key phases, each serving a specific purpose:

• Discovery & Planning (~10-15% of timeline): Understanding requirements, documenting specifications, planning project structure, and establishing clear milestones. For redesigns, this includes auditing existing content and functionality.
• Design (~20-25% of timeline): Creating visual concepts that align with your brand and serve your users effectively. Includes initial design, client feedback rounds (typically 2), revisions, and final approval before development begins.
• Development (~40-50% of timeline): Building the actual website – frontend interfaces, backend functionality, content management systems, integrations, and features. This phase typically represents the largest time investment.
• Testing & Refinement (~10-15% of timeline): Comprehensive testing across browsers, devices, and user scenarios. Includes functionality testing, performance optimisation, accessibility review, and client feedback incorporation.
• Launch (~5% of timeline): Final preparations, DNS configuration, deployment to live servers, and immediate post-launch monitoring to catch any issues quickly.
• Post-Launch Support (30 days after launch): Bug fixes, refinements based on real user feedback, performance monitoring, and final adjustments. This period ensures the site performs well under actual usage conditions.

These phases overlap in practice. Design decisions sometimes emerge during development, testing identifies improvements, and content refinement continues throughout. The percentages provide general guidance, but every project is unique.

When to Start Preparing:

Allow preparation time before engaging developers:

3-6 months before desired launch for substantial projects requiring:

• Brand development from scratch
• Extensive content creation (50+ pages)
• Photography or video production
• Multiple stakeholder approvals
• Complex integration planning

2-3 months before desired launch for moderate projects with:

• Existing brand assets
• Straightforward content requirements
• Standard functionality
• Streamlined decision-making

Dependencies That Cause Delays:

Projects commonly stall waiting for:

• Content creation: Underestimated time requirement
• Stakeholder approvals: Committee reviews, legal sign-offs
• Third-party integrations: API access, credentials, technical specifications
• Photography: Professional shoots, editing, selection
• Decision-making: Choosing between design options, feature prioritisation
• Budget approvals: Unexpected scope changes requiring additional funds

Identify these dependencies early and plan accordingly. Developer time sitting idle whilst waiting for client input still costs you – either directly in hourly rates or indirectly in delayed launches affecting other work.

Managing Expectations:

Quality takes time. Rushing creates technical debt, poor user experience, and expensive fixes later. If you have an immovable deadline (event launch, grant deadline, regulatory requirement), communicate this immediately so developers can assess feasibility or recommend phased approaches.

Faster doesn’t always mean better. Some developers promise unrealistic timelines to win projects, then deliver poor quality or miss deadlines. Suspiciously short timelines often signal template-based approaches, offshore development, or inexperienced developers underestimating complexity.

Plan properly, communicate clearly, make decisions promptly, and your project will proceed smoothly through realistic timelines.

Existing website considerations

If you’re redeveloping or updating an existing website rather than building from scratch, additional preparation helps avoid complications.

Critical Information to Gather:

Website Background and History:

• When was the current site built?
• Who built it? (Agency name, developer contact)
• Is the original developer still involved or available?
• What platform/technology does it use? (WordPress, custom build, website builder)
• Why are you replacing/updating it? (Specific problems to solve, not just “it’s old”)

Access and Ownership:

Domain ownership (critical):

• Who owns the domain registration? (You, developer, previous agency)
• Where is it registered? (123-reg, GoDaddy, Fasthosts, etc.)
• Can you access the registrar account?
• When does it expire?

If you don’t own your domain, resolve this immediately. Previous developers or agencies sometimes register domains in their name, creating hostage situations. Transfer domain ownership to your control before proceeding with any new development.

Hosting details:

• Who provides hosting? (Your account or developer’s account)
• Can you access hosting control panel?
• What’s the hosting package? (shared, VPS, dedicated, managed WordPress)
• What’s the monthly/annual cost?
• When does hosting renew?

Website access credentials:

• Admin username/password for content management system
• FTP/SFTP access to server files
• Database access (if applicable)
• SSL certificate details

Never proceed with redevelopment if you can’t access these.

Content and Functionality Audit:

Which content needs migrating?

• Pages to keep as-is
• Content requiring updating/rewriting
• Content to archive or remove
• Blog posts or news articles (historical value)
• Product catalogues or databases

What functionality must carry forward?

• Existing integrations (CRM, booking systems, payment gateways)
• User accounts and data (membership systems)
• E-commerce order history
• Email newsletter subscribers
• Custom features or workflows

SEO Preservation Requirements:

• Current Google rankings to protect
• Important pages generating traffic
• Inbound links from other sites
• URL structure to maintain (or redirect properly)

What Problems Need Solving?

Be specific about existing site’s failures:

• Slow performance (quantify: “takes 8 seconds to load”)
• Poor mobile experience (describe specific issues)
• Difficult content management (what’s hard to update)
• Security concerns (been hacked, outdated software)
• Functionality not working (forms fail, integrations broken)
• Conversion problems (visitors don’t enquire/purchase)

Understanding what’s broken guides developers toward solutions.

Analytics and Tracking:

• Google Analytics access and tracking code
• Other analytics platforms (Matomo, Plausible)
• Conversion tracking setup
• Tag Manager configurations
• Historical data to preserve

Avoiding Hostage Situations:

Some developers or agencies create dependency by:

• Registering domains in their name
• Hosting on their infrastructure without providing access
• Custom-building functionality that only they can maintain
• Withholding source code or database access

Before engaging any developer, ensure:

• Domain registered in your name or transferable to you
• Hosting account in your name (or commitment to transfer on request)
• You receive all code, designs, and database exports
• No proprietary systems locking you to one supplier

Professional developers welcome client ownership and control. Those resisting transparency create red flags.

Migration Planning:

Discuss with your new developer:

• Content migration approach (automated versus manual)
• URL redirect strategy (preserving SEO)
• Timing of transition (staged versus immediate cutover)
• Email continuity during migration
• Testing period before going live
• Rollback plan if problems emerge

Proper planning prevents:

• Lost content or functionality
• Broken links and 404 errors
• Email downtime
• Lost search rankings
• Customer confusion during transition

Legal & compliance readiness

Modern websites carry legal and compliance obligations that must be considered during planning, not retrofitted after launch.

GDPR and Data Protection:

If you collect any personal information (contact forms, user accounts, newsletter signups, e-commerce orders), GDPR compliance is mandatory in the UK and EU.

Requirements include:

• Privacy Policy: Clearly explaining what data you collect, why, and how you protect it
• Cookie Consent: Informing visitors about cookies and obtaining consent where required
• Data Processing Agreements: If your developer or hosting provider processes personal data
• Data Security: Appropriate technical measures protecting stored information
• User Rights: Ability for users to access, correct, or delete their data

Your developer should implement:

• Cookie consent banners (when required)
• Privacy policy pages
• Secure data storage and transmission
• GDPR-compliant form processing

But you must provide the policy content and understand your obligations as data controller.

Accessibility Standards:

Web accessibility ensures people with disabilities can use your website. Legal requirements vary:

Legally required for:

• Public sector organisations (WCAG 2.1 AA standard)
• Education institutions receiving public funding
• Healthcare providers (NHS trusts)
• Larger private companies in some EU countries

Good practice for:

• Any business serving diverse audiences
• Organisations with accessibility values
• Websites wanting broader reach

Basic accessibility includes:

• Keyboard navigation (without mouse)
• Screen reader compatibility
• Sufficient colour contrast
• Text alternatives for images
• Proper heading structure
• Form labels and error messages

Accessibility benefits everyone: elderly users, mobile users, users in bright sunlight, users with slow connections. It’s inclusive design, not special accommodation.

Industry-Specific Regulations:

Certain sectors face additional requirements:

• Financial services: FCA regulations, financial promotions compliance
• Healthcare: Medical device regulations, patient confidentiality
• Legal services: SRA guidelines, client confidentiality
• Food businesses: Allergen information, nutritional claims
• Education: Safeguarding requirements, KCSIE guidance

Identify any industry regulations affecting your website during planning. Retrofitting compliance costs more than building it in from the start.

Terms & Conditions:

If you sell products, offer services, or allow user accounts, clear Terms & Conditions protect you legally.

Should cover:

• Service/product description and limitations
• Pricing and payment terms
• Delivery or fulfilment expectations
• Returns and refunds policy
• Liability limitations
• Dispute resolution process
• Governing law and jurisdiction

Consult a solicitor for T&Cs rather than copying from other sites. Your specific business circumstances require tailored terms.

Our Cyber Essentials Certification:

At Arkay Digital, we maintain Cyber Essentials certification, demonstrating our commitment to security standards. This means your project benefits from:

• Secure development practices
• Protected hosting infrastructure
• Regular security updates and patches
• Data protection controls

Security isn’t optional in 2026. Choose developers who demonstrate professional security practices.

Stakeholder & decision-maker alignment

Website projects involving multiple stakeholders require clear decision-making structures to avoid bottlenecks, scope creep, and frustrated developers.

Identify Decision-Makers Early:

Different aspects of web projects require different approvals:

Content decisions:

• Who approves page copy?
• Who signs off on brand messaging?
• Who decides what information gets published?

Design decisions:

• Who approves visual design concepts?
• Can one person decide or does a committee review?
• What happens if stakeholders disagree?

Technical decisions:

• Who approves functionality choices?
• Who decides on platform or integration approaches?
• Who authorises additional features discovered during development?

Budget decisions:

• Who approves the initial quote?
• Who authorises changes affecting cost?
• What’s the process if scope expands?

Timeline decisions:

• Who can adjust deadlines?
• Who prioritises competing requirements?
• Who decides what’s essential versus nice-to-have?

The Problem with Undefined Authority:

Projects lacking clear authority structures experience:

• Delayed decisions: Waiting for absent stakeholders to review
• Contradictory feedback: Different stakeholders requesting opposing changes
• Scope creep: Everyone adding their preferred features
• Design by committee: Compromise solutions pleasing no one
• Budget overruns: Uncontrolled additions and revisions

Establish Single Point of Contact:

Designate one person as primary contact between your organisation and the developer:

• Gathers feedback from stakeholders
• Consolidates into coherent direction
• Makes day-to-day decisions
• Escalates significant decisions to appropriate authority
• Maintains project momentum

This doesn’t mean one person makes all decisions, but they coordinate decision-making rather than developers receiving conflicting instructions from multiple stakeholders.

Managing Committee Reviews:

If committees must approve certain aspects:

• Set review schedules: Fortnightly design review meetings, not ad-hoc requests
• Consolidate feedback: One document with all committee comments, not individual emails
• Establish decision framework: What majority/consensus is required for approval
• Define revision limits: Two rounds of design revisions, not infinite iterations

Stakeholder Availability:

Confirm stakeholder availability during project timeline:

• Holidays or extended absences
• Busy periods preventing timely review
• Other projects competing for attention

If key decision-makers will be unavailable during planned development, either:

• Adjust project timeline around their availability
• Grant decision authority to available deputies
• Make critical decisions before their absence

Developers cannot proceed without decisions. Your unavailability doesn’t pause costs or extend deadlines proportionally.

Communication Preferences:

Establish how communication flows:

• Email for formal approvals and documentation
• Project management tools (ClickUp, Asana, Basecamp) for task tracking
• Video calls for complex discussions
• Slack or Teams for quick questions
• Response time expectations (24 hours, 48 hours)

Decision Fatigue and Analysis Paralysis:

Too many decisions overwhelm projects. Trust your developer’s expertise:

• You shouldn’t choose between 20 design options – narrow to 2-3
• You shouldn’t debate technical implementation details
• You shouldn’t redesign standard web conventions

Focus stakeholder attention on strategic decisions affecting business outcomes, not tactical choices better left to professionals.

Clear authority, responsive decision-making, and trust in professional expertise keep projects moving efficiently toward successful outcomes.

Your project preparation workflow

When you’re ready to engage a web developer, follow this preparation process:

1. Define your project scope – Identify whether you need a brochure site, e-commerce platform, custom application, or mobile app. List specific functionality requirements and integration needs. Clarify whether you’re building from scratch or redeveloping an existing site.
2. Document your audience and goals – Create clear profiles of your target users, their needs, and what you want the site to achieve for your business. Include user journeys where possible and note any accessibility requirements for your sector or audience.
3. Gather brand assets and design direction – Collect logos (vector formats preferred), brand guidelines, colour codes (hex values), and existing marketing materials. Create a collection of 3-5 website examples you admire with specific notes on what appeals to you about each.
4. Prepare or plan your content – Write or outline core page content, source images, and gather all information the site will present. Remember: content should inform design, not follow it. Allow 4-8 weeks for content creation if writing yourself, or 2-4 weeks working with professional copywriters.
5. Clarify timeline and budget – Determine realistic launch dates (allowing 8-16 weeks for substantial projects), identify any hard deadlines, and establish budget parameters for scope alignment. Calculate total cost of ownership including hosting, maintenance, and ongoing support.
6. Organise existing assets – If redesigning, verify domain ownership, gather hosting credentials, document current website issues, identify content to migrate, and ensure you have access to all accounts and systems.
7. Confirm decision-making structure – Identify who approves content, design, technical decisions, and budget. Establish a single point of contact to coordinate stakeholder feedback. Confirm stakeholder availability during planned project timeline.
8. Research compliance requirements – Consider GDPR obligations for data collection, accessibility standards for your sector, industry-specific regulations affecting website functionality, and terms & conditions needs if selling products or services.
9. Schedule initial consultation – Contact developers with this preparation complete. You’ll have substantive discussions rather than vague explorations, receive accurate quotes rather than rough estimates, and begin development with clarity rather than assumptions.

Thorough preparation typically takes 2-4 weeks but saves weeks of mid-project delays and prevents costly mistakes.

Ready to start your project?

Once you’ve worked through this preparation checklist, we can help you move forward efficiently. At Arkay Digital, we use a structured project kickoff process that captures your requirements systematically, ensuring nothing gets missed and giving you a clear roadmap from concept to launch.

Our approach means:

• Accurate quotes based on complete requirements, not guesswork
• Realistic timelines with defined milestones and deliverables
• Transparent communication through every project phase
• Professional security standards (we’re Cyber Essentials certified)
• No surprises – thorough planning prevents mid-project scope disputes

Contact us to book a consultation, or if you’re ready to get started. We’ll guide you through our discovery process and provide a detailed, transparent quote.

We work primarily with SMEs and educational institutions across the UK, delivering WordPress websites, custom web applications, and mobile apps. Whether you’re building from scratch or redeveloping an existing site, proper preparation protects your investment and sets your project up for success.