Community
Include the people who perform, approve, receive, or are affected by the work so the solution respects stakeholders and fits the organization.
Operations consulting
I help early-stage ventures, small businesses, nonprofits, and programs understand an operating problem, design a practical response, and implement or test that response when the engagement calls for it.
How operations work is handled
Operations work succeeds only when the people involved can use it, the recommendation fits the evidence and authority available, and the engagement leaves behind a practical improvement. These values govern the diagnosis, design, setup, testing, and handoff.
Include the people who perform, approve, receive, or are affected by the work so the solution respects stakeholders and fits the organization.
Understand the operating circumstances and likely response to a change before recommending the scope, sequence, responsibility, or tool.
Remove practical barriers to effective work through a clearer decision, procedure, workflow, intake path, operating system, or tested process.
Scope limitations used across the service menu
Every engagement is limited to the stated processes, participants, materials, meetings, tools, test users, delivery period, and correction rounds. Added departments, audiences, workflows, features, historical-data migration, ongoing administration, or major changes to an approved process require a new or revised scope.
I do not provide legal, tax, audit, clinical, engineering, safety, licensed cybersecurity, HR-law, certification, or other regulated professional advice. I can organize client- or specialist-approved requirements into an operating process, but I do not create the underlying legal or licensed rule.
Custom software, complex integrations, enterprise technology selection, media spend, software fees, ongoing outreach, guaranteed sales or recruiting outcomes, and organization-wide change management are excluded unless a written scope specifically includes them.
Services and packages
The order shows how multiple packages can connect: needs analysis, workflow design, SOP documentation, setup and testing, specialized systems, and ongoing operations. You may start later in the path when reliable, approved work from the earlier stages already exists.
First identify the real need, then define the workflow, responsibilities, decisions, and handoffs.
A focused look at the operating problem, what is actually causing it, and a useful next action.
A focused look at the operating problem, what is actually causing it, and a useful next action. Decision-ready findings, a current-state view, and prioritized recommendations.
A leader knows that work is slow, unclear, inconsistent, or overly dependent on one person, but the right fix is not yet obvious.
The analysis of one clearly defined process, such as receiving a customer request, assigning a task, scheduling a program, approving a purchase, or following up after a sale.
A review of one business function made up of as many as three connected processes.
The same analysis method expanded to as many as five connected processes across teams, levels, or operating areas—for example sales → onboarding → service delivery → billing → follow-up.
Define who owns each action, what status means, how work moves, and when a decision must be escalated.
Define who owns each action, what status means, how work moves, and when a decision must be escalated. A future-state workflow, ownership rules, status definitions, and handoff requirements ready for documentation or setup.
Work repeatedly stalls between people, ownership is unclear, status is difficult to see, or exceptions have no reliable path.
Design one recurring start-to-finish process, such as receiving a request and assigning it, approving an expense, or preparing and sending a recurring report.
Design as many as three connected processes that share people or information.
Design as many as five connected processes involving up to ten distinct responsibilities across teams or operating areas.
Turn the approved design into usable procedures, then set it up, test it, and pilot it when selected.
Turn a real, existing process into instructions people can follow, update, and test without guesswork.
Turn a real, existing process into instructions people can follow, update, and test without guesswork. Clear steps, controls, exceptions, templates, and a maintenance path.
A recurring task works, but its steps live in memory, vary by person, or are difficult to teach and maintain.
Written instructions for one routine task that is already performed in one generally consistent way.
Instructions for as many as three connected recurring tasks, with no more than thirty major actions across the set.
A small operating manual containing as many as six related procedures for a team or operating area.
Set up an approved process, test it in the chosen tool, and—at the highest level—run a controlled pilot before handoff.
Set up an approved process, test it in the chosen tool, and—at the highest level—run a controlled pilot before handoff. A working setup, test evidence, clear corrections, and a practical handoff.
A workflow or operating design has already been approved, but the organization needs focused help configuring, testing, and handing it over.
Set up one already-approved process in one client-approved tool, such as a form, spreadsheet, folder system, template set, or basic task board.
Configure and test up to three approved connected processes using no more than two client-approved tools.
Configure and test up to five approved connected processes using no more than three client-approved tools, then run a controlled pilot with up to ten client-selected users.
Apply the approved process to intake and follow-up or to client-supplied compliance administration.
Design the path from first contact through information collection, qualification, acknowledgment, and handoff.
Design the path from first contact through information collection, qualification, acknowledgment, and handoff. A minimized-data form, messages, tracker fields, rules, and testable branches.
New clients, members, volunteers, or participants arrive through inconsistent channels and follow-up depends on memory.
Build one intake path for one defined group, such as prospective customers, members, volunteers, or program participants.
Build one intake system for one defined group arriving through as many as three routes—for example website form, referral, and direct email—and moving through up to two transfers, such as inquiry → qualification → assigned staff member.
Build an end-to-end intake and follow-up system for up to two defined groups, such as customers and referral partners or volunteers and participants.
Translate client-supplied requirements or adviser guidance into calendars, responsibilities, evidence structures, and reminders.
Translate client-supplied requirements or adviser guidance into calendars, responsibilities, evidence structures, and reminders. An administrative system to complete and prove the work—not legal advice or certification.
The organization already has requirements from an authority or adviser but lacks a repeatable way to assign, complete, and evidence the work.
Organize up to eight requirements that the client, regulator, funder, contract, or qualified adviser has already identified.
Organize up to twenty client-supplied requirements involving up to five people responsible for different actions.
Build and configure one administrative workspace for up to thirty-five client-supplied requirements.
Improve the recurring work behind sales, recruitment, nonprofit programs, and program delivery.
Build the operating system behind consistent outreach: audience, stages, qualification, follow-up, ownership, and measurement.
Build the operating system behind consistent outreach: audience, stages, qualification, follow-up, ownership, and measurement. A working pipeline, scripts, stage rules, and an evidence-based next test.
The offer or opportunity exists, but prospecting, recruiting, qualification, follow-up, or pipeline visibility is inconsistent.
Create a simple manual sales or recruitment process for one defined target group.
Build a repeatable pipeline for one defined target group in a client-approved spreadsheet or existing CRM.
Build and test a sales or recruitment system for up to two defined target groups.
Put the recurring cycle behind a program into a usable run system for participants, volunteers, records, and communications.
Put the recurring cycle behind a program into a usable run system for participants, volunteers, records, and communications. Schedules, role sheets, templates, exception routes, and measurable operating materials.
A nonprofit, community initiative, or recurring program relies on informal coordination and needs a dependable operating cycle.
Organize one event or short program cycle from preparation through completion.
Build the repeatable operating system for one ongoing program.
Create a detailed manual for up to two connected programs involving up to ten distinct responsibilities.
Bounded hourly support
Use hourly support for a defined advisory task, document review, research assignment, meeting, update to existing material, or limited implementation help that does not fit a package.
Operations Consulting inquiry
The form belongs to Operations Consulting. You do not need to diagnose the problem or know the package. If you selected a package button above, the service field will already be filled in.
Open the form in Google Forms ↗Looking for market research instead?