A focused Local Legacy website refresh can take 1–3 weeks. A larger rebuild usually takes longer, and the useful estimate comes after we understand the scope, content, access, and approvals. A launch date is a plan with dependencies, not simply the number of days needed to arrange a homepage.
You do not need to arrive with every word written. You do need to help us understand the business, confirm facts, and make decisions as the work develops. One person who can provide timely, consolidated feedback makes that process much clearer.
The sequence we use
Local Legacy starts by learning how your business works, who the website needs to reach, and what visitors should be able to do. The usual sequence is discovery, proposed page structure and design direction, build, a review round, final approval, and launch.
| Stage | What we work on | What we need from you |
|---|---|---|
| Discovery | Business goals, audience, existing site and required functions | Accurate service details, priorities, constraints and access information |
| Structure and direction | Proposed pages, message hierarchy and design approach | A decision on the direction before detailed build work proceeds |
| Build | Site structure, design, mobile layout, basic SEO setup and agreed functions | Missing facts or assets, with one person coordinating answers |
| Review | The working website and agreed customer tasks | Consolidated feedback, factual corrections and content approval |
| Final approval | Resolution of review items and launch readiness | Approval from the designated decision-maker |
| Launch | Agreed release steps and checks | Access and availability for any owner-controlled account actions |
We also help turn your knowledge into website copy. The exact content volume and deliverables belong in the proposal, so writing support does not become an undefined task for either side.
What makes a focused refresh different from a rebuild?
A refresh fits when the foundation works and the main problems are dated visuals, unclear messaging, or a few weak pages. That is the kind of focused work for which a 1–3 week timeframe may be realistic after the assignment is understood.
A rebuild may involve a different page structure, platform, content system, or substantial functional changes. Existing pages and URLs may need a migration plan. A larger project also has more decisions to approve, even if the visual design feels simple.
We recommend considering a rebuild when the site is hard to update, works poorly on phones, has a confusing structure, or needs substantial changes to what it does. The assessment should identify which problems can be fixed within the current system and which require replacement.
Our refresh planning guide covers what to retain and check. The timeline conversation turns that work into a sequence for your project.
What to provide before the build depends on it
Gather your existing logo and brand materials, current website and domain access, approved photographs, contact details, and a clear service-area description. We also need relevant prices you want published and any legal or industry requirements you must follow.
You are the authority on facts that cannot be verified from the outside: work you accept, qualifications you hold, how estimates are handled, and the promises you can make. Tell us which claims need approval from another person before they go live.
Use account invitations rather than placing passwords into a shared content document. If a former provider controls an account, identify that early. Access issues can delay launch even when the new pages are finished.
For a new Cape Coral business, the missing input might be approved service details. For an established Port Charlotte business, it might be access to the old platform. For a Fort Myers company adding services, it might be deciding which offers belong in the first phase. These are illustrative situations; the dependency matters more than the city.
Four common reasons a date moves
The offer changes during design. If the target customer or core service changes, the page structure and writing may need to change too. Our owner's warning is straightforward: “A new design cannot fix an unclear offer.” Resolve the business decision before expecting layout changes to settle it.
Feedback arrives in conflicting pieces. One reviewer asks to simplify a page while another asks to add several offers. Give the team a single approved direction rather than a collection of unresolved opinions.
New functions appear late. Adding online payments, a booking workflow, or a custom estimate tool may require new work and external setup. Identify these needs during discovery and price changes deliberately.
Content or access remains unavailable. We can help with writing, but we cannot responsibly invent your services, credentials, project permissions, or account authority. Separate what can proceed from what needs your input.
How to discuss a firm launch event
Tell us why the date matters: a new opening, an announcement, a campaign, or a replacement deadline. Then decide what must be live for that event and what can follow.
A focused first phase can be useful if it still gives visitors accurate information and a working next step. Do not move essential contact testing or factual approval into “phase two.” The scope can become smaller; the basic customer journey still needs to work.
Ask the proposal to state when the schedule starts, what approvals it assumes, and how changes affect the date. We give a more useful timeline once the scope is clear rather than promising the same duration for every website.
Does the 1–3 week range apply to a new large website?
No. It describes a focused refresh. A larger rebuild needs its own timeline based on content, functions, migration, and review needs.
Do I need finished copy before contacting you?
No. Bring your knowledge of the business and whatever material already exists. We help shape clear copy, with the included work defined in the scope.
What can I do to keep the project moving?
Name one decision-maker, confirm the offer and page plan early, gather account access, and return consolidated feedback at the agreed checkpoints.
Discuss your launch date. Share the website's purpose, current state, and any real deadline so we can plan a practical website-design scope.