Operations consulting for agencies and service-based businesses

Email on your own domain, shared drives that make sense, calendars that actually connect — Google Workspace is the backbone most small organizations are running badly or not at all. I set it up correctly from the start: accounts, groups, permissions, and the security settings that usually get skipped.

If you're already somewhere else — old Gmail accounts, Outlook, whatever your registrar bundled in — I migrate everything over without losing a message, a contact, or a calendar invite.

And after launch, it's managed. People join, people leave, questions come up — that's mine to handle, not another thing on your plate.

Email is where decisions go to get buried. Somebody forks the thread, somebody drops off the cc line, and three weeks later nobody can find what was agreed. Slack fixes that — when it's set up deliberately.

I build the workspace around how your team actually works: a channel structure that maps to your real projects, integrations with your calendar and files, and notification defaults that don't drive everyone insane.

Then I write down the norms — what goes where, what deserves a channel, what still belongs in email — so the tool sticks instead of becoming one more inbox.

Every team says the same thing: we don't know what's due, who owns it, or whether it's done. A project system fixes that — but only if it's built around your actual workflow instead of somebody else's template.

I'm tool-agnostic. Notion, Asana, Trello, ClickUp — the right answer depends on how your work flows, and I've built on all of them. I set up the boards, the ownership, the statuses, the recurring work, and the templates.

Then I roll it out with your team and document how it runs, so it survives past the first two weeks of enthusiasm.

Custom sites, written from scratch — no templates, no page builders, no monthly platform hostage fee. Just fast, clean code that reflects the quality of your work.

I handle the whole arc: structure, copy shaping, design, build, and launch. You review real pages as they come together, not wireframe abstractions.

And once it's live, I maintain it. Need a change? Send an email. No CMS to learn, no training videos, no “quick call” with an agency.

Sometimes the tool you need simply doesn't exist: your registration system needs to talk to your website, your intake process needs a portal, your team runs a workflow no off-the-shelf product touches.

I design and build custom web applications that connect the systems you already use and automate the work between them. The Park Avenue platform in the case study — eight live integrations, a full admin back office — is exactly this service.

One experienced person, a flat scoped price, and a fraction of what an agency would bill for the same build.

DNS is the plumbing nobody thinks about until email stops landing or the site stops loading. Records rot, registrations lapse, and the person who set it all up left three years ago.

I take it over cleanly: consolidate your domains, fix the records, set up the email authentication (SPF, DKIM, DMARC) that keeps you out of spam folders, and document everything.

Then I keep it renewed and correct. You never think about it again — which is the entire point.

Most operational pain isn't a tool problem — it's a process problem wearing a tool costume. Work stalls at the same handoffs, data gets entered twice, and one person quietly holds the whole thing together.

I map how the work actually flows — not the org-chart version, the real one — and find where it breaks. Then I rebuild it: fewer handoffs, automation where it's earned, and clear ownership at every step.

Everything gets documented and handed off. The goal is a process that runs without you standing next to it.

Not chatbots. Not party tricks. Working agents that take real tasks off your team's plate — drafting the routine responses, categorizing the intake, moving data between systems that used to require a human ferry.

I start by finding the repetitive work that's eating hours, then automate it with guardrails: human review where judgment matters, full automation where it doesn't.

It builds on the tools you already run, so it feels less like adopting AI and more like the busywork quietly disappearing.

Thirty-five years of professional design practice behind every mark, layout, and system — including two decades running one of the industry's most respected design agencies.

Logos and identity, brand systems, decks that don't embarrass you in the room, one-pagers, templates your team can actually use without breaking them.

You get real files, organized and handed off properly, plus the rules for using them — so the brand stays coherent long after I'm done.

The newsletter that actually goes out is worth ten that were planned. I set up the platform, the templates, and the list so staying in front of your clients becomes routine instead of a quarterly guilt spiral.

