§ 02Who it’s for

One product. Three groups who need faster answers.

Customers & users

Ask, wait, leave.

They ask the same questions again and again. If the answer takes too long, they leave.

Developers & partners

Dig, then wait.

They search static docs, file issues for things already written down and wait for your team to reply.

Your own team

Three tools, four answers.

They search too many tools for one policy and still get different answers.

§ 04Use cases

Four teams. Four reasons to sign.

Head of CX · COO

Customer support

Fast answers in 50+ languages, with human handoff when it matters.

DevRel · CTO

Developer & API docs

Answers inside the IDE, the docs and community Slack.

COO · People · IT

Internal knowledge

One place for policy, onboarding and process questions.

VP Sales · CPO

Sales & product-led growth

Answer pre-sales and activation questions the moment they’re asked.

§ 06For the CFO

Where the savings come from.

Headcount & people

Delay the next 1-5 support hires as repeat questions drop.

40-60% of L1 agent cost

Tooling

Fewer helpdesk seats and fewer separate knowledge tools.

~$1,200 per seat saved

Facilities

Less contact-centre space, hardware and telephony per seat.

$6–15K per seat / year

Engineering

Give engineers back time spent answering docs questions.

$60–90/hr reclaimed

§ 07Pricing

Priced to start small, built to scale.

Starter

$149/mo

Get started with an AI agent.

~65-200 conversations/mo
4,000 credits · 1 project
Chat widget
Basic analytics

Answer support questions from your docs.

Pernoex answers in chat, email, voice, Slack and the IDE, with a source on every answer.

pernoex.comBuilt on ClaudeUK-headquarteredGlobal

§ 02Who it’s for

One product. Three groups who need faster answers.

Customers & users

Ask, wait, leave.

They ask the same questions again and again. If the answer takes too long, they leave.

Developers & partners

Dig, then wait.

They search static docs, file issues for things already written down and wait for your team to reply.

Your own team

Three tools, four answers.

They search too many tools for one policy and still get different answers.

§ 04Use cases

Four teams. Four reasons to sign.

Head of CX · COO

Customer support

Fast answers in 50+ languages, with human handoff when it matters.

DevRel · CTO

Developer & API docs

Answers inside the IDE, the docs and community Slack.

COO · People · IT

Internal knowledge

One place for policy, onboarding and process questions.

VP Sales · CPO

Sales & product-led growth

Answer pre-sales and activation questions the moment they’re asked.

§ 06For the CFO

Where the savings come from.

Headcount & people

Delay the next 1-5 support hires as repeat questions drop.

40-60% of L1 agent cost

Tooling

Fewer helpdesk seats and fewer separate knowledge tools.

~$1,200 per seat saved

Facilities

Less contact-centre space, hardware and telephony per seat.

$6–15K per seat / year

Engineering

Give engineers back time spent answering docs questions.

$60–90/hr reclaimed

§ 07Pricing

Priced to start small, built to scale.

Starter

$149/mo

Get started with an AI agent.

~65-200 conversations/mo
4,000 credits · 1 project
Chat widget
Basic analytics

If it answers,
it should show the source.

Answer support questions from your docs.

Your docs have the answer. Your customers just can’t find it.

One product. Three groups who need faster answers.

Connect once.
Answer everywhere.

One knowledge base. Six places to answer.

If it answers,
it should show the source.

Four teams. Four reasons to sign.

Better support. Fewer agents. Lower cost.

Where the savings come from.

Priced to start small, built to scale.

See Pernoex answer from your docs.