Systems I've built for real businesses

The problem

NJS Royale Event Centre was growing fast, but bookings ran on phone calls, spreadsheets and memory. Tours were scheduled by back-and-forth messages, payments were tracked by hand with no reminders, and nobody could see who had toured, who was ready to book or which deposits were outstanding. Follow-ups were missed and bookings slipped away.

What I built

• Discovery first: mapped the full journey for the venue's three halls (Grande Royale, Signature and Ivycrest), including the rule that balances are due 14 days before the event.
• An 8-stage Event Booking pipeline: Tour Scheduled → Tour Completed → Interested in Booking → Payment Pending → Booking Confirmed → Event Completed → Closed / Lost, with 30+ custom fields.
• A branded tour-booking page in Zoho Bookings, with 30-minute slots, a shareable link and QR code. Every booking lands in the CRM automatically, and cancellations sync back.
• Three payment plans: one-time, two-deposit and three-deposit. Layout rules show only the fields for the chosen plan, and field dependencies limit each plan to the payment stages that make sense.
• 9+ workflow rules for lead-to-deal conversion, payment-stage updates, deposit tracking, due-date calculations, staff reminders and a fully-paid confirmation flow.
• 30+ email templates for tour follow-ups, payment notices, deposit receipts, overdue reminders, booking confirmations and post-event thank-yous, all tested end to end.
• Recorded video walkthroughs so the team could run the system themselves.

What changed

• Every tour request is captured the moment it's booked. No more lost follow-ups.
• Staff can see exactly where each client is, and deposits are tracked down to the last payment with automatic reminders.
• Clients get professional, timely emails at every milestone, without anyone typing them.

In the client's words

★★★★★ "What Damilare built for us exceeded every expectation. We went from juggling spreadsheets and phone notes to having a system that practically runs itself. Every tour booking flows straight into our CRM, payments are tracked automatically, and our clients get professional emails at every step without us lifting a finger."Olaoluwa M. Oreniwa, NJS Royale Event Centre

Tools

Screens

The problem

Repair enquiries arrived through WhatsApp, Instagram, Facebook Messenger and a website form. Staff checked each app by hand, replies were slow, and details were re-typed into the CRM when they were captured at all. Customers also kept asking "is my device ready yet?"

What I built

• Four n8n workflows: WhatsApp, Instagram and Messenger chatbots plus a repair intake form, connected through Meta's developer apps and webhooks.
• An AI agent (OpenAI with conversation memory and a structured output parser) that works out what the customer wants (new repair, status check, update or general question) and asks for any missing details.
• Duplicate-safe GoHighLevel logic: it finds the contact or creates it, checks for an open opportunity, and only creates a new one when needed.
• A Device Repair pipeline in GoHighLevel with 7 stage workflows: lead created, intake complete, diagnosing, quote approval, repair approved, repairing, and ready for pickup. Each one messages the customer and creates the right task for staff.

What changed

• Customers get an instant reply on the channel they used, at any hour, and hear from the shop automatically as their repair moves along.
• The team works from one GoHighLevel pipeline instead of four inboxes.

Tools

Screens

Customer contact details are blurred.

The problem

Cudium helps African SMEs and importers pay internationally. Their sales are relationship-driven (inbound, outbound and through agents), and they had just adopted Zoho with no structure in place. They wanted clarity and usability first, with only the automation that genuinely helps.

What I built

• A leads board that shows contact progress at a glance: Not Contacted → Attempted to Contact → Contacted (interested / not interested).
• Custom lead fields that match how Cudium sells: countries money is sent to, monthly transaction volume, business type, current payment methods and lead intent.
• A deal pipeline built on the real customer journey: Qualified (low intent) → Qualified (high intent) → KYC in Progress → Approved → First Transaction Done → Active Client, with win probabilities at each stage.
• Blueprint-guided stage changes: staff move deals with buttons such as "KYC Approved", and the first transaction amount must be verified before a client is marked active.
• Automatic next actions: new leads get "Review new lead" and "Confirm high intent" tasks, and high-intent leads get a call task straight away.
• Call logging with a purpose and an outcome on every call, plus lead conversion into account, contact and deal.
• Recorded walkthrough videos so the team could use the system on day one.

What changed

• The team works from one CRM where every prospect's stage, next step and history are visible.
• Deals can't skip steps: KYC and the first transaction are confirmed before a client counts as active.

Tools

Screens

Screens are from the client walkthrough videos, recorded with sample records.

The problem

Leads came in through several Framer website forms with no record of which form they used, and older contacts were split between GoHighLevel and Pipedrive. There was no single list to work from.

What I built

• A Make scenario from Framer to Folk. A webhook receives each form, then two cleaning steps normalise the data and work out the lead source (wish-list, contact, consultation or newsletter) and the page it came from.
• Duplicate-safe logic: Make looks the person up in Folk first, then updates the existing record or creates a new one.
• CRM consolidation: imported 1,825 GoHighLevel contacts and 1,036 Pipedrive records (people and organisations) into organised Folk groups: Framer contacts, suppliers, leads, clients and partners.

What changed

