Frequently Asked Questions
Have questions? Here are some of the most common things our clients ask before starting a project with us.
All questions
How do we start a project?
Send a short overview through our contact form. Include the problem you want to solve, the services you need and any timing constraints. We can then discuss scope, priorities and a suitable next step.
How are timelines and pricing agreed?
Both depend on the scope, content, integrations and review process. We discuss these before work begins and record the agreed deliverables, milestones and fees in a project agreement.
Can you work with our existing brand or Figma designs?
Yes. Share your brand guidelines, design files and relevant product context. We review the material for consistency, missing states and responsive requirements before planning the work.
How do design reviews work?
We agree review points and collect feedback against the project goals. Consolidated feedback from your team helps us prioritize revisions and avoid conflicting changes.
Will the website work on phones and tablets?
Responsive behavior is part of the build. We test representative screen sizes, navigation, forms and content layouts. Any specific device or browser requirements should be included in the project scope.
Can you connect forms and external systems?
We can plan integrations such as enquiries, job applications and other business workflows. Access requirements, validation, storage and failure handling are considered alongside the visible form.
How do you assess campaign performance?
We agree the outcomes that matter, such as qualified enquiries, before a campaign starts. Reports should connect activity to those outcomes and identify what to improve, rather than relying only on impressions or clicks.
Can you help with content and landing pages?
Yes. We can help clarify the audience, structure the offer and create a landing-page journey. The scope can include content, design, implementation and measurement requirements.
What is included in hosting and maintenance?
Hosting setup and ongoing maintenance are scoped separately for your needs. We can discuss deployment, backups, monitoring, updates and responsibilities so you know who handles each part after launch.
How should private uploads be handled?
Private files should be stored separately from public website assets. Access, backup and retention requirements are agreed for the workflow, and the website should avoid exposing uploaded documents through public URLs.



Still have questions?
Can’t find the answer you’re looking for? Get in touch and we’ll be happy to help.
Get in touch