The automations that run this studio.
A studio selling automation should be able to show its own. Here are the six we run on every day, what each one replaced, the two times they broke, and the one step we still do by hand.
The engagement. Internal. DappaSol is a small studio, and the hours between client work used to go on chasing: replying to enquiries, following up, making invoices, remembering things. We sell automation for exactly those jobs, so we built ours first and kept the logs.
| System | What it does | How often | What it replaced |
|---|---|---|---|
| Enquiry alert | Every form on dappasol.com writes to one log and pings a phone on Telegram. | As each enquiry lands. Wired July 2026, one outage | Checking the inbox by hand |
| Instant reply | The person who writes in gets an acknowledgement straight away, in plain words. | On the contact, start, reach and diagnostic forms; 19 sent so far | A reply the next morning |
| Follow-up sequence | Day 1, day 3 and day 7 emails to people who download a kit. Anyone on the stop list is skipped. | Day 1 at once; days 3 and 7 by a daily job at 09:00 IST | Follow-ups written by hand, or not sent |
| Recurring invoices | Builds each invoice, sends a preview, waits for a hold, then emails the PDF. | Preview on the 28th, send on the 1st | Making invoices by hand every month |
| Tasks and reminders | One list shared by phone, web and Telegram, with a morning digest and a ping when something is due. | A ping when something is due; digest at 08:30 IST | Notes scattered across apps |
| Buyer scan | Reads a public Shopify forum for store owners with a live problem and queues the threads. A person writes every reply. | Twice a day, 08:30 and 18:30 | Scrolling forums by hand |
The work between the work.
An enquiry comes in and sits until someone notices. A kit gets downloaded and nobody follows up. Invoices get built by hand every month. None of it is hard. All of it waits for a person to remember.
That is the same list our clients bring us. So we took our own first.
Six small systems, each doing one job.
- Enquiry alert and instant reply. Every form on the site goes to one log. A phone gets a Telegram message, and the person who wrote gets a plain acknowledgement. Wired in July 2026.
- Follow-up sequence. Someone downloads a kit and gets an email on day 1, day 3 and day 7. The first goes at once. The other two are sent by a job that runs daily at 09:00 IST.
- Recurring invoices. On the 28th the system builds next month's invoices and sends a preview to a phone. A one-word reply holds any of them. On the 1st the rest go out as PDFs.
- Tasks and reminders. One list that the phone app, the web app and Telegram all read. The server sends a ping when something is due, plus a digest at 08:30 IST.
- Buyer scan. Twice a day a script reads a public Shopify forum and queues threads from store owners with a live problem. It writes nothing to anyone. A person reads the queue and replies.
No AI model sits in the alert, the invoices or the reminders. They are plain rules, because plain rules are cheaper and do not make things up. The decisions stay with a person: which invoice to hold, which thread to answer, what to say.
70 follow-ups, 19 instant replies, none typed.
An enquiry that sat until someone noticed became a phone ping and an acknowledgement at once. Invoices built by hand became a preview on the 28th and a send on the 1st. Follow-ups nobody had time to write became emails that send themselves.
By 13 November 2026 the follow-up sequence had sent 70 emails: 39 on day 1, 23 on day 3 and 8 on day 7. Another 19 acknowledgements went out the moment a form came in, on the contact, start, reach and diagnostic forms.
One sat dead for five weeks.
The buyer scan stopped on 4 September 2026 and nobody noticed until we fixed it on 10 October. A privacy rule on the Mac it ran on blocked the script from reading its own folder, and it failed without telling anyone.
On 30 October we moved servers and a file permission broke. Alerts, emails and invoices stopped, and we do not have a clean record of for how long.
And the follow-up sequence still has a manual step. It cannot read the inbox, so when someone replies, a person adds them to the stop list by hand.
An automation that fails quietly is worse than no automation. Every build we ship now gets a check that shouts when a job has not run.
How this applies to you
These are the same jobs we automate for clients as business automation: lead intake, follow-up, invoicing, reminders and reporting, built inside the tools you already pay for.
It starts with a $500 AI Game Plan, credited in full to the build. The promise on it: we find you a day a week to claw back, or the Game Plan is free. Your first automation is from $2,000, live and doing the job in 21 days, or we keep building free for up to 30 more days. The conditions are on the service page.
Want to know which of your own jobs is worth it? Send me three you repeat every week. One page back within one working day: the one I would automate first and one I would leave alone. What you own at the end of a build is in the handover charter.
Free, and from a human
Send your site and one line on your week. I'll tell you what I'd automate first.
I read it myself and tell you what I'd do first, what it costs, and whether it's worth doing at all.
Got it. A confirmation is on its way to your inbox, and a reply from me follows within one working day.
Your week next
What eats your week?
Tell us the job on WhatsApp or at ishan@dappasol.com. Or send me three jobs you repeat every week: within one working day you get one page back, the one I would automate first and one I would leave alone. No charge for the look.