Steven Turgeon
Website Intake

Website Intake Form

Tell us about your business so we can build something that actually works for it.

The more we learn here, the less back-and-forth later — and the closer the first draft lands to what you had in mind. Answer what you can; nothing is locked and you can come back to the rest.

Nothing to install, nothing to lose
Every answer saves in this browser as you type. Close the tab and come back whenever — it will still be here.
Only the questions you need
Tell us what kind of project this is in step 1 and the rest of the form adapts. Quick asks the essentials; Everything adds the detail questions.
Send it back however suits you
Email, download, copy-paste, or print it and write it in by hand. All four are at the bottom.

Roughly 10 minutes on Quick. Prefer French? Use the FR switch at the top.

1What are we building?

This one answer decides which questions you get asked. Pick the closest fit — we can change it later.

The closest description

Plain language is perfect. No need to sound technical.

Who are we talking to?

So we know who to send drafts and questions to.

Who signs off on the final site?

Knowing this up front avoids a round of surprise revisions late on.

2What’s the actual problem?

The most useful part of this form. A website is a solution — we’d rather understand the problem before picking one.

A rough order of magnitude is plenty.

“More customers” is hard to aim at. “Twenty booked inspections a month, without phoning” is easy to aim at.

What kind of budget are we working with?

An honest answer here changes what we recommend — it doesn’t change what we charge for the same work.

How firm is the timing?

3Business information

The basics — who you are and what you do.

This often becomes the foundation of your homepage hero copy.

4Who is this for?

Who shows up, where they are, and what language they read in.

Who will use it?
What languages does the site need?

If you do business in Quebec, note that the Charter of the French Language sets requirements for commercial websites — we’ll flag anything relevant.

Accessibility

5What must it do — and what must it not?

Three things, ranked. Everything can’t be first, and the ranking is what protects your budget when something has to give.

Naming what you don’t want is as useful as naming what you do — it stops us building things you’ll never use.

We’ll build so these stay possible without a rebuild.

6What’s there today

If something already exists, we’d rather keep what works than start from zero.

Do you have a website now?
Do the old page addresses need to keep working?

If an old page ranks well on Google, we point the old address at the new one so you don’t lose that.

Who’s writing the words?

Waiting on text is the most common reason a site sits unfinished. Worth being realistic here.

7Domain & hosting

Where the site will live.

Without "https://" — just the domain.

Domain status

8Pages you need

Tick everything that fits. Most small business sites use 4–6 pages.

9Services / offerings

3–6 of your main services. One short sentence each — we'll polish the wording.

10Design preferences

Pick what feels right. We'll refine after the first draft.

Color palette
Typography
Design mood (pick all that apply)

Tell us what specifically you like about each — colors, layout, vibe, etc.

11Contact information & hours

What customers need to reach you.

This is the inbox that receives every Contact / Booking form submission. Often the same as your public email.

Business hours

12Google Maps

Embed a map on your contact page so visitors can find you.

13Social media

Paste full URLs. Leave blank if you don't have one.

14Website forms

What information should each form collect?

Contact form fields

Standard fields. Tick the ones you want.

Booking / appointment form
Booking form fields

15Team / staff

Skip if you don't want a team section. Otherwise, list the people you'd like featured.

16Testimonials / reviews

Real quotes from real clients only — please don't make any up.

17Call-to-action wording

The button visitors will see across the site. One sharp ask is better than three vague ones.

What you most want visitors to do.

Softer alternative for visitors not ready to book.

18How people find you

A site nobody can find is an expensive business card.

Guesses are fine. What customers actually say beats industry jargon every time.

Two or three. Knowing what you think of them tells us more than the sites themselves.

Google Business Profile

For a local business this often drives more calls than the website does. It’s free.

Paid advertising

Ads need pages built to convert. Worth knowing before we design them.

19Measuring what happens

What you measure decides what you can improve — and what you must disclose.

Do you want visitor statistics?
Advertising or tracking pixels to install

Each one you add is a third party receiving your visitors’ data, and has to be named in the privacy policy.

Cookie consent banner

Quebec’s Law 25 and Europe’s GDPR both require consent before non-essential tracking. Picking privacy-friendly analytics usually means no banner at all.

20What else does this need to talk to?

Anything the site should send data to, or pull data from.

Tools you already use

If two places can disagree about the same fact, we need to decide up front which one wins.

21Selling online

Only shown because you said the site needs to sell things.

What are you selling?

Separate with commas. These become the shop’s navigation.

Three or four is enough to build against — you’ll add the rest yourself later.

Shipping

Flat rate is simplest and the easiest for customers to understand. Surprise shipping costs at checkout are the number one reason carts get abandoned.

If you’re unsure, say so — this is a question for your accountant and we’ll leave it configurable.

Taking payment
Do buyers have to create an account?
Track stock levels?

22Accounts and logins

Anything with a login needs deciding carefully — it’s the part that’s expensive to change later.

Who logs in?
How do people get an account?
Sign in with an existing account?
Two-step verification
Will any of this be stored?

Each of these raises the legal bar. We design so card details are never stored on your server at all.

23Life after launch

A site is not finished when it launches. Deciding this now avoids an awkward conversation in month three.

Who looks after it once it’s live?
How technical is that person?
Rules you have to follow

Tick anything you know applies. “Not sure” is a perfectly good answer — we’ll check.

Where should it run?
If the site went down for an hour…

This decides how much we spend on backups, monitoring and redundancy. Being honest keeps you from paying for either too much or too little.

24Assets & files

List the files you'll send us — we'll match them to the website by filename.

How to send files: Email everything (logo, photos, brand guidelines, anything else) to steve@turgeons.com. For large bundles, a Dropbox / WeTransfer / Google Drive link is fine — just put the link in the relevant field below. Reference each file by the filename you list here.
How are you sending files?
Photos / images

List every photo you'll send and where it should go on the site.

25Privacy & legal

Every site we build includes a privacy policy. A few quick details lets us draft yours.

Existing privacy policy?

26Anything else?

Things we didn't ask about. Goals, things to avoid, deadlines, accessibility needs, languages, anything.

→Send it back to us

Any of these works — pick whichever is easiest.

Questions at any point? Write to steve@turgeons.com.

Before you send it

You can send it as-is and fill the rest in later — we’ll ask about anything we still need.