Client Acquisition Tools · Lakewood, Ohio
Operations platforms. Sales pipelines. Lead intelligence. Custom tools built from inside the business, not outside it.
Start a conversation →Who I am
My background is unusual: I started as a field technician, identified what was broken operationally, and built the platform to fix it — which the business then purchased, shifting my role from field work into systems administration and sales. I didn't apply for that position. I created it.
Before that, I managed production across a 140-person print operation — championing the tracking of labor and spoilage statistics that allowed the business to forecast accurately by real crew performance and waste patterns, not just machine limits. That data reached the boardroom.
I work at the intersection of business analysis, sales process, and custom software. I'm currently completing a BS in Computer Science at Auburn, having already earned a BBA from Kent State.
Technical skills
What I do
I work with businesses that have outgrown their tools — or never had the right ones to begin with.
01
Custom full-stack tools built around your workflow. Scheduling, job tracking, inventory, billing — all connected, all real-time, and designed to run without you holding it together.
02
Pipeline architecture, SOP-driven lead workflows, research frameworks, and activity tracking designed to convert — not just organize.
03
I run the same outreach sequences I build. Prospect research, structured follow-up, and pipeline management executed with discipline.
04
Before building anything, I map where time and money are leaking. I've done it from inside an operation — and that changes what I look for.
Selected work
The following case study reflects a real engagement — built, deployed, and actively used.
01 / Case Study
Commercial Flooring Contractor · Cleveland, Ohio
The problem
Scheduling ran on a fragmented mix of manual calendars, phone calls, and email threads. Every update required manual distribution. There was no single source of truth — field crews, billing, and management were each working from different information.
What was built
The result
The calendar became the company's single source of truth — replacing the patchwork entirely. Any administrator can manage it without touching code. Deliberately designed to be sustainable and future-proof, independent of the person who built it.
The problem
Sales activity was untracked and inconsistent. No structured outreach sequences, no research framework, no visibility into where prospects stood in the pipeline or what had already been attempted.
What was built
The result
Sales moved from informal and reactive to structured and repeatable. The same CRM that was built is the one actively used to manage the pipeline today — the system earns its own clients.
The problem
Equipment staging was manual and error-prone. Supply inventory had no automated awareness — items were over-purchased or missing, and locating supplies in the field was slow and unreliable.
What was built
The result
Manual prep coordination was eliminated. Over-purchasing stopped. Because every module shares the same data layer, adding inventory and equipment required no rearchitecting of what already worked.
Next Case Study
Details coming soon.
Get in touch
Phone
Portfolio
I typically respond within one business day. If you have a specific system, workflow, or acquisition problem in mind, mention it — it helps me come to the first conversation prepared.