The app you need might not exist yet.
In development: describe a tool in plain words, Cyril drafts it on sample data, and a person reviews it before it goes live. The builder isn’t part of early access.
How it will work, in five steps
Describe it.
Choose what kind of tool it is, then say what it’s for. Claire wants to track site visits on each client engagement.
No forms to design and no fields to name. Plain words are enough.
Track site visits for each client engagement. Who went, when, what the visit was for, and whether anything needs following up.
Cyril proposes it.
A first version comes back: the fields, the views, and where it will sit in Cyril. Ask for changes in the same conversation.
Claire asks for purpose to be a fixed list. It is, a moment later.
Here’s a first version: seven fields and three views.
Done. Kickoff, Review, Audit or Handover.
| Field | Type | Rule |
|---|---|---|
| Engagement | Text | Required |
| Client | Text | Optional |
| Visit date | Date | Required |
| Visited by | Person | Defaults to you |
| Purpose | Choice | Kickoff, Review, Audit, Handover |
| Notes | Long text | Optional |
| Follow-up needed | Yes or no | Defaults to no |
Try it on sample data.
The draft runs in a sandbox filled with made-up records shaped like yours. Click around, add a visit, check the views.
Your real records are never sent to the AI while a tool is being built.
Site visits
New visit| Engagement | Visit date | Visited by | Purpose | Follow-up |
|---|---|---|---|---|
| Northgate Co.SampleOperating review | 12 Oct | DHDana Hart | Review | Needed |
| Brightwater LtdSampleCost programme | 9 Oct | LMLeo Marsh | Kickoff | None |
| Harbour & PineSampleSystems audit | 3 Oct | AOAma Owusu | Audit | Needed |
| Fenwick LabsSampleHandover | 28 Sep | DHDana Hart | Handover | None |
| Morrow & LaneSampleQuarterly review | 21 Sep | LMLeo Marsh | Review | None |
It’s reviewed before anyone uses it.
Every tool is approved by the Cyril team before it can go live. Then someone at Rowan Hill with permission to publish decides who gets it.
Change a live tool later and it comes back here for review. Earlier versions are kept.
- Placement
- Tools, Site visits
- Shared with
- Delivery team, everyone at Rowan Hill
- Clients in the portal
- Off
It’s part of Cyril now.
Site visits appears in the sidebar for Rowan Hill only. Only people it is shared with can open it, and every step is recorded, with who did it.
The visits are real now: Kestrel, Ridgeline, Halloway. Nobody had to wire anything up.
Site visits
| Engagement | Visit date | Visited by | Purpose | Follow-up |
|---|---|---|---|---|
| Kestrel Freight SystemsAdvisory Engagement | 24 Sep | MBMarcus Bell | Review | Needed |
| Ridgeline Property TrustAdvisory Engagement | 18 Sep | NWNina Whitfield | Kickoff | None |
| Halloway Dental GroupAdvisory Engagement | 11 Sep | OROwen Reed | Audit | Done |
| Pemberton FoodsAdvisory Engagement | 4 Sep | CDClaire Donovan | Handover | None |
Start from a shape, not a blank page.
Each kind of tool has its own builder, and a builder can only make its own kind. The choice you make first is the boundary.
- CalculatorInputs, a formula, a result
- Quotes, fees, estimates. The formula is a set of rules Cyril checks and runs, never code that an AI wrote.
- Fixed-fee estimateDays18Day rate1,450.00Expenses6%Fee27,666.00
- ReportCharts and tables
- Pick Sales, Products or Marketing records, filter and group them, choose a chart. It reads live, and only for people whose role can open that app.
- Open deals by owner2 deals
- Internal appYour own records
- Fields, records and views for the thing your team tracks in a spreadsheet today, kept in Cyril beside everything else.
- Site visitsKestrel Freight Systems24 Sep, Marcus BellReviewRidgeline Property Trust18 Sep, Nina WhitfieldKickoffHalloway Dental Group11 Sep, Owen ReedAudit
Nothing goes live because an AI decided it should.
Building a tool is a conversation. Putting it in front of your team is a decision, and people make it.
- Built on sample dataThe sandbox is filled with made-up records. Your real records never reach the AI while a tool is built.
- Reviewed before it goes liveEvery tool is approved before it publishes. Edit a live one and it goes back for review.
- Your permissions, not the tool’sA tool reads with the permissions of whoever opens it. If you can’t open Sales, you won’t see Sales data there.
- Reads, never rewritesIn this version tools keep their own records and never change a project, a client or an invoice.
- Logged like everything elseSubmitted, approved, published, edited: every step is recorded, with who did it.
You decide who builds, and who sees it.
Building, submitting and publishing are separate permissions. A team lead can build and submit; publishing can stay with your admins.
Share a tool with a person, a team or everyone. Turn on client access and it is listed in their client portal; running it there comes later.
| Area | Build | Submit | Publish |
|---|---|---|---|
| Custom tools |
Not in this version.
We’d rather you knew now. These are planned, not built.
- Tools that change your core recordsA button in a tool that updates a deal or raises an invoice.Planned
- Public web apps on your websiteListings on your own site, fed by your records.Planned
- Tools that run on a scheduleA nightly roll-up or a weekly summary, run without anyone clicking.Planned
Build the tool your team keeps asking for.
Cyril opens to founding members first. They keep their price and get help moving in.
One email when your place opens. Nothing else.
