About

Jake maps the work and builds the software.

Jake works with the people closest to your operation to map it, prototype one core workflow, measure what changes in real use, and expand what works.

Jake Lawlor, founder of Lawlor Solutions
Jake LawlorFounder, Lawlor Solutions

10+ yearsbuilding software

60+ projectsdelivered

One weekfirst working prototype

Utahfounded & headquartered

The person you meet stays accountable for the work.

Jake founded Lawlor Solutions to keep product thinking, engineering decisions, and client communication close together. The company was founded and is headquartered in Utah.

For more than a decade, Jake has worked across product strategy, design, engineering, mobile applications, integrations, and the operational details that decide whether software gets used.

Jake leads discovery, prototyping, scope, and delivery. When a build needs additional design or engineering capacity, a small U.S.-based team joins the work while Jake remains responsible for the result.

“I like finding the point where work gets harder than it should be and building the thing that makes it simpler.”
01

Understand the work first

Jake starts with the workflow, the people doing it, and the point where the current process becomes harder than it should be.

02

Make one workflow tangible

The most important workflow becomes a working prototype so the team can measure what improves before a full production build.

03

Measure before expanding

The people closest to the work use the prototype against an agreed result, such as time saved, fewer handoffs, clearer decisions, improved service, or new capacity. What they learn shapes the full build.

Custom software should earn its place.

We do not ask you to fund the whole system from a conversation or a requirements document. We first understand the operation, build one useful workflow, and measure whether it creates enough improvement to expand.

01

Map the operation

Understand the people, decisions, tools, exceptions, and handoffs behind the work before deciding what software should do.

02

Prototype one complete workflow

Put the smallest useful version of that workflow into the hands of the people who understand it best.

03

Measure, then expand

Observe what becomes faster, clearer, or easier, then use that evidence to define what belongs in the full system.

Build software around your business, not the other way around.

Bring Jake the workflow you want to improve. Together, we'll map how it works, turn the core into a focused prototype, and measure the impact before expanding it into a fixed-price build you own.

DirectWork with Jake

One weekWorking prototype

ClearFixed price before build

OwnedYour code and IP