AI Will Love You the Day You Implement a Three-Way Match

By Nasly Duarte

Everyone is racing to build AI agents. Almost no one is building the thing that makes those agents actually work.

---

Right now, every business owner is being told the same thing: get AI, build agents, automate everything. So they do. They bolt an agent onto one process, another onto a second, and wait for the magic.

Then the agents do not speak to each other. The numbers do not line up. And the same departments that were arguing before are now arguing faster.

The problem was never the AI. It was the foundation underneath it.

The link that connects every department

Here is what most companies are missing, and it is not glamorous. It is the three-way match.

A three-way match confirms that three documents agree before a bill ever gets paid: the purchase order, the packing slip, and the invoice. The PO says what you agreed to buy. The packing slip says what actually arrived. The invoice says what you are being charged. When all three match, you know the transaction is real, complete, and correct.

That sounds like accounting housekeeping. It is not. It is the connective tissue that ties purchasing, receiving, and finance to the same version of the truth. Without it, every department is working from its own story, and no AI agent can reconcile stories that were never connected in the first place.

Why so many companies skip it

Most businesses run in silos, and silos feel safe. Keeping each department in its own lane feels like control. Purchasing does its thing. Receiving does its thing. Finance cleans up at the end.

But that same structure is what keeps company data fragmented and people guessing. It is the reason automation stalls. You cannot automate a process that was never connected, and you cannot point an AI agent at data that three departments each recorded differently.

The comfort of the silo is exactly what is holding the business back.

The private sector can borrow what the government already requires

Here is a pattern worth noticing. Government contractors run on structured, matched, documented cost processes because they are required to. Regulation forces the discipline.

The private sector is not required to, so most companies never build it. That is not a knock on small business owners. It is just the absence of a forcing function.

But the owners who choose that discipline anyway, a real PO process, a working three-way match, connected data, are the ones who get something the others do not. When the foundation is clean, AI stops being a science experiment and starts being fast, accurate, and genuinely productive.

My Perspective

AI does not fail because the technology is not ready. It fails because it is bolted onto a business that was never connected in the first place.

The three-way match is one of the simplest, oldest controls in accounting, and it is one of the most powerful things you can put in place before you automate anything. It connects your departments, cleans your data, and gives your future AI something real to work with.

That is the bridge I build. My goal is to keep you competitive and a step ahead in your market, and it starts with the fundamentals: a real PO process, a working three-way match, and data clean enough that AI can finally do its job.

Read the full article in my Buy me a Coffee Community https://buymeacoffee.com/girlgoneverde/ai-will-love-you-day-you-implement-three-way-match

Give me a call at 786-526-46 nine seven

Or book a 30 min call https://calendly.com/girlgoneverde

It looks like work. Everyone is typing. Everyone looks busy.

What Is Paying People to Type the Same Thing Twice Costing You?

Most owners ask what new software costs. The better question is what the current process is already costing them, quietly, every day.

The same job written on a printout, a notepad, and three different sheets. Each time the same information gets re-entered, you pay for it again.

An owner asked me a version of this recently. He had a team that stayed busy all day and a business that still could not answer basic questions about itself. Busy people, unclear numbers. That gap is where the money hides.

The cost that looks like work

Here is why this stays invisible. It does not look like waste. It looks like work. Everyone is typing. Everyone is busy. The cost is buried inside salaries you already pay, so it never shows up as a line item.

But it is real, and the research has measured it. Manual data entry costs businesses an average of $28,500 per employee a year. Count the people in your business who spend their day moving information from one place to another. The one who takes the order. The one who enters it. The one who closes it. The one who builds the report. You are paying a large share of each of those salaries to move one piece of information through a relay.

A third of the day, gone

The numbers get sharper. The average worker spends close to a third of their day on repetitive data entry, moving information from one system to another. Read that as an owner. A third of every salary in a coordination role may be going to re-typing data that already existed somewhere else.

You are not paying them to think, to sell, or to serve customers for that third of the day. You are paying them to be a human copy machine.

The cost of doing it twice

It is rarely single entry. It is duplicate entry. The same information typed into a second system, then a third, then copied into a report. Studies put the cost of that duplicate entry at roughly $50,000 a year in lost productivity for a small business.

And here is the line that describes nearly every business I walk into. The staff know they are doing redundant work. They have accepted it as just how business works. That acceptance is the most expensive part, because once waste is normalized, nobody questions it, and the owner pays for it every year without ever seeing the bill.

The errors hide in the same place

Re-typing does not only cost time. It costs accuracy, and accuracy costs money twice. You pay once for the person to type it wrong, and again for someone to find and fix it. Every handoff in a relay is a new chance for a number to drift, and the most dangerous drift is the one that reaches a payment.

Why it happens, and what fixes it

None of this is a people problem. It is a structure problem. The tools do not talk to each other, so people become the connection between them. Every spreadsheet, every chat group, every separate login is a gap a human has to bridge by hand. Your staff are not the problem. They are compensating for systems that were never connected.

The fix is not another tool to add to the pile. It is connecting what already exists, so the data flows once, from one source, instead of being re-typed at every step. One place the data lives, everything else reading from it, no human bridging the gaps by hand.

The busiest team in the building can still be the most expensive thing you own. Busy is not the same as productive. Sometimes busy is just the sound of the same work being done four times.

I wrote the full breakdown, with every number and the research behind it, for my community.

Read the full piece at www.buymeacoffee.com/girlgoneverde. 

Then count how many times one piece of information moves through your your desk before it lands.

---

Mindful Dollar | Nasly Duarte | Doing More With Less | mindfuldollar.blogspot.com

Your Data Was Structured for Convenience. AI Needs More.

By Nasly Duarte