• One CRM instead of three places to look.
• Every new website enquiry arrives in Folk automatically, with its source attached for follow-up and reporting.

In the client's words

★★★★★ "Excellent work and responsive to my whole brief."Treehouse Life (UK) · 5-star Fiverr review · ongoing collaboration

Tools

Screens

Contact data in the background is blurred.

The problem

A veterinary supplier had years of orders in Zoho Invoice but no easy way to answer the questions that drive repeat sales: who buys the most, which products lead revenue, how this year compares with last, and which clinics have quietly stopped ordering.

What I built

• A data sync from Zoho Invoice into Zoho Analytics: customers, invoices, line items and products.
• Dashboard reports: revenue by month across years, top products by revenue, top customers by lifetime value with average order and order count, and customer activity.
• SQL query tables that work out each customer's last purchase and days since their last order, and label them active (ordered within 90 days), at risk (90–180 days) or lapsed.
• A dashboard plan covering overview, customer, product and order KPIs, including repeat purchase rate, churn, cross-sell pairs and reorder timing.

What changed

• The business can see at a glance who its best customers are, what sells, and exactly which clinics to win back.

Tools

Screens

Customer names are blurred.

The problem

The finance team had moved from Tally to Zoho Books and matched their bank statement, but weren't sure the books were actually right. They needed someone to check everything and tell them what to fix before relying on the reports.

What I did

• Reviewed the general ledger, sales and purchase sub-ledgers, bank and tax accounts and the reconciliation status, using exports from the live organisation.
• Confirmed what was solid: all 610 manual journals balance, and all 899 bank-statement lines were imported and matched.
• Found 14 issues (2 critical, 6 high, 5 medium, 1 low): accounts under the wrong statement headings, missing opening balances on two bank accounts, sales and purchase invoices stuck in draft, and a period-end reconciliation that was never formally completed.
• Wrote a findings and remediation report with the fix order (structure → sub-ledgers → tax → lock the reconciliation).
• A follow-up call to set up GST and TDS on invoices and show the team how to record payments already received.

What changed

• The client went from "it looks done, but is it?" to a clear, prioritised list of fixes and an order to do them in.

Tools

Screens

Names, phone numbers and account balances are blurred. The full review report is confidential to the client.

The problem

Optimize My Data, an authorised Zoho One partner, sells to automotive, manufacturing and engineering firms. An empty trial account doesn't sell anything. They needed a realistic company prospects could see running.

What I built

• Falcon Auto Spares Trading LLC, a Dubai parts distributor supplying garages and fleets, with company branding, AED currency, 5% VAT and branded estimate, sales order and invoice templates.
• Two warehouses (Dubai and Abu Dhabi) with aisle/rack/shelf bin locations.
• Master data: 47 genuine and aftermarket parts, 10 vendors and 15 B2B customers.
• A real transaction history: purchase orders, quotes, sales orders and invoices linked together, with recorded payments and monthly recurring invoices for fleet customers.
• Populated dashboards and a 5-minute demo script for the sales team.

What changed

• The partner can demo on demand, with no setup on the day, and adapt the same structure to any prospect's parts and warehouses.

Tools

The problem

An auto spare parts distributor with two GST entities, several warehouses and a field sales team ran on seven tools that didn't talk to each other: Tally for accounts, a warehouse system feeding Tally, two manufacturer portals (Honda and Bajaj), a mobile sales app, barcode middleware and Excel for reporting. Staff re-keyed data and rebuilt management reports by hand.

What I did

• Mapped every system and decided its fate: replace (Tally, Excel reporting, the warehouse system and scanning middleware), retire (the Tally mobile app) or keep standalone (the Honda and Bajaj manufacturer portals, which must stay).
• Designed the target architecture: two Zoho Books organisations (one per GST entity), Zoho Inventory for multi-warehouse stock using the existing barcodes, Zoho CRM for reps, telecallers and team leaders, Zoho Analytics for consolidated reporting and Zoho Flow to remove re-keying.
• Avoided a fragile integration: rather than syncing two ways with the manufacturer portals, Zoho becomes the single source of truth, with an optional one-way export where a portal accepts imports.
• Built a working Zoho Inventory proof of concept: a parts catalogue with Honda and Bajaj SKUs, stock across Head Office, Mumbai and Pune, FIFO valuation, barcode labels, warehouse-specific invoices with payments, and invoicing on the mobile app by scanning a part's barcode.
• Wrote the implementation proposal for the Zoho partner: a two-phase plan (finance and inventory backbone, then sales, reporting and go-live), deliverables, assumptions and fixed pricing.

What changed

• The business could see exactly how its day-to-day work (stock, invoicing, scanning) would run in Zoho before committing to the migration.

Tools

Screens

Screens are from the proof-of-concept demo, built with sample parts and customers.

The engagement

The client already used Folk CRM but felt it wasn't working as it should. We ran a 30-minute audit and consultation on their setup: groups, fields, pipeline and day-to-day workflow.

What they got

• A walk through their current setup, showing where it was creating extra work.
• Practical recommendations they could apply straight away, in order of impact.

In the client's words

★★★★★ "Recommended!"Fiverr client, Argentina · 5-star review