Nova · Business to Business

Turn any business into an agentic operation.

Nova B2B is an event-driven ambient agent platform that transforms existing business workflows into agent-augmented processes. Not a chatbot bolted on the side — a re-architecture where events, agents and skills replace the manual handoffs that slow every team down.

The problem it solves

Every business today runs on workflows — CRM cases, support tickets, marketing campaigns, developer stories, finance approvals, admin requests — and every workflow is punctuated by humans doing repetitive, low-judgement steps. Even after decades of SaaS, most enterprise time is still spent moving information around, not deciding on it.

Nova B2B replaces those in-between steps with ambient agents — event-triggered workers that understand a specific role, pick the right skill, and execute. Humans stay in the loop where judgement matters; agents handle the rest.

What we deliver

Business mapping
We start with your existing workflows — CRM, support, marketing, ops. Identify every role, every handoff, every recurring task. Nothing goes in until we know what would actually change.
Role-shaped agents
One agent per role. A marketing agent behaves like a marketer; a support agent behaves like a support engineer; an admin agent behaves like an admin. They know your process, your tools, your terminology.
Skills library
Agents draw from Nova's existing skills catalogue — docs, email, spreadsheets, browser, CRM APIs, ERP hooks — plus role-specific skills we build for you.
Event fabric
Every meaningful thing in your business — a new lead, a closed ticket, a signed contract, a failing metric — becomes an event. Agents subscribe and react. Chains of agents form workflows automatically.
Human-in-the-loop
Where judgement, approval or empathy matters, the agent hands off to the right human. Not a fake "are you sure" prompt — a real, richly-contextualised handoff.
Consulting engagement
Not a product SKU. Nova B2B is a transformation engagement — we scope, design, implement, measure and hand over. Priced against outcomes, not seats.

Where it lands

CRM transformation
Lead routing, follow-up drafting, meeting prep, deal-desk answers, forecast hygiene — the 60% of sales-ops time nobody actually enjoys.
Support at scale
Ticket triage, knowledge-base search, first-response drafting, escalation routing, root-cause summaries. Humans handle the hard 20%.
Marketing ops
Campaign brief → asset draft → approval loop → deploy → measure. Every step an agent, every handoff an event, every asset in the right tool.
Engineering ops
Backlog grooming, PR triage, incident summaries, deploy notes, on-call handovers — the coordination tax on every dev team.
Finance & admin
Invoice ingest, approval routing, vendor onboarding, expense checks, contract review. Boring, high-volume, high-error today; near-zero-touch after.
Custom vertical flows
Every business has processes no SaaS covers. Agents can be shaped around them — because agents don't require a whole product to exist.
The point isn't to replace people. The point is that most business time is spent moving information, not creating it. Nova B2B moves the information, so your people can create.

Three-tier architecture

Nova B2B is built around a strict three-tier separation: events at the top, agents in the middle, skills at the bottom. This is what makes the system composable — new events don't require new agents, new agents don't require new skills, and a change at one tier doesn't ripple through the others.

Tier 1 · Events lead.created CRM webhook ticket.opened Zendesk campaign.due scheduler deal.signed Docusign … N more any system Tier 2 · Agents · role-shaped Sales agent follow-up · quals · CRM ops Support agent triage · draft · escalate Marketing agent brief · draft · deploy Ops / admin agent invoices · approvals … Tier 3 · Skills · shared library docs docx · pdf email draft · triage spreadsheet xlsx · csv browser any web tool system APIs CRM · ERP · ITSM custom agent fires next event
Events fan into agents · agents pick skills · agents complete tasks and fire new events (dashed) — chains form without explicit orchestration

How a workflow forms

  1. An event fires. Something meaningful happens — a lead comes in, a ticket opens, a report is due.
  2. The event routes to an agent. Which agent? The one whose role owns that event type. Sales agent handles lead.created. Support agent handles ticket.opened.
  3. The agent picks skills. The agent already knows what the task looks like in context — draft an email, update a CRM record, generate a slide, read a PDF. It reaches into the shared skills library.
  4. The agent completes and emits. When the task is done, the agent fires a new event. That event might trigger another agent. Chains form organically — you didn't hard-code a workflow, you configured the participants.
  5. Humans stay in the loop. Any agent can escalate to a person with full context — one click to approve, edit, or override.
The value of the three-tier separation: adding a new business system (event source) doesn't require a new agent. Adding a new agent role doesn't require new skills. Adding a new skill lifts every agent that could use it. The system compounds.

Delivery model

  • Discovery (2–4 weeks). Map current workflows, identify highest-leverage automation targets, agree on the first three agents.
  • Build (6–12 weeks). Implement events, agents and any missing skills. Deploy to a staging environment inside your VPC or ours.
  • Ramp (4–8 weeks). Gradual rollout, human-in-the-loop mode first, measured against baseline productivity.
  • Handover. Full ownership of the agent fleet, or ongoing managed service — your choice.