Skip to content
Book
assessment · systems work

Find what is costing you time and margin, then fix it.

For owners who can name the problem area, or need it diagnosed, and want it fixed without an ongoing engagement. Start with an assessment, or go straight to a defined project on a workflow, report, or automation. Every piece of work ends with an owner on your team.

Discuss your operation ← How we work
this fits when

Signs this is the right path.

  • You know something is leaking time or money, but you cannot say which thing to fix first.
  • One workflow keeps breaking because it lives in a few people’s heads.
  • Reporting is “let me get back to you”: half a day of digging for one margin question.
  • Leads, job completions, or collections follow-up wait on someone remembering.
four kinds of work

Four kinds of focused work.

Each is scoped on its own. Most companies start with an assessment, or with the one problem they already know about.

Operations assessment

You need to know what to fix first.

Find the two or three constraints costing the owner time or hiding margin. You leave with a ranked plan, named owners, and a decision on what to fix first.

  • Interviews with the people doing the work, and read-only access to your tools
  • Written findings, ranked by impact and effort
  • A 90-day plan with owners and effort estimates
  • A tech-stack snapshot: what you pay for, what you use, what to cut
  • A walkthrough call on the findings

About two to three days of focused work, delivered roughly 10 business days from kickoff.

Workflow documentation

A recurring workflow depends on tribal knowledge.

Make one recurring workflow teachable and usable: define the handoffs, train the people doing the work, and assign someone to keep it current.

  • The workflow documented in your system of record (ClickUp, HubSpot, Notion, or similar)
  • A process map showing who triggers what and where the handoffs are
  • A short captioned training video
  • A rollout plan with an owner and a review date

Typically about two weeks per workflow.

Workflow automation

Follow-up waits on someone’s memory.

Stop leads, job completions, or collections follow-up from waiting on someone to remember. We pick the tool after we understand the workflow.

  • One workflow automated end to end, tested against your real data
  • Built on Zapier, n8n, or the native tools in your CRM or field software
  • Failure alerts to a named person, so it never breaks silently
  • A handoff guide for the office: how to check it and when to escalate
  • AI only where it holds up, with a person reviewing its output

Typically two to three weeks, including a week of monitoring after go-live.

Operating reporting

Nobody trusts the numbers.

Know each week whether jobs, margin, cash collection, and capacity are moving in the right direction, and who owns a miss.

  • One dashboard in Looker Studio, HubSpot, or the BI tool you already have
  • A written definition and source for every metric, so they stop drifting
  • Automatic refresh from your CRM, accounting, and field software, with the last update time shown
  • Alerts on the metrics you choose
  • Checked against last quarter’s actuals before handoff

Typically about two weeks.

responsibilities

Who does what.

Confirmed in the written scope before work starts.

Framework Ops owns

  • Diagnosis, design, build, and testing
  • Training the people who will use it
  • Handoff documentation and a named owner for each system
  • Telling you plainly when something should not be built or automated

You own

  • Access to the tools and people involved
  • A point person who can make decisions during the project
  • Choosing which priorities to act on
  • Running the system after handoff

Not included

  • Replacing your field software, CRM, or accounting system; we build on what you have
  • Rebuilding every workflow at once
  • Ongoing operating leadership; that is the fractional path
sequence

How it usually runs.

Each project is scoped and priced in writing before it starts.

  1. Discovery call

    Thirty minutes to agree on the problem and whether an assessment or a defined project comes first.

  2. Written scope

    What is in, what is out, the timeline, the fee, and who owns the result at the end.

  3. Assessment or build

    The diagnostic, the project, or both, with check-ins as it goes.

  4. Handoff

    Training, documentation, and the system handed to its owner on your team.

questions

Questions about this work.

Do I have to start with the assessment?

No. If the problem is already clear (one workflow, one report, one automation), we can scope that directly. The assessment is for when you know something is leaking but cannot name which thing first.

What if we take the assessment and do the work ourselves?

That is fine. The findings and the 90-day plan are written to stand on their own.

Do you replace ServiceTitan, JobNimbus, or HubSpot?

No. We build around them. The reason you bought them was right; the gaps between them and the rest of your stack are where the hours leak.

Zapier or n8n?

Zapier if your team needs to own it. n8n if the logic is branchy and someone on your side can maintain it. Sometimes the answer is the native integration, or not automating it at all. We make the call during scoping.

How is it priced?

Each project has a fixed fee, set in a written scope after the discovery call. We do not bill by the hour.

Will the reporting replace our QuickBooks reports?

No. It is the weekly operating view, not the financial close. The two complement each other.

Not quite this? The other path is fractional operations leadership.

See fractional operations leadership
next step

Bring the operational problem you cannot get off your desk.

In 30 minutes we will work out its likely cause, whether Framework Ops can help, and the right next step. Scope and fees follow that conversation, in writing.

A 30-minute video call with Chance Peare.

Book an operations call or email chance@frameworkopsllc.com →