CHRISTOPHER YU
BOOK A CALLEMAIL ME
WHAT I CAN BUILD FOR YOU

One engineer,whole system.

Three things I do, and what each one actually involves. Senior engineering without the overhead of an agency: you work directly with the person writing the code, and the price reflects that there is nobody else to pay.

Best suited for founders and small teams who have a clear problem to solve and want a senior engineer to own the implementation.

BASED
Bali · UTC+8
CLIENTS
Remote
OVERLAP
Europe & APAC
STATUS
Available now
01

Product build

from $7,500 · SCOPED PER PROJECT

New SaaS, MVPs and web applications.

A product idea, or a validated one with no engineering behind it, taken through to something running in production with real users on it. Design, frontend, backend, schema, integrations, deployment and the monitoring that tells you when it breaks. One engineer holding the whole picture, which is why the parts fit together.

YOU GET
A written spec and schema before code · weekly deploys to a real URL you can use · production setup, backups and monitoring · handover docs your next engineer can follow
WHAT I NEED FROM YOU
One decision-maker who can answer questions the same week · clarity on what must ship versus what would be nice · access to whoever actually uses the thing
02

Internal tools

from $5,000 · PER TOOL

Dashboards, workflows and business software replacing spreadsheets and manual processes.

The spreadsheet your operations actually run on, turned into software, with permissions, an audit trail, and numbers that agree with each other. This is most of what ClassPortal and Stencil are: scheduling, invoicing, reporting, roles. Unglamorous, high leverage, and usually the fastest money a team saves.

YOU GET
Roles and permissions that match how your team really works · imports from whatever you use now · reports that reconcile · training for the people who use it daily
WHAT I NEED FROM YOU
Time with the people doing the work, not just the person commissioning it · a copy of the current spreadsheet, mess included · the edge cases everyone knows and nobody wrote down
If an off-the-shelf tool solves the problem better, I will tell you.
03

Product website

from $2,500 · DESIGN + BUILD

High-quality marketing and product websites.

A site built by someone who understands the product it is selling, which means the technical claims are accurate and the demos are real. Fast, accessible, and editable by your team afterwards. This site is the sample.

YOU GET
Design and build together · real performance, not a slow page with an animation on it · content your team can edit without me · analytics wired up properly
WHAT I NEED FROM YOU
Who the site is talking to and what you want them to do · final copy, or the authority to write it · brand assets if they exist
ALSO

Rescue & takeover

from $3,500 · AUDIT FIRST

A product that is half-finished, hard to maintain, or abandoned by whoever built it. The first job is not rewriting it. It is reading it, writing down how it actually works, getting it deploying reliably, and finding out what breaks. That audit comes first and stands on its own: a written map of the system, a risk list worst first, and a repeatable deploy, whether or not I do the work that follows.

HOW IT WORKS

How an idea becomes a production system.

Five steps, in this order, on every project. Ongoing capacity for agencies and teams runs differently and has its own page.

01
Scope
We agree what ships and what does not, written down as a spec with a schema sketch attached.
YOU GET
Written spec
Fixed scope list
Estimate in weeks
02
Architecture
Data model, service boundaries, third-party choices and the failure cases, decided before any UI exists.
YOU GET
Schema
System diagram
Trade-off notes
03
Build
Weekly increments, deployed to a real URL you can use. No month-long silence ending in a demo.
YOU GET
Weekly deploys
Staging URL
Direct engineer access
04
Ship
Domain, monitoring, backups, error tracking. The unglamorous part that decides whether launch week is calm.
YOU GET
Production setup
Monitoring
Handover docs
05
Run
Iterate on real usage, or hand it over cleanly to your team. Both are fine; leaving you stranded is not.
YOU GET
Iteration
Or clean handover
Documented code
PRICING

What it costs, before you ask.

Every figure is a floor, not a ceiling. What a project actually costs depends on how much of it there is, and you get that number in writing after a call and before anyone commits to anything.

ONGOING

What you are agreeing to.

FIXED PRICE
Agreed in writing before anything starts. Changes go on a list rather than into the current build, and get priced separately.
INVOICING
Projects invoice against milestones rather than up front. Monthly work invoices at the start of each month.
OWNERSHIP
Your repos and your hosting from the first commit, so nothing is ever hostage to the relationship continuing.
MINIMUM
One month on ongoing work, with two weeks' notice to stop. Projects have no minimum beyond their own starting price.
NO HOURLY
You are buying an outcome, not my time. There is no timesheet to argue about.

These are lower than an agency would quote for the same work, and the reason is structural rather than a discount: there is one person on the invoice, and no office, sales team or account layer to carry.