Platform

From first opportunity to delivered outcome.

The Systeni AI Platform is a system of specialised agents built to find work, talk to customers, qualify and propose, build and verify, deliver and keep improving — while people decide strategy, access, budgets and every important step. It is in pre-launch.

Pre-launchApproximately 70% complete, based on our internal roadmap.

Mission Control

Simulation · illustrative data

Mission Control

Choose a scenario. Specialised agents take one step each and hand the work on — until a decision waits for a person.

What comes in

“Can you build a portal for our 40 service partners by spring?”

The agents
  1. Win the work
    • Discover
    • Communicatewaiting
    • Qualifywaiting
    • Proposewaiting
  2. Build it
    • Build
    • Verify
  3. Run it
    • Deliver
    • Operate
    • Improve
Hand-offs
  1. Communicatewaiting
  2. Qualifywaiting
  3. Proposewaiting

Nothing goes out until a person decides.

A simulation of the planned platform: agents, data and results are illustrative and come from no customer.

What is real today

Counted from the capability ledger behind the trust centre. A capability counts as live only when a named check has proved it against production.

Implemented and verified

25
  • Tenant isolation
  • Accounts, sessions and one-time links
  • Roles and capabilities
  • Rate limiting
  • Audit trail
  • Backups and restore
  • Execution engine
  • Workflow editor
  • Model qualification
  • Inbound endpoint
  • Policy engine
  • Approval gates
  • Handover to a person
  • Outbound email
  • Connections to other systems
  • Google Workspace
  • Knowledge base
  • Phones and installed use
  • Browser-side hardening
  • Handover — a copy the customer runs
  • Who operates it, in law
  • Data requests and deletion
  • Operator console
  • Twenty languages
  • Health and watchdog

In development

18
  • Step library
  • Authoritative pricing
  • The quote a customer can inspect
  • Invoices with seller, buyer and VAT
  • Why did that happen
  • Being shown round
  • Channel adapters
  • Subscriptions and checkout
  • CRM and calendar adapters
  • Before, after, and permission to say so
  • Deals and campaigns
  • The public site in search
  • Site measurement without identifying anyone
  • Systeni's own articles, case studies and newsletter
  • Academy and certification
  • Partner programme
  • Public API and outbound webhooks
  • Two-factor authentication

Planned

1
  • SSO and SCIM

The platform as designed

What follows shows how the parts are meant to work together. What runs today, what is in development and what is planned is listed above, each with its evidence.

Architecture

What is actually in the box.

Architecture

Select a layer to see what it does and what it is made of.

Layer 1 of 6

Agents

A library of roles rather than a blank prompt. Each one has a defined input, a reasoning step you can inspect, actions it is permitted to take, and a threshold at which it stops and asks a person.

12 rolesInspectableEscalation rules
Inside the console

The product, up close.

Eight screens from the Systeni console, in the states a working day brings: a reply held for a person, a quote waiting for the owner, a run you can read step by step.

Example with sample data: the inbox, with an email from a customer and the reply the agent drafted, held until a person approves it, edits it or stops it.
Example with sample data: the approvals queue, with a quote above the owner's threshold and a customer's question the knowledge base did not answer.
Example with sample data: the knowledge base, with documents marked public or internal and an answer that names the document it came from.
Example with sample data: the website chat as a visitor sees it: the AI notice first, a question the assistant could not answer with confidence, and a person from the team taking over.
Example with sample data: the agent library: the one agent an execution path reaches, with what it may and may never do, and an agent that nothing runs yet.
Example with sample data: the launch checklist at 9 of 12: two checks still stop this workspace going live, and one it can start without.
Example with sample data: the execution record of one enquiry: six steps in order, what the policy engine said where it was asked, and who released the reply it held.
Example with sample data: a week of opening hours with the appointments booked inside them, and the next three visits.

These are examples with sample data. The business, the people, the messages and the figures are invented for this page; the screens, states and controls are the ones in the console.

AI agents

Every agent is a job somebody is doing by hand.

Not a personality — a defined role with an input, a reasoning step, a permitted set of actions and an output somebody would otherwise have produced. Select one to see how it thinks.

Sales Agent

Answers, qualifies and routes every inbound lead

Sales
  1. Input

    Website chat, email, forms

  2. Reasoning

    Scores budget, timing, fit and intent against your qualification rules

  3. Actions
    • Answers instantly
    • Asks qualifying questions
    • Scores and routes
    • Books the meeting
  4. Output

    A qualified lead in the CRM with the transcript attached

Business value

Reps open only the conversations worth their time

Automation engine

What happens between the enquiry and the invoice.

Each step is a block you can open, reorder or remove. Nothing is a black box, and nothing reaches a customer before you have watched it run in test mode.

Automation engine
  1. Lead arrivesWebsite chat, web form or email
  2. AI qualifiesBudget, timing, fit, intent — scored
  3. CRM updatedRecord created, deduplicated, enriched
  4. Meeting bookedStraight into the right calendar
  5. Proposal generatedYour rate card, your terms
  6. Email sentTracked, with follow-up scheduled
  7. Tasks createdAssigned by skill and territory
  8. Invoice preparedHeld for one-click approval
  9. Management notifiedOnly the exceptions
  10. Dashboard updatedBefore anyone asks for a number
Integrations

Keep your stack. Lose the copying.

Today, connecting Systeni to the systems your team already uses is an engineering project we build for you; standard connectors have not shipped yet. The status of each is on the homepage, and Studio builds any of them as a scoped engagement.

Communication

Not shipped
  • WhatsApp Business
  • Instagram
  • Slack
  • Microsoft Teams
  • Gmail
  • Outlook
  • SMS
  • Telephony (SIP)

CRM & sales

Not shipped
  • HubSpot
  • Salesforce
  • Pipedrive
  • Zoho

Calendar & scheduling

Not shipped
  • Google Calendar
  • Microsoft 365
  • Calendly

Finance

Not shipped
  • Stripe
  • Lexoffice
  • DATEV
  • Xero
  • QuickBooks

Commerce

Not shipped
  • Shopify
  • WooCommerce

Data & automation

Not shipped
  • Webhooks
  • REST API
  • Zapier
  • Make
  • Postgres

Anything not listed connects through the REST API and webhooks. Bespoke integrations are available as a scoped, quoted service.

See it configured for your business.

The Blueprint takes about twenty minutes and tells you which of these six parts is worth switching on first.