OILOccupational Identity Lab by KamaraTech
Demo case

Follow one leader through the whole lab

Every document below is what a client receives, in full or as a marked excerpt. OI in the document names stands for occupational identity: how you and others understand what your role is for. Clara is fictional. Her pattern is common in compliance, risk, data, and transformation roles. Already left your role? A second fictional case shows the Transition Edition preview.

See the Transition case

Demo persona

Clara H.

Director, Compliance & AI Governance at a mid-size European insurer. Reports to the General Counsel. Team of five.

Fictional demo persona
  • Sixteen years in compliance. Rebuilt the firm's GDPR programme under a nine-month deadline.
  • In 2024 the board asked who owns AI risk. The answer became Clara. Accountability was added. Title, budget, and decision rights were not.
  • AI tooling and vendor decisions sit with the CIO and the Chief Data Officer. She is consulted late, then asked to sign.
  • She wants real decision rights over AI: a stronger mandate where she sits, or an adjacent route through the risk function. She does not yet know which. That is the decision the lab helps her make.
Free · with your consent

OI Threat Radar Snapshot

Real output from the Radar engine, for a fictional profile. With a real client, the inputs come from the public profile, used with consent. For this demo they were set by hand with OIL's band rubric. Every signal cites its source and date.

Posture: Escalating
ClearWatchlistEscalatingRed Zone
OI Threat Radar Snapshot · Clara H.Fictional demo persona · Radar output · evidence checked 29 October 2026

Prepared for: Synthetic persona: Clara H., Director, Compliance & AI Governance, European insurer
As of: 2026-10-29 | Library: REL-2026-W44 | Posture: Escalating

Posture: Escalating

Your current posture is Escalating: AI and technology change is actively putting pressure on how your role is enacted, especially where accountability, boundaries, and legitimacy are negotiated.

The goal in this posture is to regain defensibility: tighten mandate language, protect decision rights, and design an adaptive next step.

Pressure area 1: Authority & Accountability Shift (primarily enactment pressure)

This pressure area points to a mismatch between what you are responsible for and what you can control, especially as AI and tooling decisions move elsewhere.

Pressure area 2: Boundary Blur & Role Integrity (primarily meaning pressure)

This pressure area indicates your mandate boundaries are getting harder to defend, often because AI enables adjacent teams to move into your territory.

Signals behind this reading

  1. Article 50 AI transparency duties have applied since 2 August 2026; the marking and labelling code is assessed as adequate
    Source: European Commission, 2026-07-24 (source)
    Why it matters: Marking, detection and disclosure duties fall on providers and deployers of generative AI; systems already on the market have until 2 December 2026 for marking. Signing the code is voluntary and is not conclusive proof of compliance.

  2. First AI Act harmonised standard cited: EN 18286 on AI quality management systems
    Source: Official Journal of the European Union, 2026-10-14 (source)
    Why it matters: EN 18286 is the only standard this decision lists; applying it gives a presumption of conformity with the AI Act requirements it covers.

  3. Digital Omnibus on AI in force since 27 July 2026: Annex III high-risk duties move to 2 December 2027
    Source: Official Journal of the European Union, 2026-07-24 (source)
    Why it matters: High-risk obligations are deferred, not removed. Programmes built for August 2026 may need re-sequencing towards December 2027, while new prohibitions apply from December 2026.

  4. ICO extends AI scrutiny to agents and prepares a statutory AI and ADM code
    Source: Information Commissioner's Office, 2026-10-08 (source)
    Why it matters: The ICO's call for evidence on agentic AI closes on 20 November 2026 and will support its statutory code of practice on AI and automated decision-making.

  5. About a third of surveyed organisations report responsible-AI maturity level 3 or higher in strategy, governance and agentic AI governance
    Source: McKinsey & Company, 2026-03-25 (source)
    Why it matters: McKinsey suggests that organisational alignment and oversight structures are struggling to keep pace with the rapid expansion of AI use.