Most business data was never built to be read. It was built to be convenient. That difference is about to decide which businesses move forward.

Spreadsheets built years or days ago to solve one problem, fast forward to an AI Era, were expecting to feed something it was never designed for. 

The structure that fixed yesterday's problem is the structure that cannot feed tomorrow's tools.

I keep meeting businesses drowning in their own data. The instinct is always the same. Hire an analyst. Build a dashboard. Make sense of the numbers.

It rarely works, and I finally understand why. The problem is not at the end of the pipeline where the analyst sits. It is at the beginning, where the data is born.

Data has two authors, not one

The first author is the employee at the point of entry. How they name a customer, whether they fill the required field, which category they pick. the layout of the spreadsheet is key. Do you know how many spreadsheets ive seen where they try to make it look fancy but its not exportable to any model.. ALLOT Every small choice becomes a permanent feature of the data.

The second author is the owner, and they decide long before any employee logs in. Software licensing. Who gets access to what. How systems are configured. Whether two functions that need to talk to each other are even allowed to. These decisions set the ceiling on what clean data is possible.

When the owner does not author the structure deliberately, employees are left to figure it out alone. Each one builds a private version. A spreadsheet here. A workaround there. None of it connects, because none of it was designed to. I call it the spaghetti effect. Many reasonable individual solutions, tangled into one unreadable whole.

The shift that makes this urgent

Most data was structured for a department's convenience at a moment in time or are contacted by upper management to get then certain information and when they realize they dont have it.. they built it!! It solved one problem then. No one asked what it would need to become later.

Now data is being asked to feed AI. And data shaped by yesterday's convenience does not have the structure AI needs. The thing that was good enough then is the thing that cannot move forward now.

If you are an owner, question how your data is structured. For AI and what comes next, or for someone's convenience today. Those are not the same thing.

If you are building these data sets, ask the questions no one is asking you. How will this merge with other data sets. Does it share the same structure. Do the columns represent each category cleanly enough that another system could read them without you in the room to explain.

For the engineers and builders

Technical people get this wrong too. An engineer designs the schema and the pipeline and treats the humans entering data as an afterthought. They build elegant structure and assume clean data will flow into it.

Clean data does not flow into anything by default. It is produced by people working inside a system designed for them, configured to let the right things connect. The builder who understands this designs for both authors, the owner who sets the ceiling and the front line who fills it in. That is operations knowledge applied to engineering, and it is the difference between a system that holds and a tangle that needs cleaning forever.

My Point of View

Stop solving your data problem at the analyst's desk. It was created at the point of entry and shaped by decisions made above it. Author the structure deliberately, at both ends, with AI integration in mind, and your data can move forward. Leave it to convenience, and you will rebuild it from scratch when the next tool arrives.

I wrote the full story behind this, including the conversation that made it click and the research that backs it, for my community.

Read the full piece at www.buymeacoffee.com/girlgoneverde. Then go ask how your data is actually structured.

---

Mindful Dollar | Nasly Duarte | Doing More With Less | mindfuldollar.blogspot.com

Software Engineers Know How to Build. Few Know How a Business Runs

By Nasly Duarte

The best technical people I meet can build almost anything. The gap is never the code.

The code was never the hard part. The business was.

Paul Graham wrote a line that should sit on every engineer's desk. Enterprise software companies are not technology companies. They are sales companies, and sales depends mostly on effort.

Read that again if you build for a living. The thing that wins is not the cleanest architecture. It is understanding the business the software serves.

Most builders never get that understanding. They receive a requirements document. They build against a description of the work, not the work itself. The gap between the two is where good software quietly fails.

The skill most software engineers are missing

Technical skill has a ceiling. The ceiling is business understanding.

You can write the system. The harder question is whether you know how the business actually runs. Where the money moves. Where the work breaks down. What the owner fears at two in the morning.

That knowledge does not come from a stack. It comes from being inside an operation and watching it work.

Cross-training is the highest-leverage move

The most valuable builder in business in the coming years is not the one with the deepest technical stack. It is the one who understands how a real business runs and can build for it.

That person does not discover the pain through customer interviews. They have lived it. They build the fix that removes the cause, because they watched the cause happen.

Cross-training on business operations is the highest-leverage skill a technical person can add right now. It is the skill that moves you out of the sales-company category Graham described. It puts you in the category of someone who builds what a business actually needs.

This is the work I do at Mindful Dollar. I help business owners design their own financial architecture through autonomous agents that work alongside their employees, not instead of them, to increase profit and productivity.

The Bottom Line

Building skill alone is not enough. The builders who win understand the business first.

I wrote the full thesis for my community. It covers how I treat a small business as a research environment, why full visibility beats documentation, and how an operator builds in a sprint what a corporation gates over years. I call it The Operator's Lab.

Read the full piece on Buy Me a Coffee. 

buymeacoffee.com/girlgoneverde/buildingbusinesstoolsasanengineer

Then go find the room where you can see the whole machine.

---

Mindful Dollar | Nasly Duarte | Doing More With Less | mindfuldollar.blogspot.com

Learn to Read Code Before Writing Code

Learn to Read Code Before You Write a Line of It. This Summer. With Me.

By Nasly Duarte

Yesterday I posted about The Skill Nobody Teaches.

I am bringing a small community together this summer to learn one thing. How to read code.

Not how to write it. Not how to build an app in thirty days. How to read it first.

That sounds backwards. It is on purpose. Let me explain, and then I want you to join us.

The problem with how you were taught

Here is what most courses do. Day one, open the editor. Type this. Run it. Look, it works.

You copied it. It ran. And you have no idea why.

