MillywebDevelopmentBook a call

Terms

How audits, builds and the monthly plan work. The written scope for your project is the contract; these are the rules it follows.

Plain-language terms, last updated October 15, 2026. Questions? Email ryan@millyweb.com.

Systems audit: $500

  • Paid when booked. We find a time for the walkthrough once it’s paid.
  • What you get. A written plan: what to fix first, what each fix would cost, and which tools you’re paying for that you don’t need.
  • When. Within 5 business days of the walkthrough.
  • Credit. The full $500 comes off any build you sign within 60 days of getting the plan.
  • Refund. If the plan isn’t worth $500 to you, tell me within 14 days of getting it and I refund it in full. No form, no argument.

Builds: from $2,500

  • Written scope first. Before any work, you get a scope with what will be built, the price and a target date. Nothing starts until you approve it.
  • Fixed price. The price in the scope is the price. If something new comes up, I write it up as a change with its own price, and you decide.
  • Payment. Half when you sign the scope, half when it works on your own phone and you say so.
  • Acceptance. You get 7 days to test it. If I don’t hear back within 14 days of handing it over, it counts as accepted.
  • Fixes. Anything that doesn’t work the way the scope says gets fixed free for 30 days after acceptance.
  • Dates. Target dates depend on you getting me access and answers. If the work waits on you, the date moves by the same amount. If it waits on me, I tell you as soon as I know.

Keeping it running: $500 a month

  • What it covers. I watch the results, fix what breaks (including breaks caused by vendor changes) and send you a short note each month. Small adjustments, up to about 2 hours a month, are included.
  • Bigger changes. New features are quoted as a build.
  • Billing. Billed at the start of each month.
  • Month to month. No contract term. Cancel any time with 30 days’ notice by email.

An hour on the phone: $200

  • Paid when booked. A second opinion on a tool, vendor or plan. If it runs short, it’s still one hour.

Ownership and access

  • You own it. Once a build is paid for, the work, the code and the data are yours.
  • Your accounts. Tools are set up in your name whenever the vendor allows it. Anything I have to hold for you, I hand over on request or when we stop working together.
  • My know-how stays mine. I can reuse general methods and parts that aren’t specific to your business. I don’t reuse your data, prices or branding.

Tools and vendor costs

  • Paid directly. You pay software vendors directly. I don’t mark them up.
  • Listed up front. The audit and every scope list the tools involved and what they cost at the time.
  • Texting rules. Business texting has carrier registration and consent rules. I set up opt-outs and register your number; you agree to text only people who gave you their number for that purpose.

Your data

  • Kept private. I don’t sell, share or reuse your customers’ information.
  • Kept safe. Passwords and keys live in a password vault, never in the code. Pages that show customer data need a login.
  • Removed at the end. When we stop working together, I return or delete what I hold and remove my access.
  • Confidential. I’ll sign your NDA if you have one.

Payment

  • Invoices. Due within 15 days.
  • Late. If an invoice is more than 30 days late, work pauses until it’s paid.

Limits

  • Other people’s services. I’m not responsible for outages or changes at vendors like your phone carrier, CRM or payment processor, though on the monthly plan I fix what those changes break.
  • Cap. If something I built causes a loss, my responsibility is capped at what you paid me in the 3 months before it happened.
  • Law. These terms follow Oregon law.

Ending work

  • Either of us can stop. Stopping a build mid-way: you pay for the work done to that point, and you get everything done so far.
  • Handover. Within 7 days of ending, you get the notes, the code and access to everything in your name.