Questions worth resolving before you say yes.
The aim is not to hide important details until after contact. If a project needs a different boundary, it should be explicit in the agreed scope.
Does submitting a form start paid work?
No. A form provides project context. Paid production starts only after the applicable scope and commercial terms are accepted.
When is price agreed?
After we understand enough of the project to define the responsibility. Some technical work may need a diagnosis/discovery step before implementation can be priced responsibly.
What can be outside scope?
Third-party licences, hosting, domain registration, paid APIs, premium assets, ongoing support and material additions are separate unless the project scope says otherwise.
What happens if the project changes?
If a new requirement materially changes the agreed work, we clarify and agree the additional scope before treating it as included.
Who should own the domain?
Normally the intended client/registrant, or the agency if it legitimately manages domains for its clients.
Who should own the hosting?
Normally the client or agency that is meant to control production and billing.
Do you keep administrator access after launch?
Not by default. Temporary access should be removed after handover unless ongoing responsibility is explicitly agreed.
Must I share my hosting password?
Usually no. Delegated/restricted access is preferred. An attended remote session can also let you log in yourself.
Can I keep private files and applications closed during remote support?
Yes. Remote access is intended for the agreed technical task, not general exploration of your device.
Do you handle my card details when buying hosting or a domain?
Our preferred model is that you buy directly from the third-party provider. We can recommend the route and help configure it without handling unnecessary billing information.
What if personal data is visible during the work?
Project information should be accessed only as needed for the agreed work. Where we process personal data on a client’s behalf, applicable roles and obligations should be documented where required.
Will you market to our agency clients?
Not as a consequence of a delivery engagement. The agency’s client relationship remains the agency’s unless a different arrangement is expressly agreed.
Can you remain completely white-label?
Yes where the project suits it. Visibility and technical contact are agreed with the agency.
Can you join client calls?
Yes when the agency wants technical participation and it helps delivery.
Can we use WebAgencyOn only for overflow?
Yes, subject to actual availability. A recurring arrangement is only needed if it becomes useful.
Do you require WordPress, Grav or another CMS?
No. Technology follows the project. A CMS is used when its editing/workflow benefits justify it.
Do you use AI?
We may use specialised AI systems internally for research, content, UX, coding or review where useful, with human direction and implementation.
Can you work with our existing hosting?
Potentially, if it is compatible with the project and appropriate access is available.
Can you handle DNS, SSL and Cloudflare?
Yes where those layers are part of the web project or technical responsibility.
Do static websites need maintenance?
They can need much less routine maintenance than a plugin-heavy CMS, but domains, hosting, certificates, forms, external services and future changes can still require attention.
Can I see the site before it replaces production?
Yes where appropriate. A private review environment can be used before final deployment.
Do you back up the current website?
Where the platform supports it and the deployment scope includes it, our preferred process is to create a pre-change backup before destructive replacement.
What do you test at launch?
The agreed scope can include URLs/links, forms, HTTPS, responsive behaviour and relevant integrations. Exact QA depends on the project.
What if something fails after launch?
Use Project Support with the project reference and describe the business impact. Work outside the agreed support/delivery scope may require separate scope.
Is support unlimited?
No unless a specific service explicitly defines that. We do not imply unlimited support just because we delivered the project.
Do you provide 24/7 monitoring?
Not as part of the current standard WebAgencyOn products.
Start in plain language.
Open Project Builder and use the project form. You do not need to choose the technical solution first.
Open Project Builder