Miracle
Okoh

The first dashboard provides a single-pane-of-glass view of the entire business. Eight real-time KPI cards display monthly and lifetime figures for revenue, active clients, tasks completed, billable hours, and deals in progress. Below the KPIs sits a priority task board, a recent wins tracker, an upcoming events calendar, a content scheduling panel, and a sales pipeline Kanban board. An executive can assess the health of the full business in under thirty seconds without opening a single spreadsheet.

The sales dashboard presents a visual Kanban pipeline across seven stages — from initial contact through to Closed Won and Closed Lost. Each deal card displays the product or service name, the associated contact, the expected close date, and the deal value. Won and lost analytics provide clear forecasting data, and the revenue funnel visualization shows exactly where money is accumulating or stalling in the pipeline.

This dashboard handles all financial tracking automatically. Total revenue is shown both monthly and across the lifetime of the business. Average revenue per deal, billable hours versus total hours worked, average hourly rate, and project-specific rates are all calculated in real time using formula fields. Invoicing is automated — the system multiplies hours by rate and generates billing summaries with no manual input. This dashboard eliminated manual invoicing entirely and gave the client clear visibility into project-level profitability.

The LMS dashboard manages coaching cohorts from enrolment to completion. It tracks twelve active participants, ten sessions per month, and over eighty-nine thousand dollars in monthly programme revenue. Participants are displayed in a visual gallery filterable by payment status, enrolment status, and programme type. Training groups are managed with capacity tracking, coach assignments, and a colour-coded session calendar. All analytics — programme type distribution and monthly hours growth — update automatically.

The final dashboard gives the full team a centralised workspace. Visual project cards with custom images show status at a glance across four stages: Planning, Active, Completed, and On Hold. Shared task lists include priority levels and assignee visibility, so every team member knows what is outstanding and who owns it. A team calendar integration rounds out the hub, reducing the need for status update meetings significantly.

The underlying database consists of twelve or more relational tables covering Contacts, Projects, Deals, Tasks, Time Entries, Training Groups, Participants, Events, Content, Billing, Analytics, and Team Wins. Over thirty calculated formula fields handle financial and operational metrics automatically. Rollup fields aggregate data across linked tables. The interface supports Kanban, Gallery, Calendar, Grid, Timeline, and Chart views — all updating in real time across every dashboard simultaneously.

The new hire or client fills a simple Tally form capturing their name, role, email address, goals, and preferences. This takes approximately three minutes and is the only human action in the entire process. Everything that follows is handled by the system.

n8n receives the form submission and triggers OpenAI with a structured prompt tailored to the person's role. The AI generates a complete, personalised onboarding guide covering the tools they need to install, the team structure and key contacts, their first-week checklist and expectations, communication guidelines, and any role-specific context. No two guides are identical — each one is written specifically for that person's position.

The written guide is passed to a Text-to-Speech API, which produces a professional audio narration of the entire document. New joiners can listen to their onboarding guide on their phone while commuting or setting up their workspace — an experience that distinguishes professional agencies from the rest.

The guide is automatically formatted and saved as a named Google Doc in a dedicated folder within Google Drive. The document is structured, clean, and ready to reference at any time — no formatting work required from anyone on the team.

A Slack invitation is sent to the new person automatically. A personalised welcome message is posted in the appropriate team channel. The internal team receives a notification: the new person's name, their role, and a confirmation that they are ready to begin.

Every completed onboarding is recorded in an Airtable base with the person's name, role, start date, and a link to their Google Doc. The agency owner has a clean, searchable log of every onboarding without entering a single piece of data manually.

I created separate Airtable tables for Interested Leads, Intent Leads, and Meta and Google Ads campaign leads. Zapier and Make.com automations pull in new submissions from ListKit CSV imports, Realtor.com SMS responses, and Instagram DM intake forms — all flowing into the same base automatically. Facebook Lead Ads connect directly via Make.com, creating a new Airtable record the moment a lead submits.

Leads sourced from ListKit are automatically tagged as Intent leads on arrival. The virtual assistant reviews and reclassifies each lead as Hot, Warm, Cold, or Do Not Contact using Airtable single-select fields. This structured classification gives the BDR a clear and prioritised call list without any guesswork.

Every lead record has a follow-up date calculated automatically based on the date of first contact. The Interested Leads 2-Hour Notification automation runs on a schedule, identifying leads that require action and sending reminders to the BDR via Slack and surfacing them on the Airtable dashboard. No lead falls through the cracks.

I wrote clear standard operating procedures for both the virtual assistant and the BDR. For Instagram: the VA logs the DM lead in Airtable, the BDR is notified, and a follow-up is scheduled. For ListKit: the CSV is auto-forwarded, imported into Airtable, tagged, and reminders are triggered. Both processes are documented, repeatable, and transferable to any new team member.

