Get back the hours lost to email, quotes and paperwork
Pick the job that eats hours of someone's week, such as sorting the shared inbox or drafting quotes from your price list. We automate it with the simplest tool that does it reliably, give it access only to what that job needs, and test it on your own examples. A person on your team approves anything it sends to a customer or supplier, and the setup has a fixed price agreed before we start.
Start with one job that comes back every week
The best first job repeats every week and has a clear right answer. Sorting a shared inbox. Drafting a quote from your price list. Filling the same document from the same kind of request. When the first one runs well, you decide whether to add another.
An illustration, not a client: a bakery that takes custom cake orders by email could have each order read, checked against the menu and the calendar, and answered with a draft reply that includes the price. Someone at the bakery reads the draft and presses send.
How we set it up
1. Agree the job
What the automation does, what a good result looks like, and what it must never do. We write it down with the fixed price for the setup.
2. Choose the simplest tool
Often that is a feature in software you already pay for, a small script, or a connection between two tools. A job that means reading free-form text, such as customer emails, may need a language model. We recommend what fits the job and your data.
3. Give it only the access it needs
One mailbox folder, one document, one spreadsheet. You get the list of everything it can reach, and you can take any of it away.
4. Test it on your real examples
We run it against real cases from your business, including the awkward ones, and show you what it did with each.
5. A person approves what goes out
Drafts wait for someone on your team. Nothing reaches a customer or supplier until a person says yes.
6. A one-page runbook
What the automation does, where its instructions live, how to change them, and how to switch it off.
Three ways to start
One job
One workflow, set up and tested as above.
Team
Up to three workflows for the same team, set up one after another so each is proven before the next begins.
Care
A monthly review of what the automation did, and updates to its instructions when your prices, products or processes change.
Each setup has a fixed price agreed before we start, and care is a monthly fee. The tools it runs on are billed to your accounts by their providers, separately from our work.
Who this is for
A good fit
A small or medium business with one repetitive job that takes hours every week, and someone with time to check the drafts.
Look elsewhere if
You want to replace staff, put a chatbot on your homepage, or give software access to everything you own. If nobody can approve what it sends, it is too early to automate that job.
Why us
We build and run software that does this kind of work every day. KeySend checks Google Ads accounts daily and builds a client-ready PDF report each week, with nobody copying numbers into a spreadsheet.
We build the same limits into our products. On PostDeploy, a new connection can only read until someone grants it more. Your automation gets the same treatment: written instructions, limited access, tests, and a person who checks the result.
Questions owners ask
Will it send something wrong to my customers?
It prepares drafts, and your team decides what is sent. Nothing reaches a customer or supplier until a person approves it.
What data can it see?
Only what the one job needs, listed in writing, and you can take any of it away. Please don't send passwords or customer data by email. We arrange access separately.
Do I need to know which tool to use?
No. Tell us about the job. We recommend the tool after we have seen your examples and explain the ongoing costs and access it needs.
What does it cost?
Each setup has a fixed price, agreed in writing before we start, and care is a monthly fee if you want it. Subscriptions to the tools it runs on are billed to your accounts by their providers. We don't quote on the first call, because we need to see the job first.
What happens when our prices or processes change?
The runbook shows where the instructions live and how to change them. With care, we update them for you and check the results again on your examples.
Can we switch it off?
Yes, at any time. The runbook says how, and the automation runs in your accounts, so stopping it doesn't depend on us.
Related thoughts
-
Software needs an owner
Software becomes expensive when nobody clearly owns it. Ownership is a role, not a repository permission, and most struggling systems are missing it.
Which job would you hand over first?
Describe it in a few sentences: what comes in, what should go out, who does it today and how long it takes them. You don't need to know which tool to use. Paul reads every email and answers in English or Romanian.