Web developer in Seattle: booking and forms that keep what a customer typed
I build booking flows and forms that hold on to every detail a customer enters, even after a wrong tap or a refresh, and the pages around them load fast on mobile data. An audit of the site you have now is the first piece of work I'd do as a web developer in Seattle. It decides between a fix and a rebuild, and my team does either in Kolkata, India.
Overview
Four things to remove, or a rebuild?
A site collects extra parts over time. A plugin here, a tracking script there, an extra field on a form.
So I check first. Sometimes the finding is a handful of things to take out, and when it is, that's the job I quote.
If the audit points to a rebuild, design joins the scope, and the designer on my team draws the new screens before they're built.
What a booking flow has to get right
I'll test each of these on a phone before launch.
- 01
Nothing typed twice
a form carries the details forward from the step before. - 02
Your place held
going back a step doesn't wipe the booking. - 03
No extra steps
any field you can't justify comes out. - 04
A clear next step
the confirmation screen says what happens now and who will be in touch.
What gets built here
Service businesses and software companies
The work starts in a different place for each. Try your own booking flow on your phone and note each step that made you pause. Our first call starts from that list.
- Trades, clinics, studios and restaurants — the booking flow, the contact form and the phone number come first, each one checked on a phone.
- Software companies — the marketing site sits beside your product, so its code, its speed and the scripts it loads are built for your engineers to inspect.
What a scope from me looks like
A first scope for a site that already takes bookings
Included
- A written scope: every page and feature as its own line, agreed before work starts
- Design to build, reviewed on a staging URL that stays open the whole project
- Mobile first — checked on a real phone
- Domain, hosting and every account created in your name from day one
- Booking and form flows tested on a phone over a slow connection
- Basic on-page SEO: titles, descriptions, headings, sitemap, Search Console connected
- A runbook at handover: how to edit it, what renews and when
Phase two
- A rebuild, if the first round of removals doesn't cover it
- A link from the booking flow into the calendar you use now
- Ongoing SEO once the site has traffic to read
- A maintenance plan once the site is live
- Logo and brand design, quoted separately from the build
Not doing
- Guaranteed rankings
Where this comes from
Where my 900+ comes from
My record runs to 900+ projects completed since 2017, and the US work alone comes to 600+ projects for US clients.
On a fix, every change is made first on a copy of your site, where you can book a test appointment yourself.
The team works on your schedule, in your time zone. We meet on video, and every page sits on a staging link you can open whenever you like.
What moves the number
What sets the amount of work
When your calendar has to receive each booking, that link is the heaviest piece of work. The other lines each carry their own reason.
| What changes it | Why |
|---|---|
| How much of the current site stays | whatever stays doesn't need a new build |
| Steps in the booking flow | more steps mean more screens to build and test |
| A calendar or scheduling link | each system shares its data on its own terms |
| Tracking scripts you keep | each is loaded so it doesn't hold up the page |
| Pages that rank today | each one is carried across to the new build |
| Forms beyond booking | each sign-up or enquiry form is built and tested on its own |
What changes the size of the job.
Nearby
On the same coast: Los Angeles, San Francisco
Portfolio sites for studios and production companies are planned on the Los Angeles page, and the San Francisco page builds a software company's marketing site around a claim of its own.
FAQ
Before the audit starts
Every test runs on a real phone over a throttled connection.
Does a technical audience change how a website is built?
- A technical audience adds to the testing. I test each flow on a slow phone connection and look at the page in the browser's developer tools, since a technical visitor may look there too.
What decides the size of a booking flow?
- A booking flow's size depends on the number of steps, what each step has to remember and whether it writes into a calendar you already use. Each of those becomes a separate line of the written scope, and you'll see what a simpler flow would leave out.
When is a site slow enough to matter?
- A site is slow enough to matter when a visitor on a phone is left waiting for the first screen. I'll measure it on a mid-range phone with a throttled connection, and list each thing that holds the page up, largest first.
What happens to tracking scripts during an audit?
- Each tracking script is listed with what it measures and who reads its reports. Scripts you still use are kept and loaded after the page itself, and any that nobody reads any more come out, with your agreement.
Next step
Have customers complained about the site?
If customers have written in about the site, those messages are worth forwarding. They'll show me which pages to open first.
Published · Updated