IP Scorecard

Your business has an operating model whether you have designed one or not. The question is whether that model can function — and grow — without you at the centre of it. This scorecard measures the five dimensions of a scalable, IP-protected operating model: your systems, your documentation, your IP-ification, your training and onboarding, and your scalability. Score each item honestly. The result tells you exactly where value is leaking and what to fix first.

• Core delivery process exists as a documented system, not a personal habit The way your primary product or service is delivered is written down in sufficient detail that a competent new hire could follow it and produce an outcome consistent with your standard — without asking the founder how.
  012
• Client-facing touchpoints follow a consistent, documented sequence Onboarding, delivery milestones, communication cadence, and offboarding follow a documented protocol — not the founder's instinct about what each client needs.
  012
• Quality and consistency standards are documented and measurable There are written standards for what good looks like — not just the founder's judgment. New team members can reference these standards without needing to shadow the founder to understand them.
  012
• Financial and administrative systems operate without founder daily input Invoicing, accounts payable, payroll, and reporting run on documented systems that team members manage. The founder is a reviewer, not an operator, of financial administration.
  012
• Sales and business development follow a documented process How the business finds, qualifies, converts, and retains clients is systematised — scripts, templates, follow-up sequences, and proposal formats exist and are used consistently, not improvised by whoever is doing the selling.
  012

• An operations manual exists and is current A single document (or structured document set) that describes how the business operates. It is version-controlled, updated when processes change, and accessible to the team. Not a folder of scattered notes.
  012
• Documentation is specific enough to be followed without interpretation The test: hand the documentation to a competent but unfamiliar person. Can they follow it and produce the correct outcome? Documentation that requires the reader to "fill in the gaps" from tribal knowledge is not yet complete.
  012
• Documentation covers edge cases, not just the standard scenario What happens when a client is unhappy? When a supplier fails? When a team member leaves mid-engagement? Processes that only document the smooth path are incomplete. Edge case protocols are what prevent the founder being called in every time something unexpected occurs.
  012
• Documentation is maintained — it reflects how the business actually operates today An operations manual written three years ago and never updated is worse than no manual, because it creates a false sense of security. Documentation has a review cycle and is updated when processes change.
  012

• Documented systems are formally owned by the business entity, not individuals The IP in your systems belongs to the company. Employment and contractor agreements include IP assignment clauses. There is no ambiguity about who owns the documented processes, frameworks, and methodologies the business operates on.
  012
• Key systems are protected — trade secret, copyright, or contractual confidentiality The mechanisms that prevent a departing employee or competitor from simply copying your systems and replicating your model. Confidentiality agreements, access controls, and documented trade secret protocols. Protection does not happen automatically — it must be designed.
  012
• An IP Asset Register records all documented systems and their protection status Every documented system, framework, methodology, and tool is recorded in a single register with its description, ownership status, protection mechanism, and commercial potential. If you do not know what you own, you cannot protect it or leverage it.
  012
• At least one system has been assessed for commercial potential beyond its current internal use A documented, protected system is the foundation of a licensable product. Has the business identified whether any of its operating IP — a methodology, a process, a training framework — could generate revenue through licensing, white-labelling, or packaging?
  012

• New team members can be trained from documentation, not only by shadowing Training does not depend on an experienced team member showing a new one how things are done. A structured training pathway — using the operations manual, video walkthroughs, or documented modules — produces team members who work to the business standard.
  012
• Onboarding produces consistent performance, not variable results by individual When two team members complete the same onboarding, they produce similar outcomes. If performance varies significantly by individual rather than by documented standard, the training system is not yet complete — it is still teaching people to approximate the founder's approach.
  012
• The training system itself is documented, version-controlled, and updatable The training pathway is not a set of informal onboarding conversations — it is a documented program that can be delivered by any capable manager, updated as the business evolves, and scaled to new hires without the founder's direct involvement.
  012

• Revenue can grow without proportional increases in founder involvement The test: if revenue doubled in the next 12 months, would the founder's hours double too? A yes is the definition of a non-scalable model. A no — achieved through documented systems, trained team, and delegated decision-making — is the output of this entire framework.
  012
• The business has been tested — it operated effectively without the founder for 2+ weeks Theoretical scalability is not scalability. Has the founder actually stepped away — taken leave, been unreachable — and the business operated to standard? If not, the systems exist on paper but have not been activated in practice.
  012
• A scalability roadmap exists — a plan for the next growth stage that does not require the founder's personal capacity as the growth lever There is a documented plan for how the business grows — whether through hiring, licensing, franchising, or another IP-led model — that does not assume the founder works more hours, takes more calls, or carries more personal relationships. Growth by founder exhaustion is not a roadmap. It is a constraint.
  012
• The business's operating model could be explained to and operated by a new owner The ultimate scalability test: could a qualified buyer step in, use your documentation and systems, and run this business to the same standard you have? If the honest answer is no — because too much lives in your head — then this is the most commercially expensive gap on this scorecard.
  012

Your Total IP Scorecard Result

The THINK IP Operating Models Process

Your score identifies the gap. The THINK IP Operating Models engagement is how you close it — systematically, in the right sequence, building IP assets at each stage rather than simply documenting for documentation's sake.