My story

Newest first. Keep scrolling and you dig down to 2009.

2024 to 2026

Head of Product

  • Head of Product, CodifiAug 2024 to Oct 2026
  • Head of Product, digital transformation, Chronicle HeritageAug 2024 to Oct 2026

In August 2024 the company pivoted. Our parent Chronicle Heritage folded Codifi in and the mission became digital transformation: moving a national firm off a patchwork of ArcGIS Online, Field Maps, Survey123 and legacy FileMaker databases and onto one workflow.

I became Head of Product and reported to the CEO. The job grew from shipping features to changing how a whole company works. That meant training, rollout, listening to skeptics, and earning trust in more than twenty offices and practice groups at the same time. That year the original product team of around 20 offshore developers left and I took over product and engineering as one team of three. We dropped rigid two-week sprints for design and engineering working as one and shipped three major versions that way. I kept writing most of the frontend the whole way through.

Two people in hard hats and hi-vis vests in a deep, narrow trench, seen from above. One is scraping the trench wall with a long-handled tool.
Phoenix. Facing a trench wall, to read the soil in it.

The margin analysis: what Codifi did to the numbers

I led a review of 1,082 jobs joined to Codifi usage and the GIS timesheets to find out what the product had done to the firm’s margins. Finished Codifi jobs held their margin even though they were put on field-heavy work. Fixed-fee jobs came out about six points higher. GIS hours after fieldwork fell 38%. In Memphis 95% of the year’s field work ran on Codifi with margins held.

What I did
  • Prepared the review: 1,082 job numbers with revenue, cost of sales and wages, joined to Codifi usage and 15,500 hours of GIS timesheets
  • Finished Codifi jobs at margin parity with the rest, 61.0% against 61.2%, on field-heavy work
  • Finished fixed-fee jobs 5.8 points higher where Codifi was used, 63.1% against 57.3%
  • GIS hours after fieldwork, per revenue dollar, down 38% on finished Codifi jobs
  • Memphis moved 95% of its 2026 field work onto Codifi with margins at parity

Three versions and 25 releases

A team of three shipped three major versions. From 2.0 in July 2025 on that was more than 25 releases counting every point release. Version 3.0 in February 2026 was the third major version I had worked on. It brought Hydra, our solution architect’s offline sync engine. Then 3.1 in March with forms that do the math, 3.2 in June with a redesign across web and mobile, and 3.3 in August with sync from device to device and no internet at all.

What I did
  • More than 25 versions cut between 2.0 and 3.3.5, counting every point release. From 2.0 on I built the iOS app and uploaded it myself: at least 14 uploads to App Store Connect across nine versions, and two Expo SDK upgrades
  • Led product for the move to Hydra and designed what a crew touches: sync status, recalling an earlier value and a history of every edit, offline ones included
  • Designed and built the forms’ calculated fields and conditional visibility on Ripple, our solution architect’s formula engine
  • Owned the design system and led the 3.2 redesign across web, mobile and the marketing site, prototyped in the real product and iterated with field crews
  • Designed and built Nearby Sync for crews with no signal, Camera Compass, Draw Mode and GeoTools on the web, and survey-grade positioning from the Emlid Reach RX2
  • Built the raster pipelines: USGS 3DEP LiDAR flattened into digital elevation models with hillshades, and historical topo layers for field maps

How I designed and built it

Codifi on an iPad, seen at an angle, from the App Store screens I designed: a list of 1,338 records, and in the header a cloud icon with a small cross on it, the offline state.

We’re on a Mission

I travelled across the company, sat down with the people doing the work, and cut two hours of interviews into a film about why the work matters. I have never struggled to finish an edit like this one: every person told a story that deserved to make the final cut.

What I did
  • Produced, shot and edited Chronicle Heritage’s mission film
  • Interviewed staff across the business, in person and remotely

Watch the film

Still from the film: a surveyor in a hi-vis vest walks across open desert scrub, with a flat-topped mesa behind.

Leading the company on AI agents

I was an early adopter, so I led the company’s move to AI. That changed how we wrote code and how fast an office got its database. Hours instead of weeks. On a normal day I run up to nine repositories at once in herdr, each in its own space, with several tabs and several agents working different tasks in each.

What I did
  • Changed how we brought offices on. It used to take weeks or months on a few databases across two or three offices. With agents I worked with up to twenty offices at a time and turned database builds around in hours
  • Ran the same loop with every office: fold in their changes, build a demo, send a triage of open questions, repeat
  • More than 1,100 AI-assisted commits across the web and mobile apps
  • Wrote the layered docs agents work from and trained teammates on the workflow

How I work with agents

The rollout: a national firm changes how it works

