Getting real value from the CRM, field-service platform, project-management tool, or inventory system you already pay for.
How I Work
You bring the project.
You bring the project.
I carry it through.
Fokaos is operations consulting and implementation for owner-led construction companies, skilled trades, and small agencies. You don't buy a standardized system off a menu. You bring an operational project, constraint, or need — and I take ownership of designing, building, implementing, and stabilizing the solution around the way your business operates, working alongside the people who know it best.
Fokaos provides operations consulting based in Muskegon, Michigan — serving West Michigan and remote-first teams nationwide.
What I take on
Four kinds of work — not packages to choose from.
What ties these together isn't the problem type. It's the role: someone who comes inside the business, understands the day-to-day work, and carries the project through. For worked examples of each, see Project Examples.
Making the path between people dependable — sales to production, office to field, onboarding to delivery, approvals, and closeout.
Designing and standing up something that doesn't exist yet — an inventory program, an onboarding system, a new function.
Untangling data, processes, and software that years of growth have left messy — and making the fix hold.
Who I work with
Built for owner-led construction, trades, and agencies.
The problems rhyme across industries, but the details don't. Here's what the work looks like in each:
Sales-to-production handoffs, project-management software, and the systems that keep jobs off your desk.
Explore →Field-service software, dispatch, and technician workflows that finally act like one system.
Explore →Client onboarding and delivery systems so work stops routing through the owner.
Explore →Local operations consulting for owner-led businesses across West Michigan — and remote.
Explore →
What stays the same
If everything is custom, the method is what you're hiring.
Six steps, every engagement. Understanding happens inside the work — proportional to what we need to know to solve the problem responsibly, not a product you have to buy before we begin.
Understand
Get close enough to the day-to-day work to see what's happening now.
Define
Agree on what Fokaos is solving, what success looks like, and where the boundaries are.
Design
Build the solution around the business in front of us — not a prebuilt framework.
Implement
Put it into operation with the people who will use it.
Test
See what holds up in practice and adjust what doesn't.
Stabilize
Document, train, clarify ownership, and make sure the solution survives without Fokaos holding it together.
How working together works
What an engagement looks like.
The specifics change with the project. This is the shape most engagements follow.
What happens first?
A 20-minute intro conversation — what's happening, what you already know, and what you want to be different. If it's clear enough to scope responsibly, we move toward a proposal.
When is discovery paid?
Only when meaningful unknowns make direct scoping irresponsible — unclear constraints, competing options, or a current state nobody fully understands. If the need is already clear, we skip it.
What does Fokaos own?
Project architecture, design, coordination, implementation leadership, and stabilization. I stay through to a working, documented result — not a recommendation handed over at the door.
What does your team own?
Domain expertise, internal approvals, and the authority to make decisions inside your business. You bring what only you know; I bring the structure and implementation. We build it together.
Can we keep our existing systems?
Usually, yes. Replacement isn't assumed. Most projects are about getting more out of the software and tools you already have, not adding new ones for their own sake.
How long does a project take?
It depends on scope — from a few focused weeks to a phased build over months. We set expected ranges during scoping so there are no open-ended surprises.
How are changes handled?
Through a simple scope and change process. New requests get named, sized, and agreed — rather than quietly absorbed until the project loses its shape.
What happens after launch?
Pilot, adjust with the team, train, document, and clarify ownership — so the new way of working holds up in day-to-day use instead of unraveling once attention moves on.
Will you stay forever?
No. The goal is a solution your team can maintain without me. Ongoing support is available if you want it, but it's never a dependency I build in on purpose.
How is sensitive information handled?
Client operations, internal challenges, and project details stay private unless you've explicitly given permission to share them. The work often touches parts of a business that aren't polished yet; I treat that access accordingly.
Scope & investment
Priced to the project, not a menu.
Every engagement is scoped to the work. Some projects are a few thousand dollars; others are substantial builds. We figure out which yours is together — based on what it requires, after I understand it well enough to scope it responsibly.
No fixed package, no diagnosis you're required to buy first. Just the work in front of us and an honest scope.
Start with what you already know
You don't pay me to rediscover a problem you already understand.
If you can tell me what needs attention, what's happening now, and what you want to be different, that's often enough to begin scoping the work.
Sometimes the project still holds meaningful unknowns — technical constraints, system limits, unclear ownership, competing options, or a current state nobody fully understands. In that case, I may recommend a short paid discovery phase before either of us commits to a larger build.
The principle
Clarity before commitment.
Discovery is used when the uncertainty is material — not as a tollbooth every client has to pass through.
If we can responsibly define the project without it, we will.
A quiet note on trust
The work often brings me into parts of a business that aren't polished yet. I treat that access accordingly. Client operations, internal challenges, and project details stay private unless I've been explicitly given permission to share them.
Common questions
Quick answers
How do I know if my project is a fit?+
If there's an operational thing your business needs built, fixed, or working — a software rollout, an inventory program, a sales-to-production handoff, a CRM cleanup — it's likely a fit. You don't need to diagnose it perfectly or pick a service off a menu. Bring it and we scope it together.
How much does an engagement cost?+
Every engagement is scoped to the work. Some projects are a few thousand dollars; others are substantial builds. We figure out which yours is together, based on what it requires — not a fixed package.
When is a paid discovery phase needed?+
Only when the project holds enough uncertainty that quoting the build immediately would be irresponsible — unclear technical constraints, competing options, or a current state nobody fully understands. If the need is already clear, we move straight into scope and proposal.
What do I walk away with?+
A working solution — designed around your business, put into operation with the people who use it, tested in day-to-day use, and stabilized so it can survive without Fokaos holding it together. Documentation, training, and clear ownership are part of the finish.
What kinds of businesses does Fokaos work with?+
Owner-led construction companies, skilled trades, and small agencies. The best fit isn't about headcount — it's when capable people are already doing the work but a defined operational project needs more ownership, structure, or implementation capacity than the team currently has available.
Have a project that's been waiting for an owner?
You don't need to arrive with the solution designed. Bring the operational project, constraint, or mess — and we'll figure out the most useful way to take it on.
Talk Through a Project