You did not build anything. You transcribed. And the first time a real problem shows up messy, with no clean answer in the back of the book, you freeze. Because nobody taught you to read the thing. They only taught you to copy it.

I learned a different way, and it is the only reason I made it from accounting into AI.

How I actually learned

I am an accountant. Before I ever touched a balance sheet, I had to understand what a balance sheet was. What it is for. Why the two sides have to meet. Nobody hands you a calculator on day one and calls you an accountant.

You learn to read the thing before you are trusted to build the thing.

Code is no different. The people who last are not the ones who type fastest. The machine already won that race. The people who last are the ones who can read what is in front of them, understand it, and decide whether it is any good. That is judgment. Judgment does not get automated.

So this summer, that is what we are building. The judgment. The reading comes first, and the reading is the work.

What we are doing together

This summer, we read. That is the whole focus, and it is enough.

We will sit with real code and trace it line by line. We will study GitHub repos so you can see what good code actually looks like. We will learn to look at something and understand what it does and why, before anyone writes a word of their own.

And we are not reading a fake calculator nobody needs. We are reading SoulAccess. A real app I am building, with real users, real decisions, and real things that can break. You learn on the real thing, the way real architects study real buildings.

Building comes later. This summer, we get good at reading. Almost nobody does this part, and it is the part that makes everything after it possible.

This is for you if:

• You are switching careers and tired of tutorials that leave you more lost than before.

• You keep "learning to code" and still cannot read a single repo with confidence.

• You want to understand AI tools, not just be replaced by them.

• You learn better with a community than alone at 1am with forty open tabs.

Join, and your workbook is free

When you join the community, you get my Notion workbook. The exact one I use to map and read through what I am building before a single line gets written. It is yours free, the moment you are in.

Then this summer, you read alongside us, in public, on a real project.

The person who can only write code is replaceable. The person who can read it, question it, and know when it is wrong is the one still standing.

Come learn to be that person.

Join the community and grab your free workbook below.

Is AI Coming for Accountants - National Accountant Day

I truly believe AI Is Coming for Accountants. Here Is the Distinction That Will Matter More Than Any Credential.

The accountants who are afraid of AI are asking the wrong question.

The question is not whether AI will replace accountants. The question is which accountants AI will replace first, why the answer has nothing to do with credentials, years of experience, or the software you know how to use.

I have spent 20 years inside accounting operations across construction, manufacturing, insurance restoration, retail, and trade services. I have watched skilled accountants get bypassed, automated around, and made redundant — not by AI, but by anyone who understood the system underneath the numbers better than they did. AI is about to accelerate that pattern at a scale no one is fully prepared for.

Here is the distinction that will determine who survives the next three years of accounting automation  and it is not the one most people are talking about.

The Two Layers of Accounting

Every accounting function has two layers. Most accountants only know one of them.

Layer 1 is the software layer. This is where most accountants live. QuickBooks, Xero, Bill.com, SAP, NetSuite. How to enter a transaction. How to reconcile an account. How to run a report. How to close the month. These are skills. They are real and necessary. But they are also exactly what AI is best at: pattern recognition, data entry, classification, reconciliation, and report generation at a speed and accuracy no human can match.

Layer 2 is the systems layer. This is where the accountant understands why the numbers look the way they do. How the chart of accounts was designed and whether it actually reflects how the business makes money. Where the transaction originates before it ever reaches the accounting software. Why the AP balance is wrong even though every invoice was entered correctly. What the cash flow statement is actually telling you about the next 90 days of the business.

Layer 1 is what AI replaces. Layer 2 is what AI cannot  "Yet".

The accountants who only know Layer 1 are already at risk. The ones who understand Layer 2 are not just safe. They are about to become significantly more valuable.

What Layer 2 Actually Looks Like in Practice

A Layer 1 accountant looks at an accounts payable aging report and sees invoices. A Layer 2 accountant looks at the same report and sees a procurement workflow that is three approvals deep, a vendor relationship that has been deteriorating for six months, and a cash position that will be short in 47 days if three specific invoices clear at the same time.

A Layer 1 accountant reconciles the bank statement. A Layer 2 accountant notices that the reconciling items are always in the same cost code, asks why, and finds a data entry pattern that has been masking a billing error for eight months.

A Layer 1 accountant closes the month. A Layer 2 accountant reads the month and tells the business owner what happened, what it means, and what decision they need to make before the next period opens.

AI can do Layer 1 faster than any human. AI cannot yet do Layer 2 — because Layer 2 requires understanding the operational context that produced the numbers, not just the numbers themselves.

Why This Distinction Matters More Than Your CPA

I say this with respect for the credential. The CPA is a rigorous, meaningful qualification. It tests technical knowledge at a depth that matters. But the CPA tests Layer 1 proficiency — knowledge of the rules, standards, and procedures that govern financial reporting.

It does not test whether you understand the business system that produced the financial data you are reporting on.

The accountants who will thrive in an AI-augmented world are the ones who can walk into any business, read the operational reality through the financial statements, and design the system that makes the numbers accurate, timely, and decision-ready. That skill is not tested on any exam. It is developed over years of being embedded inside operations — not just recording them.

AI is going to make the credential table stakes. Everyone will have access to technically accurate financial reporting at near-zero cost. The competitive advantage will belong to the accountant who understands the system well enough to know when the technically accurate report is operationally misleading.

What AI Actually Does to the Accounting Profession

AI does not eliminate accounting. It eliminates the parts of accounting that never required human judgment in the first place.

Invoice processing does not require human judgment. It requires pattern matching, data validation, and rule application. AI does that better than humans already.

Three-way matching does not require human judgment. It requires comparing three documents against each other at the line-item level. AI does that faster and more accurately than any AP clerk.