What to watch

  • Approval workflows change: you become the final signer for AI-assisted outputs without control over the system design or data.
  • New KPIs appear that depend on AI or tooling performance, but ownership sits outside your function.
  • Requests arrive that bypass your function's normal intake process (ad hoc AI use, shadow workflows).

Next step

Recommended: book the 20-minute debrief to pressure-test your mandate language and decision rights. If there is a fit, a free preview of your options follows.


This Snapshot is an exposure-signal summary. It is not a diagnosis, not an employment prediction, and not legal or compliance advice.

Signals come from the published sources listed above and are interpreted through the Occupational Identity Lab's research framework. Identity-related readings are inferred from evidence about roles like yours, not measured directly. Posture and pressure areas describe exposure patterns for your role type, not an assessment of you as a person.

Confidence for this Snapshot: Medium. Basis: your public professional profile, used with your consent, plus the cited published sources. No other personal data is used.

Demo note: Clara is fictional, so no real profile was processed. The footer describes what a real Snapshot is based on.

Free, if there is a fit

OI Prototype Snapshot

Built after the 20-minute debrief from Clara's own material. It shows what the lab would produce before she pays.

OI Prototype Snapshot · Clara H.Fictional demo persona · Draft v1 for discussion

Preview, produced after the 20-minute debrief and before any payment.

Persona: Clara H. (fictional), Director, Compliance & AI Governance, mid-size European insurer
Edition: OIL Prime, In-Role Edition
Status: Sketch for discussion. These are options, not decisions.

How to read this: the debrief showed one gap. Clara carries accountability for AI risk without the decision rights to match. Two routes follow from that gap. One builds the mandate where she sits today, in compliance. The other builds an adjacent route to the same decision rights, in the risk function, where model validation authority already exists. This snapshot sketches both so she can see what each would ask of her. Which one carries more weight is a decision for the lab, not for this page.


1) OI Signature (one-liner)

"I make AI decisions defensible before they are made, not after they go wrong."


2) Primary OI Prototype

AI Assurance Lead (in-role mandate expansion)

Who it serves: the board, the General Counsel, the CIO, and the business units deploying AI.

Offer in 90 days:

  • An AI approval gate with clear decision rights
  • An evidence standard for AI-assisted decisions
  • A seat in the AI investment forum

Operating model: in-role. A formal mandate letter. Quarterly reporting to the board audit committee.

Proof at day 90:

  • A signed decision-rights memo
  • The evidence standard adopted by 2 business units
  • The first 5 AI use cases passed through the gate

Non-negotiables:

  • No sign-off without evidence
  • No governance theatre

3) Hedge OI Prototype (the fallback)

AI Model Risk Lead (adjacent mandate in the risk function)

Who it serves: the Chief Risk Officer, AI model owners, and the board risk committee.

Offer: independent validation of AI models before they go live, an AI model inventory, and the right to challenge models that are not ready.

Operating model: a second-line role reporting to the Chief Risk Officer, with formal validation authority.

Proof needed:

  • Co-validation of one AI model with the risk team
  • A contribution to the AI model risk standard
  • An invitation to the model risk committee

Why it exists: it keeps a second credible route to real decision rights open if the Primary stalls. It is a fallback inside the firm, not a plan to leave.


4) Augmented Practice Playbook (preview)

Week 5 deliverable. Preview only.

Three principles:

  • Automate / Delegate / Protect: decide what tools do, what the team does, and what only Clara does.
  • Verification gates: every AI-assisted output passes an acceptance check before it is used.
  • Evidence packs: every high-stakes decision has a traceable evidence pack.

5) 90-Day Experiment Plan (preview)

Week 6 deliverable. Preview only.

Experiment Goal Measure Horizon
E1 Send a decision-rights memo to the GC and CIO proposing the AI approval gate Invited to the AI investment committee within 30 days 3 weeks
E2 Publish evidence standard v1 for AI-assisted claims decisions Adopted by 2 business units; rework on AI sign-offs down 6 weeks
E3 Hedge test: two conversations with the Chief Risk Officer's team about AI model validation, plus an offer to co-validate one model Invited to co-validate a model or to join the model risk committee 8 weeks

