Alex Voigt

I’m Alex

I design software, and then I build it.

For three years I have been the designer, the frontend engineer and the Head of Product behind Codifi, field data software for crews who work where there is no signal. Before that I was a pastor for nine years, published twelve iOS apps, and made a lot of films.

Alex Voigt at a wooden desk, looking at the camera: short dark hair, a trimmed beard, a black sweater. A laptop and an iPad on a stand are in front of him, and two woven plates hang on the white wall behind.

What brings you here?

Three years, one product.

Codifi is field data software for people who work a long way from a cell tower: archaeologists, wetland scientists, survey crews. It takes a project from the blank form to the finished report in one product, instead of six apps and a lot of copying by hand.

I designed it, wrote most of what you touch in it, and led it as Head of Product.

Open the case studyVisit www.codifi.com

Alex and Hugo stand on a sand dune with an arm round each other’s shoulders, each holding a wooden sandboard, under a clear blue sky.
Hugo and me, March 2026.

Three of us built it.

Codifi was built by a team of three, each covering what the others could not: what to build, how it works underneath, and whether it actually does.

  • Alex Voigt

    Head of Product

    Designed the product and its design system, wrote most of what you touch in it, and led it from the first sketch to a company-wide rollout.

    Alex on LinkedIn

  • Hugo Bounoua

    Solutions architect

    Architected Hydra, the sync engine, and Ripple, the formula engine, and built much of the backend underneath them.

    Hugo on LinkedIn

  • Jonathan Sims

    Project manager

    Ran the projects, the regression testing and QA, and the log of what users asked for, so each release started from what crews needed and was tested before it went out.

    Jonathan on LinkedIn

I would work with both of them again tomorrow. Hire us together and you get a team that has already taken a product from a crew’s request to the release that answers it. Hire any one of us and you get someone the other two will vouch for.

Message me on LinkedInSee what we built

How I work

When I design and code the same feature, the interface shapes the data model and the code keeps the design honest.

  1. Design it

    In the real product, not beside it. A prototype I can put on a device beats a mockup I have to explain.

  2. Build it

    I write the frontend myself, in TypeScript, React and React Native, usually with an AI agent on the other side of the desk.

  3. Put it in the field

    A build goes to a crew, and I go with it when I can. There is only so much you can learn from a screen.

  4. Fix what they tell me

    Then ship again. Usually within days, because the person who heard the problem is the person who can fix it.

A field archaeologist in a hi-vis vest shakes soil through a wooden screen, a cloud of dust falling from it, in an overgrown clearing.
Memphis, on a site visit. Screening the soil from a shovel test.

The long way here

Developer, pastor, designer, product lead. Newest first, back to 2009.

  1. 2024 to nowHead of ProductCodifiChronicle Heritage
  2. 2023 to 2024Founding designer at CodifiCodifi
  3. 2022 to 2023A year of UX contractsTrellus and Connect7
  4. 2013 to 2023Pastor and multidisciplinary designerFlorida Conference of SDAs
  5. 2009 to 2014Twelve iOS appsSelf-publishedErhard Furniture and Flooring

A camera, most weekends

I shoot and cut film, and I carry a camera when I travel. It is the same job as product work: decide what the story is, then leave out everything else.

See the film and the photos
Still from the film We’re on a Mission: a pickup truck drives toward the camera down a dirt road, its dust lit from behind by a low sun.A green valley under a snow-covered volcano in south Iceland, with a row of small white farm buildings along its floor and storm cloud above.Joshua trees in silhouette against a low desert sun.