Bank reconciliation does not require human judgment in most cases. It requires matching transactions. AI does that in seconds.

What AI cannot do. What it will not do for a very long time, is understand why the three-way match keeps failing for one specific vendor, trace that failure back to a purchase order workflow that was never designed correctly, and redesign the system so it does not happen again.

That is a human judgment call. It requires operational knowledge, systems thinking, and the ability to see a financial problem as an operational problem in disguise.

The Accountant AI Cannot Replace

The accountant AI cannot replace is the one who sees the full system.

They understand that accounts payable is not just paying what is approved. It is the final step in a workflow that began at estimate or purchase order, passed through approval, touched procurement, and only reached AP after every upstream decision was already made. If AP is wrong, the problem is almost never in AP. It is somewhere upstream — and finding it requires tracing the transaction back through the system to its origin.

They understand that cash flow is not a report. It is a forecast built on the operational rhythm of the business — billing cycles, collection patterns, payment obligations, and the timing gaps between all three.

They understand that the chart of accounts is not a list of categories. It is an architectural decision that either makes the business's financial story legible or obscures it in ways that compound for years.

AI will augment every one of these capabilities. It will surface patterns faster, flag anomalies earlier, and generate reports that used to take days in seconds. The accountant who understands the systems layer will use AI to multiply their impact. The accountant who only knows the software layer will watch AI do their job and wonder what happened.

The Bottom Line

AI is not coming for accounting. It is coming for the parts of accounting that never required systems thinking in the first place.

The distinction that will matter more than any credential in the next three years is simple. 

Do you understand the system that produces the numbers, or do you only know how to record them?

That question has always mattered. AI is just about to make the answer impossible to hide.

#OperationsAccounting #AIforAccounting #FinancialSystems #AccountingAI #NaslyDuarte

Howdy! Nasly here. If you find value in these breakdowns and want to support the work I do bringing you the latest in AI, operations, and business systems, please consider treating me to a virtual caffeine boost! You can hit the "Buy Me a Coffee" button below, and yes, I am officially accepting crypto now too! Your support keeps this whole thing running.

Future PropTech Miami - Energy, Water and Space Intelligence

Energy, Water and Space Intelligence

By Nasly Duarte

Last week I attended an amazing insightful event. and i want to tell you about my trip to the Future PropTech Miami because my mind is completely blown! As an AI student I am always looking for the next big thing and this conference absolutely delivered. We need to talk about three incredible innovators that are completely revolutionizing how we use energy, water, and space.

First up is Akila. They are tackling energy waste using some seriously advanced AI technology. Specifically they rely on computer vision and machine learning algorithms. Imagine a digital twin of a building which is basically a perfect 3D virtual copy. Akila uses computer vision through a network of cameras and sensors to see exactly how energy is flowing and where it is being wasted in real time. Their AI software runs complex simulations to optimize cooling systems and lighting automatically. It is literally building an artificial brain for real estate!

Next I listened to Frederico Teixeira Egli talk about space intelligence. Have you ever wondered if a building is actually using its square footage properly? Frederico discussed how AI spatial analytics can find the absolute best use for a building footprint. By feeding foot traffic data and occupancy metrics into predictive algorithms the software can redesign floor plans to maximize utility. This means fewer wasted empty rooms and a much better flow of people. The AI learns how humans naturally move and adapts the space to fit our exact needs.

Finally we have Seth Guttenberg who is the CEO and cofounder of arkIQ. If you know me, you know that i can live with out electricity but I cant live without water. arkIQ built an incredibly smart water detection machine. They use internet-connected sensors combined with AI anomaly detection. The software learns the normal baseline water flow of a building. The exact moment a pipe starts leaking or water is being wasted the AI flags the anomaly before a catastrophic flood happens. It is predictive maintenance at its absolute finest saving millions of gallons of water!

We really need to pay attention to these technologies right now. Whether you are a solopreneur, a creator, or managing a massive operation, if we do not start looking at how we use energy, water, and space in both our commercial buildings and our own homes we are heading toward a very unfortunate future. The tools are here. AI is giving us exactly what we need to build smarter systems. 

Let us start building them today!

References

https://futureproptechmiami.com/conference/speakers

https://www.akila3d.com/blog/akila-profiled-in-nvidias-physical-ai-for-smart-cities-video/

Hey everyone! Nasly here. If you find value in these breakdowns and want to support the work I do bringing you the latest in AI, operations, and business systems, please consider treating me to a virtual caffeine boost! You can hit the "Buy Me a Coffee" button below, and yes, I am officially accepting crypto now too! Your support keeps this whole thing running.

AI, Process Replication, and Financial Operations

I DO NOT want AI to find accounting errors faster.

I want AI to help design systems where fewer errors make it to the financial statement

By Nasly Duarte

That is the difference between using AI as a cleanup tool and using AI as a financial operations architecture tool.

A lot of the conversation around AI in accounting focuses on speed. Faster reconciliations. Faster variance analysis. Faster anomaly detection. Faster close cycles.

All of that matters.

But if the process is weak, speed alone can become dangerous. A faster tool on top of a broken workflow does not create better financial visibility. It just moves the confusion faster.

The question I keep asking is this:

Will AI help business owners and operators replicate their real processes, or will it distract them with more fancy tools?

Because the financial statement should not be a mystery we solve at month-end.

Revenue should be traceable from customer activity. Costs should be traceable from labor, materials, vendors, usage, fulfillment, and delivery. Expenses should be traceable from commitments, approvals, invoices, payments, and allocations. Cash movement should connect back to the events that created it.

When that structure exists, reconciliation becomes a validation layer instead of the first place we go looking for the truth.

That is the work I am interested in as an AI Financial Operations Architect.

Not AI for the sake of AI.