What happens in the lab

These sketches become decision-grade artifacts in six weeks.


Prepared after the debrief. Preview.

Week 1

Identity Risk Map

Starts from a full Radar report and Clara's own evidence. Severity is agreed with her, not computed.

Identity Risk Map · Clara H.Fictional demo persona · Draft v1 for discussion

Week 1 deliverable. One page. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.

The four pressure areas below match her OI Threat Radar Snapshot. Each one carries a severity, the evidence from her situation, and one question to carry into later weeks. Severity is a judgment Clara and Seni make together from her own evidence. It is not a measured score.

Pressure area Severity Evidence from her situation Priority question
Authority & Accountability Shift (primarily enactment pressure) High She signed the documentation for an AI-assisted claims-triage model she had no part in designing. She is not a member of the AI investment committee that approves the use cases she later has to defend. What decision rights would make her accountability legitimate?
Boundary Blur & Role Integrity (primarily meaning pressure) Medium-High The CIO, the CDO, and business units run AI work that reaches compliance only at sign-off. "Who owns AI risk?" was answered by default, not by design. Where does compliance end and AI governance begin, and who decides?
Expertise Compression & Replaceability (primarily value pressure) Medium Tool-assisted checks: vendor assurance and documentation checks are increasingly done with tools. Risk to her standing: her role may be reframed as "checking". Which parts of her judgment cannot be reduced to checks?
Meaning & Status Erosion (primarily meaning pressure) Medium Credit for AI programmes goes to delivery teams. Accountability stays with her. What would make her contribution visible to the board?

Red lines check (private, not scored)

Signing documentation she cannot verify conflicts with her value "no signing what I cannot verify". Flag for the Week 2 non-negotiables.

Stakeholder strip

Stakeholder Role in her situation Stance
General Counsel Her line manager and sponsor Supportive
CIO Owns AI tooling and vendor decisions Neutral
Board audit committee Trusts her; sees AI risk only through summaries Trusting, under-informed

Prepared in OIL Prime, Week 1. Draft v1 for discussion.

Week 2

OI Signature

The story she can defend in any room, and the lines she will not cross.

OI Signature · Clara H.Fictional demo persona · Draft v1 for discussion

Week 2 deliverable. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.


A) Headline options (pick one)

  1. "I make AI decisions defensible before they are made, not after they go wrong."
  2. "I give leaders a straight answer to one question: can we stand behind this AI decision?"
  3. "I turn AI risk from a late signature into an early standard."

B) OI Signature v1 (first person)

I have spent 16 years making complex rules work in practice. When the GDPR programme had to be rebuilt in nine months, I rebuilt it. Supervisors still ask for me by name. That trust is my licence to operate.

Today the hard question is AI. Customers and supervisors need to trust the decisions an insurer makes with it. They cannot trust what nobody checked.

So my purpose is simple. I make decisions defensible under uncertainty. I set the evidence standard before a model goes live. I make clear who decides, who verifies, and who signs.

I do not sell certainty. I say what we know, what we assume, and what we do not know yet. I will not sign what I cannot verify.

I work in defined review windows, with a clear route for urgent items. Good governance does not depend on one person being awake at midnight.


C) Six non-negotiables

# Non-negotiable Boundary script
1 No sign-off without evidence "I can't sign this because I haven't seen the evidence behind it." / "What I can do is review it as soon as the evidence pack is complete."
2 No shadow governance "I can't approve this outside the agreed gate because it would create a second, unofficial process." / "What I can do is bring it through the gate this week."
3 No false certainty "I can't say this model is safe because we have not tested the cases that matter." / "What I can do is state what is verified, what is assumed, and what is unknown."
4 Defined escalation windows (not always-on) "I can't be the always-on backstop because that hides the real coverage gap." / "What I can do is review in set windows and log urgent items in the escalation registry."
5 No vendor claims accepted without proof "I can't accept this assurance claim because no evidence came with it." / "What I can do is list the proof we need and review it when it arrives."
6 No governance theatre "I can't add a review step that changes nothing because it gives false comfort." / "What I can do is design a check that can actually stop or change a decision."