Built using Airtable Interface Designer, the dashboard gives management instant visibility into the full RevOps pipeline. Key metrics — total leads, follow-up lag, lost leads, reply rate, average follow-up time, deals closed, and meetings booked — update automatically via Make.com and Zapier integrations. Separate views serve the BDR's daily workflow and the manager's strategic overview. Automated Slack summaries are delivered daily, reducing manual reporting time by 80%.

The central table tracks every applicant across the full pipeline. Each record contains the candidate's full name and contact information, a passport photo upload for quick identification, the role they applied for via a linked Job Roles record, their current application status, a duplicate detection flag, and a rejection trigger link. Eleven candidates are tracked across roles including Business Analyst, Tech Support, Sales Manager, Copywriter, and Admin Support.

Each open role has its own record showing the job title, department, hiring manager, the list of candidates who applied, and the current status — Open or Closed. Six roles are tracked simultaneously. The linked candidate records mean hiring managers can move between the pipeline view and the role view without any duplication of data.

The Airtable interface presents candidates in a Kanban board grouped by application status: Applied, Reviewed, Interviewed, Hired, and Rejected. Each card displays the candidate's photo, name, applied role, and application date. A pie chart provides an at-a-glance distribution of the full pipeline. This view was designed specifically for hiring managers who need to review applicants quickly without opening individual records.

When a candidate submits the branded Airtable application form, a confirmation email fires automatically via Gmail. Their full record is created in the Candidates table with all form fields populated. A duplicate check runs immediately, searching for any existing records where the email or name matches. This happens without any manual intervention from the HR team.

Automation 5 runs every time a new record is created. It searches the Candidates table for any record where the email address matches the new submission. If a match is found, the Duplicate Status field is updated accordingly, flagging the record for HR review. This prevents the team from advancing or communicating with the same candidate twice.

When a candidate's status is updated to Rejected and the rejection email has not yet been sent, an automation introduces a three-working-day delay before sending a single, professionally worded rejection email via Gmail. The Email Sent checkbox is verified before every send to guarantee the email goes out exactly once, regardless of any subsequent record edits. All automated emails are logged, giving the team a complete communication audit trail.

The patient completes a JotForm intake form capturing personal information, presenting symptoms, preferred appointment date and time, identification and insurance file uploads, and a consent e-signature. The consent is built directly into JotForm — no third-party signing service is required. All sensitive fields are present on the form but hidden from the administrative view to protect patient privacy.

The first action in the Zapier workflow is a filter that checks whether the consent signature field was completed. If the consent is confirmed, the workflow proceeds to the next step. If the consent is missing, the entire automation halts immediately. No appointment is ever created, no record is ever filed, and no communication is ever sent without the patient having provided informed consent.

A named folder is automatically created in Google Drive using the patient's name and appointment date as the folder title. The identification and insurance documents uploaded through the intake form are stored in this folder immediately. Every patient has a dedicated, organised record in Drive without any manual filing by clinic staff.

A patient record is created in the clinic's Airtable CRM with all form data included — name, contact information, symptoms, appointment details, and the link to their Google Drive folder. The intake status is set to Received automatically. The Serenity Health and Wellness base provides a clean, searchable patient register with appointment dates and completion statuses visible at a glance.

A detailed Google Calendar event is created for the appointment, including the patient's name, contact information, and any notes submitted through the intake form. A confirmation email and SMS are sent to the patient with the appointment details. These communications are sent the moment the appointment is confirmed — not the next time a staff member checks their inbox.

Twenty-four hours before the scheduled appointment, Twilio sends an automatic SMS reminder to the patient with the date, time, and a request to arrive ten minutes early. Patients who have preferred email communication receive the same reminder via Gmail instead. The reminder path is determined by the communication preference captured in the intake form.

As soon as an appointment is confirmed, a Slack message is posted to the clinic's internal appointments channel with the patient's name, appointment time, and a calendar link. Forty-eight hours after the visit, Gmail sends an automatic follow-up email thanking the patient and inviting feedback. The delay is managed by Zapier's built-in delay step — no scheduling or manual triggering required.

The client or their assistant opens the Google Sheet and types a single blog topic into a new row. The status field is left as Pending. That is the complete extent of the manual work required. The system handles everything that follows.

Make.com watches the Google Sheet for new rows with a Pending status. The moment a new topic is detected, the scenario triggers instantly and the workflow begins.

The topic is sent to OpenAI with a structured prompt that specifies the client's brand voice, desired structure, and formatting guidelines. ChatGPT returns a complete, professionally written blog post including an engaging introduction, structured body content with subheadings, actionable insights or tips, and a strong conclusion with a call to action.

