Already a customer?Go to portal

Mizell Software

919-909-0806 · hello@mizellsoftware.com

The two things I have built and kept running.

Each film on this page is the real product, redrawn as animation. The names and numbers in them are made up. The links under each one open the live site.

Concerts For You

Finds the bands you already listen to, playing near you.

  1. 0:00

    A front door that asks one question

    The first screen asks where you listen and sends each answer down its own path. The same pattern sorts a customer request before anyone has to read it.

  2. 0:03

    Reading the file you already have

    Fourteen thousand plays go in as a raw export and come out as a clean list of artists. Your spreadsheets and system exports can be read the same way, with nobody retyping them.

  3. 0:07

    A map that sets the rules

    Drop a pin, drag the circle, and everything after it respects that distance. Service areas and delivery zones work the same way.

  4. 0:12

    Decisions, one card at a time

    Each show is a card: skip it or act on it, and the count goes down. Approvals, leads and review queues become a stack you clear instead of a list you scroll.

  5. 0:18

    Watching what is not ready yet

    Artists playing further out get their own list, and you hear when one of them books a date near you. Anything waiting on a date, a price or a reply can tell you when it moves.

  6. 0:23

    Numbers that count themselves

    What you brought, what can be followed and what is close, totalled with nobody adding it up. The same view works for jobs, sales or hours.

What it runs on
One small server that runs the site and the data behind it, with a single database file. The shows come from Ticketmaster’s own data, so no recommendation service sits in the middle deciding what you are shown.
What it costs to run
It shares that server and that database file with Wedding 2027. Those are my two products, not anybody else’s, so the two of them together are one hosting plan and one domain rather than one bill each. What I would build you is that same shape on the platform I run this business on: one setup I update in one place, your own domain in front of it, and your data kept to itself, separated from mine and from anybody else’s. That data comes back to you in a named format whenever you ask for it.

Want something like this for your business? Call me at 919-909-0806 or tell me about the job.

Wedding 2027

A four-country trip and every deposit in it, kept in one place.

  1. 0:00

    A plan that draws itself

    Four countries and ten weeks, laid out as a route and then as days. A build schedule or an event runs the same way.

  2. 0:04

    Money against every line

    Record a payment on one card and the totals at the top move with it. Deposits, invoices and budgets stay in one place instead of three.

  3. 0:08

    Two options, side by side

    Switch between two villas and every detail changes with the choice. Quotes and vendors compare the same way.

  4. 0:13

    Proof that updates the record

    A confirmation email lands and the rail pass is marked booked. Receipts and vendor mail can close out your paperwork without anyone typing.

  5. 0:18

    A ledger that adds it all up

    Paid, owed and committed, broken out by category and by country. The report you rebuild every month is already there.

  6. 0:22

    Changes asked for in plain English

    Type what you want moved and the assistant does it, then says so. Your team can ask for a change without learning the software.

What it runs on
The same server and the same database file as Concerts For You. It is a second site on the same setup.
What it costs to run
Nothing beyond the hosting plan Concerts For You already pays for.

Want something like this for your business? Call me at 919-909-0806 or tell me about the job.

Both of them run on one server, on purpose.

Two products on two servers means two of everything: two sets of security fixes, two rounds of updates, two databases to change, and two places to look when something quietly breaks over a weekend. One person cannot keep that up for long, so I build everything on one server, with one database file and one place to check when something goes wrong.

This matters to you as much as to me, because your software would be the same shape. The cost of keeping a small piece of software alive is almost entirely the cost of the attention it needs. That arrangement is the one that needs the least of it.

ONE SERVICE ONE NODE PROCESS ONE SQLITE FILE CONCERTS FOR YOU WEDDING 2027 TWO PRODUCTS, ONE HOSTING PLAN ONE SERVICE ONE NODE PROCESS ONE SQLITE FILE CONCERTS FOR YOU WEDDING 2027 TWO PRODUCTS, ONE HOSTING PLAN

What would you like to make easier?

Tell me about the job your team keeps doing by hand. We can work out where software would help.