The First Application I Built: Appliance Pros, Paper to Platform

More than 10 years ago, before LaunchThat and before I was shipping modern TypeScript systems, I built my first real application for a service company in Tallahassee.

At the time I was in college for computer engineering. I had planned that path since high school. But this project changed what I believed I wanted to build, and who I wanted to build it for.

The business problem

I was managing Appliance Pros of Tallahassee, running day-to-day operations for five technicians and helping train new hires.

The workflow was almost entirely paper:

• Daily schedules printed each morning
• Job details written by hand
• Parts requests sent through phone calls and manual notes
• Field notes dropped off at the end of the day

It broke constantly in the real world. Papers got wet from rain or appliance leaks. Handwriting was unreadable. Notes got lost in trucks. Office processing created delays before anyone could update customers, bookkeeping, or ordering decisions.

The business could only move as fast as the paperwork moved.

Building the app

I built a WordPress-based Service Tech application that drivers could use directly from their phones and tablets.

Core capabilities included:

• Daily scheduling with technician-level assignments
• Job details and history available in the field
• Structured technician notes and updates
• Parts ordering workflows tied to active jobs
• Internal training and documentation for common appliances and failures

What mattered was not just replacing paper with digital forms. It was making operations legible and connected across field techs, office coordination, suppliers, and customers.

Measurable outcomes

Once the team adopted the app, the company performance changed quickly:

• We handled roughly 2x the jobs with the same staffing
• Wrong-part ordering dropped after integrating ordering and bookkeeping flows
• Average cost per part dropped by about 15% by comparing and routing orders across multiple suppliers
• Customers received daily email updates for the first time, which improved satisfaction and reduced inbound status calls

For the first time, operations were consistent enough to scale.

The personal turning point

This was the first time I experienced software as a direct business multiplier, not just a technical exercise.

The gains in efficiency and the bonus structure tied to those gains were producing income that felt comparable to a full-time salary while I was still in college. I watched software create measurable leverage in a traditional local business, and it fundamentally changed how I thought about my future.

I had spent years aiming to become a computer engineer. But after this project, I shifted toward entrepreneurship, business, and economics with a focus on building digital systems that solve owner-level operational problems.

What came next

The work at Appliance Pros directly led to my next chapter: partnering with a high-school friend to build Virtue Motorsports.

At Virtue, I built a similar operations and inventory system for car part distribution. That system helped us scale to $1M+/year in sales, manage a very large SKU catalog, and maintain competitive pricing while keeping margins healthy.

That progression also shaped what I did after graduation. I immediately started my digital agency, LaunchThatBrand, and began building products for our own businesses and side ventures.

Looking back, this "first app" was not just a college project. It was the blueprint for everything after it:

• Build software close to the workflow
• Measure business outcomes, not feature counts
• Use systems to create leverage for small and mid-sized operators

That pattern still drives how I build today.