What we build
AI agents with a role, a scope and a place in your organisation.
Not a chatbot bolted onto a website. Each agent is designed for a specific kind of work, connected to the systems that work touches, and limited to what it is allowed to do.
Areas
Where agents earn their place.
Areas we build in — not packages to pick from. The right combination depends on your business, and we say so when an agent is not the answer.
Sales
Agents that qualify inbound requests, keep the CRM current and hand warm conversations to your team with context attached.
Customer support
First-line answers grounded in your own documents and policies, with clear escalation to a person when the agent should not decide.
Operations
Routine coordination — status checks, reminders, follow-ups, hand-offs between systems — run on a schedule or on events.
Research
Structured reading and summarising of documents, listings, tickets or reports so people start from a brief, not from raw material.
CRM
A native CRM on the platform, or agents working through your existing one: contacts, leads, deals, notes and tasks kept in order.
Back-office
Document handling, data entry between tools and internal requests, with approval steps where money or commitments are involved.
Custom workflows
Multi-step flows that combine agents, tools, conditions and human approval — designed for one business, not chosen from a menu.
Anatomy of an agent
More than a prompt.
Every Noro agent is a folder of real files on our platform. The interface edits those files; engineers can edit them directly. Both see the same thing.
- 01
Instructions
What the agent is for, how it speaks, what it must never do — written and versioned as a file.
- 02
Knowledge
Your documents, policies and product data, indexed so the agent answers from your material and cites it.
- 03
Tools
The actions it may take: read a record, create a lead, send a message, call an API — each with a risk level.
- 04
Permissions
Per tool: autonomous, approval required, or restricted. Money and commitments always get a person.
- 05
Memory
What it keeps between conversations, scoped to your workspace and never shared with another client.
- 06
Relationships
Who it reports to, whom it can delegate to, and when it hands off to your team.
Agents together
Agents that work with each other, not just with you.
A supervising agent can route work to specialists and collect results; a specialist can hand back when a case is outside its scope. Hierarchy says who oversees whom; workflows say what happens in which order. We design both.
What an engagement is designed to include
Noro’s platform is built out in stages. At scoping we say which of these is live for you on day one and which arrives with a later release.
- A written map of the work before any agent is built
- Agents with instructions, knowledge, tools and permissions you can read
- Development, test and production environments per agent
- Human approval steps wherever an action has consequences
- A client login to see runs, leads, usage and bills
- Ongoing operation: monitoring, adjustments, reporting