D) Value proposition by stakeholder

Stakeholder One-line value proposition
Board audit committee You will see AI risk as evidence, not as reassurance.
General Counsel Our AI decisions will carry a record we can defend to a supervisor.
CIO / CDO A clear gate and a clear standard, agreed up front, so approval stops being a late surprise.
Business unit heads You know what evidence your AI use case needs before you build it.

Prepared in OIL Prime, Week 2. Draft v1 for discussion.

Week 3

Future Relevance Map

Which future options hold up, tested against trends in three horizons.

Future Relevance Map · Clara H.Fictional demo persona · Draft v1 for discussion

Week 3 deliverable. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.

Each trend is tagged as a Pull (it raises demand for her), a Pressure (it raises the cost of staying as she is), or an Opportunity (it opens new ground).


A) Trend radar

Horizon Trend Impact type So what for Clara
Now AI use cases multiplying faster than oversight capacity Pressure Her team cannot review everything. She needs a gate and a standard, not more manual checks.
Now Supervisors asking for evidence that AI-assisted decisions were checked Pull Her evidence standard becomes something the firm needs, not something she is asking for.
Next Agentic AI entering claims and underwriting workflows Pressure Decisions will be made faster and with fewer human steps. Decision rights must be set before that happens.
Next AI assurance becoming a buyable market of tools and advisors Opportunity Assurance methods are maturing fast. Someone inside the firm has to judge them, in compliance or in risk.
Beyond EU AI Act obligations phasing in through 2027 and 2028 Pull A mandate for AI governance becomes easier to argue for, and easier to measure.
Beyond AI governance as a recognised executive function with its own seat Opportunity A seat will exist for someone. Both of her routes lead towards it.

B) Implication matrix

Trend Primary: AI Assurance Lead Hedge: AI Model Risk Lead
Use cases outpace oversight Pressure: needs an approval gate now Pressure: validation queues grow too
Supervisors expect evidence of checks Pull: strengthens the case for a mandate Pull: validation becomes a supervisory expectation
Agentic AI in claims and underwriting Pressure: decision rights urgently needed Opportunity: agents need validation before go-live
AI assurance becomes a market Opportunity: tools can support the gate Opportunity: validation tools need expert judgment
EU AI Act phasing in through 2027 and 2028 Pull: gives the board a reason to act Pull: model risk duties gain weight
AI governance as its own executive seat Opportunity: she can claim the seat early Opportunity: the risk route leads there too

C) Two opportunity lanes

Lane 1: Make AI approval a governed gate inside her insurer

  • Thesis: the insurer will pay for AI decisions it can defend, and she is best placed to design that capability.
  • Offer wedge: an AI approval gate with decision rights, plus an evidence standard for AI-assisted claims decisions.
  • Proof wedge: the first 5 AI use cases passed through the gate, with evidence packs on file.
  • Skill wedge: turning compliance judgment into a standard that business units can follow without her in the room.

Lane 2: Hold validation authority over AI models in the risk function

  • Thesis: the risk function already owns model validation; extending it to AI gives her decision rights by an adjacent route.
  • Offer wedge: co-validation of one AI model with the Chief Risk Officer's team.
  • Proof wedge: a contribution to the AI model risk standard and an invitation to the model risk committee.
  • Skill wedge: validation methods for AI models, learned alongside the risk team.

Prepared in OIL Prime, Week 3. Draft v1 for discussion.

Week 4

Primary and Hedge OI Prototypes

Where the two options are designed and chosen: a Primary, and a Hedge kept as the fallback.

Primary and Hedge OI Prototypes · Clara H.Fictional demo persona · Draft v1 for discussion

Week 4 deliverable. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.


A) Strategy canvas

Each factor is rated Low, Medium, or High for her role as it stands and for the Primary OI Prototype.

