Services · Development

Custom software, built around how you work.

Web, mobile, and business systems designed from your real workflow. Planned before we write code, delivered in stages you can test, and maintained by the same team after launch.

What you get

Deliverables

01

Product & technical scope

A scoped MVP or build plan with milestones, estimates, and risks surfaced up front.

02

Production-grade codebase

Maintainable, tested, documented code you own — no lock-in, no throwaway.

03

Architecture & infrastructure

Cloud architecture, CI/CD, and observability set up for scale and handover.

04

Launch & support

Deployment, monitoring, and an ongoing support model after go-live.

How we build

Planned first, then built

Plan before code

We map the workflow and agree on scope before writing code, so the build solves the right problem.

Architecture first

Systems designed for your data and scale, not squeezed into a template.

Delivered in stages

Working software you can test at each milestone, not one reveal at the end.

Maintained by the same team

The people who built it keep it running after launch.

How we work

The process

01

Consult

Understand the business goal and constraints.

02

Plan

Architecture, scope, and milestone plan.

03

Build

Iterative sprints with regular demos.

04

Test

QA, security, and performance hardening.

05

Ship

Deploy, monitor, and support.

Selected work

Systems we have built

Pricing

How we price it

Prices are in US dollars, converted at NT$32 to US$1; Taiwan clients are invoiced in New Taiwan dollars, and other currencies are quoted on request.

01

Hourly engineering

Senior full-stack engineers, including design, development, testing, and documentation.

02

Planning is priced separately

Architecture and scoping before development, billed at the consulting rate.

03

Project total

Estimated hours per module, quoted as a firm number once the architecture is agreed. We do not quote a total while the scope is still vague.

04

Payment schedule

Three stages on small and mid-size projects: signing, design approval, and acceptance. Larger or longer projects move to four stages tied to milestones.

Scope

What is and is not included

01

Included

System design and interface mockups, development and testing, deployment, source code and documentation, two online training sessions, and 30 days of warranty after launch.

02

Not included

Cloud hosting, third-party licences and API fees, domains and certificates, hardware, and scope added after signing, which is quoted as a change order.

03

After the warranty

The system moves to a monthly maintenance plan, from US$220 a month. If requirements keep coming, a dedicated team costs less and includes maintenance.

Ongoing development

Dedicated team

Minimum three months. Maintenance is included in the fee rather than billed separately. Prices are in US dollars, converted at NT$32 to US$1; Taiwan clients are invoiced in New Taiwan dollars, and other currencies are quoted on request. The same model can absorb the maintenance function for systems you already run, including systems we did not build.

Half month

US$4,100 / month

Around 10 person-days a month from a dedicated senior full-stack engineer, working to your priorities.

  • Works out at US$410 per person-day
Most chosen

Full month

US$7,500 / month

A dedicated senior engineer full time. Best when requirements keep arriving and scope cannot be fixed up front.

  • Works out at US$375 per person-day

Team

From US$14,500 / month

Two or more full-time engineers, with project management and a technical lead.

  • Works out at US$360 per person-day

FAQ

How long does a system take to build?

It depends on scope; an MVP is usually 4 to 12 weeks. You get a schedule with milestones at the end of the planning phase, rather than a flattering number up front.

Who owns the code?

You do. Source code, database and cloud accounts are handed over in full. No lock-in, and you do not have to come through us to change it.

What stack do you use?

Next.js, Astro, React and Node, on AWS, GCP or Cloudflare. We choose for whether your team can take it over, not for fashion.

Can we start with a small piece?

Yes, and usually we suggest it. Build one workflow end to end, prove it, then decide whether to widen.

What happens after launch when nobody is looking after it?

After the 30-day warranty it moves onto a monthly maintenance plan, or a dedicated team if work keeps coming. The people who built it keep maintaining it, so there is no second handover.

A system to build,
or one that needs taking over?

Book a consultation →