Millyweb DevelopmentMillyweb

Ryan Milly

Quoting, booking and follow-up for service businesses. Newberg, Oregon.

I started Confidence Moving Labor in Amity in 2018. At its biggest we had 25 people on payroll. The first system I built was for us: confidencemove.com gives a customer a real moving estimate in about two minutes, priced the way I quote on the phone. Now I build the same kind of thing for other trade and service businesses, and keep it running after it’s live. Most owners start with a $500 systems audit.

A Confidence mover strapping a hot tub standing on its side in a narrow side yard while another crew member steadies it
Strapping a hot tub to get it out of a side yard, September 2018.

A few jobs from 2018

Two movers beside a grand piano in a round sunroom
Box truck packed floor to ceiling with stacked boxes
Two movers walking an upright piano out of a front door
Two movers carrying a long boxed item down a truck ramp
Rows of new cabinets staged in a parking lot for a commercial delivery
Two movers loading a box truck from the ramp
Crew member sweeping an empty room after a move-out

What’s costing you time?

Check what sounds familiar. The box on the right is roughly what I’d tell you on a first call. If it looks right, email it to me and that’s where the audit starts.

What happens at your shop?

Here’s where I’d start

    Email this to me

    Rates

    If we build something after the audit, the $500 comes off the build.

    Systems audit

    $500

    We go through how a lead becomes a paid job at your shop: calls, quotes, scheduling, deposits, follow-up. You get a written list of what to fix first, what each fix costs, and which tools you’re paying for that you don’t need.

    A build

    from $2,500

    One connected piece, written up and agreed before any work starts. Usually a quote estimator, missed-call text back, booking with a deposit, or getting your CRM, texts and calendar to talk to each other. You test each part on your own phone before I move on.

    Keeping it running

    $500 a month

    Automations break quietly when a vendor changes something. I watch the results, fix what breaks, and send you a short note each month on what happened.

    An hour on the phone

    $200

    For a second opinion on a tool, a vendor or a plan.

    Before you book

    Do I need to be good with computers?

    No. If you can tell me how your week goes, that’s what the audit needs. You’ll test everything on your own phone before it counts as done.

    Who owns what you build?

    You do. Accounts go in your name where possible and you can see the code. Nothing is stuck behind my login.

    What happens when something breaks?

    If you’re on a monthly plan, I usually catch it first. If not, you have the notes and anyone competent can pick it up. Either way, every build sends a person an alert when it stops working.

    What about my customers’ information?

    Passwords and keys live in a vault, never in the code. Every page that shows customer data needs a login. I’ll tell you which outside services touch your data and why.

    Do you only work around Newberg?

    I know Willamette Valley businesses best, but all of this runs online. I work with owners anywhere in the US.

    What’s running now

    Everything here is live. I’ve put what went wrong next to each one.

    Confidence Moving Labor homepage with an instant job estimate
    confidencemove.com

    Confidence Moving Labor

    My own company, rebuilt so someone can get a real number without waiting for me to call back. The estimate works the way I quote on the phone: load, unload or both, truck size, stairs and elevators, anything over 200 pounds, and drive time. Pricing is per mover and shows what goes to wages, insurance and margin.

    Anything over four bedrooms gets an in-person look. The hour math stops being honest past that, and I’d rather say so.

    What broke: deploys said they succeeded and the live site never changed. The code was on one branch and the host was publishing another, so every update went to a hidden preview. Now every deploy names the branch and gets checked on the real address.

    confidencemove.com

    Mesh Controller public build log
    gocontroller.app, the public build log

    Mesh Controller

    The system everything else here runs on. Four servers, 60-some containers, and one gateway that lets AI agents use about 680 tools without drowning in them. Agents see 16 tools up front and search for the rest by what they do.

    Every change has to pass a check before it deploys, and a daily report flags the problems that don’t throw errors. One of those checks cut a health scan from 11.4 seconds to 4.25, mostly by measuring first. My first guess about what was slow was wrong.

    What broke: the very first run of that check found a command endpoint open to the internet with no password. It was closed the same day and tested from both sides. Later a binary swap failed silently and locked us out until I could get in through the host’s web console. There’s a written procedure for that now.

    gocontroller.app

    Other things I’ve built

    RevenueFirst.aiFollow-up for service businesses, so a lead keeps hearing from you until it books or says noLive
    Gutters & LightsOne site for two seasons. The side that leads changes with the calendarLive
    AOS FilesPacific Northwest history and investigations, with a case file templateLive
    Helix and MemBrainA memory layer for AI assistants: a Chrome extension plus a knowledge base on my own serversLive
    Just Little StepsSite and booking for a childcare business in McMinnville and NewbergLive
    Lead pipelinePulls Oregon’s 55,802 licensed contractors and maps data into scored leads, about $2.42 a runRuns on my servers

    How a job runs

    I build with AI the way I ran crews. Clear scope up front, and somebody checks the work at the customer’s door.

    1. We talk it through. What breaks if we don’t build this? Does something you already pay for do it?
    2. I write it down. What it does, what it doesn’t, and what “done” means. You sign off.
    3. One piece at a time. Nothing half-built piles up.
    4. It has to pass a check. Code and security checks run before anything goes live. If they fail, it doesn’t ship.
    5. You try it on your phone. The next piece waits until you say this one works.
    6. Notes stay with the project. Whoever touches it next, me or anyone else, knows what happened.

    When something breaks in a way that wasn’t obvious, I write down what happened, the proof, and the fix. I call them scars, and they come up before anyone works on that part again. Here’s a real one, trimmed:

    kind      gotcha
where     cloudflare pages deploy
claim     Deploy reports success, site never updates.
evidence  Repo on master, production branch is main.
          Every push lands as a preview.
fix       Always deploy with --branch=main, then
          check the live URL, not the tool output.

    About Ryan

    I started Confidence in 2018 and grew it to 25 people. I hired out of a recovery program from day one, and we still do.

    That set the tone for everything. Be clear about what the job is, estimate heavy so people can budget, and tell customers what to watch out for with any crew, even if they don’t hire us. About three out of four leads that called us booked.

    When I stepped back from the trucks I went looking for tools for the office side: quotes, missed calls, deposits, reviews. The software was priced for bigger companies, and the lead marketplaces wanted 15% of every job, so I started building my own.

    I don’t hand-type the code. I direct AI to write it, and I own the parts that decide whether it works: what it should do, the rules it has to follow, the checks it has to pass, and making sure it actually works where the customer sees it. It’s the same job as running a crew.

    Confidence, by the numbers
    Founded2018
    Peak staff25
    Peak revenue (2022)$432,000
    Margin that yearabout 28%
    Leads that booked76%
    Google rating4.8 (64 reviews)
    Holiday lighting route60–70 homes a year

    Building AI systems since 2023.

    If you’re hiring

    I’m open to remote implementation and delivery work. I’ve been the non-technical customer, I’ve run a payroll, and I ship working systems with real process around them. The work above is the evidence, failures included.

    Ask me for a résumé at ryan@millyweb.com, or find me on LinkedIn and GitHub.

    • Implementation consultant
    • Solutions consultant
    • Technical account manager
    • AI program or project manager

    Day to day: Claude and other LLM agents, MCP, n8n, Go and Python, Docker and Linux, Postgres, Cloudflare, Twilio, CRM integrations. Studying for Security+.

    Tell me where your week goes sideways.

    A few lines about your business is enough. Write to ryan@millyweb.com. I read every one myself, and if I’m not the right fit I’ll tell you who is.