Not another dashboard that looks impressive but does not explain the business.

Not automation that hides weak assumptions under a cleaner interface.

I want to help build systems where the business can explain how work becomes numbers.

That starts with line items, estimates, budgets, source data, controls, and process discipline.

If the business cannot explain how the numbers should be created, AI cannot responsibly automate them.

But when the process is clear, AI can help map the workflow, test assumptions, flag missing inputs, identify exceptions earlier, and strengthen the path from operations to financial reporting.

That is the real opportunity.

I do not want AI to make reconciliation the hero. I want AI to help design financial operations where reconciliation confirms the truth, instead of discovering the problem too late.

Florida's First Applied AI Program Has a Responsibility to This Conversation

 

Miami Dade College launched Florida's first Associates & Bachelor of Science in Applied Artificial Intelligence.

That is not a small thing. It means MDC made a decision that AI literacy is not a luxury for a four-year university student. It is a right for the working adults, the career changers, the first-generation students who make up the MDC community.

I am one of those students.

I have spent over 20 years in operations accounting across construction, manufacturing, insurance restoration, and retail. I enrolled in the Applied AI program because I believe the people who understand both the operational side of business and the architecture of AI are the people who will determine whether this technology serves workers or replaces them.

What I am watching in this industry concerns me deeply.

Hyundai and Boston Dynamics are deploying humanoid robots in automotive manufacturing facilities trained on the labor of human workers. OpenAI published a 13-page policy paper this week proposing wealth funds and robot taxes to manage the economic fallout. Not one proposal in that paper addresses ownership of the AI training data generated by skilled physical labor.

The workers being displaced built the intelligence that is replacing them. They own none of it.

This is the defining workforce question of our time. And it is being answered right now, in real factories, without the workers at the table.

Florida's first Applied AI program sits in the middle of one of the most diverse working populations in the country. Miami is a manufacturing city. A logistics city. A garment city. A construction city. The workers in those industries are MDC's community.

The program has an opportunity to do something no other applied AI program in the country is doing. Train students not just to use AI tools but to understand and protect the labor rights of the people those tools are built on.

To Madeline Pumariega, President of Miami Dade College. To Manny Perez, Dean of Engineering Technology and Design. This series is part of a larger framework that I want to bring into that conversation formally.

To Pedro Santos and Mr. Knight at Entech. The panel discussion we shared was the beginning of this conversation. The framework has grown significantly since then and the Entech network represents exactly the kind of industry partner a pilot needs.

The capstone project for Florida's first Applied AI program should not just demonstrate what AI can build. It should demonstrate what AI must protect.

I help business owners design autonomous financial systems that work alongside their employees and strengthen the way their teams make decisions. My approach is grounded in years of seeing what happens when systems are built without people at the center.

Follow the blog at mindfuldollar.blogspot.com.

#MiamiDadeCollege #AppliedAI #LaborEquity #MiamiDynamics #ResponsibleAI #OperationsAccounting #NaslyDuarte

 The Mindful Dollar  ·  AI Explained Simply

"Skilled Labor Is Dead." I Disagree.

By Nasly Duarte | Mindful Dollar — Doing More With Less

I was sitting in a virtual live event this week when the speaker put up a pyramid. Tech at the top. Media and Data below it. Intellectual Property in the middle. And near the bottom, in red text: Skilled Labor. Component Labor at the base.

Then the speaker said it: "Skilled labor is dead."

The chat started moving. People nodding along. The room was full of builders and tech-forward thinkers ready to automate the future from behind a screen.

And I thought: that's not just wrong. It's incomplete in a way that could actually hurt people.

I've spent 20 years in accounting. I've lived the screen-only career. And what I've learned — through my body, not just my brain — is that the conversation about the future of work is missing something critical.

The Pyramid Gets It Backwards

The U.S. construction industry needs to attract 349,000 new workers in 2026 alone, according to Associated Builders and Contractors. Over the next decade, the industry will need 1.9 million workers just to keep up with growth and retirements. And 91% of construction firms report struggling to find qualified workers.

The retirement cliff is staggering: 41% of the construction workforce will retire by 2031. For every five Baby Boomers leaving the trades, only two younger workers are coming in behind them.

This isn't just construction. In manufacturing, 2.1 million jobs could go unfilled by 2030. And 77% of manufacturers report ongoing difficulty even finding workers.

Meanwhile — and this is the part that should make anyone in the tech space pay attention — white-collar layoffs have dominated headlines in 2025 and 2026, with technology, media, and finance companies cutting tens of thousands of positions. The skilled trades are experiencing the exact opposite. Demand is outstripping supply.

Every piece of AI technology we build still needs physical infrastructure. Servers need buildings. Buildings need electricians. Data centers need cooling systems. The cloud lives in a warehouse somewhere, and somebody had to pour that concrete, run that wiring, and connect those pipes.

When I hear "skilled labor is dead," I hear someone who has never had to call a plumber on a Sunday.

But that's not actually the argument I want to make. The real issue goes deeper.

What 20 Years at a Desk Taught Me That No Conference Will

Here's what nobody warned me about when I started my accounting career: sitting at a desk for hours and hours is a health hazard.

It doesn't matter if you work four-day weeks or seven-day weeks. It doesn't matter if AI cuts your workload to four hours a day. If you're sitting for long stretches, your body is paying a price. Slowly. Quietly. Until it isn't quiet anymore.

I lived it. Years of sedentary work did real damage to my body — damage I didn't see coming until it was already done. If you want the full story, follow my Think Like a Healer series, where I document what years of sedentary work actually does and what I'm doing to reverse it.

That experience gave me a perspective on the future of work that I don't hear anyone in the AI space talking about.

