ZovaWorks Talk to me

Independent AI and software consulting

I turn problems into shipped, working systems

ZovaWorks is the practical step that gets you from a fuzzy AI or software idea and something real you can actually deploy. We will sketch the system together, then I'll wire the parts that should talk, and ship a focused tool that earns its keep.

Send me the problem See how I work
Works with
Businesses of any size
Projects
Scoped to one problem
Start with
A few sentences from you

How I work

What working with me looks like

Most work moves left to right, in series; but every project taps in wherever the signal is weakest. Let's make it happen.

  1. 01Step 1 of 5

    Clarify

    We work out what the problem really is and what the smallest useful version would be. And we agree up front how you'll tell whether it worked.

    We agree what done looks like first, and change it as we learn.

  2. 02Step 2 of 5

    Prototype

    I build a rough working version fast, so there's something real to try and poke holes in before anyone commits to the full build.

    It's fine if the first version is ugly.

  3. 03Step 3 of 5

    Automate

    If someone puts together the same report by hand every Friday, or sends the same reminders, that job belongs to software. I build it, and your people keep the work that needs judgment.

    Start with the task everybody dreads.

  4. 04Step 4 of 5

    Integrate

    When two of your tools hold pieces of the same record, someone ends up typing it twice. Where the tools allow it, I link them so a change in one shows up in the other.

    Enter it once, and it goes where it's needed.

  5. 05Step 5 of 5

    Ship

    We get it in front of the people who'll use it. Real use turns up problems no test does. I'll offer a way to report them from inside the tool, and a round of fixes after launch is included.

    Often two or three people try it first, then the rest.

Checks on AI

The parts that keep an AI system trustworthy

When software starts making decisions, four practical concerns get wired into the map from day one.  A custom dashboard tailored to your needs and instrumentation you can trust, that lets you reason about what the system is doing.

  • ACTIVITY LOG

    A record of what it did

    I keep a log of each step, so when an answer looks off you can see what the tool was given and what it did with it.

  • FAILURE PLAN

    A plan for when it fails

    Apps go down, and AI can come back with nothing useful. I plan for that. A failed step gets tried again or handed to a person, and I set it up to tell someone.

  • TESTING

    Evaluations

    Measure whether the output is good enough, on purpose — a feedback loop so quality is checked, not assumed.

  • HUMAN REVIEW

    Where a person steps in

    You decide what the tool can do on its own and what needs a person's okay. We write down what it must never do, and test for it.

Examples

A few ways that might look

These are made-up examples, not past client work. Each one is the kind of problem you might bring me.

Scroll to watch each one come together, or jump to the one that looks like yours.

  • SpreadsheetbecomesSmall app

    The spreadsheet only one person understands

    If your scheduling lives in a spreadsheet with a dozen tabs, I'd turn it into a small app that does the same job, checks what people type, and remembers who changed what.

  • Shared inboxbecomesSorted and drafted

    An AI that sorts the inbox nobody owns

    Say requests pile up in a shared inbox. I'd build a rough version that reads each one, drafts a reply, and routes it to the right person. You'd try it before we commit to more.

  • QuotebecomesDraft invoice

    Retyping the quote as an invoice

    If someone rebuilds every approved quote by hand as an invoice, I'd connect your quoting and accounting tools so approving one drafts the other. You'd check it instead of retyping it.

  • How it works nowbecomesWhere AI fits

    Finding where AI fits

    Say you keep hearing you should be using AI and can't tell where. We'd walk through how the work gets done and find the one or two steps where it would help. If it's none, I'll say so.

  • Missed callsbecomesAI receptionist

    The phone that rings during lunch

    Calls go to voicemail while you're busy. I'd set up an AI receptionist to answer the usual questions, take a name and number, and hand off to a person if it can't help. We'd test it before it's live.

  • IdeabecomesWorking tool

    A small product built from scratch

    You have an idea for a tool and nobody to build it. I'd start with the simplest version, build it with AI helping on the code, launch it, and hand it over with notes on how it works.

About me

Who you'd be talking to

Based in
Washington State
Writing code
Over twenty years

Hi, I'm Eric.  I'm an independent builder who likes the part where a vague idea becomes a system that you can point at.  I have been building solutions in complex spaces for decades.  Finding gaps in processes, or inefficiencies in workflows, and then designing solutions that turn those into smooth and hidden business wins is what I enjoy.

I keep engagements small and direct: no account managers, no hand-offs to a junior team. If we work together, you're working with the person designing and building the thing. 

EricFounder of ZovaWorks

Contact

Tell me what's tangled

A few sentences about the problem is enough. No pitch deck needed. I read these myself, and if it's not a fit, you'll hear that from me.

  • Writing to me doesn't commit you to anything.
  • I don't sell what you send or add you to a list.
  • I usually reply within a day or two.

More details (optional)

* requiredGoes straight to me.

Got your message

Thanks. I read these myself and I'll write back, usually within a day or two.