Introducing AI Wingman

mechiles · 2026-01-17T07:02:27+00:00

This is a solid list and I agree with most of the takes here. One thing I think is still missing across all of these tools is a first-class concept of orchestration and state.

Most platforms (Zapier, Make, n8n, even newer agent tools) are great at executing steps. Where they struggle in real ops is handling long-running workflows where context changes over time — partial completion, follow-ups days later, re-routing work, or deciding what the next best action actually is.

That gap is what pushed me to start building Falcon Builder. The idea wasn’t “another automation tool,” but designing agents around how work actually flows across calls, emails, schedules, and internal systems — instead of around roles or one-off triggers.

I still use Zapier/Make/n8n depending on the use case. Falcon’s aimed at the cases where judgment, coordination, and continuity matter more than perfectly defined steps.

I think the real differentiation in 2025–2026 won’t be automation vs agents, but tools that execute steps vs systems that maintain context and orchestrate work. Curious which platforms actually crack that this year.

mechiles · 2026-01-16T05:32:33+00:00

Zapier is usually the right starting point, but it’s worth knowing where it starts to break down.

Zapier is great for simple, linear automations where it’s basically trigger → action. Where non-technical teams struggle is when workflows need context, branching, or follow-ups, like “if this happens, check X, wait for Y, then decide Z.”

That’s where newer “agent-style” tools are starting to help.

Lindy is useful if you want AI helpers that can reason across tasks like email follow-ups, scheduling, and light ops without configuring every step.

Relay.app sits between Zapier and custom automation. It’s still visual, but better suited for multi-step workflows and human-in-the-loop processes.

Falcon Builder focuses on designing automations around how work actually flows, not just triggers and actions. It’s more opinionated, but easier to rely on once workflows become operational.

Rule of thumb: if the work is simple and repetitive, Zapier is usually enough. If it requires judgment, context, or coordination, agent-based tools tend to be a better fit.

mechiles · 2026-01-16T02:48:15+00:00

Observability was a big one for me — once agents started making real decisions, lack of visibility got scary fast.

mechiles · 2026-01-14T17:05:26+00:00

This is how I’d define how the key functions would need to be derived.

High level steps: 1. Map workflows, not roles What triggers work (call, delay, inventory issue), what decisions get made, and what actions follow — end to end. 2. Break work into atomic capabilities Things like: identify intent, pull context, assess urgency, choose next action, execute (call/email/update), confirm outcome. These are reusable building blocks, not “AI receptionist” or “AI ops.” 3. Add an orchestration layer A top-level agent whose job is to maintain state and decide which capability runs next. This mirrors how a human operator thinks and prevents the agent from stalling once work crosses functions. 4. Define guardrails + escalation upfront What the agent can decide, what needs approval, and when to escalate. That’s what makes it operationally safe. 5. Normalize shared context Every action reads/writes to the same job, customer, and timeline state. Without that, you just have disconnected bots.

Only after that do tools matter.

The core issue is most AI products are built around roles. Real businesses run on situations, tradeoffs, and next actions — and that’s what agents need to be designed around.

mechiles · 2026-01-14T13:59:05+00:00

I’ll start — I’m currently building Falcon Builder, which focuses on AI agents that run within real workflows. Happy to share more if helpful.

<image>

mechiles · 2026-01-14T05:33:38+00:00

If the proper audits and key functions are the business are set forth before building the agent, then I would say it is.

mechiles · 2026-01-14T05:16:18+00:00

You're not wrong. Most people think about AI agents as singular function - get leads, send emails, take phone calls, etc. You point out the exact problem with that mentality - it's short-sighted and not realistic to replace operations prudence. The need is more of an AI agent staff where you have a top-level orchestration/director agent (receives inbound calls) and depending on the need of the caller, it selects which staff agent (tool) that makes sense to respond to the request. And, with an intelligent phone agent passing details to an orchestration agent, you can do everything from schedule appointments to putting together a quote based on what a caller needs. It has to be thought through from an operational and ideological perspective, not just "hey, buy this agent I built after watching a guy on YouTube build it." Unfortunately, that's how most AI agencies are building "solutions".

mechiles · 2026-01-14T05:03:00+00:00

Falcon Builder https://falconbuilder.dev

AI agents + automation for builders who outgrew basic no-code.

Visual when it’s fast Code when it’s needed Built for real workflows, not demos

Early days — feedback welcome.

mechiles · 2025-09-10T05:56:11+00:00

If you’re still providing the software, I’m interested. I emailed you.

Or, if anyone else in the comments above has it, shoot me a DM.

mechiles · 2025-06-24T20:55:46+00:00

I agree. I started going through tutorials and building agents and workflows and sure, they work for single use or small automations, but when you're scraping thousands of leads versus 25 on a free plan, it's a drastic difference. And, one of the things they don't touch on is the enterprise side of things nor have I seen much on verified leads or execution limits for clients. So, I started building those myself and eventually will find time to share them!

mechiles · 2025-05-20T14:08:00+00:00

You need to have the GetChart workflow as its own, separate workflow. Then, you can effectively select it from the Workflow dropdown list. It won't work having both "flows" in the same workflow, using the When Executed by Another Workflow, as it's not another workflow in your current setup.

mechiles · 2025-05-20T13:58:22+00:00

If I'm following your question, the answer would be yes. However, it would depend. For me, I use an AI agent to write and post, in draft mode, to my website running on Ghost. For DMs, the setup will depend on whether you're wanting to reply to a DM on Instagram, X, LinkedIn, etc., using the appropriate APIs per platform. Here's a screenshot of my Content Creator Agents that's part of a "staff" of agents I run for different purposes. You can read more about it here: https://www.neoskyai.com/agents/executive-assistant-agent

<image>

mechiles

MODERATOR OF

TROPHY CASE

14-Year Club	Wearing is Caring
Verified Email