Zack Lovisa Software developer Start an estimate

About

Zack Lovisa

I have seen this industry from three sides.

The family business end, the platform end, and now the freelance end. That is why I can tell you how it actually works, and why I will sometimes tell you not to hire me.

  1. Age 12

    My parents' businesses

    First websites, built for the family. Still the work I understand best, because I watched what a website did for a small business and what it failed to do.

  2. Iowa State

    UI/UX for the Iowa DOT

    University, and design work for the Department of Transportation in Ames. Public sector interfaces get scrutinized harder than commercial ones. Accessibility is a requirement there, not a nice to have, and the standard stuck.

  3. Two years

    GoDaddy

    Inside the largest domain and hosting company in the world, watching how small business websites are actually sold at scale.

  4. Two years

    Wix

    Then the largest website builder. Two platforms, the same lesson: what these products do genuinely well, and where they quietly fall short.

  5. Now

    Freelance, Cedar Rapids

    Taking what I know about this industry wherever I go. Websites, web apps, desktop software, and games.

Disclosure

How I work with code

I learned HTML, CSS and JavaScript the long way, starting at 12. Those are old languages now. I know the code as well as I need to know it to ship in the modern age, and I use current tools, including AI, to get there.

I would rather say that plainly than have you wonder about it later. Most of this industry works this way now and will not tell you.

What you are actually hiring is judgment about what is worth building, the discipline to finish it, and someone who answers for the result afterwards. You do not have to take that on faith. My projects are public, and they are built so the logic runs and tests with no screen attached. One of them fails its own build if anyone introduces an unpredictable result. That structure is what decides whether software still works in a year.

What it comes down to

  • 01

    I get projects done.

    Scope is written down before work starts, and the price holds from there. You know the date and you know the number, and you get working software on both.

  • 02

    I stand behind my work.

    The number I quote is the number you pay. Every build ships with thirty days of fixes included, and the code and the accounts are in your name from day one.

  • 03

    Most things are worth trying.

    It is why the work runs from small business websites through to 3D multiplayer games, and why I will look at the odd project other people turn down.

Evidence

Selected work

All case studies The 3D scene

Start an estimate See the price list