Evaluating a Montreal Web Agency's Portfolio: What to Look For

Not all portfolio pieces are equal: What to look for: - Projects similar to yours (industry, size, complexity) - Recent work (last 2-3 years) - Full projects, not just design mockups - Work for Montreal businesses (shows local understanding) - Results and outcomes, not just pretty screenshots Red flags: - All projects look identical (template-based) - No details about their involvement - Only showing personal projects or spec work - Claiming work from agencies they used to work for - No live websites to actually visit Ask directly: - "Can I see 3 projects similar to mine?" - "What was your specific role in this project?" - "Can I visit the live website?" - "What results did the client achieve?" - "May I contact this client?" If an agency can't show relevant experience, they're learning on your dime.

Agencies sometimes misrepresent their role: Common misleading practices: - Showing work from when they worked elsewhere - Taking credit for template purchases - Highlighting design only (outsourced development) - Featuring sites they didn't actually build - Including outdated work no longer live How to verify: - Visit live websites (not just screenshots) - Check site footer credits (sometimes developers credited) - View page source for clues - Search for project case studies - Contact clients directly if possible Questions that reveal truth: - "Walk me through your process for this project" - "What challenges did you face and how did you solve them?" - "Who on your current team worked on this?" - "What was your exact scope of work?" Agencies with nothing to hide provide detailed case studies, not just pretty pictures.

Pretty designs hide sloppy code: What to test: - Mobile responsiveness (resize browser) - Page speed (use PageSpeed Insights) - Cross-browser compatibility - Forms and interactive features - Search functionality - Actual user experience Technical red flags: - Slow loading (3+ seconds) - Broken on mobile - Console errors (open developer tools) - Accessibility issues - Poor performance scores - Missing features they claim Bilingual sites specifically: - Actually test both languages - French version as good as English? - Language switcher working properly? - Proper hreflang implementation? - URLs structured correctly? If portfolio sites perform poorly, yours will too. Technical quality matters as much as visual design.

Local experience matters: Montreal-specific indicators: - Work for local businesses - Proper bilingual implementation - Understanding of Quebec market - Local industry knowledge - References to Montreal challenges Questions to ask: - "How many Montreal clients do you have?" - "What's unique about building for Quebec market?" - "How do you handle bilingual requirements?" - "Can you show me local client references?" What experience reveals: - Bill 96 compliance understanding - Quebec payment preferences (Interac) - Local shipping complexities - Montreal search behavior - Cultural nuances Agencies claiming Montreal expertise should easily show local work.

What portfolios don't show: Missing information tells you: - No client names: NDAs or unhappy clients? - No metrics: Didn't track or poor results? - No live links: Site dead or never launched? - Vague descriptions: Minimal involvement? - Old work only: Not getting new clients? Good portfolio indicators: - Detailed case studies - Client testimonials - Specific results and metrics - Before/after comparisons - Problem-solving narratives - Technical challenges overcome Red flag combinations: - Beautiful designs + slow websites = Visual focus over technical quality - All template-based + high prices = Overcharging - No similar projects + confident promises = Unrealistic - Outdated portfolio + modern claims = Out of touch Trust your instincts. If something feels off about a portfolio, it probably is.

Get specific about portfolio work: About specific projects: 1. "What was the client's goal and did you achieve it?" 2. "What was your team's specific role?" 3. "What challenges arose and how did you handle them?" 4. "What were the measurable results?" 5. "Is the client still with you for support?" 6. "May I speak with this client?" About their process: 1. "How do you approach projects like mine?" 2. "What's your typical timeline?" 3. "How do you handle scope changes?" 4. "What happens if we're not happy?" 5. "Who would actually work on my project?" About their team: 1. "Who on your current team worked on these projects?" 2. "What's your team's technical expertise?" 3. "Do you have in-house designers and developers?" 4. "What's your team turnover rate?" How they answer matters as much as what they answer. Evasiveness is a red flag.