packets.build

00 · AI AGENTS

AI that does the groundwork,your team makes the calls

Agents that know your organisation draft risks, suggest controls, tailor policies and answer questions about your compliance data, so your team spends its time reviewing, not starting from a blank page.

For AI-native, IT services, fintech and healthtech teams selling to enterprise.

Compliance · 3 agentsOnline
Risk generationjust now

First pass is ready. I drafted risks from your onboarding answers.

Drafted12 sample risks
Waiting for review
Control suggestionsjust now

I linked 3 controls to Sample Risk, taken from your own library.

Linked3 controls
Done
Policy tailoringjust now

I tailored Sample Access Policy to your company. It stays a draft until someone approves it.

TailoredSample Access Policy
Draft

1 waiting for review

  • AssistantA compliance assistant in every page of packets reads your risks, controls, tasks, policies and evidence, and can make changes when you ask.
  • ReviewGenerated risks wait in a review queue, and tailored policies stay drafts until someone approves them.
  • ScopeAgents work only inside your own organisation, and read Confluence, Notion and GitHub only when you connect them.

01 · WHY IT MATTERS

Most compliance work starts from a blank page

  1. Writing from scratch takes weeks

    A risk register, a control set and a full policy library are slow to draft, even with templates.

  2. Templates don't know your company

    Generic policies and risk lists need heavy rework before they describe how your organisation actually runs.

  3. Answers are spread across tools

    Finding which control covers a risk, or what a policy says, means searching several systems and documents.

02 · WHAT PACKETS IS

Agents built on your compliance data

packets agents use what your team has already told it: onboarding answers, your control library, your policies and the documents you connect. They draft risks and mitigations, suggest controls from your own library, tailor policy documents and draft your ISMS scope. The assistant in chat answers questions about your programme and makes changes when you ask.

It is part of the packets AI-powered Governance & Compliance Control Engine, so agent output lands in the same risk register, controls, tasks and policies your team works with. Agents draft and suggest. People decide what is right.

03 · HOW IT WORKS

From your context to approved work

  1. Tell packets about your company. Your team answers onboarding questions about the business, its vendors and how it runs.
  2. Agents draft the first pass. From those answers, agents draft vendors, risks and mitigation notes, and tailor your policy documents as drafts.
  3. Generate and link. Generate risks for your register, and get controls suggested from your own library when a risk is created.
  4. Ask in chat. Ask the assistant about your programme, or ask it to create or update tasks, controls and documents. Pick Confluence, Notion or GitHub to search them too.
  5. Review and approve. Generated risks wait in a review queue. Policies stay drafts until they are approved. Anything can be edited or regenerated.
Run 01 · onboarding to approvalLive

Agents draft

Your team decides

Your team decides · step 01

Tell packets about your company

Your team answers onboarding questions about the business, its vendors and how it runs.

onboarding.form3 answers

Company
Vendors you use
How you run
01 / 05

Agents draft and suggest. Generated risks and policy publishing need a person's approval. Other changes, such as suggested controls or edits you ask for in chat, apply directly, and your team can change them afterwards.

04 · KEY CAPABILITIES

What your team works with

ACompliance assistant

Chat on every page
Ask about your risks, controls, tasks, policies, evidence, vendors and frameworks from anywhere in packets.
Changes on request
Ask the assistant to create or update tasks, controls, documents and trackers.
Your documents in context
Attach documents to a conversation, or pick Confluence, Notion or GitHub to search and read, read-only.
01 / 05

05 · WHY PACKETS

AI drafts that lead to closed gaps

  • Many tools

    1. Draft
    2. Tailor
    3. Register
    4. Close gaps
    5. Expert

    Generate policies and risk lists from templates, and leave tailoring and follow-through to your team.

  • Consultants

    1. Draft
    2. Tailor
    3. Register
    4. Close gaps
    5. Expert

    Write your first policies and risk register by hand, often over weeks.

  • packets

    1. Draft
    2. Tailor
    3. Register
    4. Close gaps
    5. Expert

    Drafts from your own context into the register, controls and policies you work in, and helps you close gaps with an actionable workflow and a Compliance Lead inside your team.

Your Compliance Lead helps with judgement calls. packets supports expert judgement. It does not replace it.

06 · FRAMEWORKS

What agents draft against

  • ISO 27001

    Supported
  • SOC 2

    Supported
  • HIPAA

    Supported
  • GDPR

    Supported
  • ISO 42001

    Mapped

Framework template with requirements, controls and policies the agents work with.

ISO 42001. Framework template, plus AI governance controls that cite Annex A.

Listing a framework does not mean full coverage, certification readiness or guaranteed compliance.

07 · WORKS WITH

Sources the assistant can read

  • Confluence

    Search and read pages during chat. Read-only.

    Read-only
  • Notion

    Search and read pages shared with the integration. Read-only.

    Read-only
  • GitHub

    Search code and read files in connected repositories. Read-only.

    Read-only

08 · FAQ

Questions about AI agents

01What do the agents in packets do?

They draft risks and mitigations, suggest controls from your library, tailor policy drafts, draft your ISMS scope, add vendors from onboarding and answer questions about your programme in chat.

02Do agents act without anyone approving?

Some work needs approval: generated risks wait in a review queue and policies need approval before they are published. Other changes, like suggested controls or edits you ask for in chat, apply directly and can be changed afterwards.

03What data can the assistant see?

Your organisation's data in packets, documents you attach to a conversation, and Confluence, Notion or GitHub content when you connect them and pick them for a question. It cannot reach other organisations.

04Can the assistant change our Confluence, Notion or GitHub?

No. Those sources are read-only. The assistant can search and read them, nothing more.

05Are the controls it suggests made up?

No. Control suggestions come only from the control library in your packets account. Your team decides whether they fit.

06Does this replace a compliance expert?

No. Agents give your team a starting point. Your Compliance Lead and your team make the judgement calls.

09 · Keep exploring

Keep exploring

Stop starting from a blank page. Start closing gaps.

Talk to us about what packets agents would draft for your team.