The SkillNav handbook

The people we build for

A business depends on people who know its customers and keep things moving. They may be owners, marketers, coordinators or operations leads. Their titles matter less than the responsibilities they carry.

We want to help the person who has to turn an incomplete request into a clear next step. They should be able to use SkillNav without becoming an AI specialist or spending their day configuring software.

Our first work focuses on customer understanding and offer testing. We will expand from the jobs people repeatedly find useful.

The burden we want to reduce

Operational overload consumes a small team's capacity. Context lives across conversations, documents and people's memories. Someone chases the missing detail, explains the background again or reconstructs a process that worked last time.

SkillNav should carry more of that preparation and coordination. People should have more attention for customers, judgment and the work they care about.

Every feature should help us answer a practical question: does this make the next piece of useful work easier to complete?

Know your customer before developing the offer

Knowing a customer means understanding their situation, responsibilities, current approach and the progress they want to make. A company description is a starting point. A person's actual priority needs evidence from their work and conversations.

SkillNav should bring three kinds of understanding together:

• Your business: what it can credibly deliver, how it works and the commitments it has made.
• The person doing the work: their role, responsibilities and approved preferences.
• The customer: their circumstances, desired progress, constraints and decisions.

We keep what someone said distinct from what we observed or inferred. Unknowns remain visible. Contradictory evidence should improve the questions we ask.

This understanding should change the work we prepare. It should help someone choose a more useful next conversation, recommendation or offer.

Skills turn understanding into useful work

A skill is a reusable way to do a particular piece of business work. It brings together a method, the context it needs, the tools it can use and a clear way to judge the result.

Customer understanding helps determine which skill fits, what questions it asks and how it should adapt. If a customer is preparing to open another office, an offer-development skill should use that confirmed situation to ask about the intended result, timing and people involved in the decision. It should make its reasoning easy to inspect.

The method can be reused across customers while each customer's evidence stays with the business that owns it. Useful corrections can suggest a better skill version; changes to the shared method require review.

A job pack combines the skills needed to reach a recognizable result. Our first pack follows a simple sequence: understand a customer, review the evidence, develop an offer, prepare a test and learn from the response.

Earn trust through the work

A useful result needs more than fluent writing. People need to see where an important claim came from, what remains uncertain and what needs their judgment.

SkillNav should make the state of work clear. A prepared offer, a sent message and an observed customer response are different events. Saving or accepting one version must not imply that later work happened.

People retain control over consequential actions. Access follows the permissions of the business and the systems involved. Knowing something about a customer never grants permission to act on their behalf.

We will make business knowledge inspectable and correctable. Sharing a method between businesses does not share their private records. Work should remain recoverable when a connection fails, a run stops or someone returns from another device.

Thoughtful design removes work

The experience should help someone understand their current task and take the next useful step. We ask for information when it changes the result. We keep the working brief and its sources close together, with additional detail available when needed.

An invitation should lead into useful work. A person joining a team should be able to understand the situation and contribute without completing a product tour first.

Readable text, clear forms, comfortable controls and careful phone layouts are part of the product's usefulness. So are honest progress, understandable errors and reliable saving. A calm screen should be supported by a dependable system underneath it.

The skills behind a job should be visible enough to understand and reuse. People should be able to reach a useful result before learning how those skills are assembled.

Build confidence from real use

We will use SkillNav in our own business and invite people to use it on work they already need to complete. Their corrections, interruptions and return visits will teach us what needs to improve.

We measure the effort required to reach a useful result, including review and corrections. We also pay attention to source accuracy, failed attempts, cost and whether someone chooses to use the skill again.

An accepted draft tells us something about that draft. A customer's commitment or a completed business result tells us something different. We will keep those observations separate as we develop and test offers.

Public examples should come from work we can explain and have permission to share. Private customer material stays private unless its owner explicitly chooses otherwise.

Grow through demonstrated capability

We will support a small number of jobs well and add capabilities when repeated work justifies them. A skill earns its place through a sound method, available inputs and tools, and evaluated results.

We can learn from open methods and build with other tools. We will preserve their origins, review their assumptions and test adaptations in the situations where people will use them.

SkillNav should work on its own for the jobs it supports. Over time, people should also be able to continue the same work from an assistant they already use, with the right context and permissions preserved.

Our ambition is that each useful job leaves the team better prepared for the next one: clearer customer understanding, a method worth reusing and less work to reconstruct.