Already a customer?Go to portal

Mizell Software

919-909-0806 · hello@mizellsoftware.com

From the first call to the monthly report.

  1. Understand the job.

    One week

    You show me the job on a call. I spend the week on it and write a plan for what to build, what it costs and when it can be ready.

  2. Build the software.

    Two to six weeks

    I build what the plan says, around the tools you already use. You try it on a private copy and approve it before it goes live.

  3. Keep it running.

    Every month after launch

    I host it, watch it and fix it. You get a short report each month.

All four steps in full.

  1. Understand the job

    1 week

    $250 for the audit.

    One week of my time and a written plan you keep.

    How long
    One week
    The call
    Sixty to seventy-five minutes
    You keep
    The written plan

    What you do

    • Share your screen and do the job while I watch, on one call of sixty to seventy-five minutes.
    • Tell me which tools and accounts the job touches.

    What I do

    • Record the call only if you say yes out loud at the start.
    • Check every tool the job touches and rate it green, yellow or red. Green means I can get in. Yellow means you need a paid plan or an approval first. Red means I cannot get in, and if the job depends on it, we stop there.
    • Write the plan, and review it myself before you see it.

    What you keep

    The plan: the job as it stands, what I would build and what I would not, how we will know it worked, the timeline and the price. One flat fee of $250, paid once. You keep the plan whether or not I build anything.

  2. Build the software

    2 to 6 weeks

    $3,500 to $12,000 for a build of two to six weeks.

    One workflow with nothing outside to connect takes two to three weeks. Several related workflows, with an outside system and a screen your staff use, take four to six weeks.

    The price
    Fixed in writing before work starts
    When it changes
    Only if you ask for something the plan does not include
    Payment
    A deposit to start, the balance before launch

    What you do

    • Sign the contract and pay the deposit. Work starts once both are done.
    • Send the logins I ask for, once, at the start. The timeline moves if they arrive late.
    • Try each part on a private test address and tell me what you find.
    • Pay the balance. Then it goes live on your domain.

    What I do

    • Build it in small pieces. Each one is checked against the plan’s written list of what done means.
    • Go through everything you find with you on a call, and sort each item: a defect I fix, a preference, or new work.
    • Spend thirty minutes with you at launch. You do the real task yourself, send one change request and watch it go out.
    • Build with AI tools, and say so in the proposal.
  3. Keep it running

    Monthly

    From $350 a month.

    That is the floor. Where yours lands depends on what I built and how much upkeep it needs.

    It covers
    Hosting, backups, monitoring, updates and fixes
    The report
    Once a month, with the invoice

    What I do

    • Host it, back it up and keep it updated.
    • Watch it with automated checks that restart what they can.
    • Log every change in plain words, where you can read it.
    • Send a report each month: what changed, how it ran and what I am watching.

    Fixes and new requests

    A bug is when the software does not do what the contract says it does. A change is when you ask it to do something new, however small. In both cases, the size decides what happens next. I cover anything under about two hours. Two to eight hours comes out of that month’s allowance, after I email you and you say go ahead. Anything over eight hours gets a written quote before I start.

    If a product you already pay for changes in a way that breaks the connection, I fix it and the care plan covers it. If that company then charges more for the access itself, you pay that bill.

    If you leave

    Your license to use the software continues, your data comes out in a named format, and control of your domain, registered in your name, passes to whoever you name within five business days, without a fee or conditions. Data Guarantee covers access, backups and ownership.

  4. Train your team

    1 hour to 4 weeks

    I teach people to use AI tools on the work they already do, and what company information is safe to put into them.

    Four sessions: a working hour with your staff, a seminar for a chamber or trade group, a three-hour build and a four-week course. You can buy any one on its own. This is general practice and is not legal or compliance advice.

    Prices and details for each session

What the plan looks like.

Read an example plan

The company and the numbers are made up. The nine headings are the real ones, in the real order.

Example: Carter Irrigation, six vans, Apex NC

1. The problem, in your words

"The schedule for tomorrow is on a whiteboard in the shop. I photograph it about six every evening and text the picture to the crew leads. If a job moves after that, I call three people and hope. Twice this month two vans went to the same address and nobody went to the third."

2. What it costs you today

About forty minutes an evening, five nights a week. Roughly 160 hours a year. The two double-bookings this month cost a wasted morning each and one customer who has not called back. The larger cost is the one you did not mention: nobody except you can answer "where is Danny" without calling Danny.

3. What I will build

One screen the crew leads open on their phones: today and tomorrow, their jobs only, in order, with the address and the gate code. One screen you open in the shop: all six vans on one page, where you move a job between vans by dragging it. A move you make is on their phones inside a second. Nothing to install, and it works on the two-year-old Android in the yard.

4. What I will not build

No invoicing, no payments, no customer portal, no route optimization, no GPS tracking. Each is a real thing you may want one day and none is the job you described. I am also not replacing the whiteboard. It stays.

5. How you will know it worked

Three things, checked six weeks in. You stop photographing the whiteboard. Zero double-booked addresses in a month, counted off the schedule itself. A crew lead can answer "what is my third job" without calling you.

6. What changes for you beyond the obvious

The schedule stops being something only you can read. When you are out for a day, somebody else can move a job without your handwriting in front of them.

7. What I need from you

An hour at the start to watch the evening routine. The list of your six crews and who leads them. One crew lead willing to try it for a week and tell me it is wrong.

8. Timeline

Three weeks to the first working version, with the shop screen in week two. A week running it beside the whiteboard. Live in the fifth week.

9. Investment

A single fixed number inside the published build range, quoted in writing before anything is built. A deposit to start and the balance before it goes live. Then a monthly care plan for hosting, backups and fixes.

Carter Irrigation is not a client and never was.