Case studies

Most owners don't need more ideas. They need the step between the idea and work that happens the same way every time: who owns it, what comes first, what it depends on, and how anyone will know it's done. That step is what we build together.

Along the way the work produces SOPs, project plans, role design, technology rollouts and vendor coordination. Those are outputs, not the point.

From owner idea to a system that runs

This is a composite from several projects, because it's the same story every time. An owner says "let's do this." Staff start moving before anyone has defined what "this" is. Work gets done twice, or not at all.

The fix is answering a short list of questions before anyone starts. Take "let's start tax-planning meetings." Before the first meeting was scheduled: which clients, which advisor owns each one, meeting format and length, software access, the reports needed, who preps, what the client takes home, and where it gets documented.

1. Objective: What does done look like, in a sentence anyone can repeat?

2. Owner: One name per piece, including the pieces between people.

3. Dependencies: What has to be true first: access, data, vendors, decisions.

4. Sequence: What happens in what order, so daily work keeps running.

5. Workflow: The repeatable steps, written so a new hire could follow them.

6. Deadline and follow-up: Dates, check-ins, and a record of what was decided.

Seven times the path didn't exist yet

The first comes from my years in restaurant operations. The rest happened inside a growing professional services firm with a bookkeeping and tax operation. No names. Work still underway is marked, and results get added when they're real.

Staffing a restaurant in a college town

Completed. Workforce design, labor cost.

Opening a new high-volume restaurant in a college town meant the problem every college-town business has: seasonal swings, students leaving for breaks or other jobs right when they're needed most, and payroll all over the place.

What I did

• Stopped trying to hire the "right" number of people and over-hired on purpose, starting each new hire at 15 hours or less

• Set expectations on day one: hours may or may not be available, and you commit to showing up when we're open, including breaks and holidays

• Kept a target headcount for early, mid and late shifts, with the biggest pool on late availability

• Kept a few people who worked one day a week or one day a month to fill the gaps nobody else could

• Built a call-out list for last-minute absences

• Never stopped hiring, so the next layer was already in place when strong people graduated and moved on

Result: The model carried the store for three years. After a rough first year and a season of adjustments, the strong employees rose into good hours and leadership. The store ran well when I wasn't there, transitions were planned instead of reacted to, and payroll tracked the business instead of swinging past it.

The second office

In progress. Owner representation, cost control.

The owner decided to open a second location, about a $500K project. The architect, contractor, IT, security, furniture vendors, compliance and staff each owned a piece. Nobody owned the places where those pieces meet.

What I did

• Served as the owner-side coordinator across every vendor

• Kept a decision trail, and caught items that were agreed out loud but never made it into the drawings

• Challenged a proposed cut through the concrete slab for floor wiring, about $10K, and worked out alternatives with IT and the contractor

• Planned the office to be ready for people, not just finished construction: network, wireless, phones, security, access, signage, furniture and regulated-office requirements

So far: 33 network drops planned, 3 wireless access points, about $10K in cost challenged. Final budget against plan and opening date get added at opening.

Technology that actually gets used

In progress. Change management, workflow design.

The firm had access to a set of new tools. Turning them all on at once would have meant everyone using them differently, or not at all.

What I did

• Phased the rollout: scheduling, AI meeting summaries, CRM tools, email tools and mobile, each with training and testing

• Mapped the firm's core client processes into CRM workflows with triggers, owners, tasks, due dates and completion points

• Replaced everyone's personal scheduling tools with one firm standard: shared links, appointment types, booking windows and buffers

• Redesigned client identity verification so staff knew which method to use in which situation, with worked examples and training

• Gave each tool a named internal owner

So far: 11 client workflows mapped. Adoption by tool gets added once the rollout phases close.

Building the back office for growth

Completed. Organizational design, onboarding.

New staff, a new advisor, a second office, a technology rollout and compliance changes all landed at the same time, while the firm still had to serve clients every day.

What I did

• Sequenced the projects so daily work kept running

• Built onboarding plans covering day one, technology, training, payroll, benefits, responsibilities and follow-up

• Looked at workload, coverage and workflow before treating headcount as the answer

• Designed a part-time role around the actual work (phone coverage, rollout support, office tasks) instead of a generic job description

• Built an internship model that adds capacity instead of management load

• Moved phone lines, verification texts and shared inboxes off individual employees and onto firm-owned accounts

What it shows: Growth adds work in the gaps between roles. The fix is designing those gaps on purpose, not adding miscellaneous duties to whoever is closest.

Building a distributed operations team

In progress. Distributed operations, delegation.

A U.S. bookkeeping and tax operation needed its overseas production team to work as one operating system, not a group of remote workers waiting on the U.S. side.

What I did

• Built the operating cycle: onboarding, access, diagnostic review, cleanup and catch-up, recurring production, review, escalation and handoffs

• Replaced permanent U.S. account management with a warm handoff to the overseas team, with the U.S. side handling true escalations only

• Designed the move toward overseas team leadership, with outside HR, payroll and compliance support and U.S. oversight

What it shows: Offshoring doesn't have to mean losing control. Control comes from the structure, not from one person staying in the middle of every account.

Productizing a professional service

Completed. Service design, quality control.

"We do bookkeeping and tax" isn't a model you can scale. It wasn't clear who owned the customer, the work, the review, the communication, the filing or the liability.

What I did

• Defined a white-label model: the partner firm owns the relationship, communication, billing and final review, and the production team prepares returns behind the scenes

• Separated a partner channel from a direct-to-business channel, each with its own onboarding and pricing

• Turned bookkeeping into a repeatable cycle: onboarding, diagnostic, cleanup, monthly work, review, escalation and handoff

• Built quality control around credentialed review, escalation and knowledge transfer

• Built a pricing model running from delivery cost to client quote

Result: An outside reviewer's feedback on completed returns was favorable.

Stopping operational noise

Completed. Strategic simplification.

A referral channel brought inconsistent volume and prospects who stopped responding, and it took attention from work that paid. The easy path was to keep going because "we already started it."

What I did

• Set cutoff dates and stopped accepting new referrals

• Documented every open contact and closed abandoned files

• Wrote clear rules for leads that kept arriving after the firm had withdrawn

• Pushed to have the integration shut off at the source

What it shows: Ending something well is an operational skill too. A clean exit protects the team's time and the firm's reputation.

Field notes: smaller problems, same approach

• A client event for about 305 people. Vendors, compliance review, communication and day-of execution.

• Replacing equipment without going offline. Staged the swap so the office never went down all at once.

• Absence and capacity analysis. Looked at the real coverage picture before deciding anything about staffing.

• Handbook and process updates. Turned dense policy into grids, scenarios and decision points people actually use.

• Pay and benefits onboarding. Made compensation and benefits setup part of the onboarding plan, not an afterthought.

• Vendor selection and management. Picked vendors against defined needs, then kept ownership of the relationship clear.

• Website, staff profiles and video. Coordinated photos, bios and video so new hires showed up publicly on day one.

• Office maintenance and repairs. Gave building issues an owner and a vendor path so they stopped landing on whoever noticed.

• Compliance people can use. Converted requirements into training points and procedures staff can follow in real situations.

Have an idea that hasn't turned into a system yet?

The first conversation is free. Thirty minutes on where you want the business to go and what's missing between here and there. Let's talk.