Chronicle Heritage’s offices each had their own way of doing fieldwork: a FileMaker database here, Field Maps and Survey123 forms there, built by hand for each kind of project. We replaced that in more than twenty offices and practice groups at once. In a year monthly field users went from 13 to 108 and the share of project revenue in the domestic offices that ran through Codifi from 11% to 44%. In Memphis, late in 2024, the office ran its shovel testing in Codifi and cut its data entry after fieldwork from days to hours. I was on site to watch, listen and turn what I heard into the next release.

What I did
  • Led the rollout of Codifi across a national cultural resource management firm, more than twenty offices and practice groups at once
  • Ran the same cycle with every team: deliverable in, agent-built data model and demonstration project out, review, recap, triage, repeat
  • Trained crews and managers, in person and remotely
  • Ran site visits in Phoenix, Memphis and Pennsylvania
  • Spent days in the field with the Memphis crew, camera and notebook in hand, and turned what they said into shipped changes within days
  • Configured more than 40 data models by API, including migrations from FileMaker and ArcGIS Online

What the rollout took

A field archaeologist in a hi-vis vest and sun hat enters data on an iPad in a rugged case, standing next to a shovel and a soil screen.
Memphis. A shovel test recorded in Codifi, standing next to the hole.

The takeover: product and engineering become one team

The original product team of around 20 offshore developers left in 2024. I took over product and engineering as one team of three.

What I did
  • Took over product and engineering as one team of three
  • Put the operating model in place: the roadmap, QA and QC, retrospectives, post-mortems and pre-mortems
  • Owned the product budget and updated our SLAs and contracts

The three of us

2023 to 2024

Founding designer at Codifi

  • UX/UI Designer (founding product designer), CodifiMay 2023 to Aug 2024

I joined Codifi in May 2023, just after it spun out of an archaeology firm’s technology team to become its own company. I was employee number seven and the only product designer, so I owned what the product did and how it felt.

Then the to-do list kept growing. I started writing the frontend because waiting on handoffs was too slow. I wrote the docs and release notes, configured customer data models, field-tested GPS receivers, and sat with crews in the field. The company grew to 55 people while I took a very minimal product through MVP and redid most of its early designs.

Two early designs for Codifi’s iPad app. Left: a project’s records as a tree, with archaeological sites, site visits and artifacts, each with a type, a status and an assignee. Right: a form section with text, number and date fields.
Early designs for the iPad app. A contractor did some of this before I joined. I took it over and redesigned most of it.

First commit: I start building what I design

Nine months in I made my first commit to the mobile app: the login and dashboard screens. Version 1 had been design work for me until then. That same month it began going out to crews, as a run of dated releases that carried on into 2025.

What I did
  • Designed version 1 of the web and mobile apps, as the only product designer
  • Wrote my first production React Native in February 2024
  • 49 commits that first year, 292 the next, and nearly 1,300 in 2026

2022 to 2023

A year of UX contracts

  • UX Designer (contract), Trellus and Ad + CoJul 2022 to May 2023

In the fall of 2022 I took a formal UX/UI certificate course to put a name on work I had been doing for years. Then I took UX work for clients for about a year while I finished my last months as a pastor. On one of those projects I led a team of six designers.

Ad + Co: a clearer brand story

A redesign of a small shop’s website, to tell its story more clearly and earn a first-time visitor’s trust, inside a small development budget.

What I did
  • Ran competitive analysis, journey maps, wireframes and prototypes
  • Reviewed the site against Nielsen’s ten heuristics and WCAG 2.1 AA
  • Reordered the page hierarchy to cut what a visitor has to hold in their head
A laptop on a pink background showing the Ad + Co website’s Our Story page.

Trellus: a coach beside the call

Trellus is a Chrome extension that gives sales reps live transcription and real-time prompts beside their CRM. Users liked what it did and disliked how it looked. I led the redesign from the client’s research to developer handoff. A public review afterwards: “The entire UI overhaul is more visually aesthetic and easier to process during a call.”

What I did
  • Led a team of six designers and was the client’s point of contact
  • Rewrote the brief’s user stories around what a rep needs in the middle of a call
  • Kept us in low fidelity while the client pushed for finished screens. A pretty UI was not going to decide the UX
  • Ran the flows, sketches, wireframes, style guide and prototype. Annotated every state that changes on its own for the developer
Trellus design: a narrow panel beside a CRM shows a live call with John Doe, a suggestions box, a Great Work coaching card and a talk-time gauge.

Empower.io: somewhere to charge a phone

The case study I chose for my certificate course, on a problem I saw every care day at SALT: unhoused people have nowhere they are welcome to charge a phone. A dead phone cuts them off from family and services. I screened eight people and interviewed five, three of them on the streets of downtown Tampa. Then five usability tests.

