IVAN FERLAND / Project case study

Handy Andy: a website for a real business.

A public website for painting and general contracting, built around services, process and a clear path to a quote request.

← Home

My role

Website development

The result

A public business website gives visitors a coherent introduction to Handy Andy’s services and a path to discuss their project.

The public Handy Andy Renos website, captured October 2026.Open the public website in a new tab
PUBLIC WEBSITE · OCTOBER 2026 CAPTURE · handyandyrenos.ca

01

The problem

A visitor considering work on a home needs to understand the services, how a project is scoped and how to get in touch. The website brings those questions into one readable path, from the business introduction to a quote request.

02

Operational context

I built handyandyrenos.ca for Handy Andy Home Improvement. The public site presents painting and general contracting, with service, about, process and FAQ sections. The contractor workflow in this portfolio’s lab is a separate synthetic software demonstration.

Business identity
Public website
Visitor next step
The website presents the business to visitors. The separate lab demonstrates fictional internal operations and is not the site’s production architecture.

03

My contribution

My contribution is the website itself: a public presentation of the business with service information, an explanation of the process and contact or quote-request links. Visitors can learn how scope, preparation, materials and exclusions shape a project before starting a conversation.

04

Constraints

  • Explain services and project expectations without presenting an enquiry as a confirmed estimate or booking.
  • Keep customer information and private business operations outside this public account.

05

Implementation decisions

  • Connect the service descriptions, process and FAQs with the visitor’s next step: a quote request or contact.
  • Use clear scope and preparation language to make expectations visible before the project conversation.

06

Alternatives considered

  • A visual brochure without service scope or a clear next step would leave the visitor’s practical questions unanswered.

07

Validation approach

  • The public page presents painting and general contracting, with service, process, FAQ and contact navigation.
  • Quote-request and contact links are visible; an automated estimate, booking or payment engine is not part of this case.

08

What this shows

A public business website gives visitors a coherent introduction to Handy Andy’s services and a path to discuss their project.

09

Limits of the evidence

  • Traffic, lead generation, customer counts and business results are not quantified here.
  • The synthetic quote-to-payment lab is independent; its invoice and payment logic is not attributed to the business website.

Inspect the work

Explore website services

Discuss a website project

A similar problem in your organization?

This example can be a starting point for defining your own project, its dependencies and acceptance criteria.

Websites & web platforms