This page describes how we run programming consulting focused on automated software testing — the custom service model for teams evaluating a fit before they book time.
1. Intake (no charge)
You submit the contact form with repository context, CI vendor, and the failure modes you see most often. We respond by email with clarifying questions or a decline if the stack is outside our practice.
2. Scoping document
When there is a fit, we deliver a short scope memo: objectives, deliverables, assumptions, and whether work is project or advisory. The memo includes a not-to-exceed hour range and proposed start date.
3. Commercial acceptance
You confirm the scope in email or signed PDF. For projects, a deposit may be requested before calendar holds are placed. Session work is prepaid or invoiced per agreed cadence.
4. Delivery rhythm
Projects use weekly checkpoints — demo of merged tests, notes on pipeline changes, and risks for the next sprint. Advisory sessions end with written action items within two business days.
5. Close-out
We run a final review of open pull requests, archive temporary branches, and transfer any credentials we held. You retain all code; we retain no customer source unless contractually required for a short audit window.
Who this is for
- Engineering leads modernizing CI after a migration
- Backend teams exposing APIs to mobile or partner consumers
- Organizations in Taiwan that need English-language consulting documentation for overseas stakeholders
Who this is not for
- Teams seeking 24/7 managed testing operations
- Vendors looking for white-label automation products