A new online home
Start with the core pages, the customer questions and a useful contact path. A focused first release is easier to maintain than launching every idea at once.
Explore this serviceGood work startswith a clear relationship.
Not a mystery between the first hello and the final handover. Here is what we do, what we need from you and how decisions become a website.
CHOOSE A STARTING POINT
Not every project needsa blank canvas.
A considered refresh
Keep what is useful. Review structure, content and brand presentation, then agree whether targeted changes or a rebuild makes more sense. Existing platform constraints are part of that decision.
Explore this serviceKeep improving
A scoped update list, content maintenance or search foundations can be the right next step. Care is optional; extra systems and large content projects are separately planned.
Explore this serviceFROM HELLO TO HANDOVER
Every stage hasa next decision.
The detail varies by project. These checkpoints keep responsibility and progress visible; they are not a fixed delivery timetable.
Start with the business, not the template.
We begin with the person visiting your site and the action you need them to take. Bring an existing URL, a service list or simply the problem you are trying to solve. An incomplete brief is a perfectly useful starting point. We also clarify whether the existing platform should be retained.
- We handle
- Clarify the goal, constraints and a sensible first scope.
- You confirm
- Share business context and identify who can make decisions.
- The checkpoint
- A shared problem statement and next-step recommendation.
Put the agreement in writing.
Pages, languages, content responsibilities, integrations and revision rounds belong in the proposal. So do dependencies, third-party charges, payment milestones and acceptance criteria. A bespoke interactive site is not automatically included in an introductory website package.
- We handle
- Describe deliverables, exclusions and the review checkpoints.
- You confirm
- Confirm priorities, budget and the proposed scope before work.
- The checkpoint
- A written scope, not an open-ended list of promises.
Make the direction visible early.
We organize the content and key pages, then establish typography, image treatment and the visual direction. Reviewing one coherent direction is more useful than making isolated decisions about every button. Existing brand assets are the starting point when they are available.
- We handle
- Explain design choices against the agreed customer task.
- You confirm
- Confirm business facts and give one consolidated feedback list.
- The checkpoint
- An agreed page structure and visual reference to build from.
Build the parts that need to work together.
Responsive pages, language paths and scoped integrations are implemented together. Review happens on a preview site, not only in a static screenshot. We distinguish an in-scope correction from a new page, a new workflow or a new integration before extending the work.
- We handle
- Build, check and show the agreed interactions.
- You confirm
- Review the preview and supply missing approved materials.
- The checkpoint
- A working preview and a visible list of remaining decisions.
Check the whole journey before release.
We review mobile layouts, keyboard access, links, content and the agreed enquiry or booking handoff. A visible success message is not proof that a receiver got the information. Production settings and final business information must be confirmed before a release is approved.
- We handle
- Document checks, limitations and issues that still need a decision.
- You confirm
- Approve final content, account setup and the release decision.
- The checkpoint
- An acceptance checklist and an explicit release decision.
Leave you with a website you understand.
The agreed handover explains what is editable, where accounts live and how routine updates are made. We separate optional care from the initial build. Future campaigns, extra languages and new systems can be planned when there is a real reason to add them. Ongoing response arrangements and fees belong in that agreed scope.
- We handle
- Explain the agreed edit, maintenance and recovery workflow.
- You confirm
- Keep owner access and choose the ongoing support arrangement.
- The checkpoint
- A handover record and a clear route for the next update.
A LITTLE PREPARATION
Bring what you have.We can find the gaps together.
YOUR CONVERSATION NOTES0 / 6
items have a starting point. Unchecked items stay in the outline too.
Choices stay on this page; a file is created only when requested. No account, personal-data collection, quote or project acceptance.AFTER THE BUILD
A handover,not a disappearance.
Agree these items in the proposal. Their exact form depends on the platform, licenses and selected support arrangement.
Accounts and access
Your business domains and accounts stay in your name. Identify the owner, access method and renewal responsibility for each provider. Do not send passwords through the public enquiry form.
The editable parts
Confirm which fields you can change, how bilingual updates are reviewed and when a layout change needs development. Source-code and CMS access are defined in the agreed deliverables.
Checks and recovery
Record the tested contact path, important limitations and the agreed backup or recovery route. Hosting, CMS and third-party tools have different controls; a single checklist cannot promise identical support on every platform.
Care or self-management
Choose scoped care, agreed self-editing or a later improvement project. Recurring charges, response arrangements and what counts as new work should be explicit, rather than assumed to be included forever.
THE PRACTICAL QUESTIONS
Before we begin.
Do I need to write every page before we speak?
No. An existing website, a rough service list and the problem you want to solve are enough for a first discussion. The proposal should say who gathers, writes, translates and approves the final material. Missing content affects the schedule, so it is better to identify it early.
How long will it take, and when do I pay?
Timing and payment milestones are agreed for the actual scope. Content readiness, feedback and external systems all matter. The website does not set a universal delivery deadline or deposit percentage. Your written proposal should make both clear before the project begins.
What happens when I ask for a change?
First we check whether the request corrects the agreed work or adds something new. Consolidated feedback fits the review rounds in the scope. A new direction, extra pages or additional systems should be assessed for price and schedule before they are added; care is not unlimited design work.
Will you work with my existing website?
Yes, that is a possible starting point, subject to a technical and access review. We look at what is worth keeping, what needs improvement and whether the current platform supports the goal. A rebuild is not the automatic answer to every problem.
Can we work in both English and Chinese?
Yes. We can discuss and review in either language. Publishing a bilingual website is a separate content scope: page parity, translated business facts, language navigation and ongoing updates all need an owner. A second language is quoted by its actual content volume.
Who owns the accounts and how do updates work?
Business domains and accounts stay in your name. The proposal defines the source files, editable fields, documentation and third-party licenses to be handed over. Choose scoped managed updates or agreed self-editing; confirm provider charges and access before launch.
Are the portfolio concepts included in the entry package?
No. They illustrate a range of possible directions, not a promise that every interaction is part of every package. Custom identity, sophisticated motion, ecommerce, booking integrations and substantial bilingual content require their own scope. Start with what your business actually needs.
What does AI do in the process?
AI can help organize research, drafts, development and checks. It does not decide your business facts, approve asset rights, replace a final review or promise search performance. Please do not send passwords or sensitive customer records in a project brief; any approved data access is scoped separately.
This page explains our working approach, not a replacement for your written scope or a finalized services agreement. No project is accepted and no payment is taken by this preparation tool.
YOUR NEXT STEP
Create a project briefStart with one useful question.
A clearer next signal
Make the business clear.
Strengthen the signal.
A new website, a thoughtful refresh, stronger search foundations, or a clearer digital direction.