Frequently Asked Questions

It depends on scale. A small single-page site can be deployed in as little as three working days. A large system typically involves six months to a year of intensive development, followed by a year or more of maintenance and iteration. We quote the two halves separately: how long to reach a build you can click through, and how long to converge against your feedback. On the Money Weekly platform, the first build took about two of the six months and the rest went on revision and content loading — normal, not a mis-estimate, and better said up front than argued about at handover.

For a typical 5–8 page responsive site with content ready, design, front-end build and back-office integration take roughly two to four weeks. Custom interactions or bespoke admin features are scheduled separately against the detailed requirements.

We price on page count and visual complexity, starting from around NT$2,000 per page. Unusual layout or functional requirements are adjusted against the actual work involved.

We assess module count, interface requirements, front and back office logic, and the expected schedule together, then provide a full specification and an itemised quote. No hidden costs.

Yes. Deployment support is included at no charge — we help you publish to AWS or another host so the project goes live on schedule.

Yes. We have experience integrating gateways such as NewebPay and ECPay, and can complete online payment integration securely.

No. We build on native .NET MVC, designing the back-end logic and database schema from scratch rather than depending on commercial logic modules. On the front end we use Vue.js, Bootstrap and jQuery, which keeps the system clean and extensible.

Never. Every engagement is carried out by our own team. We do not outsource or resell work, which is how we keep code quality and information security under control.

Yes. We can build you a straightforward back office where an administrator swaps banners, edits news and adjusts copy about as easily as using a word processor — no technical background required.

Of course. Technical consultation continues after warranty, and for adjustments or fixes we respond as quickly as our schedule and the scope allow.

Baseline SEO and AEO structure is part of our build standard: semantic HTML5, meta tags, automatic sitemap generation, and load-speed work targeting Core Web Vitals.

Since 2010 we have shipped 33 named projects across 16 industries: religious organisations, consumer electronics, life insurance and finance, municipal government, financial media and publishing, travel, education and tutoring, e-commerce, pet and community platforms, social enterprise, performing arts, medical clinics, national parks and water resources, IP and legal services, leasing and transport, and food and housewares. The full record is on our technical history page.

Yes — official sites and a volunteer management system for a national nature park, official sites for two reservoir authorities, a municipal citizen services platform, and long-term maintenance of several government websites, covering API integration, accessibility requirements and taking over existing systems. Some engagements are under confidentiality, so they are described by sector here; details can be discussed directly.