About
CJ Jutba
AI-native product engineer, and the whole team on most of what I ship.
I'm based in the Philippines and I build production software on my own. Systems with auth, payments and permissions, and the parts nobody demos that decide whether the thing holds up once real people are using it.
Most of my work is for founders and small teams who need one person to own the whole thing, from scoping it through to handing over something the next engineer can actually read. The most demanding version of that so far was FiscplusThe Fiscplus case study, architecture and outcome included., a compliance-grade portal for a Belgian accounting firm, carrying a complete anti-money-laundering lifecycle and granular permissions across three role-scoped portals.
What I do
I build web apps, SaaS products and the internal systems businesses run on. The work sits between engineering and product decisions rather than treating them as separate stages, because on a solo build they are the same conversation.
Engineering
Next.js · React · NestJS · TypeScript · PostgreSQL · Prisma · Drizzle
Product and delivery
Scoping · Architecture · UI and UX · Deployment · Handoff docs
View my full stackThe hardware, editor, and tools I actually use.
My background
No agency, no team behind me. What I know came from shipping things that had to work for someone other than me, and from the ones that broke first.
AI-Native Product Engineer
2024 to PresentIndependent · Freelance
- Build web apps, SaaS and internal systems for founders and small teams. The most recent is Fiscplus, a portal for a Belgian accounting firm carrying a full anti-money-laundering compliance lifecycle.
- Run an AI-native workflow, with agents working in parallel on separate parts of a build and every line reviewed before it ships. It is how one person keeps agency pace without agency headcount.
- Own the whole project. Scoping, architecture, build, deployment and a handoff the next engineer can actually pick up. One person accountable, nothing lost between hands.
- Work against the business problem rather than a ticket list. What users need, what has to ship first, and what has to hold once people depend on it.
Builder
OngoingOpen source and personal builds · Self-directed
- Ship small products end to end to test ideas properly. A run tracker, a budgeting app, a client portal, a pickleball queue manager.
- Turn what works into reusable patterns, which is most of why the next build goes faster than the last one.
- Build in the open and write up what actually happened, including the parts that did not work.
How I work
I start by cutting scope. The smallest useful version, the real workflow, and the parts that prove whether the idea holds. Everything else waits until something is in front of users.
Then I build with agents working in parallel on separate parts, and I review every line before it ships. That is all AI-native means here. It buys pace, and the review is what stops the pace turning into a shortcut. It is how one person covers what used to take a team without the quality quietly dropping.
At the end you own the code, the docs and the deployment path. No lock-in and no mess to inherit. There is a longer version of that in how I run a projectWhat a project with me looks like, scope to handoff., and I write up what actually happened, including the parts that failed, in the notesNotes and build logs on shipping and AI-native work..
Elsewhere
Most of what I build in the open is on GitHub. The graph is the honest version of how the last year went.
I'm cjjutba on GitHub, LinkedIn and X.
9,096 contributions in the last year across 25 public repositories.
Working together
I'm taking on freelance work now, and I'm open to the right full-time role. Have a look at what I've shippedEvery case study I've shipped, Fiscplus included., email me at dev.cjjutba@gmail.comReal inbox, real replies., or and I'll come back with what I'd build first.