Website pricing depends on what is delivered, not just the page count or the total on a quote. Our website builds start NT$15,000 (≈ USD 500), typically NT$30,000–100,000 (≈ USD 1,000–3,300); the main differences are pages, content, functionality, search foundations, integrations, and warranty or maintenance. Compare those scopes before comparing totals.
Define what the website needs to do
We start by asking what the site should support: explaining services, publishing projects, collecting inquiries, or selling products. A company brochure and a website that routes submissions into an internal workflow may look similar, but they involve different work. Identify the main objective before listing pages and features.
A quote may cover content preparation, configuration, testing, handover and support as well as design. If these tasks are not written down, you may assume they are included and discover otherwise during the project. We recommend separating launch essentials from later additions so the first phase has a clear boundary.
Six factors that change the scope
- Pages and templates: several pages can share a layout, while distinct layouts need their own design and testing. A page count alone does not show that difference.
- Content preparation and publishing: clarify who supplies, edits and enters copy, images and product information. We do not provide photography; you supply photos and materials. Copywriting is available as an add-on.
- Functionality: a contact form, registration flow, booking process, multilingual site, shopping cart and payment setup involve different requirements. Define fields, notifications, confirmations and exceptions.
- SEO and GEO depth: setting basic page information is different from restructuring content, adding structured data and checking crawler-readable pages. Foundations are included or added on depending on the plan, without guarantees of rankings or AI recommendations.
- Integrations: emailing a form submission is different from connecting LINE, a CRM, routing and follow-up automation. Each connection needs agreed fields, access and failure handling.
- Warranty and maintenance: we provide 30–90 days of warranty after launch, depending on the plan. Clarify its scope, optional ongoing maintenance and how new requests are quoted.
Look beyond the initial page count
Company websites often need new projects and articles over time. On the WordPress company sites we build, you can add those entries yourself in the admin without a quantity limit. That does not mean each entry receives a newly designed layout or that every special page is included. The agreed scope still applies.
Ask what you can edit after launch. A site that requires outside help for every update has a different operating model from one you can publish to yourself. Include the operating guide in the handover checklist, and identify who will handle routine updates internally.
Separate the build fee from other spending
Hosting, domains, platform subscriptions, themes, plugins, payment processing fees and photography are outside the build fee. They have different providers and payment cycles, and some depend on the features selected. Third-party pricing and plans are governed by the official websites, not by a figure copied into a proposal indefinitely.
We do not provide photography or assume that image rights are already cleared. Arrange photography separately or prepare material you have permission to use. Ownership also matters: you buy the hosting and domain in your name. We build in our environment, then hand the site over to your hosting account after sign-off.
Compare proposals using one checklist
- Are page names, shared templates and custom layouts identified?
- Who supplies, reviews and publishes copy, images and product data?
- What does the form collect, who receives it, and are integrations included?
- Are multilingual content, booking, shopping cart and payments in scope?
- What search work is included, and are unrealistic ranking promises being made?
- How do testing, sign-off, handover, documentation, warranty and maintenance work?
- Are third-party costs separated, with accounts in your own name?
If totals still differ, ask each provider to identify the delivery item behind the difference rather than asking for identical prices. A lower total may simply cover less. A higher total does not make every feature relevant to your business. Choose a scope that supports your current objective and can be operated after launch.
Plan a useful first phase
With a limited budget, we focus on core pages and the main inquiry path. Visitors should get the information they need, submit their details and reach the appropriate person. Advanced features can follow later, but essential steps cannot be left unfinished. A form that actually reaches its recipient belongs in launch testing.
Prepare content and plan sign-off early. Waiting until the quote is approved to gather every image and paragraph can keep changing the scope. Inventory your materials and essential functions before the consultation so we can quote the actual work rather than substitute a low headline price for a scope description.
USD figures are approximate. Final quotes are given after a free 30-minute consultation.
Frequently asked questions
- Does every website cost the typical amount?
- No. Our builds start NT$15,000 (≈ USD 500), typically NT$30,000–100,000 (≈ USD 1,000–3,300), but these are not fixed prices for every request or a promise that the starting price includes all features. The final quote follows a scope discussion.
- Are subscriptions and hosting included?
- No. Hosting, domains, platform subscriptions, themes, plugins, processing fees and photography are separate. See the official websites for third-party pricing and plans.
- Are warranty and maintenance the same?
- No. We provide 30–90 days of post-launch warranty depending on the plan. Confirm the warranty scope separately from ongoing maintenance, and agree the scope of new features separately.
- Can the inquiry form connect to our systems?
- We can plan owner notifications, CRM records and follow-up automation. The systems and workflow need to be scoped; do not assume all integrations are part of the base build.