About BuiltWRKS

An operator's view of the whole system.

BuiltWRKS is an operations and systems consulting practice led by Harry Protopappas in Reno, Nevada. Harry works directly with each client from diagnosis through implementation and training.

The through line

Understand the experience. Make it repeatable. Train the team.

Harry brings 25 years of customer-facing work across field service, home automation, instruction, project management, aviation, lending, rentals, e-commerce, and supply chain. The titles changed. The job stayed recognizable: understand what the person needs, solve the operating problem behind it, and help others deliver the result consistently.

At LIFT Aircraft, Harry helped launch its pay-per-flight eVTOL experience. He led on-site flight operations, worked directly with customers, and converted frontline learning into SOPs and operating manuals for future locations.

That experience shaped BuiltWRKS. A process is not finished because it looks clean in a document. It is finished when the customer experience holds up and the team can run it without the consultant in the room.

Why the range matters

Business problems rarely stay in one department.

A customer issue may begin on the website, pass through the CRM, become an inventory question, and end as a training problem. BuiltWRKS follows the work across those boundaries.

Customer first

Begin with the need and the experience. Tools, specifications, and process support the promise; they do not replace it.

Build what is practical

Use the simplest system that can handle the real workflow, including its exceptions, owners, and review points.

Leave the team stronger

Document the method, train the users, and make ownership clear before the work is handed over.

Accountability

Harry leads every engagement.

When a project needs a specialist, Harry scopes and coordinates that support with the client's approval and remains accountable for the work.

  • One operating lead from discovery through handoff.
  • Clear scope before implementation begins.
  • Plain recommendations, including when not to build.
  • Documentation and training included in the work.

Start with the problem

What is harder than it should be?

Tell us where work stalls, where customers feel it, and what needs to happen instead.