The full article is written into the Google Sheet alongside the original topic row. The status field updates to Generated. At this point the client can review the content and approve it, or they can configure the system to proceed automatically without a review step — whichever suits their workflow.

Once approved — or immediately if running in full autopilot mode — Make.com posts the content simultaneously to LinkedIn with professional formatting, line breaks, and relevant emojis, and to Facebook Pages with engagement-optimised formatting and hashtags. The sheet status updates to Posted with a timestamp. A complete audit trail of every published piece is maintained automatically in the sheet.

Every student has a record in the Airtable base with a unique ID, their enrolled course, their current progress percentage, a certificate link field that populates on completion, and a completion status. The grid view gives the academy team a live overview of all sixteen students across the three programmes, showing at a glance who is progressing, who is stalled, and who has completed their course.

A filtered Airtable view called Ready for Certificate shows only students who have reached exactly 100% progress and have not yet received a certificate. This view serves as the trigger point for the Zapier automation. Students at 75% do not appear here. Only verified course completions pass through — eliminating any risk of certificates being issued prematurely.

When a student record enters the Ready for Certificate view, Zapier detects the change within fifteen minutes. The automation applies a filter to confirm the conditions are met, formats the completion date correctly using Zapier's date formatter, and proceeds to the certificate generation step.

Zapier creates a copy of the branded Google Docs certificate template and populates it with the student's full name, the course they completed, and the formatted completion date. The completed certificate document is saved to the Springwood Academy Students folder in Google Drive, and the file link is written back to the student's Airtable record automatically.

A personalised Gmail is sent to the student with the subject line confirming their completion and the certificate document attached. A post-course feedback form is included in the email, triggered automatically at this same moment. The Certificate Sent checkbox in Airtable is ticked upon successful delivery — permanently preventing any future duplicate sends regardless of how many times the record is subsequently edited.

Every step in the automation includes a conditional check: the Certificate Sent field must be unchecked before any action proceeds. An additional Airtable automation uses a custom JavaScript script to write the exact completion date to the student's record when their status changes to Completed. This provides a complete, timestamped audit trail of every certificate ever issued by the academy.

Prospective clients complete a Tally intake form capturing their first and last name, email address, job title, company name, company size, preferred coach, and budget range. The budget and commitment fields serve as the qualification criteria for the next step. The form is clean, professional, and takes less than three minutes to complete.

A Zapier filter step evaluates the submitted data against the programme's qualification criteria — specifically the budget range and commitment level. Prospects who meet the threshold pass through to the CRM and booking stages. Those who do not are optionally tagged in Airtable as Cold or Nurture leads for future follow-up campaigns, ensuring no lead is wasted entirely.

A full record is created in the coaching CRM in Airtable with the prospect's name, email, company, source, and status set to Application Submitted. Simultaneously, Gmail sends a personalised booking email to the qualified lead — addressed by name, with a warm message and a direct link to the coach's Calendly page for discovery call scheduling. The email is sent from the coach's Gmail account and reads as though written personally.

The second automation is triggered independently by a Calendly Invitee Created event — meaning it only fires when a real booking has been made. This separation keeps the logic clean and prevents the onboarding sequence from running on unbooked leads. When triggered, it updates the Airtable record status to Call Booked, sends a calendar confirmation email to the prospect, posts a Slack notification to the internal team with the lead's details and booking time, and sends a pre-call preparation email to the prospect.

The decision to use two separate Zapier automations rather than one long workflow was deliberate. It keeps each automation focused, easier to debug, and independently triggered by the correct event. The first Zap responds to form submissions. The second responds to confirmed bookings. If the Calendly booking is cancelled or rescheduled, the second Zap handles the new event cleanly without affecting the first. This architecture allows the system to handle thirty to fifty leads per week reliably with minimal oversight.

A custom webhook module in Make.com is configured as the entry point for the scenario. When a lead submits any form on any platform, that platform sends the data to the webhook URL. Make.com receives the payload instantly and begins processing. The fields captured — full name, email address, and phone number — are mapped at this stage and carried through every subsequent step.

The second module adds a new row to a predefined Google Sheet with the lead's full name, email, phone number, source identifier, and a timestamp generated at the moment of submission. The sheet functions as the team's live CRM — always accurate, always current, requiring no manual input from anyone.

A Slack message is posted immediately to a designated channel — typically named something like new-leads — containing the lead's name, email address, and the source of the form submission. The sales team sees every new lead the moment it arrives, enabling same-day outreach and fast hand-offs between team members.

An Outlook SMTP module sends a personalised welcome email to the lead within seconds of their form submission. The email content is configured to match the funnel's context — a thank-you message, links to relevant resources, a call booking option, or next-step instructions depending on the lead's entry point. The lead's first experience of the brand after submitting their details is a prompt, professional, personalised response — delivered automatically.