Share your best AI workflow. We could show it to 2M+ people.

Today, I wanted to see how far an AI agent could go if I gave it a real business instead of a predefined automation. I entered binayah.com into Awish.ai. Binayah is a real estate company, and instead of telling Awish.ai exactly what workflow to build, I asked it to analyze the business first and find an automation opportunity. It suggested a customer acquisition funnel, which I reviewed and approved. Around 10 minutes later, the automation was ready. Step-by-step: 1. I entered binayah.com into Awish.ai. 2. Awish.ai agents analyzed the website and how the business operates. 3. Awish.ai identified customer acquisition as an area that could be automated. 4. It suggested a funnel designed to capture and qualify potential leads. 5. I reviewed the suggestion and approved it. 6. Awish.ai created the workflow and connected the required steps. 7. The funnel was ready to use in around 10 minutes. What I find most interesting is that I didn’t start by designing a workflow. The system first understood the business, found an opportunity, suggested what should be automated, and built it only after I approved. That feels much closer to having an automation consultant inside the product than using a traditional workflow builder.

After a sales call, the conversation is only part of the work. Someone still needs to write the notes, update the CRM, remember the next step, prepare the follow-up email, and make sure the deal does not disappear between meetings. I wanted that entire post-call process to happen automatically. I created an Awish workflow that starts when a sales call ends. It analyzes the conversation, extracts the important sales information, updates the CRM, creates the next actions, drafts a personalized follow-up email, and sends the team a short summary. The workflow looks for the information I would normally write down myself: what the prospect needs, the objections they raised, their timeline, agreed next steps, and anything that could affect the deal. Customer-facing actions stay under my control. The workflow prepares the follow-up, but I can review important messages before they are sent. Step-by-step: 1. I tell Awish what I want to happen after every sales call: analyze the conversation, update the CRM, prepare the follow-up, and notify the team. 2. Awish understands the request, plans the workflow, and determines which applications are needed. 3. I connect my meeting platform, HubSpot, Gmail, and Slack to the automation. 4. When a call ends, the workflow analyzes the transcript and extracts the prospect’s needs, objections, timeline, decisions, and agreed next steps. 5. It creates or updates the contact and deal in HubSpot and adds any follow-up tasks that came out of the conversation. 6. It drafts a personalized Gmail follow-up based on what was actually discussed instead of using a generic sales template. 7. It sends a short Slack summary to the team with the deal status, important points, and next action. Instead of a sales call ending as a transcript or a page of notes, it immediately becomes structured CRM data, clear next actions, and a follow-up that is ready to review. The useful shift for me is that the workflow is not replacing the sales conversation. It is handling everything that normally gets forgotten or delayed after the call.

I created a website lead workflow that researches each company, scores the opportunity, updates my CRM, drafts a personalized reply, and notifies me on WhatsApp. I had previously built similar workflows with Claude Code, but connecting external applications was often the hardest part. I had to manage OAuth setup, credentials, APIs, and different integration requirements for every app. I also found it difficult to monitor and control completed automations from WhatsApp without building additional infrastructure. To solve this, I created Awish, a tool focused on AI-powered automation. Instead of manually designing every workflow, I describe the result I want in chat. Awish’s agents understand the request, plan the automation in the background, determine which applications and steps are required, and prepare the complete workflow for me. When a new lead submits my website form, the workflow researches the company, evaluates the lead against my criteria, assigns a score, and adds the contact and research results to my CRM. It then drafts a personalized response based on the lead’s company and needs before sending me a WhatsApp notification for review. The application connections are handled through a simple sign-in flow. I connect my personal accounts with a click instead of manually working with OAuth code, API keys, or custom authentication logic. Once the workflow is active, I can monitor it, receive updates, and manage its actions directly from WhatsApp without opening the Awish application. Step-by-step: 1. I open the Awish chat and describe the workflow I want: when someone submits my website form, research the company, score the lead, add it to my CRM, draft a personalized response, and notify me on WhatsApp. 2. Awish’s agents analyze the request and create the application and automation plan on my behalf, including the trigger, research steps, lead-scoring logic, CRM fields, response draft, and notification. 3. I review the proposed plan and sign in to the required applications with my personal accounts to connect them to the workflow. 4. Awish builds the automation so each new website submission triggers company research and collects the information needed to evaluate the opportunity. 5. The workflow scores the lead, creates or updates the CRM record, and stores the contact details, company research, and lead score in the appropriate fields. 6. It drafts a personalized response using the information submitted by the lead and the additional company research. 7. I connect WhatsApp from the Awish chat, and the workflow sends me the lead details, score, CRM update, and response draft there. 8. I review and manage the automation directly from WhatsApp without needing to open Awish or build a separate messaging integration. The result is a lead-management workflow I can create through a conversation, connect to my existing applications without manually implementing OAuth, and control from WhatsApp while the agents handle the planning and execution in the background.

