Sales and Support
The ticket already knows who is writing
A helpdesk that already knows the customer’s account, open project and unpaid invoice — in one query, not six. Same platform, same per-seat price.
The deal and the invoice are the same customer.
In most stacks they are not. The CRM holds the deal, the finance tool holds the invoice, and the only thing joining them is somebody typing the same numbers twice. Cyril treats them as one customer seen from two angles: a won deal’s lines carry into the estimate and the invoice instead of travelling through an export.
From won to paid, on one record.
In our demo workspace, Pemberton Foods signs on an ordinary Tuesday in August. Follow the deal’s line items into the invoice, and the payment back onto the account the pipeline is on.
- 1
The deal is won
Nina Whitfield moves the Advisory Engagement to Won. The amount and the lines were agreed here.
- 2
The invoice starts from the deal
The deal’s lines become an estimate, then an invoice. Same customer, same lines, same total, waiting for a person to send it.
- 3
Paid shows where the deal is
The payment lands on the same account the pipeline is on, so “what do they owe us” has one answer.
66,631.00Carried from the deal, never retyped
What that means on an ordinary Tuesday.
A won deal’s lines reach the invoice without re-entry
The line items and the customer are already on the deal. They become an estimate and then an invoice without retyping: same customer, same lines, same total.
Forecasting reads the live pipeline, not a copy of it
Pipeline forecasting reads your live deals, so it reflects what actually changed this morning rather than what last synced overnight.
One customer, so one answer to “what do they owe us”
The unpaid invoice is attached to the same account the pipeline is on. Nobody has to decide which system to trust, because there is only one place to look.
The AI can answer across both
Ask Cyril answers a question like “which accounts closed this quarter and have not paid” from your own deals and invoices, citing the records it read. In a two-tool stack that question is a project, so it gets asked quarterly at best.
What two separate tools do instead.
Two tools can be made to pass records to each other, and plenty of teams do it well. What a connector cannot create is a shared idea of what a customer is. So the CRM has its own notion of the account, finance has another, and the gap between them is filled by convention — a naming rule somebody remembers, a spreadsheet that maps one to the other, a monthly afternoon spent working out which is right. That is the cost the licence line never shows.
Whether this is for you.
A good fit if
You sell work and then bill for it, your invoices are built from what was agreed in a deal, and the person raising the invoice is not the person who closed it. That handover is where the re-keying and the disagreements live, and it is what one record removes.
A poor fit if
Your billing is genuinely independent of your pipeline — high-volume transactional invoicing, or a finance function with its own system of record it will not move. The seam this page removes is not the seam costing you money.
What this does not do yet.
Cyril is pre-launch, so the useful thing to publish is the edge of what exists rather than a roadmap. If one of these is a hard requirement, say so early and we will tell you plainly whether to wait.
- It is not a general ledger, and is not trying to be. Bookkeeping, tax filing and statutory accounts stay with your accountant; exports exist for that handover.
- Revenue recognition beyond straightforward invoicing and forecasting is not covered. If you need deferred revenue schedules, treat that as absent.
- Multi-entity consolidation is not something to plan around today.
The modules this uses.
Both are part of the platform at one per-seat price — there is no bundle to assemble and no connector to buy. Each page below covers what that module does on its own.
Common questions.
Does this replace my accounting software?
Not the ledger. It covers invoicing, payment capture, expenses and forecasting on the same records as your sales and delivery work, and exports for your accountant. Bookkeeping and filing stay where they are.
What if we already have a finance tool we like?
Then the honest answer is that the gain here is narrower for you. The argument on this page is about removing the seam between two systems; if you keep a separate finance tool, the seam stays and something has to maintain it.
Is invoicing a separate cost?
No. Pricing is per staff seat and includes every module, with no base platform fee and no per-app upsell. Client portal users are free and unlimited.
Two more hand-offs
How it fits togetherSales and Projects
What you sold and what you are delivering are one thing
A CRM where the closed deal becomes the project, and tasks roll up to the customer they are for. One graph, one permission model, per seat.
See it on your own data.
Cyril is pre-launch and opening early access through a waitlist. No self-serve signup yet, and no published customers — if you want the honest version of where it is, ask.