Factor Today Primary prototype Note
Speed of sign-off High Medium Today sign-off is fast because it is late. The gate adds an earlier, deliberate step.
Depth of legal review High High Stays strong. This is her base.
Ownership of AI decisions Low High The central shift: accountability matched by decision rights.
Evidence standard Low High Today evidence is gathered case by case.
Board visibility Low High Quarterly reporting to the audit committee.
Vendor scrutiny Medium Medium Same rigour, less manual effort, because the standard defines the proof required.

B) Eliminate, Reduce, Raise, Create

Eliminate Reduce
Late-stage sign-off of AI work she did not see Manual re-checking of vendor claims
Raise Create
Decision rights at the approval gate An evidence standard for AI-assisted decisions
Board visibility of AI risk An AI assurance forum

C) Final selection

Primary OI Prototype: AI Assurance Lead (in-role mandate expansion)

Scope: owns the AI approval gate and the evidence standard. Holds a seat in the AI investment forum. Reports quarterly to the board audit committee.

Success signals: a signed decision-rights memo. An invitation to the AI investment committee. The evidence standard adopted by 2 business units. The first 5 AI use cases passed through the gate.

Organisational requirements: a formal mandate letter from the General Counsel, with the CIO and CDO agreeing to route AI use cases through the gate. A named place in the investment forum.

Risks: the CIO and CDO treat the gate as a delay. The mandate stays informal and accountability grows without rights. Business units route around the gate.

Hedge OI Prototype: AI Model Risk Lead (adjacent mandate)

Scope: independent validation of AI models before go-live, an AI model inventory, and the right to challenge models that are not ready. A second-line role reporting to the Chief Risk Officer.

Success signals: co-validation of one AI model with the risk team. A contribution to the AI model risk standard. An invitation to the model risk committee.

Organisational requirements: a Chief Risk Officer willing to extend model validation to AI, and the General Counsel's agreement that she can contribute across functions.

Risks: the hedge is read as a move away from compliance. Validation work competes with in-role delivery. The risk team may treat her as a visitor rather than a validator. Its purpose is a second credible route, not an exit.


Prepared in OIL Prime, Week 4. Draft v1 for discussion.

Week 5

Augmented Practice Playbook

How she works with AI and with her team without becoming the always-on backstop. Excerpt.

Augmented Practice Playbook · Clara H.Fictional demo persona · Draft v1 for discussion

Week 5 deliverable, excerpt. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.


A) Automate / Delegate / Protect

Automate (tools do it, with checks) Delegate (her team does it, she reviews) Protect (only she does it)
First-pass reading of vendor documentation Building the evidence pack for each AI use case Final judgment on whether a use case may go live
Drafting summaries of policy and supervisor texts Running the checklist on vendor assurance claims Negotiating decision rights with the GC, CIO, and CDO
Extracting claims from vendor assurance documents Maintaining the assumption register Speaking with supervisors on AI matters
Formatting board and committee papers Drafting quarterly audit committee reports Deciding what is escalated to the board
Tracking open actions and review dates Preparing business unit briefings on the evidence standard Declining to sign when evidence is missing

B) Five verification gates

Every AI-assisted output passes these gates before anyone uses it.

Gate Acceptance check
1. Source quality Each key claim traces to an official or primary source. Secondary sources are marked as such.
2. Assumption register Every assumption is written down, with an owner and a date.
3. Counterfactual check The reviewer states what would change the decision, and tests it.
4. Unknowns logged What is not known is listed in the pack, not left out.
5. Human sign-off A named owner signs. A name is required. A team or a tool is not enough.

C) Delegation protocol for a team of five

Step Who Rule
Brief Clara, or a senior analyst she names The brief states the question, the sources allowed, the tools allowed, and the output format.
Produce Analyst, with tool support Tool output is a draft. It is never a finding.
Verify A second team member, not the producer Runs gates 1 to 4 and records the result in the evidence pack.
Sign Clara, or a named deputy for lower-risk items Gate 5. Clara signs only with a complete pack. High-stakes items always come to her.