What I did
  • Designed in true black to save a dying battery. Sent directions as a text in a notification instead of keeping GPS running
  • Put a welcome from the owner on every charger’s page, because the people I talked to did not want to feel like trespassers
  • Fixed what testing found: clearer filter chips, sorting for reviews and a way to delete your own review
  • Seven weeks, from screener to tested prototype
Three Empower.io screens in dark mode: a café’s page with a note from its owner welcoming people to charge there, a map of nearby chargers, and a review being written.

Also, on contract

Contract

Ourtifact: a design system a developer could build from

Ourtifact records a couple’s story as an interview and turns it into a podcast-like audio keepsake. I designed its web app for a desk and for a phone: pick a story to tell, keep track of the ones in progress and listen to the ones that are finished.

What I did
  • Took the web app from wireframes to finished, responsive screens
  • Built the design system on Figma variables that map one to one onto Tailwind’s utility classes
  • Handed it to the developer with annotated screens, and taught the mapping from Figma’s auto-layout to Flexbox
Ourtifact designs on a warm orange gradient. The web app’s Create tab offers stories to tell as cards: Our Meet-Cute, Engagement Story, Funny Memory. In front of it, a phone plays Our Meet-Cute, with a photo of two hands reaching for each other at sunset and a transcript underneath.

2013 to 2023

Multidisciplinary designer and pastor

  • Multidisciplinary Designer and Pastor, Florida Conference of SDAsDec 2013 to Mar 2023

For nine years I was a pastor in Florida, and most of those hours went to making things. About ten websites and a check-in kiosk for the church lobby. Stage lighting: I bought and wired the fixtures and built the LightKey presets that ran each show. A rolling production rig for a church that set up and tore down every week. For SALT (an outreach to the unhoused) a food service trailer and the app its care days ran on. I founded its first satellite branch. And a lot of film.

The rest was customer experience and change management in disguise: working out how a nervous first-time visitor becomes part of a community, and helping teams through change they did not ask for.

Alex on a dim stage, speaking into a handheld microphone with a slide clicker in his other hand, a projected painting on the screen behind him.Hand sketch of a rolling cart: a mixing console on top with a camera on an arm above it, and labelled shelves for wireless transmitters, microphones and cables.The finished cart: a black rolling cabinet with a large digital mixing console set into its angled top.
Speaking at LifeSpring (photograph by Alex Angellakis). Below, the production rig I designed for a church that met in a rented hall: the sketch, then the thing itself.

Short-form video and social media

Reels became the best way to reach people, so I put real hours into them: about fifteen a week from 2020 to 2022. Recaps and invitations for SALT, artist features and announcements for the church. I ran the accounts and filmed, edited and produced about nine in ten of their posts.

What I did
  • Ran Instagram for LifeSpring and for SALT Outpost Tampa
  • Shot on Sony mirrorless and cut in Final Cut Pro: keying, motion tracking, colour grading and sound
  • A Christmas production for the church too: chroma keying, the graphics, and recording and mastering the music
Three of my reels. No sound.

SALT HMIS: a homeless management information system

SALT Outpost Tampa was an outreach to the unhoused. On a care day up to 60 guests and 30 volunteers shared one campus for showers, hot meals and clothes. Service was slow because every station did its data entry by hand on a clipboard. Guests waited in lines and no station could see what the others had done. I designed a custom database app that checked guests in, triaged what each one needed and put them in line. Every guest had a calmer visit and the volunteers moved people through faster.

What I did
  • Interviewed the eight station leads and turned what they needed into user stories, a site map and flows
  • Designed check-in, a record for every visit and live status at every station
  • Added a first-come shower queue after watching it run on a care day. Names were no longer called across the room and the tension over who was next went away
  • Chose AppSheet to keep it free for a nonprofit and directed a contract developer through the build
  • The Tampa Hillsborough Homelessness Coalition asked about scaling it up as the county’s official HMIS
SALT’s check-in screen on a phone, in dark mode: one guest’s visit on January 11, 2023, with Waiting, Not Needed and Received for food, showers, clothes and a supply pack. The guest’s name is blurred.
One guest’s visit, station by station. Name blurred.

Foundations: a six-part video series

I co-created a long-form web video series that teaches church doctrine through storytelling. Churches around the world have used it.

What I did
  • Co-creator and director
  • All of the videography and editing
  • The series website, its marketing, and coaching the scriptwriters
From Foundations, the series I directed and edited. No sound.

Physical product design: two rolling production carts

A church that met in a rented hall set up its sound, video and stage gear every week and tore it down again. I designed two carts to replace the folding tables and road cases. I took them all the way from measuring the gear to sketches and the build. I welded, built and painted the first one myself.