A chocolate factory client had a simple but expensive sales problem: good conversations with buyers sometimes went quiet because nobody followed up at the right time. Some opportunities were waiting on sample feedback, pricing, private-label details, minimum order quantities (MOQs), packaging, or distributor discussions. The opportunities were still active, but they were easy to lose track of. I built a follow-up workflow for the client in Awish. Step-by-step: 1. I opened the Awish chat and wrote: “Track our open sales opportunities from Microsoft Teams and Google Sheets. Every business day, review the latest customer conversation, sales stage, planned follow-up date, customer interest, and how long we’ve been out of touch. Find opportunities that need follow-up around samples, quotations, private label, MOQ, packaging, or distribution. Explain why each customer should be contacted, recommend the next action, and prepare a personalized Teams follow-up message based on the real conversation history. Never send anything without the salesperson’s approval. When the customer replies, close the old follow-up action and update the Sales Master record.” 2. Awish understood the request, planned the workflow, and selected Microsoft Teams and Google Sheets for the process. 3. I connected the client’s accounts, reviewed the plan, and approved the automation. 4. When a new customer conversation takes place in Teams, Awish updates the related sales record. 5. Every business day, it reviews open opportunities and finds deals that are overdue, at risk, or ready for the next follow-up. 6. For each opportunity, it explains why follow-up is needed and what the salesperson should do next. 7. Awish prepares a personalized Teams message using the actual conversation history, but waits for the salesperson’s approval before sending anything. 8. When the customer responds, the previous follow-up is closed and the opportunity status in Google Sheets is updated automatically. Now the sales team gets a prioritized daily list of who needs attention, why they need attention, and what the next message should be—without manually reviewing every old conversation. I want to keep building more workflows like this for real businesses. If you have a complex, repetitive process in your company that you think should be automated but you’re not sure how to build it, send it to me. I’d be happy to see if I can turn it into a working automation with Awish.

I wanted to see what Awish would automate first if I gave it a real client business instead of a predefined workflow. I used Martolia Marble, one of my previous clients, and gave Awish the website. I asked it to analyze the business, suggest automations that could support growth, and build them only after I approved them. Awish analyzed the website and proposed several opportunities. I chose two: a lead generation and email outreach workflow, and an Instagram workflow that tracks relevant trends, plans content, creates posts, and publishes them. Step-by-step: 1. I gave Awish the Martolia Marble website and asked it to analyze the business. 2. Awish identified areas where automation could support growth and suggested workflows. 3. I approved a lead generation workflow that finds relevant prospects and prepares personalized email outreach. 4. Awish selected the required apps, I connected the accounts, and the agents built the workflow. 5. I also approved an Instagram workflow that analyzes relevant trends, plans upcoming content, creates the posts, and publishes them. 6. Once the accounts were connected, both automations were ready to run without me manually building each step. What I liked most was starting with the business rather than with an automation idea. I gave Awish the website, reviewed its suggestions, and approved only the workflows that made sense for the client.

I conducted a workflow experiment with Awish, the product I built, and the results surprised me. I think this approach could be useful for anyone who wants to automate more of their business but is not sure where to start. I gave Awish my website, and it identified the automations my business was missing. The difficult part was not always building a workflow; it was figuring out which tasks were worth automating first. I opened Awish and asked: “Analyze my business from awish.ai, suggest automations that could improve how I work, and only build them after I approve.” Awish’s agents analyzed the website to understand what the business does, how customers interact with it, and where repetitive work could be automated. Instead of asking me to design a workflow from scratch, Awish suggested several automations based on the business. One suggestion was a lead workflow that finds relevant prospects and automatically prepares and sends personalized outreach emails. Another was a website inquiry workflow that analyzes new customer requests, identifies what they need, and sends me the important details as a WhatsApp notification. It also suggested a content workflow that creates and publishes posts for Instagram, X, and LinkedIn based on the business and its content strategy. I chose the lead generation and automated email workflow. Step-by-step: 1. I opened the Awish chat and asked it to analyze my business from awish.ai, suggest automations that could improve it, and only build something after I approved it. 2. Awish’s agents analyzed the website and identified repetitive sales, customer communication, and content tasks that could be automated. 3. Awish suggested a lead generation and email outreach workflow, a website inquiry analysis and WhatsApp notification workflow, and a social content workflow for Instagram, X, and LinkedIn. 4. I selected the lead generation and automated email workflow. 5. Awish’s agents understood the request and created the workflow plan, including how leads should be found, what information should be collected, and how personalized outreach should be prepared. 6. Awish selected the applications needed for the workflow and showed me the connections before anything was built. 7. I approved the plan and connected my personal accounts to the required applications through the sign-in flow instead of manually setting up each integration. 8. Awish built the automation within minutes, so new leads could be identified, researched, and contacted through the workflow without me having to design each step manually. What I like about this approach is that I do not need to know the exact automation I want before I start. I can begin with the business itself, let the agents identify useful opportunities, choose the one that makes sense to me, and then approve the build.