D) Coverage design

Clara is not the always-on backstop.

  • Review windows: two fixed review windows each week for AI approvals. Items arriving between windows wait for the next one.
  • Escalation registry: urgent items are logged with the reason, the owner, and the time. A named deputy covers when Clara is away.
  • Exceptions only: anything outside the windows needs a written reason in the registry. Repeated exceptions are reviewed monthly to see whether the windows need to change.

Prepared in OIL Prime, Week 5. Draft v1 for discussion.

Week 6

90-Day Experiment Plan

Three experiments with success and kill signals set in advance, reviewed at Day 30, 60, and 90.

90-Day Experiment Plan · Clara H.Fictional demo persona · Draft v1 for discussion

Week 6 deliverable. Clara H. (fictional), Director, Compliance & AI Governance. OIL Prime, In-Role Edition.

Three experiments. Each is a test with a success signal and a kill signal, set in advance.


Experiment 1: Decision-rights memo

Field Specification
Hypothesis If the GC and CIO see a short, concrete proposal for an AI approval gate, Clara will be invited into the AI investment committee.
Steps 1. Draft a two-page memo with the gate, decision rights, and evidence required. 2. Agree it with the GC first. 3. Present it to the CIO and CDO. 4. Ask directly for a seat in the committee.
Success signal Invited to the AI investment committee within 30 days.
Kill signal No written reply from the GC or CIO within 30 days, after one follow-up. Stop and revisit the Primary route.
Owner Clara
Horizon and review 3 weeks. Review at Day 30.

Experiment 2: Evidence standard v1

Field Specification
Hypothesis A clear evidence standard for AI-assisted claims decisions will be adopted by business units and reduce rework on AI sign-offs.
Steps 1. Draft the standard from the five verification gates. 2. Test it on one live claims-triage use case. 3. Revise with two business units. 4. Publish v1 and log rework on AI sign-offs.
Success signal Adopted by 2 business units. Rework on AI sign-offs is lower than the baseline she records in week 1.
Kill signal Fewer than 2 business units willing to pilot by week 4, or the standard adds steps without catching issues. Simplify or stop.
Owner Clara, with a senior analyst from her team
Horizon and review 6 weeks. Review at Day 60.

Experiment 3: Hedge test in the risk function

Field Specification
Hypothesis The Chief Risk Officer's team would welcome her judgment in validating AI models, which opens an adjacent route to decision rights.
Steps 1. Ask for the General Counsel's support for cross-functional work. 2. Hold two conversations with the CRO's team about how AI models are validated today. 3. Offer to co-validate one AI model. 4. Note what the risk team asks of her.
Success signal Invited to co-validate a model or to join the model risk committee.
Kill signal No interest after two conversations by week 4. Park the hedge and strengthen the Primary lane.
Owner Clara
Horizon and review 8 weeks. First read at Day 60. Final read at Day 90.

Review calendar

Day Review
Day 30 Experiment 1 result. Decide whether to continue Primary or revisit it.
Day 60 Experiment 2 result. First read on Experiment 3.
Day 90 Full re-measurement and the decision: how to weight Primary and Hedge for the next quarter.

Re-measured at Day 90

  • Radar refresh: posture and leading pressure areas, read again against current evidence
  • Augmented Practice Readiness, scored 1 to 7
  • Experiment outcomes against the success and kill signals above

Prepared in OIL Prime, Week 6. Draft v1 for discussion.

Transition Edition

Transition case: OI Prototype Snapshot

A second fictional client. Mikael lost his director role in a restructuring two months ago. This is his preview, built after the debrief: a role to land, a fallback that keeps income moving, and market tests with kill signals.

Transition case: OI Prototype Snapshot · Mikael R.Fictional demo persona · Draft v1 for discussion

Preview, produced after the 20-minute debrief and before any payment.

Persona: Mikael R. (fictional), former Director of Product, enterprise connectivity, European telecom operator
Edition: OIL Prime, Transition Edition
Status: Sketch for discussion. These are options, not decisions.