The Balance Problem

Tech work is a lot like accounting work. It takes enormous brain power. Hours of deep focus. Mental stamina. You're solving complex problems, holding abstract systems in your head, making decisions that ripple downstream.

But the human brain doesn't work in isolation from the body.

Even if we build the most incredible AI tools. Even if we automate every workflow. Even if we can run a business in four hours a day from a laptop — we still need to develop both our mind and body. Not as a nice-to-have. As a biological requirement.

Your brain chemistry needs physical output. Not just for fitness. For clarity. For regulation. For the kind of deep creative thinking that no amount of screen time produces on its own.

You can't optimize your way out of that with a better prompt.

I call this the Balance Problem, and I think it's the blind spot in every conversation about the future of AI and work.

The Interchange

Here's what I think is actually coming over the next five to ten years. I'm calling it The Interchange — the convergence of tech workers picking up trade skills and trade workers picking up tech skills. Not because the market forces them to. Because their bodies and brains require it.

The Claude builder who automates their entire content pipeline will pick up woodworking, or gardening, or welding — because they realize their sharpest thinking happens after they've used their hands.

The electrician who runs a crew of ten will start using AI to handle estimates, scheduling, and accounting — because they realize the administrative burden is what's actually burning them out.

This reminds me of the Netflix documentary The Biggest Little Farm, where John and Molly Chester buy a barren plot of land outside Los Angeles and spend eight years turning it into a thriving, biodiverse farm. The whole lesson of that film is that the ecosystem balances itself out — but only when you let both sides exist. The soil needs decomposition and growth. The land needs predators and prey. Nothing thrives in isolation.

AI — my hope — will balance us the same way. Not replace skilled labor. Balance us.

That's why I'm building Mindful Dollar at the intersection of both. I'm studying Applied AI and building software architecture — and I'm also listening to my body after two decades of desk work. "Doing More With Less" isn't just about efficiency. It's about building a life that doesn't break your body to feed your brain.

Where Do You Stand?

I wrote this post because I couldn't let "skilled labor is dead" sit unchallenged.

Are you a skilled trade and tech combo person? A developer who's picked up a physical craft? A contractor who's learning to automate? Are you interested in using AI not just to build faster, but to build a more balanced life?

Where do you see trade skills going — not just in Claude, but in the real world?

Drop a comment, send me a message, connect with me on LinkedIn. The best responses will show up in a follow-up post, because this conversation is bigger than one article.

We're building in public. Let's figure out what we're actually building toward.

Follow the Think Like a Healer series for more on what years of sedentary work does to your body — and how to reverse it.

Mindful Dollar | Nasly Duarte | Doing More With Less

#BuildInPublic #SkilledTrades #AI #TechAndTrades #MindfulDollar #DoingMoreWithLess #ThinkLikeAHealer #FutureOfWork #BalanceProblem

Sources

• Associated Builders and Contractors (ABC) — "Construction industry must attract 349,000 workers in 2026" — abc.org
• Associated General Contractors of America — 91% of firms struggle to find qualified workers
• National Association of Home Builders (NAHB) — 41% of construction workforce will retire by 2031; housing industry labor shortage carries $10.8 billion annual economic impact — nahb.org
• Deloitte & The Manufacturing Institute — 2.1 million manufacturing jobs could go unfilled by 2030; 77% of manufacturers report difficulty attracting workers — deloitte.com
• Academy of Craft Training — Construction will need 1.9 million workers over the next decade — academyofcrafttraining.org
• Skillwork — For every 5 Baby Boomer retirees, only 2 younger workers enter the trades — skillwork.com
• Metaintro — White-collar layoffs in tech/media/finance vs. trades demand outstripping supply, 2025–2026 — metaintro.com
• U.S. Chamber of Commerce — America Works Data Center, industry labor shortage data — uschamber.com
• The Biggest Little Farm (2018) — Directed by John Chester. Available on Netflix, Hulu, and Amazon Prime Video.

Is n8n Dead for Content Workflows?

The Mindful Dollar  ·  AI Explained Simply

Google Just Put an AI Content Engine Inside Your Spreadsheet. Is n8n Dead for Content Workflows?

By Nasly Duarte | Mindful Dollar — Doing More With Less

I need to start with a confession: I almost mass-deleted three n8n workflows this week.

I was organizing my LinkedIn content topics in Google Sheets — hashtags, hooks, post drafts, status columns — and then I saw it. A little purple cross icon appeared with a label I hadn't noticed before: "Drag to fill with Gemini."

I dragged it. And Gemini started filling my rows with content. Not random content. Content that matched my column headers and the patterns in my existing rows. It pulled from the web. It categorized. It wrote draft hooks based on the topics I'd already started.

I sat there staring at it like… wait. Did Google just eliminate half my automation stack?

I want to know if you had the same reaction — or if you think I'm overreacting. Keep reading and tell me at the end.

What Actually Changed (This Literally Just Happened)

Google rolled out a major Gemini update to Workspace on March 19, 2026. The Sheets update is the one that matters for builders like us who plan content in spreadsheets.

Here's what "Fill with Gemini" actually does:

• You set up column headers (Topic, Hook, Hashtags, Post Draft, Status)
• You fill in a few rows manually so Gemini can see the pattern
• You drag down and Gemini auto-populates the rest — pulling from the web, categorizing, even writing draft copy

It's not just autocomplete. It runs a separate web search for each row. It reads your column headers and figures out what data to pull. Google's VP of Product described it as Gemini being able to "figure out how to go find what you need" just by reading the structure you've built.

Available now for Google AI Ultra and Pro subscribers.

My Hot Take: Gemini Replaces the Brain. n8n Is Still the Body.

What Gemini in Sheets Does Well

