You added units. The workflow underneath them did not change.
Mellon audits how work actually moves through a property-management operation, finds where hours and margin are lost, and implements the fix with automation, AI, data, or a simpler process. Whichever one the evidence points to.
What an audit finds
A maintenance request arrives. Here is the process everyone believes in, next to the one that runs.
On paper
The request comes in.
It gets assigned to a coordinator.
The coordinator dispatches a vendor.
The tenant gets an update and it closes.
On the map
It arrives by portal, phone, text, or email. Two of those nobody watches after 5pm.
Assignment depends on who sees it first.
Dispatch waits behind everything else in that person's day.
The tenant calls to ask. That call becomes its own task.
Four steps on paper. Eleven in practice, with three handoffs and a clock on none of them.
Very little of that gap is a software-selection problem, which is why buying another tool rarely closes it. The audit produces this map for the workflow you select, then puts a number on what the gap costs each month.
See where operations lose money ↓Where operations lose money
Four leaks show up in almost every growing operation.
Revenue leaks on the clock.
Slow first response. Follow-up that stops after two attempts. Inquiries that go quiet and nobody reopens.
Admin work multiplies.
The same information typed into three systems, owner reports assembled by hand, status chased over email.
Everyone runs a different process.
The steps live in someone's memory. When that person is out, the standard leaves with them.
Leadership sees activity, not outcomes.
Numbers spread across systems that disagree, so decisions get made on anecdote.
The common thread is process. Automation layered on a broken process makes it break faster.
Here's what gets fixed first ↓What we improve
We start where the volume is, because that is where the hours are.
The audit ranks these by what each one costs you. The build that follows is fixed in scope and delivered inside the software you already run, so your team gets a better version of their own workflow instead of a new tool to learn.
High-volume communication
Tenant and prospect messages that arrive faster than anyone can work them, across four channels that do not talk to each other.
Repetitive administrative work
The same data entered twice, documents assembled by hand, reports rebuilt every month from scratch.
Routing and handoffs
Work that sits because ownership is ambiguous, and the delay nobody sees until someone complains.
Management reporting
One set of numbers everyone agrees on: capacity, response times, backlog, and the exceptions worth your attention.
Exception monitoring
The things that quietly fail. Renewals nobody flagged, requests that aged out, follow-ups that stopped.
Which of these comes first is a diagnosis, not a menu choice.
Meet the person who runs it ↓
Who runs this
An engineer who chose real estate operations.
I'm Daniel Souza. I trained as an industrial and production engineer, where the discipline is straightforward: understand the process, find where value is lost, and improve the system before adding anything to it. Mellon applies that to real estate, and the method draws on PDCA, lean operations, and continuous improvement.
The rest of my work has been operational reporting, SQL and data workflows, and decision systems in environments where accuracy and ownership matter. That is the half of this job most AI vendors skip, and it is the half that determines whether a workflow survives contact with a real team.
The recommendation is sometimes that a workflow should not be automated at all. That happens more than you would expect, and the audit is built to catch it while catching it is still cheap.
The MELLON Method
Diagnose it. Redesign it. Make it stick.
Diagnose
We map how the work moves today and price each gap. You get a prioritized roadmap with a business case, not a proposal for software.
Redesign and build
We design the future-state workflow, define who owns what, then build it, test it against the acceptance criteria we agreed, and train the people who use it.
Measure and normalize
We measure against the baseline set before launch, correct what missed acceptance, and turn the new way into the documented standard.
Then it keeps running.
Once a workflow is live, Managed Operations keeps it running and improves it monthly. We monitor performance, tune the models and logic, report cost per completed task alongside the business outcome, and administer the technical infrastructure behind it. Every plan carries a defined scope, a defined monthly allowance for that infrastructure, and spending controls with alerts and a hard ceiling. You know what you are getting and what it costs before the month starts.
Six stages, three phases, one cycle that repeats. Map, Evaluate, Lay the foundation, Launch, Observe, Normalize.
Start with the diagnosis
The Workflow Performance Audit. Starts at $3,500.
AI does not fix a broken process. It scales a good one. So every engagement starts with a paid diagnosis: we map one high-impact workflow as it actually runs, find where hours and revenue leave the building, put a number on each gap, and hand you a prioritized plan for what to fix first and what to leave alone.
You keep the roadmap whether or not you build it with us. If you do, the audit fee credits in full toward the implementation.
- A current-state process map of one high-impact workflow, selected during scoping
- Bottleneck analysis with root cause, frequency, and monthly cost
- A review of the systems you already own, including integration gaps and data quality
- An opportunity matrix scored by impact, effort, and time to value
- A prioritized 30/90-day roadmap, including what we recommend you leave manual
- A live executive readout
What we commit to. Before any build starts, we agree in writing on the scope, the acceptance criteria, the baseline, and the target metrics. If a deliverable does not pass acceptance testing, we correct it at no additional implementation fee.
Who it's for
Built for operators whose growth is capped by operations, not demand.
The fit is usually a property-management company past 300 units with five or more operational staff, established core software, and a named person who owns the process we would be changing. Enough volume that a slipped handoff is real money, and enough software that nobody is certain which system holds the truth.
The same work applies to brokerages, investment firms, and teams carrying similar operational load. It is a poor fit if you want a cheap chatbot, if there is no internal decision-maker, or if the expectation is that AI will compensate for a weak offer. We will say so on the call rather than three weeks into a project.
See if an audit fits →Founding partners
Three operators. Half the audit fee. One published case study each.
The Workflow Performance Audit is $3,500. For three founding partners it is $1,750, credited in full toward implementation if you build with us.
You get the full diagnosis: the workflow map, bottleneck analysis with monthly costs, the technology and data review, and the roadmap. We get to publish what we found, anonymized to whatever level you require, plus a testimonial. Founding partners also get priority scheduling and the work done directly by me.
Case study permission is a condition, not an option. That is the whole trade. Three spots, closing September 30, 2026.
Apply as a founding partner →Not ready to talk yet
Five minutes to see whether an audit is worth your money.
The Workflow Readiness Check is 18 questions about volume, ownership, systems, and data. It tells you which of your workflows is most likely to be losing hours, and whether a paid audit would find enough to justify itself. If the answer is no, it says no.
The check, how to read your result, and one useful email a week. Unsubscribe anytime.
Common questions
Questions, answered.
Our software already does some of this.
Often true, and the first thing the audit checks. Some of what we recommend turns out to be a process change or better use of a feature you already pay for. We take no compensation from any software vendor.
Why pay for a diagnosis?
A free consultation is scoped to what can be guessed in 45 minutes. The audit involves interviews, system access, and your real data, and it produces a costed roadmap you keep either way. Paying for it also means the recommendation is not steered toward the largest possible project.
We could build this internally.
The audit is designed to stay useful if you do. You get the map, the costed priorities, and the design. From there you can take the blueprint to your own team, hire us to build, or use us as advisory support while your team executes.
What happens if a deliverable does not work?
Scope and acceptance criteria are agreed in writing before the build starts. If a deliverable does not pass acceptance testing, we correct it at no additional implementation fee. Ongoing performance tuning after launch is what the managed agreement covers.
What if my team will not use it?
Adoption failure is the most common reason these projects die, so the people who do the work are in the mapping, the design, the testing, and the training. Adoption gets measured after launch alongside the performance metrics.
Our data is messy.
Data readiness is scored during the evaluation stage. For plenty of companies the first recommended project is standardization rather than AI, because automating unreliable data multiplies the error.
We cannot disrupt operations.
Nothing reaches production without a controlled pilot, parallel testing, user acceptance testing, and a phased launch. The rollback plan is written before the launch plan.
What does it cost?
The audit starts at $3,500 and is quoted on the call once we know the size of the operation. Implementation is scoped and priced inside the audit report, so you see the number before committing. Managed Operations is a monthly agreement with a defined scope and infrastructure allowance.
Find the bottleneck first.
One call, 30 minutes, to see whether an audit would find enough to be worth running. If it would not, we will tell you on the call.