Where he stands:

  • Fifteen years in product at one operator. The last four as Director of Product for enterprise connectivity.
  • He led the rollout of an AI service-assurance tool that field operations first resisted, then relied on.
  • Two months ago a restructuring merged product and operations. His layer was removed.
  • He has severance and about six months before money becomes a real concern.
  • His outplacement programme is running the search. What it cannot settle is the direction: director again, or a fractional portfolio, and on what story.

How to read this: the debrief showed one gap. Mikael's story is still told in his last employer's language: titles, org charts, a product line that no longer exists. The market does not buy that story. It buys a problem he can solve. Two routes follow. One is a director role built on his strongest proof. The other is a fractional practice that keeps income and visibility moving while the first route plays out. This snapshot sketches both, with the market tests that will settle between them.


1) OI Signature (one-liner)

"I turn AI tools that operations teams distrust into products they rely on."


2) Primary OI Prototype

Head of Product, AI-enabled operations (infrastructure and network businesses)

Who it serves: COOs and CTOs at telecom and infrastructure operators who have bought AI tools that their own teams do not yet trust.

Offer: product leadership that turns internal AI tools into services that operations teams adopt and enterprise customers will pay for.

Why it is the most likely to land: it rests on his strongest proof, the service-assurance rollout, and it names a problem these buyers already have.

Proof at day 90:

  • Three second-round conversations with hiring leaders in the target group
  • One request for a written "first 100 days" proposal
  • His OI Signature used, unchanged, in every conversation

3) Hedge OI Prototype (the fallback)

Fractional product leader for scale-ups that sell into operators

Who it serves: founders of B2B scale-ups whose product has to pass an operator's procurement, security, and field-adoption tests.

Offer: a fixed-price two-week product diagnostic, then two days a week for up to two clients.

Proof needed:

  • One paid diagnostic sprint
  • One returning client or referral

Why it exists: it gives him a second credible route if the director search stalls, and it keeps income and visibility moving while it runs.


4) Augmented Practice Playbook (preview)

Week 5 deliverable. Preview only.

Three principles for the search:

  • AI researches, he decides: AI drafts briefs on target firms. He chooses where to spend a conversation.
  • Verify before you speak: every claim about a firm is checked against a primary source before it reaches a conversation.
  • No volume applications: no AI-written applications sent at scale. Each approach is written for one person.

5) 90-Day Experiment Plan (preview)

Week 6 deliverable. Preview only. Success and kill signals are set before each test starts.

Experiment Test Success signal Kill signal Horizon
E1 Twelve targeted conversations with hiring leaders and two search partners, using the OI Signature Three second-round conversations and one request for a written proposal Fewer than two second-round conversations by week 6: rework the story, not the volume 6 weeks
E2 Offer the two-week diagnostic to five scale-ups that sell into operators One paid sprint by day 60 No paid sprint by day 60: narrow the offer or drop the Hedge 8 weeks
E3 Publish three short pieces on what it takes for operations teams to trust AI tools, and give one talk at an industry meetup Two conversations started by the target buyers themselves by day 90 None by day 90: stop publishing and move the time to E1 12 weeks

Runway check at day 60: if E1 and E2 both hit their kill signals, he widens the target group before money becomes the deciding factor.

What the lab does not do: promise a job in a set number of weeks.


What happens in the lab

These sketches become decision-grade artifacts in six weeks.


Prepared after the debrief. Preview.

See fees and terms →
How to start

Start with a conversation

Send a short message: what is shifting in your role, or what you are deciding next. You get a personal reply, not a sales sequence. If it is useful, the next step is your free Radar Snapshot.

OILOccupational Identity LabbyKamaraTech
OIL by KamaraTech · kamara.tech The demo cases and personas are fictional. Third-party figures are reported as published by their sources, with dates. OIL is professional development. It is not therapy, medical or legal advice, or a promise of employment outcomes. OIL PrimeDemo case fileFor organisationsContactKamaraTech homePrivacyLegal information