The Nuncily platform
One workflow handed over end to end, set up for you, at a single monthly price. Best when your process is a request, a handful of exchanges, and a system to update.
Conversations to completion.
Nuncily takes a business request from the first message to a finished outcome — asking, checking, and acting across your systems — and brings in a person only when judgment is required. Run it on our platform, or have our team build the automation around your own process.
Hi — sending my Q2 records over
Thanks. I need three things for Q2: bank statement, expense log, and last quarter's invoices.
statement.pdf
The statement stops on 19 June — 11 days short. Send the rest?
A request doesn't finish itself.
Somewhere between the request and the result, a person is doing the same thing over and over.
A client sends what's needed. Half of it is missing. Someone asks for the rest. Nothing comes back for four days. Someone asks again. Something arrives, but it's in the wrong format. Someone asks a third time. It arrives. Someone checks it against what the process actually requires. Two more things are missing. Someone asks again.
None of this needs judgment. All of it needs a person's afternoon.
Chasing clients is the most expensive work you don't bill.
It never shows up as a line item. It shows up as late evenings, squeezed deadlines, and a team that can't take on more clients.
Hours lost every week
Every person on the team spends part of each week sending reminders, checking what arrived, and asking again.
Deadlines put at risk
When records arrive late, the work gets squeezed against the filing date, and penalties are one slip away.
Clients who feel chased
Repeated nudges strain relationships that should feel like support, not pressure.
Billable time given away
Qualified people doing admin is capacity the practice pays for and never bills.
Your team stops chasing. Your clients stop being chased.
How Nuncily works
Every request moves through the same loop, whether it's a two-message exchange or a week of back-and-forth.
Receive, understand, collect
A request arrives on whatever channel the customer already uses. Nuncily works out what outcome is actually being asked for, then asks for exactly what the process requires — nothing generic, nothing padded out.
Hi — sending my Q2 records over
Thanks. I need three things for Q2: bank statement, expense log, and last quarter's invoices.
statement.pdf
The statement stops on 19 June — 11 days short. Send the rest?
Clarify, validate, act
Anything ambiguous gets resolved in the same conversation. What comes back is checked against what the process actually requires, then Nuncily updates the systems the request depends on.
Nuncily
CRM
Billing
Practice mgmt
Helpdesk
Spreadsheets
Internal APIs
Verify, complete — or escalate
The outcome is checked before it's called done. The business gets a finished process, not another task — and when judgment is required, a person picks up the thread with full context, not a cold handoff.
- 11 complete
- 2 chased, awaiting reply
- 1 needs you — unusual expense
Watch a request arrive and leave finished.
Three requests, three channels, one loop. Pick a scenario and follow it through: what comes in, what Nuncily does with it, what goes back out, and which of your systems it writes to along the way.
Incoming
3- WhatsApp|Client
Hi — sending my Q2 records over
- WhatsApp|Client
Here's the first one
statement.pdf - WhatsApp|Client
Missed that — here you go
statement-june.pdf
Nuncily working
4- Engine|Nuncily
Outcome identified: Q2 record collection for one client.
- Engine|Nuncily
Checked against what the quarter requires. All three documents now cover the full period.
- System|Practice management
Documents filed against the client's Q2 record.
- Engine|Nuncily
Filed record re-read and checked before the outcome is called done.
Outgoing
3- WhatsApp|Nuncily
I need three things for Q2: bank statement, expense log, and last quarter's invoices.
- WhatsApp|Nuncily
The statement stops on 19 June, 11 days short of the quarter. Can you send the rest?
- WhatsApp|Nuncily
That's everything for Q2. Nothing further needed from you.
Stage
Loop complete
- 01Receive
- 02Understand
- 03Collect
- 04Clarify
- 05Validate
- 06Act
- 07Verify
- 08Complete
Connected systems
Practice managementupdated
Document storeupdated
Client recordupdated
A client sends their quarterly records on WhatsApp. Nuncily asks for what's missing, checks what arrives, and files it.
Use the platform, or have us build it.
Same loop underneath: ask, check, act, verify, and escalate only when it matters. The difference is whether your process fits a ready-made workflow or needs building around your systems.
Custom automation, built for you
Our team designs and builds automation around your own process and systems, starting with free proof on your own data and a guaranteed pilot. Best when the work is specific to how your business runs.
Quarterly filing became mandatory. The chasing didn't get any easier.
Since April 2026, HMRC has required UK sole traders and landlords above an income threshold to submit records quarterly instead of annually, under Making Tax Digital. The filing itself is largely automated. Getting the records isn't. Every quarter, practices spend unbilled hours asking clients for documents, re-asking for what's missing, and checking what comes back.
Nuncily receives the client's message on WhatsApp, asks for exactly what's needed, reads what arrives, asks about anything unclear in the same conversation, follows up with anyone who's gone quiet, updates the practice's systems, and hands back an exceptions list instead of a stack of unopened messages.
The same loop applies to onboarding, verification, claims intake, KYC, and renewals — any process built from a request, a handful of exchanges, and a system that needs updating once everything checks out.
Hi — sending my Q2 records over
Thanks. I need three things for Q2: bank statement, expense log, and last quarter's invoices.
statement.pdf
The statement stops on 19 June — 11 days short. Send the rest?
Automation executes steps. Nuncily owns the journey.
- A workflow tool runs the steps you've already defined.
- When a case doesn't fit the script, it stops and waits for someone.
- It hands back a task.
- Nuncily owns the outcome, not just the steps.
- When something doesn't fit, it asks, checks, or escalates — then keeps going.
- It hands back a finished result.
Client onboardingQuarterly filingVerification and KYCClaims intakeRenewalsRecord updatesBilling queries
However your customers already talk to you.
A request can start as a WhatsApp message, an email, a form on your site, or an event from another system. Nuncily reads it the same way regardless of where it came in, and replies on the same channel.
The channel is an interface. What happens after the message arrives is the product.
Nuncily
WhatsApp
Email
SMS
Web chat
Web form
API
It acts inside the systems you already run.
Nuncily updates records, flags exceptions, and pulls what it needs from the systems your team already uses — CRM, billing, practice management, spreadsheets, and internal APIs among them. Specific integrations depend on what your process runs on.
Nuncily
CRM
Billing
Practice mgmt
Helpdesk
Spreadsheets
Internal APIs
A person picks up when judgment is required.
What Nuncily handles
- Collecting what a request needs, and re-asking for what's missing
- Answering routine questions in the same conversation
- Checking what comes back against what the process requires
- Updating the systems the request depends on
What people handle
- Anything genuinely ambiguous, outside the defined boundaries
- Final sign-off where a process requires it
- Judgment calls that carry real consequence
Assigned to your team
Full conversation and everything collected so far attached — not a cold handoff.
Permissions, not blanket access.
The business is trusting Nuncily with real client data. The product is built around four principles.
- Scoped permissions
- Nuncily acts within permissions you define, system by system — not blanket access.
- An audit trail
- Every action is logged: what was read, what was changed, and when.
- Verification before completion
- An outcome is checked against what the process requires before it's marked done.
- Escalation, not guessing
- Anything outside its permitted actions goes to a person instead of being assumed.
- 14:02:11Readbank_statement_q2.pdf
- 14:02:14Flagged11 days missing from statement
- 14:03:40Sentfollow-up request to client
- 16:47:02Receivedupdated statement.pdf
- 16:47:19Verifiedstatement complete for Q2
- 16:47:20Updatedpractice management record
Your clients' data stays protected, and stays yours.
Hosted on AWS
Stored and processed on Amazon Web Services, in the London region.
Encrypted throughout
In transit and at rest, for every file and the database behind them.
Never used to train AI
Our AI runs on Amazon Bedrock in London. Your data isn't shared with any model provider.
Not kept by the AI
Documents and messages aren't stored by the AI service once a request is processed.
GDPR as standard
Handled under UK GDPR and the Data Protection Act 2018, with your firm as controller.
Yours to take back
You own your data. When you leave, export it, and we delete it within 30 days.
Give it to us. We'll take it from here.
Tell us the process that keeps coming back to your team, and we'll show you what it looks like handed over.
Loading available times…
Open the calendar in a new tab- A conversation about your process, not a slide deck.
- 30 minutes. We'll show the loop running on a process shaped like yours.
- No obligation, and your details stay with us.