FutureMinds

Practical AI systems for smarter business decisions. Find what’s worth automating, what should stay human, and where AI can actually save...
Johor Bahru, MY
Created byProfile pictureGrayson Jong
23 joined
Profile picture
Grayson JongProfile picture@grekkie·18h

Automation Starts Before the Automation

A workflow can fail before the automation even starts.

Example:

A maintenance request enters the system:

“Water leaking.”

The temptation is to immediately automate:

→ classify it

→ route it

→ notify a vendor

→ update the tenant

But there’s a problem.

Where is the leak?

How severe is it?

When did it start?

Are there photos?

Can someone access the property?

Has the same issue happened before?

If the input is incomplete, the workflow creates more back-and-forth downstream.

So I'm testing a slightly different way of thinking about automation:

1. Capture the request

2. Check whether the information is complete

3. Collect what's missing

4. Then trigger the operational workflow

The interesting part isn't always replacing a manual task.

Sometimes the biggest opportunity is preventing unnecessary work from being created in the first place.

For anyone building automations: how often do you check input quality before designing the workflow?

Profile picture
Grayson JongProfile picture@grekkie·1d

The Automation Gap Nobody Measures

A workflow can respond instantly and still be broken.

That’s something I’ve been thinking about while looking deeper into property and real-estate operations.

Take a new lead:

Lead arrives → instant reply sent → looks automated.

But then:

• The CRM record is incomplete

• Nobody clearly owns the lead

• The next follow-up isn’t scheduled

• The lead changes status but nobody acts on it

• The conversation eventually goes cold

Or maintenance:

Tenant reports issue → AI classifies it → vendor is contacted.

But has the vendor actually accepted the job?

Has an ETA been confirmed?

Has the tenant been updated based on something that actually happened?

This is why I’m starting to think “time saved” by itself is a weak automation metric.

Before automating a workflow, I’d rather map:

Source → Capture → Owner → Next action → Exception → Confirmation → Closure

Then measure things like response time, time-to-owner, missed follow-ups, unresolved age and incomplete records.

Automation should remove friction from a working process — not make a broken process move faster.

What workflow have you seen that looks automated on the surface but still breaks underneath?

Profile picture
Grayson JongProfile picture@grekkie·2d

One boring workflow can be worth more than 10 AI tools.

Take a real estate lead:

Inquiry comes in → details are entered → lead gets assigned → agent follows up → viewing gets booked → notes go into the CRM → next follow-up gets scheduled.

None of those steps looks complicated.

But one weak handoff can mean:

• A slower response

• Missing CRM information

• A lead repeating themselves

• A forgotten follow-up

• An agent working with incomplete context

That’s why I’m becoming more interested in the workflow BEFORE the automation.

Before asking:

“What AI tool should we use?”

I think a business should ask:

Where does work wait?

Where is information entered twice?

What gets forgotten?

Which step happens often enough to measure?

Where is human judgement still necessary?

AI shouldn’t be the starting point.

The workflow should.

What repetitive business process would you audit first?

Profile picture
Grayson JongProfile picture@grekkie·3d

The Invisible Handoff

The expensive part of a workflow is often the handoff nobody measures.

Take a real estate lead.

The enquiry enters the CRM.

It gets assigned to an agent.

The system says the lead has been “handled.”

But has anyone actually taken ownership of the next action?

That gap matters.

Before automating a workflow, I’d measure four timestamps:

→ When the enquiry arrived

→ When someone became responsible for it

→ When the first meaningful response happened

→ When the next action was scheduled

Because these reveal very different problems.

A slow response might be a capacity issue.

A fast assignment followed by silence might be an ownership issue.

Repeated manual updates might be a process issue.

Automation should close a specific operational gap.

It shouldn’t just make a messy process move faster.

What process in your business looks “complete” inside the system but still depends on someone remembering what to do next?

Profile picture
Grayson JongProfile picture@grekkie·4d

THE EXPENSIVE PART OF A LEAD ISN'T ALWAYS GETTING IT.

I've been looking more closely at how real estate teams handle incoming leads.

And one workflow keeps standing out:

Lead arrives → someone sees it → someone qualifies it → someone owns it → follow-up happens → CRM gets updated → next action gets scheduled.

That's a lot of handoffs for something that sounds as simple as:

"We received a new lead."

Imagine a property enquiry comes in at 9:47 PM.

The prospect wants:

• 2 bedrooms

• Dubai Marina

• AED 2–3M budget

• investment rather than own use

• wants to speak tomorrow morning

The interesting AI opportunity isn't necessarily:

"Let AI sell the property."

It might simply be:

→ Extract those five details automatically

→ Match the enquiry to the right pipeline

→ Flag missing information

→ Assign ownership

→ prepare the next action

→ make sure the lead doesn't disappear into WhatsApp

The human still handles the relationship, advice, negotiation and closing.

