How solo founders can build a free, connected analytics stack in under two hours — no code, no hires, no subscriptions
Learn how to wire three lightweight automations that deliver real-time analytics on signups, traffic sources, and user behavior every morning. Built with free tools like GA4, Make.com, and Google Sheets, this stack replaces expensive software and your first marketing hire.
TL;DR
You don't need a $500/month analytics stack or a marketing hire - Three free automations (Make.com + GA4 + Google Sheets) give you daily signup tracking, anomaly alerts, and weekly funnel analysis.
Push beats pull - Dashboards are useless if you forget to check them. These automations send insights to Slack or Telegram so the data finds you.
Build in sequence, not all at once - Start with the daily signup logger, then the anomaly detector, then the weekly funnel digest. Each one takes about 30 minutes.
The entire stack costs $0 - GA4, Google Sheets, and Make.com's free tier handle everything a pre-100-user product needs for data-driven decision making.
Act on data, don't just collect it - The automations surface what's happening. Pair them with a daily execution plan (manually or via an AI growth platform) to turn insights into action.
What You'll Build: A Three-Automation Analytics Stack That Replaces Your First Marketing Hire
Most solo founders assume they need a dedicated marketing person or a $500/month analytics subscription before they can make data-driven decision making part of their workflow. That assumption is expensive and wrong. By the end of this tutorial, you'll have three connected automations running that surface your most critical growth numbers automatically, giving you real-time analytics on signups, traffic sources, and user behavior without writing code or hiring anyone.
Your success criteria are simple: every morning, you'll wake up to a summary of what happened yesterday (who signed up, where they came from, what they did), a flag if anything broke or spiked, and a weekly digest that tells you exactly where your funnel leaks. All of it free. All of it built in under two hours.
Prerequisites and Setup Checklist
Before you start wiring automations, confirm you have the following in place. Missing any one of these will stall you mid-build.
Google Analytics 4 (GA4) installed on your site with at least one conversion event configured (e.g., signup button click). GA4 setup guide.
A free Make.com account (formerly Integromat). The free tier gives you 1,000 operations/month, which is plenty under 100 users. Sign up at Make.com.
A Google Sheet that will serve as your lightweight data warehouse.
A Slack workspace or Telegram account for receiving automated alerts. Discord works too.
30 minutes for each automation (90 minutes total, plus 30 minutes for testing).
Potential blockers: If you haven't set up GA4 events yet, start there first. This tutorial assumes you have at least a "page_view" and one custom event (like "signup_started") already firing. If you need help building a free growth dashboard from scratch, handle that prerequisite first.
Why Three Automations Instead of One Dashboard
Dashboards are passive. You have to remember to check them. And when you're building, shipping, and doing customer support all by yourself, you won't. 73% of small-to-midsize businesses struggle with data analytics costs, but the real problem isn't cost. It's attention. You need data that finds you, not data you have to go find.
The three automations you'll build solve this by pushing insights to where you already are (Slack, Telegram, email). Each one answers a single question: Who signed up?, Is something broken or spiking?, and Where is my funnel leaking this week? This approach is deliberately minimal. As one analytics expert put it: "If acting on the data an hour later makes no meaningful difference to your business outcome, you probably don't need real-time processing." You need timely, not real-time. And you need it automated.
Step 1: Create Your Central Data Sheet
Action
Open Google Sheets and create a new spreadsheet called "Growth Pulse." Add three tabs: Daily Signups, Anomalies, and Weekly Funnel.
In the Daily Signups tab, create these column headers in Row 1:
Date | Email | Source | Medium | Landing Page | Signup Event Fired
In the Anomalies tab:
Date | Metric | Expected Range | Actual Value | Alert Sent
In the Weekly Funnel tab:
Week Starting | Visitors | Signup Page Views | Signups Started | Signups Completed | Drop-off %
Checkpoint
You should have one Google Sheet with three empty, labeled tabs. This is your zero-cost data warehouse. Bookmark it.
Common failure
Don't skip the column headers. Make.com references them by name when mapping data fields. Misspelled headers will cause silent failures later.
Step 2: Connect GA4 to Google Sheets via Make.com (Automation #1 — Daily Signup Log)
Action
Log into Make.com and create a new scenario. Name it "Daily Signup Logger." You'll build a flow that runs once per day, pulls yesterday's signup data from GA4, and writes each row to your Google Sheet.
Add the first module: Search for "Google Analytics 4" and select "Run a Report." Connect your Google account and select your GA4 property.
Configure the report with these settings:
Date range: Yesterday
Dimensions:
date,sessionSource,sessionMedium,landingPageMetrics:
eventCountDimension filter:
eventNameequalssignup_started(or whatever your signup event is named)
Add the second module: Search for "Google Sheets" and select "Add a Row." Map the GA4 output fields to the corresponding columns in your Daily Signups tab.
Checkpoint
Click "Run once" in Make.com. If you had any signups yesterday, you should see a new row appear in your Google Sheet within seconds. If you had zero signups, the scenario should complete with zero operations (no error).
Common failure
If you get a "property not found" error, confirm you've granted Make.com access to the correct GA4 property (not a Universal Analytics property). Check under GA4 Admin → Property Settings for your property ID.
Step 3: Add a Slack or Telegram Notification to Automation #1
Action
Add a third module to the same scenario. After the Google Sheets module, add a Slack → "Send a Message" module (or Telegram → "Send a Message" if you prefer). Connect your workspace.
Set the message template to something like:
📊 Daily Signup Report
Date: {{date}}
New signups: {{eventCount}}
Top source: {{sessionSource}} / {{sessionMedium}}
Top landing page: {{landingPage}}
Set the scenario schedule: Click the clock icon and set it to run daily at 8:00 AM in your timezone.
Checkpoint
Run the scenario once manually. You should receive a formatted message in your Slack channel or Telegram chat. If the message arrives but fields show "empty," double-check your field mappings in the message template.
Step 4: Build the Anomaly Detector (Automation #2 — Spike and Drop Alerts)
Action
Create a new Make.com scenario called "Anomaly Alert." This automation checks whether today's traffic or signups deviate significantly from your recent average. It's your early warning system for things like a Reddit post going viral or your site going down.
Module 1: Google Analytics 4 → "Run a Report"
Date range: Last 7 days
Dimensions:
dateMetrics:
sessions,eventCount(filtered to your signup event)
Module 2: Tools → "Set Variable"
Calculate the 7-day average sessions and the most recent day's sessions. Use Make.com's math functions:
Average = sum of sessions / 7
Deviation = (today's sessions - average) / average * 100
Module 3: Filter
Add a filter between Module 2 and Module 4 that only continues if the absolute deviation exceeds 50%. This prevents you from getting alerted over normal noise.
Module 4: Slack → "Send a Message"
⚠️ Traffic Anomaly Detected
Yesterday's sessions: {{todaySessions}}
7-day average: {{averageSessions}}
Deviation: {{deviation}}%
Action: Check GA4 and your landing pages.
Module 5: Google Sheets → "Add a Row" to the Anomalies tab for your records.
Schedule: Daily at 9:00 AM (one hour after Automation #1 so alerts arrive separately).
Checkpoint
To test, temporarily lower the deviation threshold to 1% and run the scenario. You should receive an alert. Then set it back to 50%.
Common failure
Division by zero if you have days with zero sessions. Add a filter before the math module: only proceed if total sessions > 0.
Step 5: Build the Weekly Funnel Digest (Automation #3 — Where Users Drop Off)
Action
Create a third Make.com scenario called "Weekly Funnel Digest." This runs every Monday and tells you where your funnel leaked the previous week.
Module 1: Google Analytics 4 → "Run a Report"
Date range: Last 7 days
Metrics:
sessions(total visitors),eventCountfor each funnel stepRun separate report rows filtered by event name:
page_viewon your signup page,signup_started,signup_completed
Module 2: Tools → "Set Multiple Variables"
Calculate drop-off percentages between each step:
Visitor-to-signup-page rate = signup_page_views / sessions * 100
Signup-start rate = signup_started / signup_page_views * 100
Completion rate = signup_completed / signup_started * 100
Module 3: Google Sheets → "Add a Row" to the Weekly Funnel tab.
Module 4: Slack → "Send a Message"
📈 Weekly Funnel Digest ({{weekStarting}})
Visitors: {{sessions}}
Saw signup page: {{signupPageViews}} ({{visitorToSignupRate}}%)
Started signup: {{signupStarted}} ({{signupStartRate}}%)
Completed signup: {{signupCompleted}} ({{completionRate}}%)
Biggest drop-off: {{worstStep}}
Fix this first.
Schedule: Every Monday at 8:00 AM.
Checkpoint
Run the scenario manually. Your Slack message should clearly show which funnel step loses the most users. Your Google Sheet should have a new row in the Weekly Funnel tab.
Step 6: Wire the Three Automations Together with a Master Sheet View
Action
Go back to your "Growth Pulse" Google Sheet. Create a fourth tab called Dashboard. Use simple IMPORTRANGE or cell references to pull the latest row from each of the three tabs into a single view.
Add these summary cells:
=QUERY('Daily Signups'!A:F, "SELECT * ORDER BY A DESC LIMIT 7")
=QUERY('Anomalies'!A:E, "SELECT * ORDER BY A DESC LIMIT 5")
=QUERY('Weekly Funnel'!A:F, "SELECT * ORDER BY A DESC LIMIT 4")
This gives you a single-tab view of your last 7 days of signups, recent anomalies, and last month of funnel data. Bookmark this tab. It's your entire analytics stack.
Checkpoint
The Dashboard tab should auto-populate with data from the other three tabs. If queries return errors, check that your column ranges match the actual data in each tab.
Configuration and Customization
Variables You Should Adjust
Anomaly threshold (50%): If your traffic is very low (under 20 sessions/day), raise this to 100% to avoid false positives. If you're above 100 sessions/day, lower it to 30%.
Signup event name: Replace
signup_startedandsignup_completedwith whatever custom events you've defined in GA4. Common alternatives:begin_checkout,generate_lead,form_submit.Notification channel: Slack works well if you live there. If you're a solo founder who checks Telegram more, use that. The key is choosing the channel you actually look at.
Schedule timing: Stagger your three automations by at least 30 minutes. Running them simultaneously can hit Make.com's free-tier operation limits on busy days.
Safe Defaults
The date range of "yesterday" for daily reports and "last 7 days" for weekly reports works for nearly every pre-100-user product. Don't change these unless you have a specific reason.
Verification and Testing
Test each automation individually first. Click "Run once" in Make.com for each scenario and verify three things: data appears in the correct Google Sheet tab, the Slack/Telegram message arrives, and the field values match what you see in GA4.
Then test the edge cases:
Zero signups day: Trigger Automation #1 on a day with no signups. It should complete without error and send a message saying "0 signups."
Anomaly with low traffic: Manually edit a value in the Anomalies sheet to confirm the deviation formula works correctly.
Weekly funnel with missing events: If one funnel step has zero events, the drop-off calculation should still work (show 100% drop-off at that step, not an error).
Your success definition: after 48 hours, you should have received at least two daily signup reports and one anomaly check (even if no anomaly was detected) without any manual intervention.
Common Errors and Fixes
"Scenario execution failed: 403 Forbidden"
Cause: Your Google account connection expired or you didn't grant sufficient permissions. Fix: Go to Make.com → Connections, delete the Google connection, and re-authenticate. Make sure you check all permission boxes during OAuth.
"No data returned" from GA4 module
Cause: Your date range is set to "today" but GA4 hasn't processed today's data yet (GA4 can lag 24-48 hours for some reports). Fix: Always use "yesterday" as your date range for daily reports. For the weekly funnel, use "last 7 days" ending yesterday.
Slack message arrives but all fields are blank
Cause: Field mapping mismatch. The variable names in your message template don't match the output field names from the GA4 module. Fix: Open the Slack module, click into each {{variable}}, and re-map by selecting the correct output from the dropdown instead of typing manually.
Google Sheets "Row limit exceeded" error
Cause: Unlikely at your scale, but if you're logging individual page views instead of aggregated events, you'll fill up a sheet fast. Fix: Only log aggregated daily totals, not individual hits. One row per day, not one row per visitor.
Make.com free tier operations running out mid-month
Cause: Each module execution counts as one operation. Three scenarios with 5 modules each, running daily, use roughly 450 operations/month. If you add more modules or run scenarios more frequently, you'll exceed 1,000. Fix: Audit your scenarios and remove any unnecessary modules. Or upgrade to Make.com's $9/month plan for 10,000 operations.
Replacing the Marketing Hire with Data-Driven Decision Making
What you've just built does 80% of what a first marketing hire would do with analytics: track signups, flag problems, and identify funnel weaknesses. Companies using real-time insights are 23 times more likely to acquire customers, but you don't need enterprise tools to get there. You need three automations and the discipline to act on what they tell you.
For founders who want to go beyond raw data and get specific guidance on what to do about the numbers they're seeing, heycatch can layer on top of this setup. It acts as an AI growth platform that translates your traction data into a daily execution plan, telling you which funnel step to fix today and how. Think of it as the decision layer on top of the data layer you just built.
The broader trend supports this approach. The shift is from collecting data to being able to trust and act on it quickly. Your three automations handle the "trust" part by keeping data simple and transparent. The "act quickly" part is on you.
Next Steps and Extensions
You now have a working analytics stack that costs $0 and runs without you. Here's where to go next:
Add a revenue tracking automation. If you're using Stripe, connect it to Make.com and log each payment to your Growth Pulse sheet. Track MRR alongside signups to see your full path to $1k MRR.
Build a traffic source deep-dive. Once you know which sources send signups, create a weekly report that breaks down behavior by source. This tells you where to double down. If you need a framework, check out this guide on segmenting early users by behavior.
Layer in outreach automation. Your analytics stack tells you what's happening. Your next automation should influence what happens: automated follow-up emails to new signups, or scheduled social posts driving traffic to your best-converting landing page.
Every automation you add compounds. According to Formstack's automation research, 60% of employees could save 30% of their time with workflow automation — that's nearly a full day back every week. But resist the urge to build ten at once. Ship these three, run them for two weeks, and let the data tell you what to automate next.
Frequently Asked Questions
Do I really need real-time analytics before 100 users?
Not real-time in the enterprise sense. What you need is timely, automated reporting that surfaces changes without you manually checking dashboards. Daily and weekly automations give you enough signal to make decisions at the pre-traction stage. True real-time processing (sub-second data) is overkill and expensive until you're handling thousands of concurrent users. Building a self-managed real-time streaming platform costs 8x more upfront than a managed service, plus $300K–$500K per year just to staff it.
How much does this automation stack cost to run?
Zero dollars. GA4 is free. Google Sheets is free. Make.com's free tier provides 1,000 operations per month, which comfortably supports three daily/weekly automations for a pre-100-user product. If you outgrow the free tier, Make.com's paid plan starts at $9/month.
Can I use Zapier instead of Make.com?
Yes, but Make.com's free tier is more generous for this use case. Zapier's free plan limits you to single-step Zaps (one trigger, one action), while these automations require multi-step flows. You'd need Zapier's paid plan ($19.99/month) to replicate what Make.com does for free.
What if I'm not using Google Analytics 4?
You can substitute any analytics tool that has a Make.com integration or API access. Plausible, Fathom, and Mixpanel all work. The logic stays the same: pull daily metrics, write to a sheet, send a notification. You'll just need to adjust the module and field mappings in Step 2.
When should I stop using this and hire an actual marketing person?
When you consistently have more growth tasks than hours in the day, and the bottleneck is execution rather than data. Typically, that's around $3k-$5k MRR for solo founders. According to Jason Lemkin, most founders shouldn't hire their first demand-gen marketer until they hit ~$20K MRR. Until then, automations like these handle the analytical work, and tools like heycatch can handle the strategic planning, keeping your spend at near-zero.
What's the best no-code platform for growth workflow automation?
For solo founders under 100 users, Make.com offers the best balance of power and free-tier generosity. n8n is a strong open-source alternative if you're comfortable self-hosting. For founders who want growth-specific automation (not just data plumbing), an AI growth platform like heycatch provides opinionated, stage-aware guidance alongside the raw data.
Sources
https://heycatch.ai/blog/real-time-analytics-build-a-free-growth-dashboard
https://heycatch.ai/blog/ai-driven-launch-system-the-execution-layer
https://www.integrate.io/blog/real-time-data-integration-growth-rates/
https://heycatch.ai/blog/data-driven-marketing-why-your-relaunch-is-a-replay
https://www.formstack.com/blog/workflow-automation-statistics
https://www.confluent.io/blog/cost-build-data-streaming-platform/
https://help.zapier.com/hc/en-us/articles/8496181445261-Zap-limits