What Does a Realistic Small Business Website Timeline Look Like When the Launch Has to Beat Tax Season?
The situations described here are composites drawn from the types of jobs and decisions we encounter regularly. Names and specific figures are illustrative.
A three-preparer tax and bookkeeping practice had an eight-year-old website. It still listed a preparer who had retired, and the “schedule an appointment” button opened an email draft. The week after the fall extension deadline, the owner asked us one thing: could a new site be up before filing season opened in late January? That is a question about a small business website timeline, and the honest answer was yes, if the parts she controlled moved as fast as the parts we controlled.
Most owners hear “how long does a website take” and think about the build. The build is the part that is easiest to predict. Below is how the other parts went for her, week by week, and where the extra weeks came from.
The plan we wrote on the first call
We worked backward from the date that mattered. The IRS opened the 2026 filing season on January 26, and most years land in that same late-January window. Her busiest call weeks start right around then, when W-2s show up in mailboxes. She did not want to be learning a new appointment system in February.
So the target was not “launch by January.” It was “launch by mid-December,” because a new site is not finished the day it goes live. Google has to recrawl it, swap old URLs for new ones, and settle the pages into results. A site that launches the week before the rush is still only partly indexed while the rush is happening.
The plan for a site her size was eight pages and roughly eight weeks: one week of discovery, two weeks of content and photos, a few weeks of design and build overlapping with content, and two weeks of review and launch. That is in the normal range for a professionally built small business site. Most of the build estimates you will find online sit somewhere between four and ten weeks for a site like this, and they mostly agree on what makes it run long.
Where the first two weeks went
Discovery went fine. We mapped the pages she needed: individual tax prep, small business bookkeeping, payroll, an about page with real photos of the three preparers, a “what to bring” page, and a booking page. We pulled her old site’s URLs so every one of them would have somewhere to redirect.
Then we asked for the login to her domain. That is where the schedule started to slip.
Her domain had been registered eight years earlier by the person who built the original site. It sat in his registrar account, under his name. He had moved on to other work and answered emails about once a week. She assumed the domain was hers because she had paid for it. Legally and practically, the registrar treated him as the registrant.
This comes up on a large share of the rebuilds we take on. The fix is not complicated, but it is slow. Under ICANN’s transfer rules, a domain cannot move to a new registrar within 60 days of being registered or transferred, and only the registrant of record or the administrative contact can start a transfer. Some registrars also apply a 60-day lock after a change of registrant. So the order of operations matters. We did not try to move the domain before launch. We asked the former web person to change the DNS records to point at the new host and to start an account-to-account handoff inside his registrar so she would own it. It took him four weeks to do both.
We would have kept building either way. But a site that is ready with nowhere to point is not live, and it was the first thing on the calendar that nobody could speed up by working harder.
The content weeks, which became five
The second slip was the one almost every project has. We had planned two weeks for her to review service page drafts, send photos, and write a short bio for each preparer. She was not slow because she did not care. She was slow because her days were full of clients, and writing about her own business felt harder than doing it.
The misconception she brought in, and most owners bring in, is that design is the slowest part. In practice, designers and developers wait on words and photos far more than owners wait on designers. We have built a real estate site in about a month when the owner had content ready and answered questions the same day. The same scope can run three months when every page waits a week for approval.
What helped was changing the ask. Instead of “write the payroll page,” we sent her eight specific questions about payroll clients, recorded a twenty-minute call, and drafted the page from her answers. She edited instead of writing. That got the service pages done in week five instead of week three.
Here is how the plan and the reality lined up by the end:
| Phase | Planned | Actual | What moved it |
|---|---|---|---|
| Discovery and page map | Week 1 | Week 1 | On schedule |
| Domain and DNS access | Week 1 | Weeks 1 to 5 | Domain held in the former web person’s account |
| Content and photos | Weeks 2 to 3 | Weeks 2 to 6 | Owner writing between client meetings |
| Design and build | Weeks 3 to 6 | Weeks 4 to 8 | Pages waited on approved copy |
| Review, redirects, launch | Weeks 7 to 8 | Weeks 9 to 10 | Holiday week and a second review round |
Design and build, the part people picture when they think about a website project, slipped only because it was waiting on the two rows above it.
The decision in week seven
By week seven the calendar was tight. Launching in the second half of December was still possible, but only with the eight core pages. She also wanted six more: a page for each type of business return she handled and a page answering common questions about extensions and estimated payments.
The choice on the table was to hold launch until all fourteen pages were ready, which would have pushed it into mid-January, or launch the core eight before the holidays and add the rest in February.
We recommended launching the core. The pages that would carry January were the ones people use to decide and book: individual prep, bookkeeping, the preparers, what to bring, and the booking page. The extra pages were good ideas that would help over a full year, not in the first three weeks of filing season. Holding everything for them would have traded four weeks of Google catching up for pages that would not have mattered much until spring.
“Google’s own guidance says a small site that changes its URLs can take a few weeks for most pages to move over in search. Those weeks belong in the plan before your busy season starts, not in the middle of it.”
Vlad Bogza, Founder, Powerful Media Solutions
This was also the point where spending more stopped helping. She asked whether paying a rush fee would get everything done by mid-December. It would not have. No amount of developer time writes her bio, approves her pricing language, or makes a former vendor answer email faster. Extra money buys speed on the parts that were already on schedule.
What happened after launch
The site went live in the last week of December. Every old URL had a 301 redirect to its closest new page. We submitted the sitemap and requested indexing for the main pages.
Then we waited, which is the part of a website timeline that rarely shows up on a quote. Google’s own documentation says crawling can take anywhere from a few days to a few weeks, and that for a small to medium site with URL changes it can take a few weeks for most pages to move over. That matched what we saw. The home page and booking page showed the new versions within about ten days. Two of the old service URLs kept showing in results until early February before the redirects took over.
| After-launch step | Typical time, per the source |
|---|---|
| Google recrawling pages you submit | A few days to a few weeks (Google Search Central) |
| Most pages moving to new URLs on a small to medium site | A few weeks (Google Search Central) |
| Keeping old-URL redirects in place | Generally at least one year (Google Search Central) |
| Domain transfer blocked after new registration or transfer | 60 days (ICANN) |
The first weeks of filing season were not dramatically different from the year before in raw call volume. What changed was what the calls looked like. Clients booked through the online calendar instead of leaving voicemails, and the “what to bring” page cut down on second appointments for missing documents. By mid-February, about a third of new appointments came through the booking page. The six extra pages went up in late February, once the office could spare an afternoon to review them.
What owners usually ask at this point
The first question is always some version of “how long does a website take.” For a typical service business with five to fifteen pages, eight to twelve weeks from first call to launch is a realistic range when someone else is building it. It can be shorter if your content is ready on day one, and longer if the site needs online payments, client portals, or integrations with outside software.
The second is whether to build it yourself to save time. A drag-and-drop builder can be faster for a small, simple site, but the content and domain problems do not go away just because you are the one building. We wrote about that tradeoff in our post on whether to hire a web design company or build it yourself.
The third is how far ahead of a busy season to launch. Our working answer is four to six weeks before the first busy week, so Google has time to process the new pages and you have time to fix what real visitors find. If your old site ranks well, lean toward the longer end, because that is the ranking you are asking Google to move.
The fourth is whether SEO work should wait until after launch. It should not. Page structure, redirects, and the wording of service pages are decided during the build, and those decisions shape how the site shows up for months. That is why we plan SEO work into the build instead of adding it later.
What we would tell the next owner who calls in October
The calendar risk on a website project sits mostly outside the code. Find out today who controls your domain, your hosting, and your Google accounts. Gather photos before anyone asks for them. Decide which pages actually carry your busy season and accept that the rest can come later. If your season starts in late January, mid-October is about the right time to start, not early.
Her own summary was that the build was the easy part, and the real work was writing her content and getting her domain back. A realistic small business website timeline plans for both, and for the weeks after launch when Google is still processing the new pages.
If you are weighing a rebuild against a busy season of your own, you can read more about how our web design service plans a build.
Sources