That's an important distinction I'm learning while building AI Opportunity OS™:

Don't start by asking what AI can replace.

Start by finding where information, time or responsibility keeps falling through the cracks.

Sometimes the best automation opportunity is sitting between two human actions.

Profile picture
Grayson JongProfile picture@grekkie·5d

NOT EVERY AUTOMATION NEEDS AI

One mistake I think businesses can make is treating every automation problem as an AI problem.

I find it more useful to separate workflows into three buckets:

1. Rule-Based Automation

“If this happens → do this.”

Example:

New website lead → add to CRM → assign salesperson → create follow-up task.

You probably don't need AI for most of that.

2. AI-Assisted Automation

The workflow is predictable, but one step requires understanding messy information.

Example:

New enquiry → AI reads the message → identifies intent/budget/location → CRM records it → salesperson reviews the suggested response.

AI handles interpretation.

The system handles the workflow.

The human keeps control.

3. Agentic Automation

The AI is allowed to make multiple decisions and take actions across a process.

This can be powerful — but it's also where reliability, permissions, monitoring and exceptions become much more important.

So before choosing ChatGPT, Claude, n8n, Make, Zapier or another tool, ask:

What type of problem am I actually trying to solve?

Sometimes the smartest AI decision is realising that you don't need AI at all.

That's the kind of thinking I'm trying to build into AI Opportunity OS™ — identify the opportunity first, then decide what technology actually belongs there.

Profile picture
Grayson JongProfile picture@grekkie·6d

Before You Automate a Workflow, Run This 5-Question Test

Before you automate something in your business, ask yourself these 5 questions:

1. How often does it happen?

A 10-minute task happening 100 times a month can matter more than a 2-hour task happening twice.

2. Is the process predictable?

If the same basic steps happen every time, automation becomes much easier.

3. Does it actually need AI?

Copying data, sending reminders or moving information between systems may only need normal automation.

Use AI when the workflow involves things like interpreting text, classifying information, extracting data, summarising or drafting.

4. What happens when it gets something wrong?

The higher the risk, the more human oversight you need.

5. Can you measure the result?

Time saved.

Faster response times.

Fewer errors.

Lower cost.

More completed follow-ups.

If you can't define what “better” looks like before building it, it'll be difficult to know whether the automation actually worked.

This is one of the biggest ideas behind AI Opportunity OS™:

Problem → workflow → opportunity → solution → measurement.

Not:

Cool AI tool → find somewhere to use it.

If you've already gone through the free AI Opportunity Starter Kit and want the complete system, the full AI Opportunity OS™ goes deeper with the Workflow Mapper, Opportunity Score™, AI suitability framework, ROI tools, worksheets, 100 workflow opportunities, 60 research prompts and the 30/60/90-day roadmap.

Profile picture
Grayson JongProfile picture@grekkie·Sep 16

Before automating a workflow, measure the “before”

One mistake I think is easy to make with AI is building the automation first and deciding whether it helped afterward.

Before changing a workflow, write down four things:

1. Time — how long does the task currently take?

2. Volume — how often does it happen?

3. Rework — how often does someone need to correct or redo it?

4. Outcome — what business result is this workflow connected to?

Then automate a small part and compare.

If you can’t explain what improved afterward, the automation may be technically impressive without being commercially useful.

Map → measure → improve → automate → measure again.

Better AI decisions start with understanding the current process.

Profile picture
Grayson JongProfile picture@grekkie·Sep 15

New: AI Opportunity OS™ — Free Starter Kit

Not sure where AI actually belongs in a business?

I’ve made a free 8-page starter version of AI Opportunity OS™ to help you identify repetitive workflows, score AI opportunities, compare AI vs normal automation, and estimate whether an idea is worth testing.

Free to access. No subscription.

Start with the free kit, use the framework on one real workflow, and only move to the full toolkit if you find it useful.

Check it out:

Profile picture
Grayson JongProfile picture@grekkie·Sep 15

A “cool” AI workflow can still be a bad business decision

One thing I think people underestimate with AI automation is this:

A workflow can look impressive and still create almost no real business value.

For example, an AI agent might be technically advanced, but if it only saves 10 minutes a month, requires constant checking, or creates expensive mistakes, it probably isn’t a good first project.

A better AI opportunity usually has five things:

  • it happens often

  • it takes meaningful time or money

  • the process is clear enough to map

  • mistakes can be controlled or reviewed

  • the result can actually be measured

That’s why I think businesses should stop asking:

“What’s the coolest thing I can automate?”

and start asking:

“What recurring problem is expensive enough to justify fixing?”

The most valuable automation is often boring.

Things like:

  • lead follow-up

  • repetitive reporting

  • document sorting

  • customer request triage

  • scheduling

  • recurring admin work

FutureMinds is being built around this kind of thinking:

less hype, more measurable business value.

What’s one boring task in your business or work that you’d happily never do manually again?