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

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

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.

 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