What we ask in discovery
| Topic | Example questions |
|---|---|
| Goals | What counts as a lead, and how many do you need? |
| Customers | Who calls you, and what do they ask first? |
| Services | Which services make the most money? |
| Areas | Which towns or neighborhoods matter most? |
| Content | What photos, reviews and proof do you have? |
| Systems | Which CRM, booking or payment tools must connect? |
Expect practical questions, not design trivia. Colors come later.
What we review
We look at your current site, your Google Business Profile, your competitors and any traffic data you have. Search Console shows which pages bring visits. GA4 shows where visitors leave. For a redesign, we list every URL that earns traffic or links. Google's site move guide says each old URL needs a matching new one.
What discovery produces
- GoalsLeads, services and areas agreed in writing.
- SitemapEvery page and how the pages connect.
- Content planWho writes, photographs and approves each page.
- TimelineDated milestones for design, build and launch.
The sitemap is the site's information architecture. Nielsen Norman Group separates it from navigation. The structure comes first, and menus follow from it. Read more on information architecture.
Why it saves money
Good example. A pest control company agrees on six service pages, three city pages and call tracking before design starts. Design then moves fast, with few revisions.
Bad example. A company skips discovery, and the team designs a homepage before anyone decides which services to feature. Every later page triggers new debates.
Our web design projects start with discovery, and you keep the plan whether or not you build with us.