Sonaris for AI consultants
Map a client's process on a canvas, turn the findings into playbooks they can search, sell the sprint as a fixed package and run the pilot as a project. A two-person consultancy, run from one workspace.
- Process maps from discovery workshops1 / 14Canvas
- Playbooks and engagements the client can see5 / 14FolioProjectsChatProfiles
- Packages, a site and a pipeline10 / 14CommercePaymentsSitesFormsCRM
- Lead to engagement to pilot, connected11 / 14Flows
An illustrative workspace. The business, people and figures are fictional.
Map the process before automating it
Discovery workshops happen on an infinite canvas: sticky notes for each step, connectors for hand-offs and notes for where the hours go. The canvas can stand alone or sit as a tab inside the engagement, next to the tasks it turns into.
- Shapes, sticky notes, images and connectors
- Free-standing or hosted inside a project
- Cards linked to the files they describe
Deliverables the client can actually find
Readiness reports, prompt playbooks and usage policies are pages in a folio shared with the client's team as guests, who comment inline but can't edit. Each engagement is a project with phases from discovery to training, and a chat room for the people doing the work.
- Pages that embed live tasks, files and forms
- View, comment or edit access per page, for guests too
- Project phases, owners and timelines
- Guests see their own engagement and nothing else
Approved uses
Drafting, summarising and searching internal documents with the approved assistant.
Customer data
Stays out of prompts unless the tool is on the approved list and the data is needed for the task.
Packages, a site and a pipeline
The readiness sprint, the pilot build and the training day are Commerce services with fixed scopes and milestone contracts. The Sonaris site publishes articles from a folio, a self-check form turns readers into contacts and deals, and a booking page takes the discovery call.
- Services, packages and contracts with milestones
- Publish a folio to your site, under a path or on its own
- Form submissions become a contact and a deal
- Booking pages on the same contact record
From self-check to signed sprint to live pilot
Flows reads the self-check answers and routes the deal, turns a won deal into an engagement with a contract and a client room, and, when the pilot phase starts, calls out over HTTP to the systems the pilot touches.
- Branch on any field, such as team size or process type
- Call out over HTTP when a step lives outside Sonaris
- Every run has a log, and limits stop a runaway flow
- Trigger · FormsReadiness self-check submittedwhen
- ConditionTeam size over 50if
- Action · CRMMove deal to “Discovery call”then
- Action · ChatPost to #pipelinethen
- Trigger · CRMDeal wonwhen
- Action · ProjectsCreate project from “Readiness sprint”then
- Action · CommerceContract from the deal valuethen
- Action · ChatOpen a room and invite the client teamthen
- Trigger · ProjectsPhase advanced to Pilotwhen
- Action · HTTPNotify the client's ticketing systemthen
- Action · PaymentsIssue the pilot milestone invoicethen
- Action · ChatPost the pilot plan to the client roomthen
Every engagement with its map, its playbook and its contract attached
The workshop canvas, the report, the client's questions, the contract and the pilot tasks all hang off one engagement, so the consultancy can run several at once without losing the thread of any of them.
Discovery
Report
Next
- CanvasWorkshop map: AP process
- FolioReadiness report shared
- FormsSelf-check: Tarn Housing, 140 staff
- CRMDiscovery call booked
- ChatBrightmoor CFO: “Let's pilot it”
- CommercePilot contract · £18,000
- Sites“Map first” article published
Start with one module. Add the rest as you grow.
Every module works with every other from the day you switch it on, and your data exports whenever you want.