Topic research and enrichment. If I have a column of broad topics — "Miami construction workforce," "AI in accounting," "contractor licensing Florida" — Gemini fills adjacent columns with trending angles, relevant statistics, and draft hooks. That used to require a separate n8n node hitting an AI API.

Pattern-based content generation. Write three posts in a specific format, drag down, and Gemini generates more in that same pattern. For batching a week's worth of content in one sitting, this is fast.

Zero setup cost. No webhook URLs, no OAuth tokens, no node configuration. It just works inside the sheet you already have open.

What Gemini in Sheets Cannot Do

It cannot publish. Gemini fills your spreadsheet. It does not post to LinkedIn. You still need either a scheduling tool or an automation platform to move content from sheet to platform.

It cannot run on a schedule. Gemini responds when you interact with it. There's no "run this every Monday at 6 AM" trigger. n8n's Schedule Trigger exists specifically for this.

It cannot handle approval workflows. If you want a human review step before publishing (and you should — more on this below), Gemini doesn't offer that. n8n can route a draft to Telegram or Slack for your sign-off before it goes live.

It doesn't close the loop. After a post publishes, n8n can mark the row as "Posted" and add the live URL back to your sheet. Gemini doesn't do post-publish tracking.

Here's Where I Want to Fight About It

I think most builders are overengineering the research step.

If you're paying for Google AI Pro anyway, why are you running a 10-node n8n workflow with Perplexity and OpenAI just to generate topic ideas and draft hooks? Gemini does this natively now, inside the sheet, with zero config.

But — and this is important — I also think anyone publishing AI-generated content straight to LinkedIn without human review is playing with fire.

Where do you land on this?

• Are you comfortable with fully automated post-to-publish pipelines?
• Or do you keep a "Ready" column and review every draft before it goes out?
• Has an AI-generated post ever embarrassed you? (Be honest.)

I keep a human-in-the-loop step because my voice is my brand. But I know builders who skip it entirely and post three times a day on autopilot. I want to hear what's actually working for you.

The Stack I'm Landing On (Tear It Apart)

Here's my current thinking. Tell me what you'd change:

Layer	Tool	Why
Topic research & draft generation	Gemini in Sheets	Faster, zero config, web-grounded
Human review & editing	Me, in the same Sheet	Edit Gemini's drafts, mark rows as "Ready"
Scheduled publishing	n8n	Reads "Ready" rows, posts to LinkedIn on a schedule
Status tracking	n8n	Updates row to "Posted," adds the live post URL

Gemini replaced the research and first-draft nodes in my n8n workflow. It did NOT replace the scheduling, publishing, and status-tracking nodes.

Gemini is the writer. n8n is the operations manager.

Less nodes. Less complexity. Same output. Maybe better output, because Gemini's web search is pulling fresher data than a cached AI prompt would.

