Work in Practice

The shape of the work, without the case-study theatre.

These are high-level examples of the kinds of problems I help solve for solo operators, small businesses, and growing teams. The details vary, but the pattern is usually the same: something important is harder to run than it should be, and the systems around it need to get clearer.

Solo operator · Small business

Website, lead flow, scheduling, and systems cleanup

Making a small business easier to run behind the scenes

A solo operator had built their business across a custom domain, contact forms, multiple email accounts, calendars, and third-party tools that weren’t fully aligned. I helped simplify the setup so inquiries landed in the right place, calendars stayed in sync, and the business felt easier to trust day to day.

Fewer missed leads, fewer booking problems, and less manual checking between platforms.

Early-stage · Growth-stage SaaS

Internal systems, workflow, access, and process infrastructure

Clarifying the operational layer behind a growing company

As a company grows, important work often ends up split across spreadsheets, SaaS tools, internal docs, and people’s heads. I’ve worked in that layer across support, enterprise IT, and technical operations — improving the workflows, ownership, access patterns, and systems that keep the business moving behind the scenes.

Clearer workflows, less duplicated effort, and operations that feel more stable as the team scales.

Cross-functional internal operations

Process design across People Ops, Finance, RevOps, Support, and IT

Cleaning up the overlap between teams, tools, and responsibilities

Some of the hardest operational problems aren’t owned by one team. They sit in the gaps between departments — where tools overlap, handoffs break down, and responsibilities get fuzzy. I help make those edges clearer so people know what belongs to whom, where the work moves next, and how to coordinate without constant interpretation or follow-up.

Better handoffs, clearer ownership, and a business that feels easier for people to operate inside.

Automation and internal tooling

Practical automation, internal tools, and workflow support

Reducing repeated work without overbuilding the answer

I’ve built automation and lightweight internal tools to remove repeated operational work — from reminders and workflow support to internal apps and scripted processes. The goal isn’t automation for its own sake. It’s to reduce drag, support the people doing the work, and avoid creating a bigger system than the problem actually needs.

Less manual effort, more consistent execution, and tools that support the workflow instead of fighting it.

AI-supported operations

Internal support workflows, Slack agents, and bug-surfacing systems

Making support signals easier to catch early

I’m interested in AI where it helps teams work more clearly, not where it adds hype. One example is using an internal Slack-based agent to triage incoming issues, surface likely customer-reported bugs, and make support signals easier for the right people to act on before they disappear into chat noise.

Faster triage, better visibility into recurring problems, and less operational signal getting lost in the stream.

If one of these sounds familiar, we should probably talk.

The details are specific to the business, but the pattern is usually recognizable: a valuable workflow has outgrown the tools, handoffs, or ownership model holding it together.

Start a conversation