That includes the technical part almost everyone skips: domain authentication, so your email reaches inboxes instead of spam folders.

Signups, segments, and the automations that make sense for your business — welcome sequences, reminders, follow-ups — wired in and documented.

This is the customer-facing side of getting paid: how you accept cards, take deposits, send invoices, and run recurring billing — set up so paying you is the easiest part of working with you.

I also build the follow-up workflow, because the real leak isn't the processing fee — it's the invoice that sits unpaid for sixty days because nobody chased it.

Everything connects to your bookkeeping, so getting paid and recording it aren't two separate jobs.

The financial system of record behind everything else, built on Xero — my preferred platform. I set up your chart of accounts around how your business actually earns and spends, not a generic template.

Bank feeds, bill pay, and payment platforms all connect, so your books reconcile themselves instead of living in your memory and a shoebox of receipts.

When it's done, you — and your accountant — get clean books and a system that stays clean. Tax season stops being archaeology.

Paying people is the one operational task with zero tolerance for “oops.” I get you running on Gusto: employees and contractors, tax withholding and filings, direct deposit — configured correctly the first time.

It connects to your bookkeeping so every payroll run books itself, and it runs on schedule without you re-learning the system every cycle.

Most CRMs get set up in a hurry during a slow week and never get touched again. Fields go unused, stages don't match how deals actually move, and half the pipeline is stale data nobody's cleaned out in a year.

I set it up the way it should have been from the start: stages that reflect your real sales process, required fields that actually get filled in, and automations that route leads and follow-ups without someone having to remember to do it manually.

If you're migrating from spreadsheets or switching platforms, I handle the migration too, so you're not starting from zero or dragging bad data into a clean system.

A good hire can go sideways fast if the first two weeks are disorganized. No clear process, no documentation, nobody assigned to actually walk them through how things work.

I set up the HRIS system that runs the administrative side, cleanly, correctly, and connected to payroll. Then I build the actual hiring and onboarding workflow: job postings, candidate tracking, offer letters, and a first-week plan that doesn't rely on someone's memory.

The result is a process that works whether you're hiring your second employee or your twentieth.

Most scoping happens too fast, based on assumptions nobody checked. A brief gets read, a proposal gets written, and three months later everyone realizes they had different pictures of what "redesign" or "platform migration" actually meant.

I run project definition as its own phase: stakeholder interviews to find out what success actually looks like, a roadmap that breaks the work into estimable pieces, and a workshop where both sides reconcile any remaining gaps before committing to budget or timeline.

What comes out is a scope document both sides helped build and both sides trust, which makes the rest of the engagement, and the eventual SOW, dramatically less likely to blow up.

Utilization looks like a simple number until you ask what counts as available time and what counts as billable work. Most tools get both wrong by default, which means the dashboard is lying to you in a way that feels authoritative.

I audit how time is actually being logged, find where untracked work is disappearing, and get to a number you can actually manage against. Then I fix the resource planning that depends on it, so staffing decisions are based on real capacity instead of gut feel or whoever's least busy this week.

This usually surfaces margin leakage nobody had a name for until someone looked at the whole picture at once.

Every business has at least one process that lives entirely in someone's head. It works until that person is out, or busy, or gone, and then nobody can run it.

I sit with how the work actually happens, not how it's described in a meeting, and write it down properly: the steps, the exceptions, the judgment calls that usually go unspoken. The result is documentation someone else could actually follow.

This matters most during hiring, during a busy stretch, or any time you need the business to keep running without you personally holding it together.

A report that was accurate when it was built two years ago is often wrong now, not because anyone broke it, but because the business changed and the report didn't. Nobody revisits a dashboard that still loads and still shows a number.

I go through what you're actually tracking, check it against what's really happening, and find where the two have drifted apart. Sometimes the fix is a formula. Sometimes it's realizing the metric was never the right one to track in the first place.

You end up with fewer reports, but ones you can actually trust.