I studied IT, then went all in on design. Now I build apps.

Sun, 26 Jul 2026 15:43:20 GMT

I like building things that work. Not demos, not mockups, the actual thing running for a real person. It took me a long way around to get to do it for a living.

I studied IT, then went where the money was

My degree is in IT, in the Philippines. The problem was the math. Starting salaries there, for the kind of job my diploma pointed at, were low enough that no amount of working hard was going to change my situation quickly. I could see the ceiling before I even started.

So I looked online instead, and I found graphic design work. I went all in on it. Not as a side hustle, as the thing. I learned the craft properly, worked with clients, and got paid in a currency that made the math work.

That decision taught me something I still use: the skill you can sell today is not always the skill you trained for. Pick the one that opens the door.

Then I could not stop exploring

Design paid the bills, but what got me hooked was everything else the internet turned out to allow. Funnels, ads, automations, CRMs, agents. I kept pulling threads. Every time I learned one thing, it showed me three more that were possible for one person with a laptop.

I was not building software yet. I was just collecting the map.

The part that changed everything

For most of that time, building an app meant one of two things: hire a developer, or spend years becoming one. Both were out of reach for the ideas I had, which were usually small and personal and not worth anyone's quote.

Then AI got good. Not "writes a snippet" good. Good enough to ship a real product with, if you know what you want and you check its work. That is the door that opened for me, and I walked through it and never came back out.

My first app went nowhere, and I am glad it did

The first one was called Bus Queue. I built it in Lovable.

The idea came from riding buses in the Philippines. You stand there and watch a crowd form with no order to it, everyone guessing who was there first, and it fixes itself only through patience and luck. So I built a waitlist for the bus. Take your spot in the queue on your phone, keep your place, stop hovering.

I still think it was a good concept. It also never took off. The honest reason is that it solved a problem people had on one particular day rather than every day, and soon after that I flew back to the US and the reason to keep pushing it went with me.

That one taught me the difference between an idea that is clever and a problem someone has on a Tuesday morning and again on Wednesday. Clever is not enough. Repeat is what matters.

Then I tried again, and this time it stuck

Orbit started as a personal CRM. I just wanted to stop losing track of people. Then it needed tasks, so I added tasks. Then notes, then a pipeline, then AI agents that watch a contact and tell me who is going cold. It quietly turned into the thing I used to need three separate tools for, somewhere between GoHighLevel, Notion, and Todoist. Other people use it now, which still surprises me a little.

Tandem I built for my wife. We spend real time in different time zones, and the apps for that are either a shared calendar or nothing. So Tandem does shared habits, real love letters that arrive on a delay, a playlist that is only ours, and a room where we can watch a movie together while we are 8,000 miles apart. It is the one I am softest about.

After that it was mostly tools I wanted for myself and could not find in the shape I wanted:

Vid, because I record a lot of walkthroughs and wanted my own Loom.
Whisp, so I can talk instead of type and have it land as clean text.
Prism, a browser I built in Electron for research, so my tabs stop punishing me.
Flow, a deep work timer that actually blocks the noise instead of politely suggesting I focus.
And a handful of small ones I open every week and never think about, which is the highest compliment a tool can get.

I build with Claude Code now, most days. The AI writes most of the code. The judgment, the review, and the part where I open the real page on a real phone before anyone else sees it, that stays mine. I wrote about exactly where AI falls short if you want the unglamorous version.

What I actually like about this

It is not the code. The code is a means.

What I like is the moment a problem stops being a problem. Someone was doing something annoying by hand every day, and now they are not, and the reason is a thing that did not exist last week. That loop never gets old for me. It is the same feeling I chased in design, except now I get to fix the mechanism instead of the surface.

Shipping fast turns out to be the easy half. The hard half is making it dependable enough that a real person can lean on it. That is where most of my hours go, and it is the part I would want you to judge me on.

If you need something built

An app, a website, a landing page, a funnel, an automation, an agent connected to the tools you already use. Tell me what it should do and I will tell you honestly whether I am the right person for it, and what version one should be.

You will work with me directly, and most first versions are live in days.

Book a call, send me the details, or look at what I have shipped first. Some of it is free to use right now, no email required.

May 2026.

Wed, 13 May 2026 12:00:00 GMT

Where I am. Back in New Jersey after a stretch in Korea. Just wrapped a six-month run at a digital marketing agency. Re-settling into Elizabeth. Reading more, scrolling less. Drinking too much coffee.

What I'm building. NeilOS, my personal AI command system. I built it while running the agency's operations. Now it's the workbench I run almost everything from. 20+ n8n workflows shipped this year. 8 MCP servers. A daily journal. A stack of skills. Slowly turning into the most interesting thing I've ever built.

What I'm thinking about. The gap between "agency that ships campaigns" and "operations layer that ships infrastructure." Most agencies sell the first; the second is where the durable value is. Also: what an operator's job looks like when AI does the rote work and the human owns the judgment.

What's next. Looking for my next full-time operator role. Somewhere big ideas need to become shipped systems. Open to project work in the meantime. If that sounds like a fit, I'd love to hear about it: busqueneil@gmail.com.

Neil Busque: Notes from the Build