Kigan mark
KIGANStudios & Platform
Loading

Kigan 2.0

An AI-native professional services company built around Studios and a shared intelligence Platform.

How Kigan works

Specialised AI does the heavy lifting. I stay accountable for the judgment, evidence, and outcome.

“Kigan is not AI for its own sake. It is a way to turn focused capability into better business outcomes.”

Studios · Shared platform · Human accountability

Common starting points

Unclear offer or brand direction

Brand Studio

Manual handoffs eating time

Workflow Studio

Useful content not creating pipeline

Growth Studio

Knowledge scattered across tools

Platform

Studios

Focused Studios, one shared operating system.

Kigan is built as a small AI-native services company: each Studio focuses on a business outcome, while the Platform carries the evidence and learning forward.

Active

Brand Studio

Discovery, positioning, messaging, identity direction, and brand systems for businesses that need clearer market shape.

Good fit when the business is changing faster than the way it explains itself.

Active

Workflow Studio

Review-gated AI workflows, scoped integrations, and agent systems built around the tools a business already uses.

Good fit when manual handoffs, repeated decisions, or scattered tools are slowing the work down.

Emerging

Growth Studio

Content, lead generation, marketplace offers, newsletters, and sales support systems that turn learning into pipeline.

Good fit when useful thinking exists but is not yet becoming consistent demand.

Shared

Kigan Platform

The memory, evidence, decisions, reusable tools, and operating context that let each Studio improve the next one.

Good fit when knowledge is spread across people, files, chats, and tools with no reliable centre.

Start here

Choose the problem, not the technology.

Two small first engagements for making the next decision clearer. Each starts with evidence, keeps consequential choices human-approved, and leaves a useful artefact behind.

Brand Studio

Brand Clarity Foundation

For when

You are doing good work, but the offer is hard to explain or apply consistently.

You leave with

A clear, evidence-backed foundation for what you do, who it is for, and how to say it before investing in a larger build.

  • A clarified offer and audience direction
  • Core positioning and messaging guidance
  • A practical foundation for future design, copy, or website work

Human approval: You approve the direction, claims, and language before anything is treated as final.

Not included by default: Not a finished website, campaign, visual identity, or promise of commercial results.

Ask about Brand Studio

Workflow Studio

Workflow Proof Plan

For when

One repetitive, messy workflow is absorbing attention and you need to know what is worth changing first.

You leave with

A grounded view of the current workflow and a scoped recommendation for where AI or automation may help safely.

  • A current-state workflow map
  • The data, tools, decisions, and handoffs involved
  • A scoped proof or pilot design where the evidence supports it

Human approval: You approve access, boundaries, risk tolerance, and any move from design into a controlled proof or pilot.

Not included by default: Not an autonomous system, broad integration programme, or production deployment by default.

Ask about Workflow Studio

Platform

The part that makes Kigan compound.

The Platform is not a product pitch yet. It is the operating layer behind the Studios: the place where knowledge, judgment, proof, tools, and delivery patterns are captured so each project leaves Kigan stronger than it found it.

Operating loop

01Client work
02Evidence
03Decisions
04Reusable tools
05Next Studio engagement

Memory

Shared context keeps decisions, client work, and reusable methods from disappearing between tools.

Evidence

Outputs are tied back to files, checks, source material, and review notes wherever the work allows it.

Tools

Agents, automations, prompts, code, and templates are improved as reusable capabilities instead of one-off tricks.

Governance

AI can prepare, compare, and execute scoped work. People approve money, legal, compliance, payroll, and public claims.

A delivery model built around earned trust.

01 · Discover

I clarify the business outcome, the people involved, the evidence available, and the decisions that cannot be guessed.

02 · Shape

I choose the Studio path, define the system, and mark where AI can move quickly and where human approval stays required.

03 · Prove

I build a focused artifact or workflow, test it against real material, and keep claims tied to what the work actually shows.

04 · Evolve

I feed what worked back into the Platform so future Studio work starts with better context, tools, and judgment.

Proof in progress

Show the artifacts before claiming the category.

Kigan does not need inflated case studies to sound credible. It needs visible artifacts, careful claims, and a clear distinction between what can be inspected now, what is in active use, and what is still being tested.

Available to inspect

Brand system

The public site, logo system, colour tokens, typography rules, and reusable brand references are working artifacts, not a future promise.

In active use

Client discovery framework

Discovery, strategy, messaging, quality checks, and client handoff patterns are being shaped through real work and can be explained on request.

Testing in public view

AI Platform spike

The platform work is being tested through evidence, decisions, workflows, and architecture spikes before broader claims are made.

Public first-party work

Newsletter Automation

Kigan first-party public work: a draft-first workflow for sourcing, branded copy, assembly, and Gmail draft creation for review.

Inspect the public repository (opens in a new tab)

Hermes Agent Framework

Kigan first-party public work: inspectable orchestration, planner architecture, workflows, and safety documentation.

Inspect the public repository (opens in a new tab)

n8n Security Automation

Kigan first-party public work showing structured security automation with explicit authorization boundaries, reusable workflow definitions, validation gates, and controlled automation pipelines. The example is security-focused; the transferable evidence is governed workflow engineering and checking discipline.

Inspect the public repository (opens in a new tab)

“Agents prepare. Systems enforce. Humans approve the decisions that cannot be delegated.”

Kigan operating principle

Bring me the problem worth solving.

A short conversation is usually enough to tell whether this belongs in Brand Studio, Workflow Studio, or nowhere yet.

Send the messy version. I'll help shape the question before we decide what to build.

Email me directly