Starting and growing the service

01 · HOW A CLIENT ENGAGEMENT BEGINS

Begin with one customer question.

Example entry questions a partner can qualify with a client:

  • What is validating access against this exposed edge profile?
  • Can we create an internal high-confidence signal without touching production?
  • What does an operator do after access to a controlled target?
  • Can we turn observed behavior into detection content for this client?
Qualifyclient question
→
Chooseprofile + exposure
→
Deploylive in hours · one path
→
ReviewFindings + service value

OHIIHO deploys the Surface in hours; your team runs the service, with OHIIHO’s enablement behind it.

02 · THE FIRST ENGAGEMENT

The engagement starts with a conversation.

Each partner engagement starts with a conversation about the client question, the team and the workflow it already runs, and is built around one defined Surface mission and one workflow destination.

Surfaceone mission, one exposure profile, one workflow destination.
Enablementinitial training, runbook, analyst workflow and scheduled reviews.
A good startSurface deployed; collection confirmed; Finding path demonstrated; partner analysts trained; client offer defined.
03 · ENABLEMENT & TRAINING

OHIIHO enables the partner to offer, deploy and run the service.

The enablement path moves from commercial orientation (what the partner can offer and to whom), through architecture orientation (Surface, targets, boundaries and deployment) and SOC workflow (Finding triage, investigation and escalation), to presales proof (Research evidence, diagrams and objection handling) and service readiness (runbook and reporting cadence).

04 · BUILDING THE SERVICE

A Surface supports a recurring service.

Preventive signalearly alerts
→
Deeper engagementbehavior
→
Investigation + detectiondefensive content
→
Recurring briefingsdelivered by your team

Services a partner can build around a single Finding: detection tuning, threat hunting, purple-team validation, incident-readiness review, CTI briefing, executive risk update, or an additional edge or internal Surface mission. Resale rights are set by the partner agreement.

05 · CLIENT REPORTING

Two views of the same activity.

Analyst view
Observed facts, Finding details, session or artifact links where available, and the recommended hunt or triage action.
Executive view
What happened, why it matters, its relevance to the client, what the team did next, and the limitations and confidence attached.

The partner turns the same first-party material into operational and executive value, without changing the facts between views. This is a reporting practice, not a universal automatic briefing generator.