Building a SaaS Solo, With an AI Pair

I built Bin X because I run Eco Moving Utah and I was living the problem it solves. No bigger reason than that.

Eco Moving Utah rents stackable moving totes in Salt Lake County, with free delivery and pickup. From the outside it looks simple. A customer picks 20, 40, or 60 totes. I deliver them. I pick them up two weeks later. On the inside it is bookings, scheduling, payments, reminders, and a pile of small details that cannot get lost.

I spent more than 20 years in software, including a decade as Chief Technology Officer (CTO) at MonitorBase. I knew what a real system should look like. I also knew I was one person. That is where the AI pair came in.

One engineer, two sets of hands

Bin X is a bin rental CRM and scheduling product for operators like me. It went live at app.binxhq.com on October 19, 2026. Signup and login worked. A Neon Postgres database sat behind it. Real payments through Stripe were unblocked the next day.

Eco Moving Utah is operator number one on it. The first real test was never a demo. It was my own business, with real customers and real money.

Building solo used to mean every task waited in the same line. Code, copy, documentation, testing, and follow up all took turns behind whatever was loudest that day. The agent changed the shape of that line. I still make the calls on architecture, data, and product direction. The agent takes the first pass at the work around those calls. Drafting. Checking. Organizing. Keeping lists current while I stay on the decision in front of me.

That is what pair work means here. Not two opinions voting. One engineer accountable, and a second set of hands that never gets tired of the repetitive parts.

What the pair does well

The best use of the agent is not a big dramatic build. It is the steady work that makes a product real.

It turns a feature idea into a checklist, then works that list without losing the thread between sessions. It drafts the plain language a new operator will actually read. It checks a flow against the rules I already set, like keeping Bin X on subscription pricing only. I dropped the transaction fee idea on November 4. A straight CRM subscription is cleaner for operators and cleaner for me. A good pair catches when old wording or old logic still points at the model you abandoned.

The agent also knows the operator side because it helps run it. The same system that tracks deliveries and pickups for Eco Moving Utah reminds me what a small rental business actually needs from its software. Simple beats clever. A screen that saves a phone call beats a dashboard nobody opens.

What I never hand over

Speed does not change who decides.

Pricing is my call. Product direction is my call. Anything customer facing waits for my approval. Anything involving money waits for my approval. Design sign off waits too. Those rules were already in place for the moving company. Building software did not loosen them.

That boundary is not a lack of trust in the tool. It is the reason the tool works. If I had to recheck every small draft like it might have committed the business to something, there would be no leverage in it. Because the agent cannot commit the business, it can move fast on everything short of committing it.

I was laid off in April 2026 after serving as Chief Technology Officer (CTO) and then VP of Development. Building Bin X this fall reminded me that a team is not only a headcount. A team is clear ownership, a shared list, and work that does not stall when one person has to go run a tote route.

Write down the decisions only you can make. Keep those. Hand the agent the first pass at everything else, and keep your approval as the gate before anything real ships or sends. That is the whole system.