Loading…
Loading…
About · Chippewa Valley, Wisconsin
I've been the person inside the business who had to make the tools actually work — not the agency strategist who disappears after the deck.
The value isn't just the code. It's understanding how operations, marketing, CRM, and websites connect when nobody else has the time to own the seams between them.
Day job
Outside engagements are disclosed to and approved by my employer. The day job — leading technology and marketing for a wealth management firm — is where most of what I know was learned, so it stays in the picture rather than hidden.

Services
Story below. Offer first — so you know what I actually take on.
Stop copying data between tools, building reports by hand, or chasing paperwork that should run itself.
More on automation →
A site that shows what you do, makes it easy to contact you or book, and helps you win the next customer — I handle the build; you can stay hands-off or learn light updates later if you want.
More on web design →
Figure out what's working on the site you already have — and make real changes, not a PDF that sits in a Drive folder.
More on web consulting →
Clean up the CRM so it matches how you actually sell — fewer duplicates, clearer stages, less busywork for the team.
More on CRM →
The story
The shortest version: I started in IT through an internship at a telecom company while I was studying at Chippewa Valley Technical College in Eau Claire. The work itself was fine — the management wasn't a fit, and I didn't see a future there worth staying for. About a year in, I landed at a wealth management firm and felt the difference immediately: independence, the ability to make decisions on my own, room to figure things out without asking permission for every move. I've been there ever since, now running technology and marketing for the firm.
Most of what I know about scoping work, talking to non-technical stakeholders, building things that don't fall over, and finishing projects that actually get used — I learned there. The day job has been a faster and deeper education than school was, and some of the projects I've owned are the largest I'll ever touch.
The outside work started recently. I went back for a four-year degree, and the program included a capstone: build a website for a small business that was just getting started. The scope grew — full stack, social strategy, runbooks, the whole picture — and about six weeks before the class ended, the client asked if I'd stay on as a paid consultant. That was the moment this stopped being another idea and started being a thing I was actually building.
The family piece is part of it too. Multi-generational small business owners on both sides — a shoe store, an HVAC company, a shop that builds ambulances. The instinct to own something has been around me my whole life. I'd have regrets if I never tried it. So here we are.
And if it doesn't work, that's on me. I'd rather try and find out than spend the rest of my life wondering.
The roles behind it
Financial services is where I learned what breaks when tools, marketing, and operations pretend they're disconnected.
Wealth management firm — 2025 to present
Lead technology and marketing across the firm: Salesforce, DocuSign, Orion, WordPress, cybersecurity, vendor management, and marketing operations. Day-to-day spans vendor sites, growth measurement (GA4, Search Console), Salesforce administration, and product-style web projects run as separate workstreams.
Wealth management firm — 2022 to 2025
Supported operations across Active Directory, storage, phone systems, and helpdesk. Built Salesforce automations, API integrations, document pipelines, and analytics tooling so marketing and IT could trust the same numbers and stop doing manual glue work.
WIN Technology — 2019 to 2022
Maintained enterprise network infrastructure — routers, switches, SONET/DWDM/IP equipment — plus Linux and Windows server environments. Ran monitoring and support across multiple platforms.
Client lens
What you get when the builder has sat in the operations seat — not just the vendor portal.
I have been the person filing the ticket and the person clearing the queue. That makes scope conversations honest — and estimates grounded in how firms actually move.
Leads do not break in one tool; they break in the handoff. I map attribution, forms, routing, and reporting together so fixes stick after launch.
Sites and automations that do the job. Stay hands-off if you want me on updates, or get a short handoff if you'd rather own light changes later.
Engagements are scoped to a written plan: what's included, what “done” means, and what you own afterward. If the fit is wrong, I say so early.
Proof
Representative projects — each links to a full write-up with what was built and what changed.
One Drop Refillery
Wix + Square site for a local shop — clear storefront, orders and events, search and tracking from launch.
→ Live site that matches the business and gives visitors a next step.
Full write-up →A lightweight CRM I built for my own consulting work — clients, pipeline, tasks, time, and invoices without enterprise bloat.
→ Private beta live; the tool I use day to day.
Full write-up →Ads leads were stuck in one tool while sales waited on typing. Automated the handoff into Salesforce in seconds.
→ Lead capture under 30 seconds, fully automated.
Full write-up →Tracking and reporting so spend decisions rest on which channels produce clients — not vanity clicks.
→ Campaign-level ROI visibility; quieter channels that didn’t pay were cut.
Full write-up →Contracts and forms generated, sent, and filed on a path that doesn’t need babysitting for the standard case.
→ Standard path runs without manual intervention; exceptions surface cleanly.
Full write-up →High-volume document recovery, generation, and e-signature routing — including work on custodian transitions and similar ops-heavy projects.
→ Proof I can handle hard, high-volume automation when the job calls for it.
Full write-up →Want the lanes instead? Browse services — automation, web design, web consulting, and CRM.
Engagement shape
Clear scope — a written plan for what's included, what “done” means, and what you will own after handoff.
Same-day replies when something is blocking you during active work — not a slogan, an operating rule.
No jargon walls — plain language in scoping, documentation, and handoff.
Handoff your way — stay hands-off with me on updates, or get notes/runbooks when you want to own light changes.
Tools
Not a résumé dump — the tools where I have real production mileage.
Off the clock: hunting, fishing, lifting, and road time with family. Quiet outdoor days are where messy integrations usually sort themselves in my head — and a big part of why I keep the client list small enough to finish work well.
Send a short note about what you need — website, CRM, automation, or analytics. Prefer to talk? Book fifteen minutes.