The Bigger Pattern (This Isn't Just About Content)

This is something I keep seeing as AI tools mature, and I think it matters for every builder reading this:

The generation layer is getting commoditized. Every platform is adding AI content generation natively — Google Sheets, Notion, Canva, even email clients. The thing that still requires you to build something is the orchestration layer — getting the right content to the right place at the right time with the right approvals.

That's where n8n (or Zapier, or Make, or Claude Code) still earns its keep.

But here's my question for the group: how long until Google adds scheduling and auto-publish to Sheets too? If Gemini can already research, draft, and organize — publishing feels like it's next. And if that happens, does n8n lose its role in this workflow entirely?

I genuinely don't know the answer. I'm curious what you think.

What Should I Doing Next (And What I Want From You)

Should I simplify my n8n workflow this week. Remove the OpenAI research nodes and let Gemini handle topic enrichment directly in my content calendar sheet. My n8n setup will get leaner — it just reads, publishes, and updates.

Doing more with less. That's the whole point.

Next week, I'm building my full n8n workflow setup — screenshots, node configs, and the Google Sheet template. So you can use it or tell me what's wrong with it.

But before that, I want to hear from you. Seriously. Drop a comment, reply, DM me — whatever works:

1. What does your content automation stack look like right now? (Sheet + n8n? Notion + Zapier? Something else entirely?)
2. Have you tried "Fill with Gemini" yet? What was your first reaction?
3. Human review or full autopilot? And has skipping review ever burned you?
4. Hot take: will Google eventually add scheduling and publishing directly to Sheets? Or is that a bridge too far for a spreadsheet app?

The best answers are going in next week's post. I'll credit you and link your profile. Build in public means building together.

---

Connect with me on LinkedIn — I'm documenting this entire workflow evolution .

Mindful Dollar | Nasly Duarte | Doing More With Less

---

#BuildInPublic #n8n #GeminiAI #GoogleSheets #ContentAutomation #LinkedInStrategy #MindfulDollar #DoingMoreWithLess

It’s 2026. Why Are We Still Hiring People to Be Entire Departments?

 It’s 2026. Why Are We Still Hiring People to Be Entire Departments?

How one job post exposes an industry-wide systems failure — and what AI could fix tomorrow.

By Nasly Duarte

AI Solution Architect | Accounting & Operations Strategist

The Job Post That Stopped My Scroll

I was scrolling through job postings the other day — something I do regularly, not just for myself, but to study the market. When you’ve spent over a decade working in accounting and operations across construction, retail, and service industries, you start reading job descriptions the way a mechanic listens to an engine. You can hear what’s wrong before anyone tells you.

This particular post caught my eye. Assistant Controller. A company doing wastewater treatment projects across three counties in South Florida. Salary range: $61K to $90K. Benefits included. Sounded reasonable.

Then I read the responsibilities.

General ledger management. Accounts payable. Accounts receivable. Payroll. Monthly, quarterly, and annual financial reporting. Internal controls. GAAP and IFRS compliance. Audit support. Budgeting. Forecasting. Cash flow management. Bank reconciliations. Staff supervision and mentoring. System implementations. Process improvements. M&A support.

I read it again. Then I counted. That’s not one job. That’s three.

Three Roles, One Title, One Salary

Let me break this down, because this is not a matter of opinion. These are distinct, well-defined roles in any properly structured finance department.

Role	Core Responsibilities	Market Salary
Assistant Controller	GL maintenance, month-end close, reconciliations, AP/AR oversight	$60,000 – $75,000
Controller	Financial reporting, internal controls, audit management, staff supervision, compliance	$90,000 – $130,000
CFO	Strategic planning, budgeting & forecasting, cash flow management, system implementations, M&A	$150,000+

That job post asks for all three tiers. At the bottom-tier price. This isn’t a company being intentionally exploitative — it’s a company that doesn’t have the internal structure to know the difference. And that’s a much bigger problem.

The Problem Isn’t the Person. It’s the System They Don’t Have.

Here’s what I’ve learned from working inside companies like this: the bloated job description is never the disease. It’s always the symptom.

When a company posts a role that spans three departments, what they’re really telling you is that they don’t have integrated systems. Estimating lives in one place — maybe a spreadsheet, maybe a standalone tool. Project management lives in another. Accounting lives in Sage or QuickBooks or whatever was set up ten years ago and never revisited.

Nobody reconciles the estimate to actual costs in real time. The project manager knows they’re over budget on materials, but accounting doesn’t see it until month-end close. By then, the damage is done. The variance shows up as a surprise in the financial statements instead of a flag on the dashboard weeks earlier.

So what do they do? They hire a person to be the bridge. One human being to manually connect all the disconnected pieces. They ask that person to reconcile the GL and manage cash flow and build internal controls and run audits and implement new systems and supervise staff. Because without a system, everything falls on a person.

That person burns out. Leaves. And the cycle starts over with a new job post that looks exactly the same.

The AI Elephant in the Room

It’s 2026. Let that sink in for a moment.

NLP models can read and categorize invoices. AI agents can automate recurring journal entries and flag anomalies. Machine learning can forecast cash flow based on historical patterns and project timelines. Automation can handle the repetitive, time-consuming close process that eats up the first two weeks of every month.

Half of what’s in these job descriptions is work that a well-designed system handles — not a person working 60 hours a week trying to hold everything together with spreadsheets and willpower.

The question isn’t whether AI can help. The technology exists. The tools are accessible. The question is: why isn’t leadership asking? Why are we still solving architecture problems with headcount?

I think the answer is simple and uncomfortable: many companies don’t know what they don’t know. They’ve never seen what an integrated system looks like, so they can’t imagine it. They hire executives with titles but no experience in modern systems design. And those executives hire people the same way they were hired — to fill seats, not to build infrastructure.

What This Actually Costs

Let’s talk about the real price tag of this pattern, because it’s not just an HR problem.

Turnover costs. Replacing a mid-level finance employee costs 50–200% of their annual salary when you factor in recruiting, onboarding, lost productivity, and institutional knowledge that walks out the door.

Bad data. When one person is doing the work of three, corners get cut. Reconciliations get rushed. Variances get missed. Financial statements become less reliable, which means decisions are being made on information that’s incomplete or wrong.

Late reporting. When budget variances don’t surface until month-end — or worse, quarter-end — you’re managing projects in the rearview mirror. In construction, where a single project can run into the millions, that delay can be catastrophic.

Human cost. This is the one nobody puts on a spreadsheet. The person in that seat is working nights and weekends. They’re stressed, exhausted, and isolated because no one else in the company understands the full scope of what they carry. They’re not just managing accounts — they’re managing the entire financial nervous system of the business with no support and no system underneath them.

People are being set up to fail by design. Not out of malice, but out of structural ignorance. And that has to change.

What the Fix Actually Looks Like

The good news is this isn’t a mystery. The path from chaos to clarity is well understood. It just requires someone who can see both sides — the accounting reality and the technology architecture.

In a properly integrated system, the estimate flows into job costing. Job costing feeds the general ledger in real time. Reporting is automated. Exceptions and variances surface the moment they happen, not thirty days later. Cash flow projections update dynamically based on project progress and billing schedules.

You don’t need a $500,000 ERP implementation to get there. You need someone who understands the accounting workflows and the technology — someone who can map the process, identify where data breaks down between departments, and build the connective tissue that turns fragmented information into a living, breathing system.

That person exists. Companies just aren’t looking for them because they don’t know to ask. They’re still writing job posts for three people crammed into one title, hoping the right human will somehow compensate for the missing architecture.

Two Questions, Two Audiences

This isn’t about shaming anyone. Companies like the one in that job post are the backbone of infrastructure — they build the systems that give us clean water. They deserve better operational design. And the people they hire deserve to be set up for success, not survival.

So I’m asking two questions, and I want both sides of this conversation in the same room.

To employees: Have you ever been hired for one job and ended up doing three? What did that cost you — not just professionally, but personally? How long did you stay before you realized the role was structurally impossible?

To business owners: What’s really stopping you from investing in the systems that would eliminate the need for these impossible hires? Is it budget? Is it not knowing where to start? Is it that no one has ever shown you what the alternative looks like?

Drop your answers below. I want employees and owners seeing each other’s reality — because the gap between what companies post and what employees experience is a conversation that’s long overdue.

Nasly Duarte is an AI Solution Architect and accounting strategist based in Miami, FL. She builds intelligent systems that bridge finance and operations, and writes about the intersection of technology, workforce development, and human well-being.