We build digital products for ambitious brands

Share your target users, business goal, existing website or product, priority features, reference examples, budget range and desired timing. Include available content, brand materials and integration requirements, with access to existing systems when a review is needed. We use this brief to agree the first-release scope, milestones, responsibilities and acceptance criteria before development.

Yes, we can connect product planning, brand and interface design, frontend, backend and launch preparation in one engagement. Depending on the project, the agreed scope can include a CMS, enquiry forms, assessments, booking, CRM integration or an AI FAQ assistant. We define the deliverables and exclusions before work starts, so optional features are not assumed to be included.

Yes, we first review the available code, content, hosting, access permissions and the problems you want to solve. We then recommend what to retain, improve or rebuild, with migration work and technical constraints included in the estimate. For a website migration, redirects, important URLs, content and analytics continuity can be part of the agreed scope; search rankings are not guaranteed.

We prepare an estimate after reviewing the scope, separating design, development, integrations, testing and launch work where relevant. Domains, hosting, paid CMS or plugins, email, AI usage and other third-party subscriptions may have recurring costs; we identify these separately from our delivery fee. Payment milestones, optional work and ongoing support are agreed in the proposal.

As a planning reference, a focused website may take 4-6 weeks, while custom software or a mobile app may start around 8-12 weeks. These are estimates, not committed delivery dates; content readiness, integrations, feedback and release requirements can change the schedule. After reviewing the brief, we confirm milestones, responsibilities and acceptance criteria in the agreed project plan.

We compare the request with the agreed scope and acceptance criteria to distinguish a correction from additional work. For a scope change, we explain the effect on cost, dependencies and schedule, and confirm the revised plan before proceeding. You can prioritize essential changes for the current release and move other ideas to a later phase.

Next.js, React and TypeScript are common starting points for our web products. Database and cloud choices depend on your integrations, budget, deployment region and the team maintaining the product. For software and mobile apps, we review the product requirements before agreeing the architecture and any paid services.

A CMS can be included so your team can edit agreed page content, articles, images or other defined content types. We confirm editing permissions, supported fields and any training or documentation during scoping. Content entry, migration, copywriting and translation can also be included or quoted separately; structural changes and new features may still require development.

We recommend a deployment setup and region based on your audience, integrations and operating requirements. Domain and production hosting accounts should be under your control, with our access and deployment responsibilities agreed in advance. Performance work is assessed against the actual pages, features and expected usage. Hosting fees, monitoring, backups and ongoing operation are defined separately in the scope.

We agree ownership and delivery terms before development, including the project source code, repository access and handoff documentation. Client-controlled accounts should hold the code repository, domain, hosting and other agreed production services, with our access arranged for development and handoff. Open-source components, commercial plugins, fonts and other third-party assets remain subject to their licenses; their use and costs are confirmed separately.

We work in English and Chinese, using written requirements, milestone updates and agreed review sessions for remote collaboration. We arrange call windows around the teams' time zones and confirm communication channels at the start. If you are visiting Guangzhou, share your travel dates and project brief to request a meeting; availability and arrangements are confirmed individually.

We agree the post-launch correction period and its coverage in the project terms. Ongoing maintenance, dependency updates, backups, monitoring and analytics review can be scoped separately, with support hours and response arrangements confirmed in writing. New features and changes to third-party services are assessed separately, and we can prepare a handoff if your own team will maintain the product.