The Framework → The Navigator

The Navigator: the thinking layer

The Navigator: the thinking layer beneath the 8-phase framework. The business-knowledge questions to answer honestly before you build each phase, the thought pattern that makes it work, and the readiness signal that says you’re ready for the next one.

The eight phases tell you what to build. The Navigator is the pre-work that happens on paper, on a whiteboard, or in conversation before a single line of code exists: the questions that extract the right knowledge from your head before you ever touch a database or talk to an AI agent.

If you can’t answer a question confidently, that’s not failure. It’s knowing exactly where the system needs to fill the gap. The questions you struggle with are the exact gaps.

Product Formulation

Questions

Can you list every material in your product from memory?
Do you know the current cost of each material, and how often those costs change?
Can you describe every labor step from raw material to finished product?
What’s the most complex variant of your product? Can you decompose it?
Where do you currently guess instead of know?

Thought pattern

Your product is not one thing. It’s a tree of decisions: material choices, dimension options, hardware selections, finish types. Each branch has a cost, a time, and a constraint. You’re mapping the tree, not just the trunk.

Readiness signal

You can describe any product variant to someone with zero context and they could calculate a rough cost from your documentation alone.

Operational Mapping

Questions

If you disappeared for a week, could your team produce without calling you?
Where does work physically stop moving? What’s the bottleneck you already know about but haven’t fixed?
How many handoff points exist between raw material arrival and finished product leaving?
Which steps require skill and which require time? (They need different solutions.)
What happens when something goes wrong at step 3? Does step 4 know?

Thought pattern

You’re not mapping what should happen. You’re mapping what actually happens, including the workarounds, the informal systems, and the things that only work because one specific person knows to do them.

Readiness signal

A new hire could look at your operational map and understand the flow from receiving to shipping without asking you to explain it.

Relational Database

Questions

What information do you currently track in spreadsheets, notebooks, or your head?
When someone asks “how much did we spend on materials last month?” how long does it take to answer?
What information do two or more people need access to simultaneously?
What are you tracking that you never use? What are you NOT tracking that you wish you were?
If a customer calls about a project from 6 months ago, how fast can you pull up every detail?

Thought pattern

A database isn’t a filing cabinet. It’s a set of relationships. Material connects to product, product to project, project to client, client to quote. If any connection breaks, you’re relying on memory to bridge the gap.

Readiness signal

You can ask the system a question that would have taken 30 minutes to answer manually, and get the answer in seconds.

Knowledge Base & SOPs

Questions

What do you explain to people repeatedly? That’s your first SOP.
If your best employee quit tomorrow, what knowledge leaves with them?
When something goes wrong on the floor, where does someone look for the answer?
What decisions do you make on instinct that you’ve never written down the logic for?
What would a new hire need to read to be useful in their first week?

Thought pattern

There are two types of knowledge in your shop: explicit (written procedures, specs, price lists) and tacit (what people just know from experience). Phase 4 converts tacit into explicit. Every time you say “you just have to know that,” that’s an undocumented SOP.

Readiness signal

Someone can ask the AI agent a question about your product, process, or a past issue and get an answer that you would agree with.

Project Intelligence

Questions

On your last project, where did the estimate differ from reality? Do you even know?
What’s your most profitable product type? How do you know: gut feeling or data?
When you lose money on a job, can you trace exactly where the loss came from?
Are you making the same mistake you made three months ago? Would you even know?
What would change about your pricing if you had perfect data on every past project?

Thought pattern

Every completed project is a test of your system’s accuracy. The gap between estimated and actual isn’t a failure. It’s the most valuable data your business produces. Treat closeout as the beginning of the next improvement.

Every change order is either a pricing error, a scope-definition failure, or a production mistake. Track which one. The pattern tells you where the system is weakest.

Readiness signal

After three completed projects tracked in the system, you can identify at least one systematic error in your original cost model you wouldn’t have found without the data.

You can tell me, using the system, your average change-order rate by project type and whether it’s trending up or down.

Configure → Price → Quote

Questions

How long does it currently take to produce a quote? What would change if it took 10 minutes?
When two different people quote the same job, do they get the same number?
What variables in your pricing are you least confident about?
Have you ever won a job and then realized mid-production you underpriced it? What did you miss?
If material costs changed tomorrow, how many places would you need to update?
Can your current quoting handle the same product at two different order quantities at two different price points in the same proposal?

Thought pattern

A quote is not a creative act. It’s a calculation. The goal isn’t AI-generated quotes; it’s a system where the quote is the inevitable mathematical output of specs + labor + materials + margin. No guessing.

Readiness signal

Your system produces a quote that matches what you’d quote manually within 5%, and you can explain every line item’s source.

You can generate a quote, revise it, and the system tells you exactly what changed and how it affects the total, without manually comparing spreadsheets.

Sales & Client Management

Questions

Do you know your close rate? Not a guess, the actual number?
When a lead goes cold, do you know why? Price, timing, scope, or trust?
How many quotes are sitting unanswered right now? When did you last follow up?
What’s the lifetime value of your best customer versus your average customer?
If someone asked “what’s your sales pipeline worth right now?” could you answer in 10 seconds?

Thought pattern

Sales is not separate from operations. Every quote is a promise about your production capacity, material costs, and timeline. If sales isn’t connected to operational data, you’re making promises you can’t verify.

Readiness signal

You can open the system and see every active lead, every outstanding quote, and every project in progress, on one screen, updated in real time.

You can trace any dollar from first contact through quote, contract, change orders, production costs, and final payment.

Content & Marketing

Questions

Do you have photos of your last 10 completed projects? Organized, or scattered across phones?
If someone asked “what makes your product different?” can you answer in one sentence?
What does your ideal customer search for online when they need your product?
Are you proud enough of your work to show it publicly?
What story does every project tell that your customer cares about?

Thought pattern

Marketing isn’t a separate activity you bolt on at the end. If Phases 1–7 are done right, marketing is just publishing what your system already knows. You’re assembling, not creating.

Readiness signal

You can produce a complete social-media post (image, caption, product specs, customer context) in under 5 minutes using only data already in the system.