Everything your business runs on, in one place.
The everyday tools your team opens each morning, the apps your business adds on top, and an AI underneath that can work across all of them. Nothing to integrate, because nothing was ever separate.
Five kickoff workshops, two overdue invoices, and one open ticket from Calder & Voss.
Look closer at any of it.
What each part actually does, and how it uses everything around it. Three layers, one set of records.
Everyday
Where the day starts. Part of the operating system, not an add-on.
- MailYour inbox, with shared and team mailboxes. Cyril reads context from the rest of the business before you reply.
- DriveMy Drive and Shared Drives for the whole company, with retention and legal holds built in rather than bolted on.
- DocsOrganisational memory. Write it once and every other part of Cyril — and its AI — can draw on it.
- CalendarOutlook calendar sync, with Google Calendar in beta, and aware of the deals, projects and tickets a meeting is actually about.
Apps
Turn on what you need. Each one already knows your people, customers and documents.
- SalesAccounts, contacts and deals, for B2B or B2C.
- ProjectsDelivery that starts where the deal closed.
- SupportTickets and a client portal that already know the customer.
- FinanceInvoicing, payments, expenses and forecasting.
- MarketingCampaigns, lists and segments, sent to your Sales contacts.
Six more, on the same records
Same people, same customers, same permissions.
- ReportingRevenue, pipeline, invoice ageing and customer health, read from the source.
- HRPeople, hiring, onboarding, reviews and time off.
- LegalContracts, signatures, obligations and renewal dates.
- ProductsOne catalogue that deals, estimates and invoices share.
- TechnologyIn developmentAn IT desk, devices, software licences and access.
- Client portalTickets, invoices, documents and projects for your clients. Portal users are free.
Underneath
Shared by everything above. Nothing to integrate, because nothing was ever separate.
- Ask CyrilThe foundation under every app — not a bolt-on module. It plans, shows the plan and waits for you.
- AutomationTriggers, conditions and actions across Sales, Finance, Support, Projects and more. Your rules, run every time.
One graph underneath all of it.
Everything above works because none of it is really separate. That is the whole trick, and it cannot be retrofitted.
One data graph
A single schema spans everyday and apps alike. A question can cross any boundary because nothing is siloed.
Every record explains itself
Each entity exposes a machine-readable view built for a model, not a database — enums resolved, relations folded in, internals stripped.
One permission model
An agent is a caller, not a god mode. Each step it plans is checked on the server against the asking person’s permissions before it runs.
Every AI run on the record
Every Ask Cyril run is recorded: the plan, who approved it and what each step did.
One customer, seen from four apps.
In most stacks the CRM, the project tool, the helpdesk and the finance tool each keep their own copy of Kestrel. In Cyril there is one record, read from four angles, so nothing has to be typed twice or kept in step.
- SalesAdvisory EngagementFixed Price, added 31 Aug 2026Won
Sales holds what was agreed.
- ProjectsAdvisory EngagementDeadline 20 Oct 2026In Progress
Projects starts from the deal, not a summary of it.
- Support#13 Request for a project updateAnswered by Claire DonovanResolved#7 Meeting rescheduleOpened in the client portalPending
Support sees the project and the invoice on every ticket.
- FinanceROWA-100159,085.00, due 30 Sep 2026Draft
Finance reads the amount and lines from the deal itself.
Ask Cyril can answer across all four in a single query, inside the permissions of whoever asks.
How Ask Cyril worksSee it on your own data.
Cyril is pre-launch and opening early access through a waitlist. If you want the honest version of where it is, ask.
One email when your place opens. Nothing else.
