Powered by AI.
Run by humans.

We design and build AI agents, client portals, internal tools and websites.

NEXIRT Copilot
⏎send⇧+⏎newline

Encrypted in transit · never used for training · reviewed by an engineer · Privacy

(c) 2026 NEXIRT. NEXIRT robot created by Newton Cazzaro. All rights reserved. Licensing: https://nexirt.com/legal/robot
Anatomy of an agent

One request, from inbox to done.

Follow one sample enquiry through the six layers of a system we build.

Skip the walkthrough ↓
  1. All six layers

    One system, built around how your team already works.

    Six layers, from the channels your customers use to the AWS account it can run in.

    Status: Working

  2. Layer 1 of 6 · Channels

    An enquiry arrives through your website form.

    Forms, email and chat all arrive in one place.

    Trace: channel.receive

    Status: Working

  3. Layer 2 of 6 · Agent

    The agent reads it and works out the steps.

    It sorts the request and decides which steps to run.

    Trace: agent.route

    Status: Working

  4. Layer 3 of 6 · Knowledge

    It pulls the matching service notes and past conversations.

    It works from your own documents and history.

    Trace: knowledge.retrieve

    Status: Working

  5. Layer 4 of 6 · Tools & systems

    It checks CRM, calendar and payments, then drafts a reply.

    Tools are the systems you already use, called with the access you grant.

    Trace: tools.crm.lookup tools.calendar.check tools.payments.read tools.email.draft

    Status: Working → Draft · needs approval

  6. Layer 5 of 6 · Guardrails

    Nothing reaches a customer until a person approves it.

    You choose the checks; anything customer-facing waits for a person.

    Trace: guardrail.review human.approve

    Status: Draft · needs approval → Approved

    How we keep agents safe →
  7. Layer 6 of 6 · Your cloud account

    The reply goes out, and every step is logged.

    It can run in your AWS account, so the data and the audit log stay yours.

    Trace: channel.send audit.write

    Status: Approved → Done · logged

  8. All six layers

    One system again.

    A custom build starts with a 1–2 week Discovery Sprint: a working prototype and a fixed-price quote.

    Status: Done · logged

    Talk to an engineer →

    Example runs: Try another workflow

    A web-form enquiry arrives.

    Plays through the stack and stops for your approval.

Start with a conversation, not a contract.

You see a working prototype and a fixed price before you commit to a build.

  1. Talk to an engineer

    Tell us the problem. An engineer replies within one business day.

  2. Discovery Sprint

    One to two weeks with your team, for a fee agreed up front, ending in a working prototype.

  3. Fixed-price quote

    Scope, timeline and one number. The sprint fee counts toward the build.

  4. Build and launch

    Weekly previews, then a rehearsed launch with handover docs.

How the Discovery Sprint works

Built by us. Running today.

Client portal request page with sample data: an online booking request at 60% complete, with its status and timeline.
NEXIRT Copilot conversation with sample data: a visitor asks for online booking and the request is filed for the team.
Client portal · sample dataNEXIRT Copilot · sample conversation

Our client portal, the Copilot above and this website are NEXIRT builds.

See concept studies

See how it works

Tell the Copilot what you need. Engineers build it, AI does the routine work, and a person approves anything that reaches your customers.

Read the transcript

NEXIRT runs your website and your business email, and gives you one portal for everything in between.

Inside your client portal, tell the NEXIRT Copilot what you need. It drafts a plan and files the request.

Engineers build it. AI does the routine work, and a person approves anything that reaches your customers.

Powered by AI. Run by humans.

Tell us what slows your team down.

Talk to an engineer

Systems can run in your own AWS account, where feasible · Anthropic and AWS Bedrock don't train on your data · How we handle security →