We map the repeated work in your company, build the automations to match, host them on a dedicated server in your own cloud account, and check every workflow every 15 minutes. When something stops, you hear it from us first.
Free one-hour audit · live in about two weeks · leave any time and keep everything
Dinero Technologies is a Thane-based technology and government-solutions firm. We build and operate software for public institutions and private enterprises, and we run our own company on the same automation platform we sell. That means the discipline you would expect on an institutional project, applied to the everyday work of your business: security by design, documented handover, and someone accountable when it breaks.
We start from the tasks your team does by hand today, then design the automation to fit them. Below are the areas we most often build in, with examples of what has shipped.
Capture every enquiry, route it to the right person, and follow up without anyone remembering to.
Invoices, reminders, reconciliation and month-end packs generated on schedule from your accounting system.
Multi-step processes with a human decision in the middle: purchase orders, onboarding, dispatch, site reports.
Timely, consistent messages on the channels your customers already use, with your voice and your approval.
The numbers you check every morning, assembled overnight from the systems that hold them.
Where a language model genuinely saves hours: reading documents, drafting replies, classifying and extracting.
The platform is the same. The workflows, integrations and approval rules are designed for each client. These are the environments we work in most.
Departmental workflow automation, inspection and reporting pipelines, audit-ready trails.
Lead routing, site visit scheduling, contractor follow-ups, progress and payment reporting.
Order intake, dispatch updates, supplier reminders, stock and receivables digests.
Appointment confirmations, reminders, report delivery, recall campaigns with consent.
Proposal follow-ups, client onboarding, timesheet and invoice cycles, monthly reporting.
Order notifications, abandoned enquiry follow-ups, returns handling, daily sales summaries.
Admissions enquiry handling, fee reminders, attendance and progress updates to parents.
If your team does the same steps every day, it can be mapped, built and watched.
No six-week discovery phase. We start from the three tasks that cost you the most time, build them properly, prove them in front of you, and keep watching them for as long as you keep us.
A call where you walk us through the repeated work. We write down exactly what “done” means for each task and what a failure would cost.
A dedicated server is provisioned in your cloud account from our audited template. The workflows are built against your real tools, with approval gates where they belong.
We do not describe the system; we demonstrate it. You watch every check pass, a real restore complete, and a deliberate failure get caught.
From here the retainer buys attention. Every 15 minutes we confirm every automation is on and running; every night we confirm the backup is fresh.
Every engagement runs on Company Automation OS, the platform we built and operate in-house. Your automations and data live on a server in your own cloud account. Our watch layer never logs in: your server pushes a status report every 15 minutes, and a missed report is the alert.
A workflow that has been switched off never throws an error, so ordinary monitoring reads it as perfect health. Every check below maps to a failure we have seen take a business down, and every failure has a pre-agreed response.
Is every automation still switched on, and has each one executed within its expected window? The check most vendors do not have.
Did last night’s backup run, is it young enough, the expected size, and did it land off-site? A stale backup is treated as no backup.
Full disks are the most common way a healthy server silently stops writing. We alert at 80% and act before 90%.
An expired HTTPS certificate breaks every incoming webhook at once and looks like silence. We alert 14 days out.
A run that errors is investigated: expired API key, changed field name, rate limit. Transient failures retried, structural ones fixed.
Two consecutive missing reports and the server itself is presumed down: network, provider outage, or a reboot that did not come back.
Server bill, API usage and execution counts week over week. A workflow suddenly running ten times more is either a win or a loop.
What ran, what failed, what we fixed, what it saved. Written for the owner, not the engineer. One page, on the 1st.
Every interaction happens in WhatsApp or Telegram, the apps you already have open. Read the morning digest, approve what needs a human, trigger a workflow by typing its name.
What ran overnight, what is waiting on you, what we fixed. Thirty seconds to read with your tea.
A quote, a reminder, a reply: the draft lands on your phone with two buttons. Nothing is sent without your yes.
“Run invoice reminders now.” “Status.” “Pause lead intake until Monday.” Plain words, no menus.
No noise. If we fixed it, you get one line saying so. If we need you, you get a question.
This is the part most vendors cannot offer, because their business model is the lock-in. Ours is the watching, and watching is only worth paying for while it is good.
At handover we show you the three steps to end the relationship: revoke our key, cancel the retainer, keep running. It takes under five minutes and everything keeps working the next morning. A vendor who cannot show you the exit is selling the lock-in.
One setup fee to build and prove it, then a monthly retainer for the watching. Your server, roughly ₹1,000 to 2,000 a month, is billed by your cloud provider to your own card. It is not our margin and we never touch it.
Your first automations, run properly and watched
An operations layer, not a script collection
By invitation · pilot pricing
More than eight workflows, an on-premise or government-cloud requirement, integration with legacy systems, or a department-wide rollout. We scope it, quote it as a project, and run it on the same platform with the same guarantees.
Pilot pricing in INR, exclusive of GST; annual billing and USD invoicing are available on request. The AI Team tier stays off the public rate card until two pilots have run it for 90 days. We would rather price it from evidence than from optimism.
| What you get | Starter | Growth | AI Team |
|---|---|---|---|
| Build | |||
| Automations built to specmulti-step approval flows from Growth up | 3 | 8 | 8 + AI queue |
| Dedicated server in your cloud account | ✓ | ✓ | ✓ |
| 38-check acceptance test at handover | ✓ | ✓ | ✓ |
| Change hours included per month | 2 h | 6 h | 12 h |
| Watch | |||
| Silence detection every 15 minutes | ✓ | ✓ | ✓ |
| Nightly backups, off-site, restore-tested | ✓ | ✓ | ✓ |
| Fixes and re-runs included | ✓ | ✓ | ✓ |
| Morning digest on your phone | ✓ | ✓ | ✓ |
| Monthly plain-language report | ✓ | ✓ | ✓ |
| Quarterly review | · | ✓ | ✓ |
| Control | |||
| Trigger and approve from WhatsApp / Telegram | · | ✓ | ✓ |
| Phone status console | · | ✓ | ✓ |
| Shareable status page | · | ✓ | ✓ |
| AI | |||
| Knowledge base your automations can read | · | · | ✓ |
| Named AI staff working a reviewed queue | · | · | ✓ |
| Hard monthly AI spend ceiling you set | · | · | ✓ |
| Exit | |||
| Keep server, data, workflows and domain if you leave | ✓ | ✓ | ✓ |
| Revoke our access yourself, any time | ✓ | ✓ | ✓ |
About 15 minutes, on a call, on your finished server. Nobody else pitching you does this, because it only works if the system actually does what the page says.
38 checks against your finished server: firewall, TLS, container health, backup schedule, restore, alert delivery, every workflow enabled and reachable. You watch each one pass.
A real restore onto a scratch database, including the encrypted credentials. Your data comes back while you watch, which is the only way to know a backup is real.
We switch off a workflow and wait. Within 15 minutes your phone gets the alert, the workflow is re-enabled, and the message says what happened. Then we do it again with the server.
$ ./acceptance-test --server dinero-ops-01 --live ── network ───────────────────────────────── ✓ only ports 22, 443 reachable from outside ✓ ssh: password auth disabled, 2 keys (owner, operator) ✓ https: certificate valid, renews in 61 days ── services ──────────────────────────────── ✓ docker: 4/4 containers healthy ✓ n8n: 6 workflows active, 0 disabled, 0 erroring ✓ postgres: 41 MB, 0 long-running queries ✓ heartbeat: last push 04m11s ago → watch layer ── backups ───────────────────────────────── ✓ nightly job: last run 03:02, 41.3 MB, off-site ✓ ✓ restore → scratch db: 4.2 s, 6 workflows, 11 credentials decrypt OK ── alerting ──────────────────────────────── ! disabling workflow "Quote follow-up" for the test… ✓ silence detected after 1 check (14m52s) ✓ alert delivered → WhatsApp +91 •••• 5599 ✓ workflow re-enabled, 0 runs lost ── summary ───────────────────────────────── 38 passed · 0 failed · 0 skipped · 6m40s $
No uptime percentages, no revenue outcomes, no claim that AI will run your marketing. Every promise on this page maps to a check we can run in front of you or a screen we can show you, which is also why the first month of monitoring is free. You should be able to watch it work before you pay for it.
We start from the work, not the tools. In the discovery call you walk us through a normal week; we pick the three tasks that are most repeated, most annoying, or most costly when missed. Each becomes a one-page spec with a clear definition of done. Anything customer-facing gets an approval gate by default.
n8n is an open-source workflow engine you can run on your own server. Zapier and Make are excellent, but your workflows live on their servers, under their pricing, and leave with them. With n8n the workflows are files on a machine you own, and there is a large market of freelancers who can edit them if we ever disappear.
Hetzner or DigitalOcean by default, in a region near you; AWS, Azure or an Indian government-empanelled cloud if your policy requires it. The server is created under your login and billed to your card. We never resell hosting, so there is no markup and no dependency on our account.
During the build we need API keys for the tools a workflow touches: CRM, accounting, email, WhatsApp Business. Those keys are stored encrypted on your server, not with us. After handover we hold one SSH key for maintenance, which you can revoke yourself, and nothing else.
Over WhatsApp or Telegram, from a number you save at handover. Alerts fire only on change: something broke, or something we fixed. Routine health is folded into the 07:00 digest. A second recipient, an ops manager or a partner, is a one-line change.
Two missed heartbeats in a row and we treat the server as down. We check the provider, restart if it is a simple reboot, and if the machine is gone we rebuild from the template and restore last night’s backup. Because we restore-tested it, that is a known, measured procedure, not a hope.
Yes. Dinero Technologies builds and operates platforms for public institutions, and the same practices apply here: data residency in India, append-only audit trails, role-based approvals, and documentation written for the next officer, not the last vendor. Enterprise and departmental scopes are quoted as projects.
Cancel the retainer, revoke our key, keep running. There is no notice period on the pilot. Everything, server, data, workflows, domain, backups and runbooks, is already yours, so there is nothing to hand over. We show you the three steps at handover so you know they are real.
Tell us about the three tasks your team repeats most. We will map them, build them on a server you own, and show you all three running within two weeks.
One hour on a call. No slides, no proposal deck. You leave with a written map of what to automate first and what it would cost.
First month of monitoring is free on every tier. If it is not obviously worth it after that, we part friends and you keep the server.
