Teach. Run. Verify.
Show it once.
It runs forever.
Sircl learns any task you show it in your old software, then runs it for you and checks every result. No code. No API. No new system.
For teamsstuck on software with no APIand for anyonetired of retyping their own admin
Sircl is in development. Join early access to help shape it.
Teach Sircl to create Shopfront orders in LOGIX
Show me the task two or three times. I’ll work out the steps, then you check them.
- Open LOGIX · Orders · NewVerified
- Fill customer, SKU, quantityVerified
- Save and read back the order numberWaiting
In plain English
So what is it, actually?
Sircl watches you do a task once, works out the steps, and then does that task for you whenever you want. Think of it less as software you configure and more as someone you train on their first day, who then never forgets and never gets bored.
You already know how to do it
If a person can do the task on screen, that is the only skill needed. No code, no flowcharts, no consultant. You do the job once while Sircl watches the window you choose.
It works out what you meant
A language model reads what you did and writes the steps back in plain English, picking out which values change each time. You correct it in words if it got something wrong.
Then it does it, and checks
Run it by chat, on a schedule, from a trigger, or over an API. After each run it reads the screen back to confirm the result is what the task was actually for.
And three things it is not
Not a new system to move into
Nothing migrates. Sircl drives the software you already have, exactly as it is.
Not an integration project
No API needed, no vendor to ask, no six-month roadmap slot.
Not a macro that breaks quietly
When the screen changes it stops and tells you, rather than carrying on against the wrong thing.
Teach. Run. Verify.
The daily tax
Copy. Paste. Again.
Your newest tools talk to each other happily. Then there is the system everything actually runs on, the one from 2004, on a Windows box in the corner, with no API, no export worth the name, and a vendor who quotes six figures to look at it.
So somebody bridges the gap by hand. An order arrives by email, and a person retypes it into the old system. An invoice lands, and a person retypes it into the ledger. It is slow, it is dull, and it is where the mistakes come from.
The work is already understood. It just has nobody to do it but a person with a keyboard.
Illustration of a typical legacy order-entry screen.
How teaching works
Show it once.
Then never again.
Teaching Sircl a task takes about as long as doing the task twice, because that is essentially what it is. Here is the whole thing, start to finish.
Five stages: Ask: Describe it in a sentence. Show: Then just do the job. Twice. Draft: It writes the steps back to you. Approve: Test it before you trust it. Run: Then it just runs.
Stage 1
Describe it in a sentence.
No flowchart, no scripting, no integration project. Write what you want the way you would brief a colleague. A language model reads it and tells you what it needs from you.
What you type is the whole specification.
Stage 2
Then just do the job. Twice.
Sircl records the one window you pick, not your screen, while you work through it normally. Doing it two or three times is what lets it separate the parts that change from the parts that never do.
Passwords are blurred before anything is stored.
Stage 3
It writes the steps back to you.
What it watched becomes plain-language steps, with the values that vary each run picked out. If it misread something, you correct it here in words, not in code.
You can read every step before it runs once.
Stage 4
Test it before you trust it.
Run it against one real case while you watch. Sircl shows what it did and what came back. Nothing becomes a live workflow until you have seen it work and pressed approve.
Nothing runs on its own until you say so.
Stage 5
Then it just runs.
Start it by chat, on a schedule, from a trigger, or over an API that Sircl generates for software that never had one. Every run is checked against what the task was for.
Every run verified. Every run recorded.
Teach Sircl to create Shopfront orders in LOGIX
Live. I'll check every run and stop if the result isn't right.
- Open LOGIX · Orders · NewVerified
- Enter customerSHOPFRONT LTDVerified
- Enter SKU and quantityBRK-220-RED × 24Verified
- Save, read back the order numberVerified
Not just at work
Get your Sundays back.
Everybody has tasks like this. A freelance designer in Bristol has an admin night. A shop owner retypes online orders into a till system from 2009. A landlord logs the same repair across three portals. It is the same problem as the warehouse, just quieter.
9pm, every Sunday
Admin night
Receipts downloaded from five different websites. Each one typed into a spreadsheet, then uploaded again to the accounting app. Two clients chased for invoices. Portfolio updated. About three hours, every week, for work nobody pays her for.
One Sunday
She shows it once
She types: help me with my Sunday admin. Sircl replies: show me once. So she does it the usual way, while Sircl watches only the windows she picked, with her bank details blurred before anything is stored.
Ten minutes later
It reads the steps back
Download receipts, add to the expenses sheet, upload to the accounting app, email the overdue clients. Four lines of plain English. She corrects one, checks the rest, and saves.
Next Sunday, 9pm
Her phone buzzes
Sunday admin done. Fourteen receipts filed, two invoice reminders sent, every step checked. One receipt was unclear, so Sircl stopped and kept it for her. One tap sorts it out.
She closes the laptop and goes out for dinner.
That is the whole product, really. Not “automation”. Three hours back, every week, without having to learn anything.
At home, Sircl gives you your Sundays back. At work, it gives your team their days back.
Maya is an illustration of the problem we are building for, not a customer and not a testimonial. Sircl is in development and has no users yet. If this is your Sunday, the sign-up form below is where to tell us about it.
Features
Built to be trusted with real work.
Automation nobody trusts gets switched off within a month. These are the things that decide whether it stays on.
Verified runs
Sircl doesn't just click and hope. After each run it reads the screen back and checks the result is what the task was meant to produce. If it isn't, the run stops and tells you.
Run replay and signed records
Every run keeps a step-by-step record you can replay: what it saw, what it typed, what came back. Useful when something looks wrong, and useful at audit time.
Every workflow becomes an API
Once a task is taught, Sircl exposes it as an endpoint and as a tool your AI assistants can call. Software with no API gets one, without the vendor's involvement.
Guard rules and approvals
Set the limits in plain language, value thresholds, out-of-hours rules, anything that should need a human. Sircl pauses and asks rather than pressing on.
Adapts when apps change
When a button moves or a field is renamed, Sircl spots the mismatch, proposes the fix, and waits for you to approve it. No silent changes to a working process.
Works with what you already have
Desktop applications, old web portals, spreadsheets, terminal screens. If it renders on screen and a person can operate it, it is in scope.
The obvious questions
“Isn’t this just RPA?”
Fair question, and the honest answer is that it operates software the same way, through the screen. What’s different is who builds it, and what happens on the day the application changes.
Classic RPA failed most often not because the robots couldn’t click, but because a brittle script written by someone who had left broke quietly, and nobody could tell until the damage was done.
| Where it bites | Traditional RPA | Sircl |
|---|---|---|
| How it's built | A developer or consultant builds the automation in a visual designer, selector by selector. | You do the job while it watches. The recording is the specification. |
| How long until it works | Weeks to months, usually with a professional-services engagement attached. | About as long as doing the task two or three times. |
| When the app changes | The script breaks silently and keeps running against the wrong thing until somebody notices. | The mismatch is detected, the run stops, and a fix is proposed for you to approve. |
| How you know it worked | It reports that the steps ran. Whether the outcome was correct is your problem. | It reads the result back off the screen and checks it against what the task was for. |
| Who can change it | Whoever holds the licence and knows the tool. Often an outside contractor. | The person who does the job. In plain language. |
“Why not just get an API?”
Because it usually isn’t yours to decide. The systems this is built for were sold in the 2000s by vendors who have since been acquired, wound down, or who quote six figures and a twelve-month roadmap slot to open anything up.
Some have no API at all. Some have one that covers the three things you don’t need. Some would require an upgrade that means re-validating every process in the building.
If you can get a good API, use it. Sircl is for the very common case where you cannot.
“What about when the screen changes?”
This is the thing that kills screen-driven automation, so it’s worth being specific. Sircl doesn’t depend on a button staying at fixed coordinates. It works from what the screen means, the field labelled “Customer”, the button that saves.
When something moves or is renamed, the run stops rather than guessing. Sircl shows you what it expected, what it found, and what it proposes to do instead.
You approve the fix. It never silently rewrites a process you’re relying on.
Use cases
The jobs nobody wants to do twice.
The same problem turns up at both ends of the scale: a person doing something a computer could do, because the software will not talk to anything else. It does not much matter whether that happens four hundred times a day or four times a month.
- Warehouse
Order entry, all day
Orders arrive by email or portal and get keyed into the warehouse system one at a time, by hand.
"Take every order from the Shopfront inbox, enter it into LOGIX, and reply with the order number."
- Finance
Invoices into the ledger
PDFs land, get checked against the purchase order, then retyped into accounts.
"Read each invoice, match it to the PO, enter it into Sage, and flag anything over £5,000 for me."
- IT & HR
One joiner, three systems
A single new starter means the same details typed into payroll, the rota, and door access.
"Set up Priya in payroll, the rota and access control, then send me the three confirmations."
- Operations
The 7am report
Someone opens the old system, runs the same report, pastes it into a spreadsheet, emails it round.
"Every weekday at 7am, pull the stock report, tidy it, and email it to the ops group."
- Freelancers
Invoices, expenses, timesheets
Hours in one tool, receipts in another, invoices in a third, and chasing done by hand when nobody pays.
"On the 1st, invoice each client from my timesheet and chase anything over 30 days."
- Small shops
Online orders into an old till
Orders come in through a modern storefront and get retyped into a stock system that predates it by a decade.
"Copy today's online orders into the till system and tell me what's run low."
- Landlords
Rent and repairs, three portals
The same repair logged in one place, chased in another, and recorded in a spreadsheet nobody enjoys.
"Log this repair request in the portal, note it in my sheet, and remind me if it is still open in a week."
- Job seekers
Tracking forty applications
Every portal wants the same history retyped, and the spreadsheet tracking it all is always out of date.
"Add this application to my tracker and show me the cover letter before anything is submitted."
- Clubs & volunteers
Member lists in two places
A new member joins, and their details are typed into the website and then again into a spreadsheet.
"When someone joins through the website, add them to the members sheet and send the welcome email."
- Sunday admin
The three-hour evening
Receipts downloaded from five sites, filed, uploaded, then invoices chased. Every week, the same clicks.
"Do my Sunday admin, and stop and ask me about anything unclear."
Illustrative examples of the kind of task Sircl is being built for. Not case studies, and not customers. Sircl is in development.
When it goes wrong
Everything breaks
eventually.
Any automation that claims otherwise is selling you something. What actually matters is what happens in the hour after it breaks . So here is that hour, in full.
Five stages of a failed run: Running: A normal Tuesday morning. Mismatch: It notices before it types. Stops: It stops, and nothing is half-done. Tells you: You hear about it from Sircl, not from a customer. Proposes a fix: It proposes the fix. You approve it.
1. Running
A normal Tuesday morning.
The workflow has run forty-one times this month without anyone thinking about it. Then the vendor pushes an update overnight, and the Quantity field moves.
2. Mismatch
It notices before it types.
Sircl checks the screen matches what it expects before acting, not after. A field it was taught to rely on isn't where it should be, so it does not guess, and it does not carry on.
3. Stops
It stops, and nothing is half-done.
The run halts at a safe point. No partial order is left in the system, nothing is saved in an in-between state, and the next queued run is held rather than repeating the same failure forty times.
4. Tells you
You hear about it from Sircl, not from a customer.
You get told what it expected, what it actually found, and a screenshot of the moment it stopped. Not a stack trace, the actual screen, so you can see for yourself in two seconds.
5. Proposes a fix
It proposes the fix. You approve it.
Sircl works out what most likely changed and offers the correction. You can accept it, edit it, or do the task yourself once more to re-teach it. The workflow resumes only when you say so.
Run 42 · awaiting approval
Step 3 · Enter quantity
expectedfield “Quantity” below “SKU”
foundfield “Qty / Unit” in a new column
- No partial order written to LOGIX
- 3 queued runs held, not retried
Proposed fix: use the field now labelled “Qty / Unit” for quantity.
Security & privacy
Watching your screen is a big ask.
We know. So these are the rules Sircl is being built to, and where each one actually stands today.
Sircl is in development. Anything marked Planned is something we intend to deliver, not something that exists yet.
One window, not your screen
You pick the application window to record. Sircl captures that and nothing else, not your inbox, not your messages, not the rest of your desktop.
Sensitive fields blurred automatically
Password boxes and fields that look like card or bank details are blurred during recording, before anything is stored.
Processed on your device where possible
Recordings are processed locally where the task allows it, so the raw video of your screen doesn't need to travel.
Credentials in an encrypted vault
Passwords Sircl needs to operate an application are kept encrypted and are never written into a workflow's steps or its run records.
You choose the AI model
Pick the model that suits your policy, including self-hosted options for teams that cannot send data to a third party.
UK data residency
PlannedWe intend to offer UK-hosted storage and processing. It is on the roadmap, not in place yet. Ask us where we've got to.
Planned pricing
Free to start. Paid when it pays.
Personal use is free because that is how you find out whether this works for you, on your own machine, with your own software. Teams pay because teams are where the hours add up.
We have not set prices yet, on purpose. Sircl is in development, and we would rather work out what it is worth with the people who use it first than guess at a number today and defend it later. What is settled: personal use will be free, and early-access members get founding-member pricing when the rest is decided.
Personal
PlannedFree
The way in. Enough to automate your own Sunday night.
- 3 workflows
- Runs on your own computer
- Verified runs and replay
- Community support
Pro
PlannedPaidset with early members
For freelancers and sole traders whose admin is the business.
- Unlimited workflows
- Schedules and triggers
- API for every workflow
- Email support
Team & Enterprise
PlannedTalk to us
Where Sircl earns its keep: shared workflows, real volume, audit.
- Shared workflows and handover
- Guard rules and approvals
- Signed run records for audit
- Choice of AI model, self-hosting
What it will refuse to do
Being able to operate any screen is not a licence to operate every screen. Guard rules are built to block the things that would get you, or us, into trouble.
- Tasks that break a site's terms, like bulk ticket buying or scraping where bots are forbidden
- Anything past a limit you set, without asking you first
- Running on credentials you have not explicitly given it
- Carrying on when the screen is not what it expected
Working here
Come and build
the boring part.
Most of what makes this work is unglamorous: reading a screen correctly, refusing to guess, stopping safely when something moves. If that sounds more interesting than it sounds exciting, we should talk.
We’re pre-launch and small. That means genuine influence over what gets built, and all the uncertainty that comes with it. Being honest about both halves of that is the point.
There are no funded roles open today. We are not going to post a job we cannot yet pay for. Tick “I’d like to hear about roles at Sircl” on the form below and we will come to you first when that changes.
Register your interestMaking screens legible to a model
Turning a recording of someone working into a reliable, repeatable set of steps. Computer vision, UI understanding, and a lot of judgement about when not to guess.
Running other people's software safely
Desktop and browser automation that behaves itself: sandboxing, credential handling, knowing when to stop. The unglamorous work that decides whether anyone trusts this.
Product and design
Making something genuinely technical feel obvious to someone who has never automated anything, and will not read a manual. Most of the difficulty is here.
Talking to the first customers
Sitting in warehouses and small offices watching how work actually gets done, and bringing back the truth rather than the flattering version.
Areas we expect to hire into, not a list of vacancies. If something you do well is missing from it, say so anyway.
FAQ
Questions, answered plainly.
Something not covered here? Join early access and tell us in the form. A human reads every one.
What is Sircl?
Do I need an API?
Which apps does it work with?
Is my data safe?
How much will it cost?
Is it for companies or for individuals?
Will it do anything I ask?
When can I use it?
How do I get involved as a design partner?
Early access
Be first to try Sircl.
Sircl is in development. Join early access to help shape it. Tell us what you’re retyping today and we’ll build for that.
- Early access when we open it up, in the order people joined
- Founding-member pricing when pricing is announced
- A say in which systems and tasks we support first
Teach. Run. Verify.