GOOD QUESTIONS

A little clarity before we begin.

Choosing a website and CMS comes with questions. Here are some useful starting points; the details of your project will be agreed together.

What would you like to know?

Will I be able to update the website myself?

That is the goal. Your CMS is organized around the content you need to manage, such as pages, services, images and frequently asked questions. We agree which parts should be editable and walk you through those tasks at handover. Larger design or functionality changes may still need development work.

What is a CMS, and why use it?

A CMS is a content management system: an admin area where you can update your website’s content without editing code. It can be tailored to your pages, images and publishing workflow while supporting a custom website design. We can discuss the tools and responsibilities that fit your project.

Who owns the website and the content?

Ownership, source code access, content rights and third-party licences should be set out in your project agreement. Hosting, domain and other provider accounts can also be discussed before work begins so that access and handover are clear.

Can you work with my existing website or CMS?

An existing site is a useful starting point. We can review its structure, content and integrations to work out what can be retained, what should change and whether a migration makes sense. Access to the current system helps establish the scope.

How are hosting and deployment handled?

Hosting is chosen to suit the application, database, media and maintenance needs. We discuss providers, running costs, account ownership and deployment access as part of planning. Hosting fees and ongoing management are not automatically included in every project.

How will security and backups be managed?

Security involves application configuration, access controls, software updates and the hosting environment. Backup arrangements and recovery responsibilities should be agreed with the relevant providers. No website can be guaranteed completely secure; the aim is a practical plan with clear responsibilities.

What happens after launch?

The handover can include CMS training and documentation. If you need continued help, we can discuss an arrangement for maintenance, troubleshooting or improvements. Scope, response expectations and costs are agreed separately.

How much will my project cost, and how long will it take?

That depends on the design, content, integrations and migration work involved. A useful estimate starts with your goals, current website, priorities and any deadline. There are no fixed prices or timelines on this site because those details need to reflect the actual project.

What should I bring to an initial conversation?

A short description of your business, a link to your current website if you have one, what you want to improve and any known deadline or budget range are helpful. You do not need a finished brief to start the conversation.

YOUR NEXT CHAPTER

Let’s make your website work for you.

A new idea, an outdated website, or a CMS that gets in the way. Tell us where you are, and we can talk about what comes next.

Start a conversation