Frequently asked questions

Answers before anyone signs a contract.

Here is how we think about scope, schedules, accessibility, ownership, hosting, and the work your staff will need to do.

Project basics

Before the first call.

What kinds of organizations does Townline work with?

We focus on municipalities, public agencies, nonprofits, and growing organizations with important information to explain and a small team responsible for keeping it current.

Do we need a finished scope before contacting you?

No. Send the current website, the problems people report, the result you want, and any deadline or procurement rule you already know about. We can help turn that into a scope.

How much does a project cost?

We quote work after a short scoping conversation because content volume, documents, integrations, accessibility needs, procurement, and review time can change the workload substantially. The written proposal identifies deliverables, assumptions, exclusions, payment milestones, and any optional work before you commit.

Can Townline work within a phased budget?

Yes. We can begin with an assessment, information architecture, accessibility repairs, or one priority service area. Each phase has its own deliverables and should be useful even if the next phase waits.

Delivery

While the work is underway.

How long does a website project take?

A focused assessment often takes 2 to 4 weeks. A redesign schedule is confirmed after we understand the page count, documents, integrations, procurement steps, and who needs to review the work. The proposal includes review dates and launch criteria.

What will our staff need to provide?

We typically need access to subject-matter experts, current analytics and platforms, existing content and documents, brand materials, policy requirements, and timely reviewers. We make responsibilities and decision dates visible so participation is predictable.

Can you migrate our existing pages and documents?

Yes. Migration begins with an inventory and rules for keeping, improving, combining, archiving, or retiring material. Important URLs, metadata, records, and search visibility are considered alongside content quality and accessibility.

Will our team be able to update the website?

Yes. We plan content types, reusable components, permissions, documentation, and training around the staff who will actually publish. Routine updates should not require a developer.

After launch

Ownership, accessibility, and ongoing care.

Does Townline guarantee WCAG compliance?

We design and test toward an agreed target, usually WCAG 2.2 Level AA, and document the checks completed, known issues, and responsibilities after launch. No vendor can guarantee that future content, documents, or third-party tools will remain conformant without continued review.

Who owns the finished website and content?

Ownership and licensing are written into the project agreement. Our intended model gives clients control of their approved content, accounts, and agreed deliverables, with administrator access and handoff documentation.

Do you provide hosting and maintenance?

Yes. A support plan can include hosting coordination, updates, backup verification, uptime monitoring, accessibility checkups, content help, priority response, and quarterly planning. We quote it after reviewing the platform, response expectations, and publishing volume.

Can you work with our existing platform or vendors?

Often, yes. We review the platform, contracts, integrations, administrator access, renewal dates, and staff capacity before recommending what to keep or replace. We do not begin with a predetermined tool.

Still deciding?

Ask the question that is holding up the decision.

Start a conversation