Skip to content
fractional coo · for contractors

Get your contracting company running without every decision coming back to you.

Framework Ops works with growing contractors to fix handoffs, make job and financial performance visible, document critical work, and give managers a cadence they can run. Led by a former roofing COO.

30 minutes with Chance Peare, founder and fractional COO.

sound familiar

When the business still runs through the owner, it looks like this.

These are the problems we are brought in for. If two or more describe your week, the call will be worth your time.

  1. Margin shows up too late

    You find out a job lost money weeks after it closed, when the books catch up.

  2. Handoffs live in one person’s head

    Sold to scheduled, completed to invoiced: it works because someone remembers. When they are out, it stops.

  3. The numbers disagree

    Sales, production, and accounting each have a number for the same thing, and none of them match.

  4. Meetings make lists, not owners

    The leadership meeting ends with action items. Next week starts with the same ones.

  5. Everything still comes back to you

    Pricing questions, customer problems, scheduling conflicts: you are still the escalation path for all of it.

  6. That is the work we take on.

    See how we work
proof

What you can check before you book.

Client results are published here only with the client’s permission and the numbers behind them. Three things are open to inspection today.

  • Sample data · fictional company

    Five working sample tools

    Built on sample data for Northside Roofing Co., a fictional roofing company. They show what an owner should be able to see and act on each week. They are not a client result.

  • The operator

    Chance Peare, former roofing COO

    Before founding Framework Ops, Chance was COO of a founder-led roofing company and worked through the same problems this site describes. His background is public.

  • The method, in writing

    How an engagement runs, published

    The sequence, who owns which decisions, what is not included, and who this is not for are all written down before you book. If something is missing, ask on the call.

how an engagement runs

The first 30 to 90 days.

An example of how the first 30 to 90 days usually run. Actual timing depends on what the diagnosis finds, and it is set in writing before work starts.

  1. 01 · 30 minutes

    Discovery call

    Your bottleneck, how work moves through the business today, and whether we can help.

  2. 02 · First weeks

    Diagnosis

    Interviews with the people doing the work, a look inside your systems, and a ranked list of the constraints that matter.

  3. 03 · Agreed together

    Priority plan

    Two or three priorities for the next 90 days, each with an owner on your team.

  4. 04 · Ongoing

    Implementation

    We build the workflows, reporting, and automations alongside your managers.

  5. 05 · Every week

    Weekly operating review

    A standing review of the numbers and the priorities, so follow-through does not depend on you.

  6. 06 · When it holds

    Hand off or continue

    Your team owns it, or we stay on in a defined operating role.

where the work happens

Four areas, each tied to a question you should be able to answer.

  • Job costing and reporting

    Which jobs, crews, and job types make money, and do we know before the month closes?

    Metric definitions written down, sources connected, and a weekly view your managers can run from.

  • Roles and accountability

    Who owns each number and each handoff, and what happens when one slips?

    Clear owners, a weekly operating review, and priorities that carry from one meeting to the next.

  • Workflows and SOPs

    Could a new hire do this without asking the one person who knows?

    The workflows that matter, documented in the system your team already uses, with a person responsible for keeping them current.

  • Practical automation

    Which follow-ups, reminders, and updates are waiting on someone’s memory?

    Automations that alert someone when they fail. AI only where it holds up, with a person reviewing what it does.

fit

Who this is for, and who it is not.

The work only holds when the owner gives it access, decisions, and an internal owner. Better to know that before the call.

A good fit

  • An established contractor with an office team and field crews, past the startup stage
  • An owner who is still the escalation path and wants to stop being it
  • Systems in place (field software, CRM, accounting) that do not work together or are not used fully
  • An owner or leader ready to give access, make decisions, and name an internal owner for what we build

Not a fit

  • Looking only for marketing or more leads
  • Shopping for software rather than changing how work gets done
  • Wanting an occasional advice call with no follow-through
  • Wanting a senior operator without giving them the authority or leadership time to act

Sound like your company? The call is the fastest way to find out.

who you would work with

Chance Peare, former roofing COO.

Before founding Framework Ops, Chance was COO of a founder-led roofing company. The methods on this site come from that work.

What he worked on as COO

  • Dispatch, scheduling, and the office-to-field handoffs that kept dropping
  • Collections and A/R follow-up
  • Moving the knowledge the office ran on out of a few people’s heads and into documented workflows
  • The weekly scoreboard the leadership team ran from
  • The automations that took routine follow-up off the owner’s plate
questions

What owners ask before booking.

If yours is not here, bring it to the call.

How is this different from a typical fractional COO or consultant?

The work is hands-on and operational: workflows your team uses, reporting your managers run from, automations that alert someone when they fail. We take ownership of the priorities we agree on, build alongside your managers, and hand each system to an owner on your team.

Where do we start if we are not sure what we need?

With a 30-minute call. We will tell you whether a focused assessment, a defined project, or ongoing leadership fits, or whether we are not the right help.

How do you scope and price the work?

After the discovery call. Fees depend on what is in scope and how involved we are, so both are confirmed in a written scope before any work starts. Projects are a fixed fee and ongoing leadership is a monthly fee. We do not bill by the hour.

Am I locked into a contract?

No. Ongoing leadership is month-to-month, and the first 30 days are covered by a money-back guarantee. The exact terms are in the written scope you approve before starting.

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.

Who do you work with?

Established contractors where the owner is still the operating system. The work was built first in roofing; we take selected work with other trade and specialty contractors when the operating problem matches what we have run.

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.