OPERIYA

Case studies

Where operational friction became a system.

Documented examples of automation, process improvement and AI-enabled workflows. Each study states plainly where the work was done: under OPERIYA, or in-house as an employee.

9
systems documented
3
organisations
20
published readings
In-house implementation experienceReal estate · Sales operations · 2026

A CRM that keeps itself, and calls that write themselves up

An in-house build: call recording that starts itself, AI summaries written without anyone typing them, and a CRM record that stays current without manual entry.

Read the full breakdown

A sales call feeds an automatic recording, the recording feeds an AI summary, and the summary writes the CRM record. On its own baseline below, the manual path it replaced — write the call up from memory, then type it into the CRM — is drawn dashed and struck through.

Sales callHUMANRecordingSTARTS ITSELFAI summaryNO TYPINGCRM recordKEPT CURRENTTHE PATH IT REPLACEDWrite-upFROM MEMORYManual entryIF THERE IS TIME
Administrative time recovered
325hours a monthModelled, not timed: 3 minutes of logging per call × 50 calls a day × 5 reps × 26 working days. Every input is stated so the figure can be recalculated with different ones.Model built by Bipasha Das from the team's own call volumes.
Net saving each month
$474$677 of administrative time at a $2.08/hour payroll rate, less $203 of telecom cost (13,000 minutes at $0.016). About $5,690 a year.Model built by Bipasha Das. Figures are converted from rupees at 96 to the dollar, the rate in September 2026.
Steps in the loop that wait on a person
1stepfrom 4 stepsCounted from the two process columns published on this page. The only remaining human step is the sales call itself.

The problem

A sales call produces two things: a conversation, and a record of the conversation. The first is the job.

The system

The system was built so that no step of the record-keeping asks a person to remember it. Calls are recorded automatically rather than on demand.

The change

The upkeep left the salespeople. Recording, writing up and CRM entry are now done by the system, which is the whole of what “zero-touch” claims — not that the calls happen by themselves, but that keeping the record of them no longer competes with making them.

Before
  1. Sales call takes place
  2. Recording started by hand, if at all
  3. Call written up afterwards
  4. CRM record updated by hand
After
  1. Sales call takes place
  2. Recording starts on its own
  3. Call summarised by the model
  4. CRM record written and kept current
In-house implementation experienceReal estate · Sales operations · 2026

The reporting layer that found a 21-hour gap

A private dashboard and reporting layer built on top of an existing CRM — which replaced hours of manual reporting and surfaced a speed-to-lead problem nobody had been able to see.

Read the full breakdown
Manual reporting removed
8–12hours a weekRecurring reporting work across the team that the automated reports replaced, estimated across a normal week. Not timed.
Median time to first response, measured
21.4hoursMeasured by the system across the leads in the CRM once the dashboards were live. A widely used benchmark for this is under five minutes. It is what was found, not what was achieved.
Before
  1. Someone asks how the month is going
  2. Export from the CRM
  3. Assemble a view
  4. Circulate it, late
After
  1. Reports send themselves
  2. Each rep gets a plan and a recap
  3. Dashboards stay live against the CRM
  4. Questions get asked of the data directly
In-house implementation experienceReal estate · Marketing and sales operations · 2026

Replacing a $156 subscription with $8 of infrastructure

A click-to-WhatsApp funnel rebuilt on the official API and self-hosted tooling: the same lead flow and a faster first reply, at roughly a twentieth of the running cost.

Paid advertising sent people into WhatsApp, which is where this market actually wants to talk. Everything after that click was rented. A messaging platform sat in the middle at a fixed monthly fee, and what it provided — a welcome message, an alert to a salesperson, a record of the lead — is not difficult work. It is plumbing, charged as software.

Read the full breakdown

Systems involved

  • WhatsApp Cloud API — the official channel
  • Chatwoot — the agent inbox
  • n8n — the automation
  • A cloud server at about $4 a month
  • The sales CRM — write-back target
Running cost of the channel
$8per monthfrom $156 per monthThe previous platform's fixed monthly fee against the new stack's all-in running cost, which ranges from about $5 to $8 depending on message volume. The upper end is used here — roughly $1,775 a year saved. Converted from rupees at 96 to the dollar, the rate in September 2026.
In-house implementation experienceReal estate · Marketing · 2026

A site that weighs 87 kB and files its own leads

An eighteen-page rebuild where every enquiry lands in three places at once, the analytics finally attribute spend to leads, and the homepage loads in under a second.

Read the full breakdown
Homepage transfer weight
87kBThe delivered homepage, static and image-optimised. Sites of this kind commonly carry 2 MB or more, which is a general benchmark rather than a measurement of the previous site.
Destinations per enquiry
3at onceWhatsApp to the sales number, a CRM webhook, and email — fired together, so a single failure cannot lose the lead.
Before
  1. Visitor submits an enquiry
  2. Email arrives in a shared inbox
  3. Someone re-types it into the CRM
  4. Ad spend reconciled by guesswork
After
  1. Visitor submits an enquiry
  2. WhatsApp opens to the sales number
  3. Webhook writes the lead to the CRM
  4. Email sent as the third copy
  5. Conversion recorded against the ad

Also in the archive

Have a workflow worth examining?

We start by mapping where time, attention and process reliability are being lost.

Book an Automation Audit

Loading the calendar