Common questions
Answers to the questions that come before a project.
Understand service scope, pricing, existing systems, content, ownership and the process for choosing the right work.
Frequently Asked Questions
What to expect when planning work with Ascent
Use these answers to prepare your brief and compare the available approaches. The individual service pages explain the work in more detail, while the written proposal sets out the actual deliverables and commercial terms for your project.
Google Maps management is described on its own page, including what is included, the £59 and £89 plans, the £99 setup and how cancellation works. No VAT is charged. Supplier not currently VAT registered. An enquiry does not purchase a plan.
FAQ
Questions, answered plainly.
Where should we start?
Start with the point where customers or staff encounter the most friction. That might be finding the business, understanding a service, making an enquiry or following it up. We use that priority to identify a useful first scope.
Can you work with our existing website and tools?
Yes, the initial review considers what is already in place. Configuration, better content or a focused connection may be sufficient. Compatibility and access are checked before committing to the solution.
How is the work priced?
Projects, ongoing management and specialist work are scoped according to the requirement. Your proposal identifies the work, charges and relevant external costs so you can assess the expected total.
Can we begin with one service?
A focused project can be a sensible starting point. Choose a defined need with a clear completion check, then decide whether related work is worthwhile.
Are software and advertising costs included?
The proposal states which external costs are included and which are paid separately. These may include media spend, software licences, domains or phone and messaging usage.
Do you guarantee rankings or sales?
No. We define and deliver the agreed work, then assess the available evidence. Customer decisions, competition and platform behaviour affect outcomes beyond any supplier’s control.
Who provides the content and images?
We agree the writing and production responsibilities in the brief. You provide or confirm business facts and approve claims. Images and other assets need suitable rights for their intended use.
How will we see work before launch?
The project includes an agreed review stage for the relevant content, design or functionality. The proposal sets out the review process and who approves the release.
What should we send with an initial enquiry?
Describe the business, the problem and the outcome you want. Include the relevant website or system and any constraints. Share passwords or private records only through an appropriate controlled process if later required.
What happens to existing pages and accounts?
We identify current routes, account ownership and relevant records during scoping. Any preservation, migration or handover work is defined before changes are made.
Can several services be combined?
Yes, where they support the same customer journey or operating need. The proposal identifies the components, dependencies and responsibilities so connected work remains understandable.
What happens after the project?
Handover and any ongoing service are agreed in the scope. Continuing maintenance, management or additional development should have a defined owner and schedule.
Explore the next step
Have a question specific to your business?
Tell us what you want to improve, what is already in place and any constraints. We can then identify the work that fits.