Engagement model

How we work.

Every F3 Insights automation and advisory engagement with a $10M–$70M company follows the same four phases, whether the work is an executive's week, company goals, finance, or revenue. It starts by finding out what is actually true in your data and ends with your team running what was built.

Four phases$10M–$70M revenueYou keep the systems
The four phases

Diagnostic, Build, Operate, Transfer

Timelines vary with scope. The shape does not.

  1. 01

    Diagnostic

    2 to 6 weeks

    Find out what is actually true: where the data lives, which numbers reconcile and which do not, how decisions really get made, and which knowledge sits in one person's head.

    • A map of your systems
    • A list of problems with costs attached
    • A build plan in order
  2. 02

    Build

    Months 1 to 4

    Reconcile the data first, then build the first systems with a person reviewing their output, and set up the weekly and monthly rhythm they run on, working alongside your team. The senior advisor works inside that rhythm from day one, so the systems are proven on real decisions rather than demos.

    • One reconciled set of numbers
    • First systems, with review built in
    • An operating rhythm in place
  3. 03

    Operate

    Months 3 to 9

    The systems run your real work. Forecast accuracy, close time, pipeline accuracy, and margin are tracked as the engagement's measures. Your people take over the controls step by step, and the advisor moves from running the work to reviewing it.

    • Measures tracked
    • Your team driving
    • Advisor reviewing, not running
  4. 04

    Transfer

    Planned from the start

    Playbooks written down, your people trained on each review step, and model review handed to named owners on your team. F3 Insights steps back to light advisory support or leaves.

    • Written playbooks
    • Trained owners
    • You keep the code, data, and documentation
The end state

You Keep the Systems

Every engagement is planned from the start to end with your team running what was built.

Success is measured in your numbers: days to close, forecast error, how many weeks ahead you can see cash, pipeline reconciled to the P&L, margin recovered, hours back in the executive team's week. The final test is your team running the systems without us.

Our approach FAQ Glossary
Next step

The diagnostic stands on its own.

You leave the first phase with a map of your systems, a list of problems with costs attached, and a build plan in order, whether or not we build it together.

Schedule a ConversationRead the FAQ