Process / what happens when

Clear steps.Fast decisions.Built in 2–4 weeks.

A typical small-business website moves from the first conversation to launch in two to four weeks. Larger or unusually complex projects get their own schedule before work begins.

One person
start to finish
Typical timeline2–4 weeks
Included feedback2 revision rounds
Your point of contactSteve, the whole way through
01

Before the clock starts

Agree on the job before making the website.

We start with the business, the customer, the pages, the features and what success should look like. You receive a written proposal covering the exact scope, schedule, two revision rounds and payment stages. The project is reserved when the proposal is accepted and the deposit is paid.

02

The typical 2–4 week schedule

Days 1–3

Direction

I organize the pages, review your materials, study the customer and establish the visual direction. Missing content or access is identified before it can hold up the build.

Week 1

Design

The key mobile and desktop layouts take shape around the real message of the business. You review the direction as a working system, not a disconnected mood board.

Week 2

Build

The approved direction becomes a responsive website. Forms, motion, accessibility, search foundations and the small-screen experience are built into the same process.

Weeks 3–4

Refine and launch

Final content, revision rounds, device testing, forms, links, search settings and the live domain are completed. Straightforward projects may launch sooner; larger builds receive a separate schedule.

03

What I need from you

Business facts

The information only you know.

Your services, audience, priorities, contact details and the questions customers ask most often.

Brand materials

What already exists.

Your logo, photography, reviews and any writing worth keeping. I organize the message and identify what is still missing.

Access

The accounts needed to launch.

Domain, hosting, email, analytics or other access is requested only when the project actually needs it.

Decisions

Clear feedback on schedule.

The two-to-four-week timeline depends on receiving materials, approvals and consolidated feedback by the dates we agree on.

04

Revisions without the loop

Two organized rounds are included.

The first round addresses the direction, hierarchy, content and major layout decisions. The second round handles refinements before final testing. Feedback is gathered together so the project keeps moving. New pages, features or a change in the agreed direction are scoped separately instead of being hidden inside endless revisions.

05

Payment stages

01 / ReserveDeposit when the project is booked
02 / ApproveProgress payment after design approval
03 / LaunchFinal payment before the site goes live
06

Launch and what follows

Before launch

Test the actual experience.

I check current phones and desktop sizes, navigation, forms, links, accessibility basics, search settings and the connection to your real domain.

Launch day

Put it where customers can use it.

The approved site is published, the domain is confirmed, forms are tested again and the ownership and account setup are documented.

First 14 days

Correct what belongs to the build.

For fourteen days after launch, I correct issues tied to the agreed project. New requests or added features are treated as new work.

Afterward

Come directly back to me.

Updates, new sections and larger improvements can be handled through WebDotMe. Any ongoing arrangement is agreed clearly instead of appearing as an unexpected monthly obligation.

Have a project that should be live in the next few weeks?

Tell me what the business needs. I will reply with the next useful question, not a sales sequence.

Start a project
Next / StartTell me what you’re making.