What I did
  • The A/V cart: measured, sketched, welded, built and painted. It saved about an hour of setup every week
  • The stage cart: sketched it with cable cubbies that plug straight into a stage box. Built it with our builder and our A/V lead. It cut setup by 45 minutes a week
  • Other live production techs asked for the plans and built their own
Three stages of the stage cart. My pencil sketch of a tall rolling cabinet with labelled cubbies for in-ear packs, XLR boxes, mics and cables. The welded black frame in a workshop, with its plywood cubbies going in. The finished cart backstage, cables running from its cubbies.
The stage cart: my sketch, the welded frame, the finished cart.

Two iPad kiosks for the lobby

I put two iPad kiosks in LifeSpring’s lobby and designed what ran on them. A first-time visitor could give, sign up for the newsletter, share a prayer request or offer to serve without having to ask anyone.

What I did
  • Chose the hardware: two 12.9-inch iPad Pros in lockable floor stands
  • Designed and built the small local website they ran, full screen in kiosk software
  • Pushed updates to both from a shared folder. Nobody had to touch the iPads
  • Made screens at the iPad’s own size for events and giving drives
Two kiosk screens photographed in the lobby. Welcome to LifeSpring, with buttons for Give, Get Our Newsletter, Share Your Prayer Request and Serve. A giving page: give on this kiosk, scan a QR code with your phone, or download the Church Center app.
The kiosk’s home page and its giving page, July 2019.

LifeSpring: a church of 80 grows past 160

I became lead pastor of LifeSpring. People found us on Google and tried us out on YouTube and Instagram before they ever walked in the door. I designed that whole path for a first-time visitor and what happened after it. The church grew from about 80 to more than 160.

What I did
  • Designed the journey from a first search to joining a team
  • Built the church’s website
  • Set up one system of graphics for the projectors, kiosks and newsletter. A design was made once and used everywhere
  • Moved giving to a single link with Apple Pay

2009 to 2014

Twelve iOS apps

  • iOS developer, Self-publishedMay 2009 to May 2014
  • iOS developer, web and graphic designer, Erhard Furniture and FlooringNov 2011 to Jan 2013

It started with Objective-C in 2009. Between 2011 and 2013 I built twelve apps under my own developer account and more for others. A 2D game was among them. Every screen, sprite and icon of my own apps was mine, which is probably where the habit of doing both jobs comes from.

For part of that time I also worked at Erhard Furniture and Flooring in Michigan: on the sales floor, and on their website, their print and digital ads, and an iPhone app that worked out how much flooring a room needs and what to charge for it.

One Place: an iPhone app for Andrews University

Andrews University’s web team brought me in to build an iPhone app for One Place, a service at the university. They did the visual design. I built it in Objective-C on the university’s developer account.

What I did
  • Built it in Objective-C to the web team’s visual design
  • Sermons from the podcast feed inside the app and a link to the live sermon in YouVersion
  • A live Twitter feed for #auoneplace, sharing to Twitter and Facebook, polls, a connect card and directions
  • Sent build 1.0 to testers through TestFlight in March 2013
Three iPhone screens from 2013 in a parchment and brown design: the One Place menu, an audio player playing a teaching, and a route on a map.
One Place in the iOS Simulator, March 2013.

Moses’ Meat Madness: a 2D game

A game for iPhone and then for iPad the next year. You drag Moses through the desert to collect the clean animals and dodge the unclean ones, with Leviticus 11 as the rulebook. I made the game and drew all of it: the sprites, the backgrounds and every state of every button.

What I did
  • Designed and built the game and drew all of its art
  • On the App Store for iPhone in May 2012 and for iPad in January 2013
Two screens from the game. Mid-game, Moses stands in a cartoon desert among pink pigs and a cow, with a score of 5. The instructions screen: touch and drag Moses, avoid the unclean animals, don’t touch the walls, Leviticus 11 is key, and collect clean animals for a time bonus.
The game running, then its instructions on the iPad.

Twelve apps under my own developer account

I started developing for iPhone in 2009, a year after the App Store opened. My first app went on sale in April 2011 and I kept shipping through 2013. I designed every icon and screen and wrote every line in Objective-C. I know the design looks dated now. I promise it was in keeping with the time.

What I did
  • Built twelve apps under my own account and put eleven of them on the App Store, from church tools to a game
  • Built for others too: One Place for Andrews University and a flooring estimator for Erhard Furniture and Flooring
  • Took up storyboards as soon as Xcode brought them in, because I like to see the prototype I am building
My App Store Connect account in January 2023, listing twelve apps with their icons: iHeatYourFace, Double Dream, two editions of Greatest Bible Adventures, iPluck, Hebrew Verbs, iPluckPrank, BushBoard, Church Count, Ellen White Answers, AdventistAlert and Today is Friday.
My App Store Connect account, January 2023.

Ask Alex

What would you like to see?

Type / for the kinds of work.