Your engineer left
The system still runs, but nobody dares touch it.
SHEET 01/ 11
What a Helper CTO is
It is not a job opening. It is an arrangement about who carries responsibility.
Most small and mid-sized companies cannot justify a full-time CTO: one month of that salary can cost more than a full year of system maintenance. The system still needs someone who sees the whole picture, can make technical calls on your behalf, and can be reached when something breaks.
A Helper CTO puts that role outside the company. We are a professional system developer with 5+ years behind us. We have written our own systems and taken over other people's — which is how we know a system survives not because it got written, but because someone stayed responsible for it.
You do not need to read the code first, and you do not need to write documentation first. You need to know three things: who owns the system, what happens next, and what it costs per month.
SHEET 02/ 11
"It's finished"
is not the same as "someone owns it"
A typical project:
Scope it
→
Build it
→
Ship it
With us:
Take over
→
Clean up
→
Ship
→
Keep watch
→
Keep growing
AI built it for you
It works — until it breaks, and no one picks up the phone.
The contractor vanished
One small change means finding someone new all over again.
SHEET 03/ 11
Take over, maintain, improve, keep building
One team, from end to end.
-
01
Take over
First, get a clear picture of where things stand
-
02
Maintain
Keep it stable and out of trouble
-
03
Improve
Make it smoother to use over time
-
04
Keep building
Grow along with your company
A good fit:You already have a system, you are willing to let us see how it is, you accept cleaning it up first, and you want a long-term partner.
Not for us:Management consulting, business models, bookkeeping, legal or marketing; pure staff outsourcing, or asking for a quote without letting us look.
SHEET 04/ 11
Step one: the system check-up
The system check-up is a paid engagement, quoted by system size. No lock-in — we just confirm we are right for each other first.
A 60-minute online meeting
Read access to the code is enough; we do not need production credentials.
A one-page report in 3–5 working days
Where things stand, the three things to fix first, and what we suggest doing next.
Three possible conclusions
Ready to take over as-is / clean up first, then take over / rebuilding would cost you less. Then you decide whether to work with us.
SHEET 05/ 11
Pick the arrangement your system needs
Basic maintenance and development-inclusive engagements, assessed as separate tiers.
System check-up
Paid, quoted by system size; a clear picture of where things stand.
Basic maintenance
NT$6,000 /month and up
Someone keeps an eye on it day to day. Billed monthly; stop whenever you want.
Development included
NT$30,000–200,000 /month
Assessed by development scope, covering improvement and continued build-out.
Getting it cleaned up and live for the first time is quoted separately, based on its condition; hosting is quoted separately by specification.
SHEET 06/ 11
Someone watches it daily; want more done, add energy
Energy is the engineering capacity we reserve for you each month.
Small things just get done
Minor adjustments within your monthly energy need no new negotiation; want more, add energy. Anything unused that month does not roll over.
What we absorb is stated plainly
Fixing defects in the system does not draw on client energy. Billable work and work we absorb are itemised separately.
Every period, the investment is visible
The confirmation sheet lists the balance, the basis of measurement, deductions, what we absorbed, cancelled items, and both signatures; once settled, it does not change.
SHEET 07/ 11
How fast we respond
A steady rhythm day to day — and nothing tying you down when we part ways.
Hosting or service failure
Responded to within 1 working day.
You report a bug
Assessment returned within 2 working days.
Security updates
At least once per quarter, with extra rounds for emergencies.
When the engagement ends, the documents and records built up along the way stay with you — handing over to someone else does not turn into a black box.
SHEET 08/ 11
Why
you can trust us
We look after our own products
We build and maintain them ourselves, and hold client systems to the same standard.
We can read what others wrote
We maintain open-source projects, and we can pick up code other people left behind.
We have handled all kinds of systems
E-commerce, payments, video, matching platforms, internal tools and IoT devices.
SHEET 09/ 11
Frequently asked questions
How is a Helper CTO different from outsourcing development?
Outsourcing delivers a project and responsibility ends at handover. A Helper CTO carries responsibility long term: once the system is with us, maintenance, improvement and further development stay with the same team, and someone picks up the phone when it breaks.
What does it cost per month?
Long-term maintenance plans start at NT$6,000/month, adjusted for system scale and scope. Development work is quoted separately. You get an exact number once the scope is confirmed — never a rough estimate.
Do we have to do the health check first?
We recommend it. The check is a 60-minute online session plus a one-page assessment, priced by system scale, and it answers whether the system can and should be taken over. Quoting without one would be irresponsible on both sides.
We already have engineers — do we still need this?
Usually yes, in this shape: your engineers focus on the core business, while maintenance, monitoring, security updates and technical judgment for everything else sit with us. That way one person is not carrying every system alone.
SHEET 10/ 11
Start with a system check-up.
Book a system check-up: paid, quoted by system size, no lock-in.
- 01 System check-up See whether we can take it on
- 02 Take over Responsibility moves to us
- 03 Keep watch Day-to-day is ours
- 04 Keep building Only when you need it