Most AI consultants will send you a proposal by end of week. ABUZZ sends you a working prototype. Here's exactly what that looks like — unglamorous Notion docs, half-built n8n flows, and all.
Monday and Tuesday: We Ask Uncomfortable Questions Before We Touch Anything
Day 1 is a discovery call. Not a sales call. There's a difference, and you'll feel it within the first ten minutes.
We're not asking what your goals are for the next five years. We're asking who manually copies data from your order form into your accounting system. We're asking why your ops manager hasn't taken a full day off in three months. We're asking which part of your business would collapse if one specific person resigned tomorrow. These are not comfortable questions. They are the right ones.
By end of Day 1, we've created a shared Notion workspace — yes, actual Notion, not a deck you'll never open again — with a rough operational audit, your three biggest friction points ranked by impact, and a first draft of what we think we can build in five days. You can see it, comment on it, and tell us we're wrong. That's the point.
Day 2 is a process map workshop. We get on a call, sometimes in person if you're in Singapore and the timing works, and we walk through your actual workflows. Not your ideal workflows. Your actual ones. The ones held together by WhatsApp forwards and a shared Excel file that three people are editing simultaneously. We map these in real time using a shared Miro or FigJam board. You will see your own operations drawn out in front of you and think, "I can't believe we've been doing it this way." That reaction happens more often than you'd expect. As we wrote in our post on the projects we've turned down, if a business isn't ready to look honestly at how it operates, no AI tool in the world will fix it. Day 2 is where we find out if you're ready.
Wednesday and Thursday: Something Gets Built. On Screen. In Front of You.
Day 3 is where most consultants would still be writing a requirements document. We're building.
The first workflow goes into n8n — our automation backbone of choice for most Singapore SME deployments. It's not the flashiest tool, but it connects to almost everything, runs on your own infrastructure if needed, and doesn't charge you per task at a rate that quietly bankrupts you six months later. Depending on what we scoped, Day 3 might produce a WhatsApp Business API trigger that auto-routes inbound customer queries to the right department, a Claude-powered document parser that reads your supplier invoices and logs them into Supabase, or a lead qualification flow that scores inbound enquiries before they hit your sales team's inbox. None of this is theoretical. You can watch the flow execute on screen.
Day 4 is staging deploy. We push the build into a test environment — not live yet, because breaking things in production is a bad look — and we run it with real data samples. This is where the unglamorous part really shows up. Slack messages at odd hours. A field that doesn't map correctly because your CRM uses a slightly different date format. A webhook that fires twice instead of once. We fix these things on Day 4 so you don't encounter them on Day 5. The Slack channel we set up on Day 1 is active throughout. You're not waiting for a status update email. You're watching it happen.
The tools in play by end of Day 4: n8n for workflow orchestration, Claude for any language-heavy processing (summarisation, classification, drafting), Supabase as the data layer when a lightweight database is needed, and WhatsApp Business API if customer-facing communication is part of the scope. These aren't random choices. They're the stack we've refined across deployments with logistics firms, F&B operators, professional services companies, and distributors across Singapore. If you want to understand what a fuller deployment looks like end-to-end, the 90-day F&B chain transformation we documented is a good reference point.
Friday: You See It. You Break It. We Fix It Together.
Day 5 is client review. Not a presentation. Not slides. A live walkthrough of what was built, running on your actual data.
We walk you through the flow step by step. You ask questions. You try to break it — and we encourage this, because the things you try on Day 5 are far less painful than the things your team discovers on Day 15. We document every gap, every edge case, every "what happens if the customer sends a voice note instead of text." These go straight into the Notion workspace as a punch list. Nothing gets lost in an email thread.
The honest version of Day 5: it's rarely perfect. There will be something that needs adjustment. A conditional logic branch that didn't account for a scenario your team raises. An output format that needs reformatting before it's useful. This is normal. A first-week build is a proof of concept with real bones, not a finished product. What Day 5 tells you is whether the direction is right, whether the tools are working, and whether the team you're working with knows what they're doing. That last one is what you're really evaluating.
Your team, by the way, has been looped in throughout the week. Not just you. The ops manager who owns the broken process. The sales coordinator who's been manually sending follow-up emails. They've seen the build. They've given feedback. They're not inheriting a system someone else designed without asking them. Same team. Bigger output. That's the whole point of the exercise.
If any of this matches what you've been looking for — actual builds, actual tools, actual transparency — talk to us. Tell us where your operations are breaking. We'll tell you honestly whether we can fix it in a week, or whether it's a longer project. Either way, you'll leave the first call knowing more about your own business than when you walked in.
